Study guide

4.1 Azure ExpressRoute Architecture & Peering Models

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

4.1 Azure ExpressRoute Architecture & Peering Models

Key Takeaways Explain This Topic AI

ExpressRoute Direct provides dual 10 Gbps or 100 Gbps physical fiber ports directly to Microsoft Enterprise Edge (MSEE) routers with support for line-rate MACsec (802.1AE) Layer 2 encryption.

Private Peering connects directly to Azure Virtual Networks via RFC 1918 addresses, while Microsoft Peering connects to Azure PaaS and Microsoft 365 services via public IPs and requires Route Filters with BGP communities.

FastPath bypasses the Virtual Network Gateway CPU data plane and programs routes directly into Azure host NICs, delivering line-rate throughput and lower latency on UltraPerformance and ErGw3AZ SKUs.

ExpressRoute does not support jumbo frames: the documented maximum ExpressRoute MTU is 1,400 bytes, ExpressRoute gateways drop fragmented packets, and ExpressRoute Direct's 1,500-byte IP MTU is a physical port requirement, not an end-to-end payload size.

The GatewaySubnet for ExpressRoute should be sized at /26 to ensure operational capacity for gateway maintenance, high-performance SKUs, and co-existence with Azure VPN Gateway.

Last updated: August 2026

Azure ExpressRoute creates a private, dedicated, high-throughput connection between enterprise on-premises infrastructure and Microsoft Cloud services. Unlike Site-to-Site VPN connections that traverse the public internet, ExpressRoute traffic travels over a private optical network fabric, delivering predictable performance, lower latency, and enhanced security for mission-critical enterprise workloads.

1. ExpressRoute Connectivity Models & Physical Topology

To establish an ExpressRoute circuit, organizations partner with network service providers or connect directly to Microsoft Enterprise Edge (MSEE) routers at designated ExpressRoute peering locations (meet-me facilities). +---------------------------------------------------------------------------------------------------+

  • | EXPRESSROUTE CONNECTIVITY MODELS |
  • | |
  • | 1. Cloud Exchange Co-location (Layer 2 / Layer 3 Ethernet Exchange) |
  • | [ On-Premises Meet-Me ] <---> [ Cloud Exchange (e.g. Equinix, Megaport) ] <---> [ MSEE Pair ] |
  • | |
  • | 2. Point-to-Point Ethernet (Dedicated Layer 2 Connection) |
  • | [ Corporate Datacenter ] <============== Dedicated Point-to-Point Fiber ==============> [ MSEE Pair ] |
  • | |
  • | 3. Any-to-Any IPVPN (Layer 3 MPLS / IP-VPN Network) |
  • | [ Branch 1 ] ----+ |
  • | [ Branch 2 ] ----+---> [ Telco MPLS / WAN Provider Backbone ] <-----------------------> [ MSEE Pair ] |
  • | [ HQ Core ] ----+ |
  • | |
  • | 4. ExpressRoute Direct (Dedicated Dual 10G / 100G Direct Fiber Ports) |
  • | [ Customer Edge Router 1 ] <============== 10G/100G Direct Cross-Connect ==============> [ MSEE 1 ] |
  • | [ Customer Edge Router 2 ] <============== 10G/100G Direct Cross-Connect ==============> [ MSEE 2 ] |
  • +---------------------------------------------------------------------------------------------------+
  • Connectivity Models Breakdown

Connectivity Model Layer Bandwidth Range Best Use Case Operational Characteristics

Cloud Exchange Co-location Layer 2 / Layer 3 50 Mbps - 10 Gbps Enterprises with infrastructure co-located in carrier-neutral facilities Virtual cross-connects provisioned quickly via software-defined cloud exchanges (e.g., Equinix Cloud Exchange, Megaport).

Point-to-Point Ethernet Layer 2 50 Mbps - 10 Gbps Single primary datacenter requiring dedicated high-speed link Dedicated point-to-point Ethernet circuits between on-premises sites and Azure meet-me facilities.

