Skip to main content
When using Azure ExpressRoute to transport production Azure workloads, the recommended configuration uses ExpressRoute circuits in both Azure regions in an Azure region pair using ExpressRoute on-ramps at each region. The Megaport solution connecting the customer’s network could be a single Port, a pair of physical Port connections (either discrete or in a LAG/LACP bundle) in a single data center, or a pair of physical Port connections diversified across multiple data center locations.

​
Creating diverse paths in an Azure paired region

These are the components required for creating diverse paths into an Azure paired region through Megaport in different data center locations:

​
Microsoft Azure

  • ExpressRoute Circuit in region 1 of the region pair
  • ExpressRoute Circuit in region 2 of the region pair
  • Virtual Network Gateway in region 1 attached to Virtual Network (vNet)
  • Virtual Network Gateway in region 2 attached to Virtual Network (vNet)

​
Megaport

  • 1 (or 2 in a Link Aggregation/LAG configuration) Port in a Megaport-enabled location
  • 1 (or 2 in a LAG configuration) Port in a Megaport-enabled location
  • 4 VXCs with each connecting to different Azure on-ramp locations
See Microsoft FAQ entries on multiple ExpressRoute circuits connecting a vNet at same (or different) peering location:

​
Helpful references

Last modified on August 21, 2026