Study guide

1.2 Virtual Network Peering & Global Peering

Designing and Implementing Microsoft Azure Networking Solutions AZ-700

Track your progress as you read

Finished sections get a check mark.

1 Introduction & AZ-700 Exam Overview

0.1 About the AZ-700 Exam: Format, Scoring & Skills Measured

2 Chapter 1: Azure Virtual Networks, Addressing & Subnet Architecture

1.1 VNet Planning, IP Addressing & Subnet Design 1.2 Virtual Network Peering & Global Peering 1.3 Azure NAT Gateway & Outbound Connectivity 1.4 Azure Virtual Network Manager (AVNM) & Network Groups 1.5 Public IP Addresses, Public IP Prefixes & Custom IP Prefixes (BYOIP)

3 Chapter 2: Azure Name Resolution & Core Routing

2.1 Azure DNS & Private DNS Zones 2.2 Azure Private DNS Resolver & Hybrid Name Resolution 2.3 System Routes & User-Defined Routes (UDR) 2.4 BGP & Custom Route Propagation 2.5 Azure Route Server & Dynamic NVA Route Exchange

4 Chapter 3: Hybrid Connectivity with Azure VPN Gateway

3.1 Azure VPN Gateway Architecture & SKUs 3.2 Site-to-Site (S2S) VPN & High Availability 3.3 Point-to-Site (P2S) VPN & Client Authentication 3.4 Azure Extended Network, Always On VPN & Azure Network Adapter

5 Chapter 4: Azure ExpressRoute & Virtual WAN

4.1 Azure ExpressRoute Architecture & Peering Models 4.2 ExpressRoute Routing, Resiliency & Global Reach 4.3 Azure Virtual WAN Architecture & Hub Routing 4.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting

6 Chapter 5: Regional Load Balancing & Application Gateway

5.1 Azure Load Balancer Architecture & Rules 5.2 Azure Application Gateway Architecture & Routing 5.3 Web Application Firewall (WAF) on Application Gateway 5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design

7 Chapter 6: Global Traffic Management & Azure Front Door

6.1 Azure Front Door Architecture & Routing 6.2 Azure Traffic Manager & DNS Load Balancing 6.3 Load Balancing Decision Matrix & Multi-Tier Design 6.4 Web Application Firewall on Azure Front Door

8 Chapter 7: Azure Private Link & Service Endpoints

7.1 Virtual Network Service Endpoints & Policies 7.2 Azure Private Endpoints & Private Link Architecture 7.3 Private Endpoint DNS Integration & Hybrid Resolution 7.4 Azure Private Link Service for Multi-Tenant Solutions

9 Chapter 8: Network Security Groups & Azure Bastion

8.1 Network Security Groups (NSGs) & Application Security Groups (ASGs) 8.2 Azure Bastion Architecture & Secure Remote Access 8.3 Azure Virtual Network Manager Security Admin Rules

10 Chapter 9: Azure Firewall & Security Policies

9.1 Azure Firewall Architecture & Rule Processing 9.2 Azure Firewall Manager & DDoS Protection

11 Chapter 10: Azure Network Observability & Troubleshooting

10.1 Network Watcher Diagnostic Tools 10.2 NSG Flow Logs, VNet Flow Logs & Traffic Analytics 10.3 Network Troubleshooting Scenarios & End-to-End Connectivity 10.4 Azure Monitor Network Insights & Defender for Cloud Network Posture

1.2 Virtual Network Peering & Global Peering

Key Takeaways Explain This Topic AI

Virtual Network Peering connects two VNets over the Microsoft global backbone SDN with line-rate throughput, zero extra hop latency, and no public internet exposure.

VNet Peering is strictly non-transitive: peering VNet A to Hub VNet B and Hub VNet B to VNet C does NOT enable communication between VNet A and VNet C without a routing NVA and UDRs.

Gateway transit allows spoke VNets to utilize a shared Virtual Network Gateway in a hub VNet by setting 'AllowGatewayTransit' on the hub peering and 'UseRemoteGateways' on the spoke peering.