Any-to-Any (IPVPN / MPLS) Layer 3 50 Mbps - 10 Gbps Distributed branch offices already integrated into a managed WAN Telecom provider integrates Azure as another branch node in the enterprise IPVPN cloud. Azure is managed like any other WAN site.

ExpressRoute Direct Layer 1 / 2 Dual 10 Gbps or Dual 100 Gbps Massive data ingestion, financial trading, ultra-high throughput Direct physical fiber connection to MSEE routers at peering locations. Supports active-active dual ports (up to 200 Gbps aggregate) and hardware MACsec encryption.

ExpressRoute Direct Architecture & MACsec Encryption

ExpressRoute Direct provides direct physical connectivity into Microsoft's global backbone without an intermediary exchange provider. Key architectural capabilities include:

Dual Physical Ports : Provisioned as active-active port pairs (e.g., 2 × 100 Gbps 2 \times 100\text{ Gbps} 2 × 100 Gbps or 2 × 10 Gbps 2 \times 10\text{ Gbps} 2 × 10 Gbps ) landing on distinct MSEE chassis in a specific peering location.

Multi-Circuit Hosting : On a 100 Gbps ExpressRoute Direct port pair, administrators can carve out multiple isolated 1 Gbps, 2 Gbps, 5 Gbps, 10 Gbps, 40 Gbps, or 100 Gbps standard ExpressRoute circuits across different Azure subscriptions and routing domains.

Line-Rate MACsec (802.1AE) Encryption : ExpressRoute Direct supports point-to-point Layer 2 hardware encryption between customer edge routers and MSEEs. Pre-shared keys (CAK/CKN) are securely stored in Azure Key Vault and rotated seamlessly without dropping BGP peering sessions.

2. ExpressRoute Peering Models: Private vs. Microsoft Peering

ExpressRoute supports two distinct BGP routing domains over a single physical circuit: Azure Private Peering and Microsoft Peering (Public Peering is legacy and deprecated). +---------------------------------------------------------------------------------------------------+

  • | EXPRESSROUTE PEERING ARCHITECTURES |
  • | |
  • | +---------------------------------------------------------------------------------------------+ |
  • | | Microsoft Cloud | |
  • | | | |
  • | | +--------------------------------------------------------------------------------------+ | |
  • | | | Azure Private Peering (RFC 1918 / Private IPs) | | |
  • | | | -> Virtual Networks, Spoke VNets, Virtual Network Gateways, FastPath VM NICs | | |
  • | | +--------------------------------------------------------------------------------------+ | |
  • | | | |
  • | | +--------------------------------------------------------------------------------------+ | |
  • | | | Microsoft Peering (Public IPs / BGP Communities / Route Filters) | | |
  • | | | -> Microsoft 365 (Exchange, Teams, SharePoint) [Requires Authorization] | | |
  • | | | -> Azure PaaS (Storage, SQL DB, Key Vault, Azure App Services) [Public Endpoints] | | |
  • | | +--------------------------------------------------------------------------------------+ | |
  • | +----------------------------------------------+----------------------------------------------+ |
  • | | (Redundant BGP /30 Subnets) |
  • | v |
  • | +---------------------------------------------------------------------------------------------+ |
  • | | Microsoft Enterprise Edge (MSEE) | |
  • | +----------------------------------------------+----------------------------------------------+ |
  • | | (Primary & Secondary VLANs) |
  • | v |
  • | +---------------------------------------------------------------------------------------------+ |
  • | | On-Premises Customer Edge (CE) Routers | |
  • | | * NAT Gateway / Public IP Pool (Required for Microsoft Peering Outbound SNAT) | |
  • | | * Private IP Addressing (Private Peering) | |
  • | +---------------------------------------------------------------------------------------------+ |
  • +---------------------------------------------------------------------------------------------------+
  • Peering Comparison Matrix

Architectural Attribute Azure Private Peering Microsoft Peering

Target Services Virtual Networks (VNets), IaaS Virtual Machines, Azure Private Endpoints Azure Public PaaS (Storage, SQL, Event Hubs) & Microsoft 365 SaaS

