Merge pull request #54036 from staleycyn/patch-1

Content-drift virtual network peering

Author: denrea

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

@@ -34,4 +34,21 @@ Consider the benefits of using Azure Virtual Network peering.
 | **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. |
 | **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. |
 | **Seamless data transfer** | You can create an Azure Virtual Network peering configuration to transfer data across Azure subscriptions, deployment models, and across Azure regions. |
-| **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. |
+| **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. |
+
+### Things to know about peering requirements and limitations
+
+While VNet peering provides many benefits, there are important constraints to understand.
+
+| Requirements/Limitations | Description |
+| --- | --- |
+| **Nonoverlapping address spaces** |	Peered virtual networks must have non-overlapping IP address spaces. Peering creation fails if address ranges overlap. |
+| **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. |
+| **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. |
+| **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. |
+
+
+
+
+
+

learn-pr/wwl-azure/configure-vnet-peering/includes/3-determine-gateway-transit-connectivity.md

@@ -8,14 +8,19 @@ Consider a scenario where three virtual networks in the same region are connecte
 
 :::image type="content" source="../media/gateway-transit-173a51a0.png" alt-text="Diagram of a regional virtual network peering. One network allows VPN gateway transit and uses a remote VPN gateway to access resources in a hub virtual network." border="false":::
 
-
-
-The Azure portal doesn't specifically mention *gateway transit* and *connectivity*. Instead, you have choices for allowing and forwarding network traffic. 
+The Azure portal provides four key settings when configuring virtual network peering.
 
 :::image type="content" source="../media/peering-settings.png" alt-text="Screenshot of the peering options in the portal." border="false":::
 
-> [!TIP]
-> Use **Ask Learn** (available in English) or **Copilot** to explore *Azure gateway transit*.
+- **Traffic to remote virtual network**. Controls whether traffic flows from this VNet to the remote VNet.
+  
+- **Traffic forwarded from remote virtual network**. Controls whether forwarded (non-originating) traffic is accepted from the peered VNet.
+  
+- **Virtual network gateway or Route Server**. Enables gateway transit. Lets peered VNets use this VNet's VPN Gateway or Azure Route Server.
+  
+- **Remote virtual network gateway or Route Server**. Enables this VNet to use the remote VNet's VPN Gateway or Route Server.
+  
+
 
 ### Things to know about Azure VPN Gateway
 

learn-pr/wwl-azure/configure-vnet-peering/includes/4-create.md

@@ -25,6 +25,6 @@ In the Azure portal, you can check the connectivity status of the virtual networ
 > [!Important]
 > Your peering isn't successfully established until both virtual networks in the peering have a status of **Connected**.
 
-- For deployment with the Azure Resource Manager, the two primary status conditions are **Initiated** and **Connected**. For the classic deployment model, the **Updating** status condition is also used.
+- The two peering status conditions are **Initiated** and **Connected**.
 
 - When you create the initial peering _to_ the second (remote) virtual network from the first virtual network, the peering status for the first virtual network is **Initiated**.

learn-pr/wwl-azure/configure-vnet-peering/includes/5-determine-service-chaining-uses.md

@@ -13,6 +13,7 @@ There are a few ways to extend the capabilities of your peering for resources an
 | **Hub and spoke network** | When you deploy a hub-and-spoke network, the hub virtual network can host infrastructure components like a network virtual appliance (NVA) or Azure VPN gateway. All the spoke virtual networks can then peer with the hub virtual network. Traffic can flow through NVAs or VPN gateways in the hub virtual network. |
 | **User-defined route (UDR)** | Virtual network peering enables the next hop in a [user-defined route](/azure/virtual-network/virtual-networks-udr-overview#user-defined) to be the IP address of a virtual machine in the peered virtual network, or a VPN gateway. |
 | **Service chaining** | [Service chaining](/azure/virtual-network/virtual-network-peering-overview#service-chaining) is used to direct traffic from one virtual network to a virtual appliance or gateway. To enable service chaining, configure UDRs that point to virtual machines in peered virtual networks as the next hop IP address. UDRs could also point to virtual network gateways to enable service chaining. |
+| **Azure Virtual Network Manager** | Centrally manages hub-and-spoke or mesh peering topologies at scale. Automates peering creation without manual per-VNet configuration. |
 
 
 The following diagram shows a hub and spoke virtual network with an NVA and VPN gateway. The hub and spoke network is accessible to other virtual networks via user-defined routes and service chaining.

learn-pr/wwl-azure/configure-vnet-peering/index.yml

@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Configure Azure Virtual Network Peering
   description: "Learn to configure an Azure Virtual Network peering connection and address transit and connectivity concerns."
-  ms.date: 02/19/2026
+  ms.date: 03/23/2026
   author: wwlpublish
   ms.author: cynthist
   ms.topic: module