Study guide

4.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting

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.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting

Key Takeaways Explain This Topic AI

MSEE devices use a BGP keepalive of 60 seconds and a hold time of 180 seconds, so without BFD a link failure behind an intermediate Layer 2 device can take up to three minutes to detect.

Bidirectional Forwarding Detection is supported over both ExpressRoute private peering and Microsoft peering and is enabled by default on the Azure side of newly created peering interfaces, so only the customer CE/PE devices need configuring.

MSEE BFD transmit and receive intervals are set to 300 milliseconds and in some scenarios 750 milliseconds; the slower of the two peers determines the rate, so you can lengthen the interval but never shorten it below the Microsoft value.

Enabling BFD on a peering created before August 2018 for IPv4 private peering, January 2020 for IPv4 Microsoft peering, or November 2025 for IPv6 requires resetting that peering.

BFD speeds link-failure detection to sub-second, but overall convergence between ExpressRoute virtual network gateways and MSEEs still takes up to a minute.

Last updated: August 2026

ExpressRoute BFD, Monitoring & Connection Troubleshooting

An ExpressRoute circuit is always deployed as a redundant pair of connections to a pair of Microsoft Enterprise Edge routers (MSEEs). Redundancy only helps if a failure is detected , and detection is exactly where naive ExpressRoute designs fall down: when a Layer 2 device sits between your router and the MSEE, the physical link on your side stays up even after the path has broken, so the only thing that notices is BGP — slowly.

1. Why BFD Exists: The Three-Minute Problem

On MSEE devices, BGP timers are configured as:

  • Timer MSEE value
  • BGP keepalive 60 seconds
  • BGP hold time 180 seconds

If a link fails and there is more than one Layer 2 device in the path, responsibility for detecting the failure falls to the overlying BGP session. With a 180-second hold time, it can take up to three minutes to notice the failure and shift traffic to the alternate connection. Three minutes of blackholed traffic is unacceptable for most production workloads.

The tempting wrong fix

You can lower BGP timers on your own edge device — when the timers differ between peers, the session establishes using the lower value, and BGP keepalive can go as low as 3 seconds with a hold time as low as 10 seconds . Microsoft explicitly recommends against this, because BGP is a process-intensive protocol and aggressive timers destabilise the control plane.

The right fix

Bidirectional Forwarding Detection (BFD) is a lightweight protocol that provides link-failure detection in a sub-second interval with low overhead. It runs independently of BGP and simply tells BGP to tear the session down when the path dies.

2. BFD on ExpressRoute: Support and Defaults

  • Question Answer
  • Which peerings support BFD? Both private peering and Microsoft peering

Is it on by default? Yes on the Microsoft side. BFD is configured by default under all newly created ExpressRoute private and Microsoft peering interfaces on the MSEEs

What must the customer do? Configure BFD on both the primary and secondary CE/PE devices — a two-step process: configure BFD on the interface, then link it to the BGP session

Is customer-side BFD mandatory? No, it is optional. But the Azure-side BFD configuration for new peerings is not optional and cannot be removed

Connectivity model Works whether you use Layer 2 connections or a managed Layer 3 connection service; configure on your edge routers or your partner's edge routers

Legacy peerings need a reset

BFD is enabled by default only for peerings created after specific dates. To enable BFD on an older peering you must reset the peering :

  • Peering Created before Action required
  • IPv4 private peering August 2018 Reset the peering
  • IPv4 Microsoft peering January 2020 Reset the peering
  • IPv6 peering November 2025 Reset the peering
  • 3. BFD Timer Negotiation

Between BFD peers, the slower of the two peers determines the transmission rate .

  • Setting Value
  • MSEE BFD transmit / receive interval 300 milliseconds
  • MSEE interval in certain scenarios 750 milliseconds
  • Can you make it faster than Microsoft's value? No
  • Can you make it slower? Yes — configure a higher value on your device

Note

Because of device-vendor differences in handling, Microsoft recommends disabling BFD echo mode for ExpressRoute connections.

