ExpressRoute connectivity partners and peering locations
The tables in this article provide information on ExpressRoute geographical coverage and locations, ExpressRoute connectivity providers, and ExpressRoute System Integrators (SIs).
Note
Azure regions and ExpressRoute locations are two distinct and different concepts, understanding the difference between the two is critical to exploring Azure hybrid networking connectivity.
Azure regions
Azure regions are global datacenters where Azure compute, networking, and storage resources are hosted. When creating an Azure resource, you need to select the resource location, which determines the specific Azure datacenter (or availability zone) where the resource is deployed.
ExpressRoute locations
ExpressRoute locations, also known as peering locations or meet-me locations, are co-location facilities where Microsoft Enterprise Edge (MSEE) devices are situated. These locations serve as the entry points to Microsoft's network and are globally distributed, offering the ability to connect to Microsoft's network worldwide. ExpressRoute partners and ExpressRoute Direct user establish cross connections to Microsoft's network at these locations. Generally, the ExpressRoute location doesn't need to correspond with the Azure region. For instance, you can create an ExpressRoute circuit with the resource location in East US for the Seattle peering location.
You have access to Azure services across all regions within a geopolitical region if you're connecting 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.
Geopolitical region | Azure regions | ExpressRoute locations |
---|---|---|
North America | East US West US East US 2 West US 2 West US 3 Central US South Central US North Central US West Central US Canada Central Canada East |
Atlanta Chicago Chicago2 Dallas Dallas2 Denver Las Vegas Los Angeles Los Angeles2 Miami Minneapolis Montreal New York Phoenix Phoenix2 Quebec City Queretaro(Mexico) Quincy San Antonio Seattle Silicon Valley Silicon Valley2 Toronto Toronto2 Vancouver Washington DC Washington DC2 |
South America | Brazil South | Campinas Rio de Janeiro Sao Paulo Sao Paulo2 Santiago |
Connectivity across geopolitical regions isn't supported on the standard ExpressRoute SKU. You'll need to enable the ExpressRoute premium add-on to support global connectivity. Connectivity to national cloud environments isn't supported. You can work with your connectivity provider if such a need arises.
ExpressRoute connectivity providers
The following table shows locations by service provider. If you want to view available providers by location, see Service providers by location.
Global commercial Azure
Service provider | Microsoft Azure | Microsoft 365 | Locations |
---|---|---|---|
AARNet | ✓ | ✓ | Melbourne Sydney Sydney2 |
Airtel | ✓ | ✓ | Chennai2 Mumbai2 Pune |
AIS | ✓ | ✓ | Bangkok |
Aryaka Networks | ✓ | ✓ | Amsterdam Chicago Dallas Hong Kong Sao Paulo Seattle Silicon Valley Singapore Tokyo Washington DC |
Ascenty Data Centers | ✓ | ✓ | Campinas Sao Paulo Sao Paulo2 |
AT&T Connectivity Plus | ✓ | ✓ | Dallas |
AT&T Dynamic Exchange | ✓ | ✓ | Chicago Dallas Los Angeles Miami Silicon Valley |
AT&T NetBond | ✓ | ✓ | Amsterdam Chicago Dallas Frankfurt London Phoenix Silicon Valley Singapore Sydney Tokyo Toronto Washington DC |
AT TOKYO | ✓ | ✓ | Osaka Tokyo2 |
BBIX | ✓ | ✓ | Osaka Tokyo Tokyo2 |
BCX | ✓ | ✓ | Cape Town Johannesburg |
Bell Canada | ✓ | ✓ | Montreal Toronto Quebec City Vancouver |
Bezeq International | ✓ | ✓ | London Tel Aviv |
BICS | ✓ | ✓ | Amsterdam2 London2 |
British Telecom | ✓ | ✓ | Amsterdam Amsterdam2 Chicago Frankfurt Hong Kong Johannesburg London London2 Mumbai Newport(Wales) Paris Sao Paulo Silicon Valley Singapore Sydney Tokyo Washington DC |
BSNL | ✓ | ✓ | Chennai Mumbai |
C3ntro | ✓ | ✓ | Miami |
Cello | ✓ | ✓ | Sydney |
CDC | ✓ | ✓ | Canberra Canberra2 |
CenturyLink Cloud Connect | ✓ | ✓ | Amsterdam2 Chicago Dallas Dublin Frankfurt Hong Kong Las Vegas London London2 Montreal New York Paris Phoenix San Antonio Seattle Silicon Valley Singapore2 Tokyo Toronto Washington DC Washington DC2 |
Chief Telecom | ✓ | ✓ | Hong Kong Taipei |
China Mobile International | ✓ | ✓ | Hong Kong Hong Kong2 Singapore Singapore2 |
China Telecom Global | ✓ | ✓ | Hong Kong Hong Kong2 Singapore Tokyo2 |
China Unicom Global | ✓ | ✓ | Amsterdam Frankfurt Hong Kong Los Angeles Silicon Valley Singapore2 Tokyo2 |
Chunghwa Telecom | ✓ | ✓ | Taipei |
Cinia | ✓ | ✓ | Amsterdam2 Stockholm |
Cirion Technologies | ✓ | ✓ | Queretaro Rio De Janeiro Santiago |
Claro | ✓ | ✓ | Miami |
Cloudflare | ✓ | ✓ | Los Angeles |
Cologix | ✓ | ✓ | Chicago Dallas Minneapolis Montreal Toronto Vancouver Washington DC |
Claro | ✓ | ✓ | Miami |
Cloudflare | ✓ | ✓ | Los Angeles |
Cologix | ✓ | ✓ | Chicago Dallas Minneapolis Montreal Toronto Vancouver Washington DC |
Colt | ✓ | ✓ | Amsterdam Amsterdam2 Berlin Chicago Dublin Frankfurt Frankfurt2 Geneva Hong Kong London London2 Marseille Milan Munich Newport Osaka Paris Paris2 Seoul Silicon Valley Singapore2 Tokyo Tokyo2 Washington DC Zurich |
Comcast | ✓ | ✓ | Chicago Silicon Valley Washington DC |
CoreSite | ✓ | ✓ | Chicago Chicago2 Denver Los Angeles New York Silicon Valley Silicon Valley2 Washington DC Washington DC2 |
Cox Business Cloud Port | ✓ | ✓ | Dallas Phoenix Silicon Valley Washington DC |
Crown Castle | ✓ | ✓ | Los Angeles2 New York Washington DC |
National cloud environment
Azure national clouds are isolated from each other and from the Azure public cloud. ExpressRoute for one Azure cloud can't connect to the Azure regions in the others.
Service provider | Microsoft Azure | Office 365 | Locations |
---|---|---|---|
AT&T NetBond | ✓ | ✓ | Chicago Phoenix Silicon Valley Washington DC |
CenturyLink Cloud Connect | ✓ | ✓ | New York Phoenix San Antonio Washington DC |
Equinix | ✓ | ✓ | Atlanta Chicago Dallas New York Seattle Silicon Valley Washington DC |
Internet2 | ✓ | ✓ | Dallas |
Level 3 Communications | ✓ | ✓ | Chicago Silicon Valley Washington DC |
Megaport | ✓ | ✓ | Chicago Dallas San Antonio Seattle Washington DC |
Verizon | ✓ | ✓ | Chicago Dallas New York Silicon Valley Washington DC |
To learn more, see ExpressRoute in China.
Connectivity through Exchange providers
If your connectivity provider isn't listed in previous sections, you can still create a connection.
Check with your connectivity provider to see if they're 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.
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're remote and don't have fiber connectivity, or you want to explore other connectivity options you can check the following satellite operators.
Connectivity through additional service providers
Connectivity provider | Exchange | Locations |
---|---|---|
1CLOUDSTAR | Equinix | Singapore |
Airgate Technologies, Inc. | Equinix Cologix |
Toronto Montreal |
Alaska Communications | Equinix | Seattle |
Altice Business | Equinix | New York Washington DC |
Aptum Technologies | Equinix | Montreal Toronto |
Arteria Networks Corporation | Equinix | Tokyo |
Axtel | Equinix | Dallas |
Beanfield Metroconnect | Megaport | Toronto |
Bezeq International Ltd. | euNetworks | London |
BICS | Equinix | Amsterdam Frankfurt London Singapore Washington DC |
BroadBand Tower, Inc. | Equinix | Tokyo |
C3ntro Telecom | Equinix Megaport |
Dallas |
Chief | Equinix | Hong Kong |
Cinia | Equinix Megaport |
Frankfurt Hamburg |
CloudXpress | Equinix | Amsterdam |
CMC Telecom | Equinix | Singapore |
CoreAzure | Equinix | London |
Cox Business | Equinix | Dallas Silicon Valley Washington DC |
Crown Castle | Equinix | Atlanta Chicago Dallas Los Angeles New York Washington DC |
Connectivity through datacenter providers
Provider | Exchange |
---|---|
CyrusOne | Megaport PacketFabric |
Cyxtera | Megaport PacketFabric |
Databank | Megaport |
DataFoundry | Megaport |
Digital Realty | IX Reach Megaport PacketFabric |
EdgeConnex | Megaport PacketFabric |
Flexential | IX Reach Megaport PacketFabric |
QTS Data Centers | Megaport PacketFabric |
Stream Data Centers | Megaport |
RagingWire Data Centers | IX Reach Megaport PacketFabric |
T5 Datacenters | IX Reach |
vXchnge | IX Reach Megaport |
Connectivity through National Research and Education Networks (NREN)
Provider |
---|
AARNET |
DeIC, through GÉANT |
GARR, through GÉANT |
GÉANT |
HEAnet, through GÉANT |
Internet2 |
JISC |
RedIRIS, through GÉANT |
SINET |
Surfnet, through GÉANT |
Note
If your connectivity provider isn't listed here, you can verify if they are connected to any of the other ExpressRoute Exchange Partners mentioned previously.
ExpressRoute system integrators
Enabling private connectivity to meet your needs can be challenging, depending on the scale of your network. You can collaborate with any of the system integrators listed in the following table to assist with onboarding to ExpressRoute.
System integrator | Continent |
---|---|
Altogee | Europe |
Avanade Inc. | Asia Europe North America South America |
Bright Skies GmbH | Europe |
Optus | Australia |
Equinix Professional Services | North America |
New Era | North America |
Lightstream | North America |
The IT Consultancy Group | Australia |
MOQdigital | Australia |
MSG Services | Europe (Germany) |
Nelite | Europe |
New Signature | Europe |
OneAs1a | Asia |
Orange Networks | Europe |
Perficient | North America |
Presidio | North America |
sol-tec | Europe |
Venha Pra Nuvem | South America |
Vigilant.IT | Australia |
Next steps
- For more information about ExpressRoute, see the ExpressRoute FAQ.
- Ensure that all prerequisites are met. For more information, see ExpressRoute prerequisites.