A Virtual Network cannot have 'UseRemoteGateways' enabled if it already contains its own Virtual Network Gateway.

Peered virtual networks must not have overlapping IPv4 or IPv6 address spaces; however, address spaces can now be added or expanded dynamically without deleting the peering.

Last updated: August 2026

Virtual Network Peering & Global Peering

Virtual Network Peering seamlessly connects two Azure Virtual Networks at Layer 3. Once peered, virtual machines and private endpoints across both VNets communicate as if they were residing within the same physical network, utilizing private IP addresses directly.

Peering traffic travels entirely across the high-speed Microsoft global backbone network . It never traverses the public internet, encounters encryption/decryption overhead (unless explicitly configured via MACsec or IPsec), or passes through gateway bottlenecks.

1. Regional vs. Global VNet Peering

Azure supports two geographic scopes of virtual network peering:

Regional VNet Peering: Interconnects virtual networks residing within the same Azure region (e.g., East US to East US).

Global VNet Peering: Interconnects virtual networks residing across different Azure regions or different continents (e.g., East US to West Europe or Southeast Asia).

  • Capability / Dimension Regional VNet Peering Global VNet Peering
  • Data Path Intra-datacenter / intra-region fiber SDN Microsoft Global Backbone WAN fiber
  • Latency Sub-millisecond (< 1 ms) Determined by physical fiber distance between regions
  • Bandwidth Full VM NIC wire speed (up to 100 Gbps) Full VM NIC wire speed
  • Gateway Transit Support Fully supported Fully supported across all global regions
  • Cross-Subscription / Cross-Tenant Supported via Azure RBAC Supported via Azure RBAC

Data Transfer Pricing Ingress and Egress billed at regional rates Ingress and Egress billed at cross-region / continental rates

2. Peering Prerequisites & Address Space Mechanics

To establish a successful peering link between two VNets, the following conditions must be satisfied:

No Overlapping Address Space: The address spaces of the two VNets must not overlap in any IPv4 or IPv6 prefix. Even a single overlapping /24 within a /16 block will cause peering creation to fail.

Bidirectional Link Establishment: Peering consists of two independent unidirectional links: VNet-A to VNet-B, and VNet-B to VNet-A. The peering status becomes Connected only when both links are created and point to each other. If one side is deleted, the remaining link transitions to Disconnected and traffic halts. +-----------------------------------------------------------------------------+

  • | BIDIRECTIONAL PEERING STATE MACHINE |
  • | |
  • | [VNet-A: 10.1.0.0/16] [VNet-B: 10.2.0.0/16] |
  • | | | |
  • | |--- (1) Admin creates link to VNet-B --->| Status: Initiated |
  • | |<-- (2) Admin creates link to VNet-A ----| Status: Connected |
  • | |
  • | Both sides must reach 'Connected' state for SDN route injection! |
  • +-----------------------------------------------------------------------------+

Tip

Dynamic Address Space Modification: Previously, changing or adding an address prefix required tearing down all existing peerings. Modern Azure SDN supports Address Space Sync : you can add a new address prefix to a peered VNet and trigger a synchronization action to inject the new routes into peered VNets without downtime.

Loading diagram... Hub-and-Spoke Topology with Gateway Transit and NVA Routing

3. The Non-Transitive Peering Rule & Inter-Spoke Routing

Virtual network peering is strictly non-transitive across the Azure SDN fabric.

The Non-Transitive Principle

If VNet A is peered to Hub VNet B , and Hub VNet B is peered to VNet C :

Workloads in VNet A CANNOT communicate with workloads in VNet C through the native peering fabric.

Azure SDN does not automatically route packets across intermediate peered hops. +-----------------------------------------------------------------------------+

  • | NON-TRANSITIVE PEERING LIMITATION |
  • | |
  • | [Spoke VNet A] <==== Peered ====> [Hub VNet B] <==== Peered ====> [Spoke VNet C]
  • | (10.1.0.0/16) (10.0.0.0/16) (10.2.0.0/16)
  • | | |
  • | X----------------- Direct Native Traffic BLOCKED -----------------X
  • | |
  • | RESOLUTION: Place Azure Firewall / NVA in Hub VNet B + Attach UDR to Spokes
  • +-----------------------------------------------------------------------------+

