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-faqs.md
+20-1Lines changed: 20 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: jaredr80
6
6
7
7
ms.service: expressroute
8
8
ms.topic: conceptual
9
-
ms.date: 05/12/2019
9
+
ms.date: 05/20/2019
10
10
ms.author: jaredro
11
11
ms.custom: seodec18
12
12
@@ -282,6 +282,25 @@ Refer to [pricing details](https://azure.microsoft.com/pricing/details/expressro
282
282
283
283
Yes. ExpressRoute premium charges apply on top of ExpressRoute circuit charges and charges required by the connectivity provider.
284
284
285
+
## ExpressRoute Local
286
+
### What is ExpressRoute Local?
287
+
ExpressRoute Local is a SKU of ExpressRoute circuit. A key feature of Local is that a Local circit at an ExpressRoute peering location gives you access only to one or two Azure regions in or near the same metro. In contrast, a Standard circuit gives you access to all Azure regions in a geopolitical area and a Premium circuit to all Azure regions globally.
288
+
289
+
### What are the benefits of ExpressRoute Local?
290
+
While you need to pay egress data transfer for your Standard or Premium ExpressRoute circuit, you don't pay egress data transfer separately for your ExpressRoute Local circuit. In other words, the price of ExpressRoute Local includes data transfer fees. ExpressRoute Local is a more economical solution if you have massive amount of data to transfer and you can bring your data over a private connection to an ExpressRoute peering location near your desired Azure regions.
291
+
292
+
### What features are available and what are not on ExpressRoute Local?
293
+
Compared to a Standard ExpressRoute circuit, a Local circuit has the same set of features except:
294
+
* scope of access to Azure regions as described above
295
+
* ExpressRoute Global Reach is not available on Local
296
+
ExpressRoute Local also has the same limits on resources (e.g. the number of VNets per circuit) as Standard.
297
+
298
+
### How to configure ExpressRoute Local?
299
+
ExpressRoute Local is available on ExpressRoute Direct only. So first you'll need to configure your ExpressRoute Direct port. Once your Direct port is created you can create a Local circuit following the instructions [here](expressroute-howto-erdirect.md).
300
+
301
+
### Where is ExpressRoute Local available and which Azure regions is each peering location mapped to?
302
+
ExpressRoute Local is available at the peering locations where one or two Azure regions are close-by. It is not available at a peering location where there is no Azure region in that state or province or country. Please see the exact mappings on [the Locations page](expressroute-locations-providers.md).
0 commit comments