IP Addressing RFC 1918 Private IPs ( 10.0.0.0/8 , 172.16.0.0/12 , 192.168.0.0/16 ) Public IPv4 / IPv6 addresses owned by enterprise (registered in ARIN/RIPE/RADb)

Gateway Requirement Requires Virtual Network Gateway (ExpressRoute SKU) in GatewaySubnet No GatewaySubnet or Azure Gateway required (routes directly to PaaS/M365)

NAT Requirements No NAT needed (direct private end-to-end IP routing) Mandatory SNAT : On-premises private IPs must be NATted to registered Public IPs

Route Filtering Azure automatically advertises VNet prefixes to on-premises Route Filters must be attached to the circuit; BGP communities filter services

Microsoft Approval No approval required (enabled immediately upon circuit provisioning) Microsoft Authorization required for Microsoft 365 BGP community filters

Microsoft Peering NAT & Route Filter Mechanics

Public IP Validation : Public IP prefixes used for BGP peering and outbound NAT must be registered to the enterprise in a Regional Internet Registry (RIR) such as ARIN, RIPE, or APNIC, or validated through Routing Assets Database (RADb).

NAT Architecture : Customer Edge routers must implement Source NAT (SNAT) so that internal client private IPs (e.g., 10.1.0.0/16 ) are translated to public IPs before packets cross the Microsoft Peering BGP boundary. The NAT IP pool must not overlap with the /30 peering IP addresses.

Route Filters & BGP Communities : By default, an activated Microsoft Peering session receives zero routes . To receive BGP routes, administrators create an Azure Route Filter resource containing specific BGP community strings and link it to the ExpressRoute circuit:

  • 12076:51004 — Azure Global Services (Storage, SQL, Cosmos DB, Azure Monitor)
  • 12076:5010 — Microsoft 365 Exchange Online (Requires Microsoft approval)
  • 12076:5020 — Microsoft 365 SharePoint Online / OneDrive (Requires Microsoft approval)
  • 12076:5030 — Microsoft 365 Teams / Skype for Business (Requires Microsoft approval)
  • 3. ExpressRoute Virtual Network Gateways & SKUs

When connecting an Azure Virtual Network to an ExpressRoute circuit via Private Peering, you must deploy an ExpressRoute Virtual Network Gateway inside the dedicated GatewaySubnet .

ExpressRoute Gateway SKU Specifications

  • Gateway SKU Max Throughput (Standard Data Plane) Max Circuit Connections Zone Redundancy FastPath Support
  • Standard 1.0 Gbps 4 circuits No No
  • HighPerformance 2.0 Gbps 8 circuits No No
  • UltraPerformance 4.0 - 9.5 Gbps 8 circuits No Yes
  • ErGw1AZ 1.0 Gbps 4 circuits Yes (Zone-Redundant) No
  • ErGw2AZ 2.0 Gbps 8 circuits Yes (Zone-Redundant) No
  • ErGw3AZ 4.0 - 9.5 Gbps 8 circuits Yes (Zone-Redundant) Yes (Full Feature Set)

Important

GatewaySubnet Sizing for ExpressRoute :

The GatewaySubnet must be sized at /27 minimum, but /26 is the recommended best practice . A /26 subnet provides 59 usable host IPs, allowing concurrent deployment of an ExpressRoute Gateway, an Azure VPN Gateway (for co-existence failover), and necessary maintenance instances allocated during platform host updates.

4. ExpressRoute FastPath Architecture

In standard ExpressRoute Private Peering, all packets entering the Azure VNet from an on-premises network must pass through the virtual network gateway VM instances in the GatewaySubnet before reaching target virtual machines. +-------------------------------------------------------------------------------------------------+

  • | STANDARD GATEWAY ROUTING vs. FASTPATH |
  • | |
  • | STANDARD ROUTING (Bottleneck at Gateway CPU): |
  • | [ On-Premises ] ---> [ MSEE ] ---> [ GatewaySubnet (VGW VMs: 1-9.5 Gbps) ] ---> [ VM NIC ] |
  • | |
  • | FASTPATH ROUTING (Bypasses Gateway CPU completely): |
  • | [ On-Premises ] ---> [ MSEE ] ================================================> [ VM NIC ] |
  • | (Direct Host SmartNIC Data Plane) |
  • | |
  • | * Note: ExpressRoute Gateway is still required for BGP Control Plane route exchange! |
  • +-------------------------------------------------------------------------------------------------+
  • FastPath Operational Mechanics

