> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure Paired Regions - HA Design

> This help topic describes the requirements for creating diverse paths into an Azure region through Megaport.

export const Image = ({src, alt = '', caption, width, height, shadow}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Image -';
  if (typeof src !== 'string') {
    src = String(src);
  }
  if (!src || src === 'undefined') {
    console.error(`${errorPrefix} \`src\` is required — rendering an empty string instead`);
    return <></>;
  }
  const img = <img className={['mega-image-style', shadow ? 'shadow' : ''].join(' ')} src={src} alt={alt} width={width} height={height} style={{
    display: 'block'
  }} />;
  return caption ? <figure>
      {img}
      <figcaption style={{
    textAlign: 'center',
    width
  }}>{caption}</figcaption>
    </figure> : img;
};

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

<Image src="/images/cloud/megaport/microsoft/azure-ha-configuration.png" alt="HA configuration for Azure" />

<Note>
  See Microsoft FAQ entries on multiple ExpressRoute circuits connecting a vNet at same (or different) peering location:

  * [Can I have multiple ExpressRoute circuits in the same metro?](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs#can-i-have-multiple-expressroute-circuits-in-the-same-metro-can-i-link-them-to-the-same-virtual-network)
  * [Can I have one virtual network connected to more than one ExpressRoute circuit?](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs#can-i-have-one-virtual-network-connected-to-more-than-one-expressroute-circuit)
  * [Can I have ExpressRoute circuits from different service providers?](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs#can-i-have-expressroute-circuits-from-different-service-providers)
</Note>

## Helpful references

* [Microsoft ExpressRoute HA FAQ](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs#how-do-i-ensure-high-availability-on-a-virtual-network-connected-to-expressroute)

* [Business continuity and disaster recovery (BCDR): Azure Paired Regions](https://docs.microsoft.com/en-us/azure/best-practices-availability-paired-regions)

* [SLA for Azure ExpressRoute](https://azure.microsoft.com/en-us/support/legal/sla/expressroute/v1_3/)