ExpressRoute partners and peering locations

• 02/15/2020
• 11 minutes to read
• • 
  • 
  • 
  • 
  • 
  • +12

The tables in this article provide information on ExpressRoute geographical coverage and locations, ExpressRoute connectivity providers,and ExpressRoute System Integrators (SIs).

Azure regions

Azure regions are global datacenters where Azure compute, networking and storage resources are located. When creating an Azure resource, a customer needs to select a resource location. The resource location determines which Azure datacenter (or availability zone) the resource is created in.

ExpressRoute locations

ExpressRoute locations (sometimes referred to as peering locations or meet-me-locations) are co-location facilities where Microsoft Enterprise edge (MSEE) devices are located. ExpressRoute locations are the entry point to Microsoft’s network – and are globally distributed, providing customers the opportunity to connect to Microsoft’s network around the world. These locations are where ExpressRoute partners and ExpressRoute Direct customers issue cross connections to Microsoft’s network. In general, the ExpressRoute location does not need to match the Azure region. For example, a customer can create an ExpressRoute circuit with the resource location East US, in the Seattle Peering location.

You will have access to Azure services across all regions within a geopolitical region if you connected to at least one ExpressRoute location within the geopolitical region.

Azure regions to ExpressRoute locations within a geopolitical region

The following table provides a map of Azure regions to ExpressRoute locations within a geopolitical region.

Azure regions and geopolitical boundaries for national clouds

The table below provides information on regions and geopolitical boundaries for national clouds.

Connectivity across geopolitical regions is not supported on the standard ExpressRoute SKU. You will need to enable the ExpressRoute premium add-on to support global connectivity. Connectivity to national cloud environments is not supported. You can work with your connectivity provider if such a need arises.

ExpressRoute connectivity providers

The following table shows connectivity locations and the service providers for each location. If you want to view service providers and the locations for which they can provide service, see Locations by service provider.

• Local Azure Regions are the ones that ExpressRoute Local at each peering location can access. n/a indicates that ExpressRoute Local is not available at that peering location.

• Zone refers to pricing.

Global commercial Azure

+ denotes coming soon

National cloud environments

Azure national clouds are isolated from each other and from global commercial Azure. ExpressRoute for one Azure cloud can't connect to the Azure regions in the others.

US Government cloud

China

To learn more, see ExpressRoute in China

Germany

Connectivity through Exchange providers

If your connectivity provider is not listed in previous sections, you can still create a connection.

• Check with your connectivity provider to see if they are connected to any of the exchanges in the table above. You can check the following links to gather more information about services offered by exchange providers. Several connectivity providers are already connected to Ethernet exchanges.

  • Cologix
  • CoreSite
  • Equinix Cloud Exchange
  • InterXion
  • NextDC
  • Megaport
  • PacketFabric
  • Teraco

• Have your connectivity provider extend your network to the peering location of choice.

  • Ensure that your connectivity provider extends your connectivity in a highly available manner so that there are no single points of failure.

• Order an ExpressRoute circuit with the exchange as your connectivity provider to connect to Microsoft.

  • Follow steps in Create an ExpressRoute circuit to set up connectivity.

Connectivity through satellite operators

If you are remote and don't have fiber connectivity or you want to explore other connectivity options you can check the following satellite operators.

• Intelsat
• SES
• Viasat

Connectivity through additional service providers

ExpressRoute system integrators

Enabling private connectivity to fit your needs can be challenging, based on the scale of your network. You can work with any of the system integrators listed in the following table to assist you with onboarding to ExpressRoute.

Next steps

• For more information about ExpressRoute, see the ExpressRoute FAQ.
• Ensure that all prerequisites are met. See ExpressRoute prerequisites.