Skip to content

Commit 9a39cea

Browse files
authored
Update 2-determine-uses.md
1 parent 0495e3f commit 9a39cea

1 file changed

Lines changed: 18 additions & 1 deletion

File tree

learn-pr/wwl-azure/configure-vnet-peering/includes/2-determine-uses.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,4 +34,21 @@ Consider the benefits of using Azure Virtual Network peering.
3434
| **Strong performance** | Because Azure Virtual Network peering utilizes the Azure infrastructure, you gain a low-latency, high-bandwidth connection between resources in different virtual networks. |
3535
| **Simplified communication** | Azure Virtual Network peering lets resources in one virtual network communicate with resources in a different virtual network, after the virtual networks are peered. |
3636
| **Seamless data transfer** | You can create an Azure Virtual Network peering configuration to transfer data across Azure subscriptions, deployment models, and across Azure regions. |
37-
| **No resource disruptions** | Azure Virtual Network peering doesn't require downtime for resources in either virtual network when creating the peering, or after the peering is created. |
37+
| **No resource disruptions** | Azure Virtual Network peering doesn't require downtime for resources in either virtual network when creating the peering, or after the peering is created. |
38+
39+
### Things to know about peering requirements and limitations
40+
41+
While VNet peering provides many benefits, there are important constraints to understand.
42+
43+
| Requirements/Limitations | Description |
44+
| --- | --- |
45+
| Non-overlapping address spaces | Peered virtual networks must have non-overlapping IP address spaces. Peering creation will fail if address ranges overlap. |
46+
| Address space modification restrictions | If you want to change a VNet's address range, you need to delete the peering first, update the address space, and then set up the peering again. |
47+
| Basic Load Balancer limitations| Resources in one VNet can’t communicate with Basic Internal Load Balancer IPs in VNets peered across regions. Use the Standard Load Balancer for cross-region connections. |
48+
| DNS resolution boundaries |Azure's built-in name resolution does not work across peered VNets. Configure Azure Private DNS zones or custom DNS servers for cross-VNet name resolution. |
49+
50+
51+
52+
53+
54+

0 commit comments

Comments
 (0)