Data Plane Bypass : When FastPath is enabled on the ExpressRoute Connection resource, Azure programs routing tables directly into the host hypervisors and Azure SmartNICs. Packets travel directly between the MSEE router and the destination VM NIC at full wire speed.

Throughput Scaling : FastPath removes the gateway CPU bottleneck, scaling network throughput to 10 Gbps, 40 Gbps, and 100 Gbps when paired with ExpressRoute Direct.

Latency Reduction : Bypassing gateway VM hops reduces inter-packet jitter and improves round-trip latency for high-frequency trading and big-data analytics.

Prerequisites & SKUs : FastPath requires an UltraPerformance or ErGw3AZ (or ErGw1AZ/2AZ for standard FastPath configurations) gateway SKU.

FastPath Feature Support & Limitations

Virtual Network Peering Transit : FastPath supports peered VNets. Traffic from on-premises to a peered spoke VNet bypasses the gateway completely.

Private Endpoints : FastPath routes traffic directly to Azure Private Endpoints deployed in the VNet without gateway throttling.

Internal Load Balancers (ILB) : Supports backend pools behind ILBs across all SKUs.

Control Plane Dependency : The ExpressRoute Gateway cannot be deleted; it is strictly required to maintain eBGP neighbor peering sessions with the MSEEs.

UDR Bypassing : By default, User-Defined Routes (UDRs) associated with the GatewaySubnet are bypassed by FastPath. To force FastPath traffic through an NVA/Firewall, specific UDR-on-GatewaySubnet FastPath support must be explicitly enabled.

5. MTU, Packet Size & Fragmentation

ExpressRoute does not support jumbo frames. This is one of the most commonly mis-remembered ExpressRoute facts, and it is worth memorising precisely because plausible-sounding 9,000-byte answers appear as distractors.

Setting Documented value Where it applies

Maximum ExpressRoute MTU 1,400 bytes The ExpressRoute FAQ states ExpressRoute supports an MTU of 1,400 bytes. Tune VM TCP/IP settings against this number, not against 1,500.

Maximum TCP/UDP packet size through an ExpressRoute gateway 1,400 bytes Applies to traffic traversing the ExpressRoute virtual network gateway.

ExpressRoute Direct physical interface IP MTU 1,500 bytes A hardware onboarding requirement of the customer router/switch ports facing the MSEE pair. It is a link-layer requirement, not a licence to send 9,000-byte payloads end to end.

Jumbo frames (9,000 bytes) Not supported Neither on provider-managed circuits nor on ExpressRoute Direct, and neither on private peering nor Microsoft peering.

Fragmentation Behaviour

ExpressRoute gateways do not support fragmented packets. A fragmented packet arriving at the gateway is dropped rather than reassembled, so the application must avoid producing IP fragmentation in the first place.

The supported mitigations are application-side: reduce the sending MTU, rely on Path MTU Discovery (PMTUD) , or apply TCP MSS clamping on the on-premises edge router.

If your workload genuinely requires IP fragmentation support, the documented option is to enable ExpressRoute FastPath , which bypasses the ExpressRoute gateway data plane entirely.

Caution

The classic MTU failure signature : small requests (a TCP handshake, an ICMP ping, a DNS lookup) succeed, but large transfers — a file copy, a database bulk load, a TLS handshake carrying a large certificate chain — hang or reset. That asymmetry between "small works, large fails" over a hybrid link is the exam's cue for an MTU/fragmentation problem, not a BGP, NSG, or firewall problem.

Loading diagram... ExpressRoute Architecture with FastPath and Dual Peering