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
Copy file name to clipboardExpand all lines: articles/expressroute/expressroute-locations-providers.md
+41-41Lines changed: 41 additions & 41 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.devlang: na
13
13
ms.topic: conceptual
14
14
ms.tgt_pltfrm: na
15
15
ms.workload: infrastructure-services
16
-
ms.date: 08/14/2019
16
+
ms.date: 08/29/2019
17
17
ms.author: cherylmc
18
18
---
19
19
# ExpressRoute partners and peering locations
@@ -34,7 +34,7 @@ The tables in this article provide information on ExpressRoute geographical cove
34
34
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.
35
35
36
36
## ExpressRoute locations
37
-
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.
37
+
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.
38
38
39
39
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.
40
40
@@ -75,68 +75,68 @@ The following table shows connectivity locations and the service providers for e
|**Marseille**|Interxion | France South | DE-CIX, Interxion, Jaguar Network |
102
+
|**London**|[Equinix LD5](https://www.equinix.com/locations/europe-colocation/united-kingdom-colocation/london-data-centers/ld5/)| UK South | AT&T NetBond, British Telecom, Colt, Equinix, InterCloud, Internet Solutions - Cloud Connect, Interxion, Jisc, Level 3 Communications, Megaport, MTN, NTT Communications, Orange, PCCW Global Limited, Tata Communications, Telehouse - KDDI, Telenor, Telia Carrier, Verizon, Vodafone, Zayo |
103
+
|**London2**|[Telehouse North Two](https://www.telehouse.com/global-data-centers/emea/london-data-centers/telehouse-north-two/)| UK South | IX Reach, Equinix |
|**Newport(Wales)**| Next Generation Data | UK West | British Telecom, Colt, Level 3 Communications, Next Generation Data |
113
-
|**Osaka**| Equinix | Japan West | Colt, Equinix, Internet Initiative Japan Inc. - IIJ, NTT Communications, NTT SmartConnect, Softbank |
114
-
|**Paris**| Interxion | France Central | CenturyLink Cloud Connect, Colt, Equinix, Intercloud, Interxion, Orange, Telia Carrier, Zayo |
113
+
|**Osaka**|[Equinix OS1](https://www.equinix.com/locations/asia-colocation/japan-colocation/osaka-data-centers/os1/)| Japan West | Colt, Equinix, Internet Initiative Japan Inc. - IIJ, NTT Communications, NTT SmartConnect, Softbank |
114
+
|**Paris**|[Interxion PAR5](https://www.interxion.com/Locations/paris/)| France Central | CenturyLink Cloud Connect, Colt, Equinix, Intercloud, Interxion, Orange, Telia Carrier, Zayo |
115
115
|**Perth**| NextDC | n/a | Megaport, NextDC |
116
116
|**Quebec City**| 4Degrees | Canada East | Bell Canada, Megaport |
117
-
|**San Antonio**| CyrusOne | South Central US | CenturyLink Cloud Connect, Megaport |
118
-
|**Sao Paulo**| Equinix | Brazil South | Aryaka Networks, Ascenty Data Centers, British Telecom, Equinix, Level 3 Communications, Neutrona Networks, Orange, Tata Communications, Telefonica, UOLDIVEO |
119
-
|**Seattle**| Equinix | West US 2 | Aryaka Networks, Equinix, Level 3 Communications, Megaport, Telus, Zayo |
117
+
|**San Antonio**|[CyrusOne SA1](https://cyrusone.com/locations/texas/san-antonio-texas/)| South Central US | CenturyLink Cloud Connect, Megaport |
118
+
|**Sao Paulo**|[Equinix SP2](https://www.equinix.com/locations/americas-colocation/brazil-colocation/sao-paulo-data-centers/sp2/)| Brazil South | Aryaka Networks, Ascenty Data Centers, British Telecom, Equinix, Level 3 Communications, Neutrona Networks, Orange, Tata Communications, Telefonica, UOLDIVEO |
119
+
|**Seattle**|[Equinix SE2](https://www.equinix.com/locations/americas-colocation/united-states-colocation/seattle-data-centers/se2/)| West US 2 | Aryaka Networks, Equinix, Level 3 Communications, Megaport, Telus, Zayo |
120
120
|**Seoul**| KINX | Korea Central | KINX, LG CNS, Sejong Telecom |
121
-
|**Silicon Valley**| Equinix | West US | Aryaka Networks, AT&T NetBond, British Telecom, CenturyLink Cloud Connect, Comcast, Coresite, Equinix, InterCloud, Internet2, IX Reach, Packet, PacketFabric, Level 3 Communications, Megaport, Orange, Sprint, Tata Communications, Telia Carrier, Verizon, Zayo |
122
-
|**Silicon Valley2**| Coresite | West US | Coresite |
|**Tokyo**|[Equinix TY4](https://www.equinix.com/locations/asia-colocation/japan-colocation/tokyo-data-centers/ty4/)| Japan East | Aryaka Networks, AT&T NetBond, British Telecom, CenturyLink Cloud Connect, Colt, Equinix, Internet Initiative Japan Inc. - IIJ, NTT Communications, NTT EAST, Orange, Softbank, Verizon |
129
+
|**Toronto**|[Cologix TOR1](https://www.cologix.com/data-centers/toronto/tor1/)| Canada Central | AT&T NetBond, Bell Canada, CenturyLink Cloud Connect, Cologix, Equinix, IX Reach Megaport, Telus, Verizon, Zayo |
|**Washington DC2**|[Coresite Reston](https://www.coresite.com/data-centers/locations/northern-virginia-washington-dc/reston-campus)| East US, East US 2 |Coresite |
@@ -158,12 +158,12 @@ The following table shows connectivity locations and the service providers for e
158
158
To learn more, see [ExpressRoute in China](http://www.windowsazure.cn/home/features/expressroute/)
159
159
160
160
### Germany
161
-
|**Location**|**Service Providers**|
161
+
|**Location**|**Service providers**|
162
162
| --- | --- |
163
163
|**Berlin**|e-shelter, Megaport+, T-Systems |
164
164
|**Frankfurt**|Colt, Equinix, Interxion |
165
165
166
-
## <aname="c1partners"></a>Connectivity Through Exchange Providers
166
+
## <aname="c1partners"></a>Connectivity through Exchange providers
167
167
If your connectivity provider is not listed in previous sections, you can still create a connection.
168
168
169
169
* 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.
@@ -180,8 +180,8 @@ If your connectivity provider is not listed in previous sections, you can still
180
180
* Order an ExpressRoute circuit with the exchange as your connectivity provider to connect to Microsoft.
181
181
* Follow steps in [Create an ExpressRoute circuit](expressroute-howto-circuit-classic.md) to set up connectivity.
182
182
183
-
## <aname="c1partners"></a>Connectivity Through Additional Service Providers
0 commit comments