Important

BFD does not make failover instant. Microsoft states that BFD gives faster failure detection , but overall connection convergence between ExpressRoute virtual network gateways and MSEEs still takes up to a minute . If an exam option promises sub-second end-to-end failover, it is overstating the feature. BFD is also the documented way to speed failover when you run geo-redundant ExpressRoute circuits or use a site-to-site IPsec VPN as backup .

4. Gateway Limits That Cause "Mystery" ExpressRoute Failures

Many ExpressRoute incidents are not faults at all — they are documented limits being exceeded.

  • Gateway SKU VPN/ER coexistence FastPath Max circuit connections Throughput Routes learned
  • Standard / ErGw1Az Yes No 4 1,000 Mbps 4,000
  • High Performance / ErGw2Az Yes No 8 2,000 Mbps 9,500
  • Ultra Performance / ErGw3Az Yes Yes 16 10,000 Mbps 9,500
  • ErGwScale Yes Yes (minimum 10 scale units) 4 / 8 / 16 by scale units 1,000 Mbps per scale unit 9,500

Additional hard limits:

The maximum number of ExpressRoute circuits from the same peering location that can connect to the same virtual network is 4 , for every gateway SKU.

ExpressRoute private peering advertises up to 1,000 IPv4 prefixes and 100 IPv6 prefixes from a virtual network to on-premises. Use the summarizedGatewayPrefixes property to advertise summarised prefixes and suppress covered spoke address spaces in hub-and-spoke designs.

Avoid advertising more than 11,000 routes to ExpressRoute across VNet address spaces, on-premises networks, and peerings.

A virtual network with an ExpressRoute gateway can peer with up to 500 other virtual networks .

NSGs on GatewaySubnet are not supported , and a 0.0.0.0/0 UDR on GatewaySubnet is not supported. BGP route propagation must remain enabled on the gateway subnet or the gateway will not function.

5. A Structured ExpressRoute Troubleshooting Order

Work outward from the physical layer. Skipping layers is how engineers spend an afternoon on BGP when an optic is dark.

Layer What to check Where

1. Circuit / provider Is the circuit Provisioned ? Has the provider completed provisioning on their side? Circuit blade — ServiceProviderProvisioningState

2. Layer 2 Is the ARP table populated on both primary and secondary? Correct VLAN ID / tagging? Get-AzExpressRouteCircuitARPTable

3. Layer 3 / BGP Is the peering Enabled ? Are the /30 peer subnets correct and non-overlapping? Is the ASN right? Get-AzExpressRouteCircuitRouteTable , peering blade

4. Route advertisement Are the expected prefixes learned and advertised? Are you over the 1,000-prefix limit? Get-AzExpressRouteCircuitRouteTableSummary

5. Gateway Right SKU for circuit count and throughput? Gateway health and metrics? Gateway metrics, Network Insights

  • 6. Path / performance Latency, packet loss, hop-by-hop path Network Watcher Connection Monitor
  • Common root causes and their signatures
  • Symptom Likely cause
  • Failover takes about three minutes BFD not configured on the customer edge devices

BGP session never establishes Reserved ASN used on-premises ( 65515-65520 , 8074, 8075, 12076 ), or mismatched peer subnets

Some prefixes missing from on-premises Route-advertisement limit exceeded, or route filter on Microsoft peering

Small requests work, large transfers hang MTU / fragmentation — ExpressRoute supports 1,400 bytes and gateways drop fragmented packets

Throughput plateaus well below the circuit bandwidth Gateway SKU ceiling; consider a higher SKU or FastPath on Ultra Performance / ErGw3Az

Private endpoint connectivity drops during maintenance Expected; set on-premises TCP timeout to 15-30 seconds

Tip

ASN 12076 is Microsoft's public ASN for ExpressRoute peerings. When ExpressRoute advertises routes to on-premises it strips private BGP ASN information, so on-premises receives prefixes with AS 12076 — which is why AS-path prepending applied by an NVA toward Route Server does not survive to the on-premises router.