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
+9-13Lines changed: 9 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,15 @@
1
1
---
2
-
title: 'Locations and connectivity providers: 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 location.
2
+
title: 'Locations and connectivity providers: Azure ExpressRoute'
3
+
description: This article provides a detailed overview of locations where services are offered and how to connect to Azure regions.
@@ -23,7 +22,6 @@ The tables in this article provide information on ExpressRoute geographical cove
23
22
> [!Note]
24
23
> 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
24
>
26
-
>
27
25
28
26
## Azure regions
29
27
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.
@@ -39,11 +37,11 @@ You will have access to Azure services across all regions within a geopolitical
39
37
40
38
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](expressroute-locations.md).
41
39
42
-
***Local Azure Regions**are the ones that [ExpressRoute Local](expressroute-faqs.md) at each peering location can access. **n/a** indicates that ExpressRoute Local is not available at that peering location.
40
+
***Local Azure Regions**refers to the regions that can be accessed by [ExpressRoute Local](expressroute-faqs.md#expressroute-local) at each peering location. **n/a** indicates that ExpressRoute Local is not available at that peering location.
43
41
44
42
***Zone** refers to [pricing](https://azure.microsoft.com/pricing/details/expressroute/).
45
43
46
-
***ER Direct** refers to [ExpressRoute Direct](expressroute-erdirect-about.md) support at each peering location. If you want to view the available bandwidth see [Determine available bandwidth](expressroute-howto-erdirect.md#resources)
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)
0 commit comments