Enabling Transitive Inter-Spoke Communication:

To route traffic between Spoke A and Spoke C through the Hub:

Deploy an Azure Firewall or third-party Network Virtual Appliance (NVA) inside Hub VNet B (e.g., private IP 10.0.1.4 ).

Associate a User-Defined Route (UDR) table to the subnets in Spoke A with a route for 10.2.0.0/16 setting Next Hop Type = Virtual Appliance and Next Hop IP = 10.0.1.4 .

Associate a matching UDR table to the subnets in Spoke C for destination 10.1.0.0/16 pointing to 10.0.1.4 .

Enable AllowForwardedTraffic on the peering configurations between the Hub and the Spokes.

4. Service Chaining: Peering Plus UDRs

Microsoft's term for deliberately steering peered traffic through an intermediate appliance is service chaining , and it is named directly in the AZ-700 objectives. Service chaining is not a switch you turn on — it is the combination of three things you already have:

  • Ingredient Role in the chain
  • VNet peering Provides the private, non-transitive Layer 3 reachability between hub and spokes

A user-defined route Overrides the direct system route so spoke traffic is sent to the appliance instead of straight to the peer

The appliance's next hop An NVA or Azure Firewall private IP set as Virtual appliance , with IP forwarding enabled on the NVA's NIC

The canonical hub-and-spoke chain

Peer Spoke A and Spoke B to the Hub , with Allow forwarded traffic enabled on the hub side of each peering.

Deploy the firewall or NVA in the hub.

On each spoke subnet, associate a route table with a UDR for the other spoke's prefix — or 0.0.0.0/0 — whose next hop type is Virtual appliance and whose next hop address is the appliance's private IP.

Traffic now flows Spoke A → Hub appliance → Spoke B, giving you inspection, logging, and policy enforcement on east-west traffic that peering alone would have delivered directly.

Gateway transit is the same idea applied to hybrid traffic: instead of chaining through an appliance, the spoke chains through the hub's VPN or ExpressRoute gateway , which is why the two tasks appear in the same blueprint bullet.

Important

Service chaining needs both halves. Enabling Allow forwarded traffic without a UDR changes nothing — the spokes still take the direct system route to each other. Writing the UDR without Allow forwarded traffic on the hub peering causes the hub to drop the forwarded packets. Exam scenarios routinely present one half and ask what is missing.

5. Peering Configuration Flags & Gateway Transit

Every peering link exposes four critical configuration flags that govern routing behavior and security: +-----------------------------------------------------------------------------+

  • | PEERING CONFIGURATION FLAGS MATRIX |
  • | |
  • | Flag Name Default Purpose & Operational Impact |
  • | -------------------------- ------- ---------------------------------- |
  • | AllowVirtualNetworkAccess Enabled Injects peered VNet address space |
  • | into default system routing tables.|
  • | AllowForwardedTraffic Disabled Allows traffic NOT originating |
  • | from within peered VNet (NVA flow).|
  • | AllowGatewayTransit Disabled (HUB ONLY) Allows peered spokes to |
  • | utilize hub's VPN/ER Gateway. |
  • | UseRemoteGateways Disabled (SPOKE ONLY) Directs spoke to use |
  • | the hub's gateway for on-prem path.|
  • +-----------------------------------------------------------------------------+

Gateway Transit Rules for Hub-and-Spoke Topologies:

Hub Peering Link Configuration: Set AllowGatewayTransit = true on the peering link located in the Hub VNet pointing to the Spoke VNet.

Spoke Peering Link Configuration: Set UseRemoteGateways = true on the peering link located in the Spoke VNet pointing to the Hub VNet.

Mutual Exclusivity Constraint: A Spoke VNet cannot enable UseRemoteGateways if that Spoke VNet already contains its own Virtual Network Gateway ( VPN Gateway or ExpressRoute Gateway ). Only one gateway path can be active.