Microsoft Cloud: Azure Region Pair via ExpressRoute – HA Design

When using Azure ExpressRoute to transport production Azure workloads, it is recommended to use ExpressRoute circuits in both Azure Regions in the Azure Region Pair using ExpressRoute On-Ramps at each region. This could be from either a single Megaport, a pair of Megaport physical connections (either discrete or in LAG/LACP bundle) in a single DC or spread across multiple DC locations (refer Azure ExpressRoute High Availability page).

Below are the components required for creating diverse paths into Azure Paired Region via Megaport in two different DC locations:

  • Microsoft Azure
    1 x ExpressRoute Circuit in Region 1 of the Region Pair
    1 x ExpressRoute Circuit in Region 2 of the Region Pair
    1 x Virtual Network Gateway in Region 1 attached to Virtual Network (VNet)
    1 x Virtual Network Gateway in Region 2 attached to Virtual Network (VNet)

Important Note: It is not possible to have more than one ExpressRoute Circuit in the same region connecting to the same Virtual Network Gateway (Attached to Virtual Network). (Azure ExpressRoute FAQ 01 and Azure ExpressRoute FAQ 02). This limitation also applies to using different service providers to provide ExpressRoute service to the same region (Azure ExpressRoute FAQ 03). Megaport has a solution to this Azure limitation using Megaport Cloud Router (MCR) product, check this KB post: MCR – Sharing an Azure ExpressRoute to a Single Region

Additional useful links:

Microsoft Cloud: Azure ExpressRoute

SLA For ExpressRoute

Megaport Global Service Agreement

©2019 Megaport. Megaport, Virtual Cross Connect, VXC and MegaIX are registered trademarks of Megaport (Services) Pty Ltd ACN 607 432 646.

Log in with your credentials

Forgot your details?