You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -44,7 +44,7 @@ The following table shows connectivity locations and the service providers for e
44
44
***ER Direct** refers to [ExpressRoute Direct](expressroute-erdirect-about.md) support at each peering location. If you want to view the available bandwidth at a location, see [Determine available bandwidth](expressroute-howto-erdirect.md#resources)
|**Amsterdam**|[Equinix AM5](https://www.equinix.com/locations/europe-colocation/netherlands-colocation/amsterdam-data-centers/am5/)| 1 | West Europe | Supported | Aryaka Networks, AT&T NetBond, British Telecom, Colt, Equinix, euNetworks, GÉANT, InterCloud, Interxion, KPN, IX Reach, Level 3 Communications, Megaport, NTT Communications, Orange, Tata Communications, Telefonica, Telenor, Telia Carrier, Verizon, Zayo |
@@ -142,7 +142,7 @@ The following table shows connectivity locations and the service providers for e
142
142
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.
@@ -224,7 +224,7 @@ If you're remote and don't have fiber connectivity or want to explore other conn
224
224
## ExpressRoute system integrators
225
225
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.
226
226
227
-
|**Continent**|**System integrators**|
227
+
| Continent | System integrators |
228
228
| --- | --- |
229
229
|**Asia**|Avanade Inc., OneAs1a |
230
230
|**Australia**| Ensyst, IT Consultancy, MOQdigital, Vigilant.IT |
Copy file name to clipboardExpand all lines: articles/expressroute/expressroute-locations.md
+25-28Lines changed: 25 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
---
2
-
title: 'Connectivity providers and locations: Azure ExpressRoute | Microsoft Docs'
3
-
description: This article provides a detailed overview of locations where services are offered and how to connect to Azure regions. Sorted by connectivity provider.
2
+
title: Connectivity providers and locations for Azure ExpressRoute
3
+
description: This article provides a detailed overview of peering locations served by each ExpressRoute connectivity provider to connect to Azure.
# ExpressRoute connectivity partners and peering locations
15
15
16
16
> [!div class="op_single_selector"]
@@ -23,15 +23,14 @@ The tables in this article provide information on ExpressRoute geographical cove
23
23
> [!Note]
24
24
> 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.
25
25
>
26
-
>
27
26
28
27
## Azure regions
29
28
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.
30
29
31
30
## ExpressRoute locations
32
-
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.
31
+
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 doesn't 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.
33
32
34
-
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.
33
+
You'll 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.
|**[Epsilon Global Communications](https://epsilontel.com/solutions/cloud-connect/)**|Supported |Supported | Hong Kong2, Singapore, Singapore2 |
81
-
|**[Equinix](https://www.equinix.com/partners/microsoft-azure/)**|Supported |Supported | Amsterdam, Amsterdam2, Atlanta, Berlin, Bogota, Canberra2, Chicago, Dallas, Dubai2, Dublin, Frankfurt, Frankfurt2, Geneva, Hong Kong SAR, Hong Kong2, London, London2, Los Angeles*, Los Angeles2, Melbourne, Miami, Milan, New York, Osaka, Paris, Paris2, Quebec City, Rio de Janeiro, Sao Paulo, Seattle, Seoul, Silicon Valley, Singapore, Singapore2, Stockholm, Sydney, Tokyo, Tokyo2, Toronto, Washington DC, Zurich</br></br> **New ExpressRoute circuits are no longer supported with Equinix in Los Angeles. Please create new circuits in Los Angeles2.*|
80
+
|**[Equinix](https://www.equinix.com/partners/microsoft-azure/)**|Supported |Supported | Amsterdam, Amsterdam2, Atlanta, Berlin, Bogota, Canberra2, Chicago, Dallas, Dubai2, Dublin, Frankfurt, Frankfurt2, Geneva, Hong Kong SAR, Hong Kong2, London, London2, Los Angeles*, Los Angeles2, Melbourne, Miami, Milan, New York, Osaka, Paris, Paris2, Quebec City, Rio de Janeiro, Sao Paulo, Seattle, Seoul, Silicon Valley, Singapore, Singapore2, Stockholm, Sydney, Tokyo, Tokyo2, Toronto, Washington DC, Zurich</br></br> **New ExpressRoute circuits are no longer supported with Equinix in Los Angeles. Create new circuits in Los Angeles2.*|
82
81
|**Etisalat UAE**|Supported |Supported | Dubai |
83
82
|**[euNetworks](https://eunetworks.com/services/solutions/cloud-connect/microsoft-azure-expressroute/)**|Supported |Supported | Amsterdam, Amsterdam2, Dublin, Frankfurt, London |
@@ -133,7 +132,7 @@ The following table shows locations by service provider. If you want to view ava
133
132
|**[PCCW Global Limited](https://consoleconnect.com/clouds/#azureRegions)**|Supported |Supported | Chicago, Hong Kong, Hong Kong2, London, Singapore2, Tokyo2 |
|**[Retelit](https://www.retelit.it/EN/Home.aspx)**| Supported | Supported | Milan ||
135
+
|**[Retelit](https://www.retelit.it/EN/Home.aspx)**| Supported | Supported | Milan |
137
136
|**SCSK**|Supported |Supported | Tokyo3 |
138
137
|**[Sejong Telecom](https://www.sejongtelecom.net/en/pages/service/cloud_ms)**|Supported |Supported | Seoul |
139
138
|**[SES](https://www.ses.com/networks/signature-solutions/signature-cloud/ses-and-azure-expressroute)**| Supported |Supported | London2, Washington DC |
@@ -172,15 +171,13 @@ The following table shows locations by service provider. If you want to view ava
172
171
|**XL Axiata**| Supported | Supported | Jakarta |
173
172
|**[Zayo](https://www.zayo.com/services/packet/cloudlink/)**|Supported |Supported | Amsterdam, Chicago, Dallas, Denver, Dublin, Hong Kong, London, London2, Los Angeles, Montreal, New York, Paris, Phoenix, San Antonio, Seattle, Silicon Valley, Toronto, Vancouver, Washington DC, Washington DC2, Zurich|
174
173
175
-
**+** denotes coming soon
176
-
177
174
### National cloud environment
178
175
179
-
Azure national clouds are isolated from each other and from global commercial Azure. ExpressRoute for one Azure cloud cannot connect to the Azure regions in the others.
176
+
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.
| Service provider | Microsoft Azure | Office 365 | Locations |
184
181
| --- | --- | --- | --- |
185
182
|**[AT&T NetBond](https://www.synaptic.att.com/clouduser/html/productdetail/ATT_NetBond.htm)**|Supported |Supported |Chicago, Phoenix, Silicon Valley, Washington DC |
186
183
|**[CenturyLink Cloud Connect](https://www.centurylink.com/cloudconnect)**|Supported |Supported |New York, Phoenix, San Antonio, Washington DC |
@@ -192,17 +189,17 @@ Azure national clouds are isolated from each other and from global commercial Az
@@ -213,9 +210,9 @@ To learn more, see [ExpressRoute in China](http://www.windowsazure.cn/home/featu
213
210
214
211
## Connectivity through Exchange providers
215
212
216
-
If your connectivity provider is not listed in previous sections, you can still create a connection.
213
+
If your connectivity provider isn't listed in previous sections, you can still create a connection.
217
214
218
-
* 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.
215
+
* 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.
@@ -233,15 +230,15 @@ If your connectivity provider is not listed in previous sections, you can still
233
230
* Follow steps in [Create an ExpressRoute circuit](expressroute-howto-circuit-classic.md) to set up connectivity.
234
231
235
232
## Connectivity through satellite operators
236
-
If you are remote and do not have fiber connectivity or you want to explore other connectivity options you can check the following satellite operators.
233
+
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.
@@ -324,7 +321,7 @@ If you are remote and do not have fiber connectivity or you want to explore othe
324
321
325
322
## Connectivity through National Research and Education Networks (NREN)
326
323
327
-
|**Provider**|
324
+
| Provider|
328
325
| --- |
329
326
|**AARNET**|
330
327
|**DeIC, through GÉANT**|
@@ -337,12 +334,12 @@ If you are remote and do not have fiber connectivity or you want to explore othe
337
334
|**SINET**|
338
335
|**Surfnet, through GÉANT**|
339
336
340
-
* If your connectivity provider is not listed here, please check to see if they are connected to any of the ExpressRoute Exchange Partners listed above.
337
+
* If your connectivity provider isn't listed here, check to see if they're connected to any of the ExpressRoute Exchange Partners listed above.
341
338
342
339
## ExpressRoute system integrators
343
340
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.
344
341
345
-
|**System integrator**|**Continent**|
342
+
| System integrator | Continent |
346
343
| --- | --- |
347
344
|**[Altogee](https://altogee.be/diensten/express-route/)**| Europe |
348
345
|**[Avanade Inc.](https://www.avanade.com/)**| Asia, Europe, North America, South America |
0 commit comments