Skip to content

Commit d78cc4b

Browse files
authored
Private Peering Update
Specifically define that Global Reach connectivity is established between the private peerings of two expressroute circuits
1 parent c7b0a71 commit d78cc4b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/expressroute/expressroute-howto-set-global-reach.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Before you start configuration, confirm the following:
3535
1. To start the configuration, sign in to your Azure account and select the subscription that you want to use.
3636

3737
[!INCLUDE [sign in](../../includes/expressroute-cloud-shell-connect.md)]
38-
2. Identify the ExpressRoute circuits that you want use. You can enable ExpressRoute Global Reach between any two ExpressRoute circuits as long as they're located in the supported countries/regions and were created at different peering locations.
38+
2. Identify the ExpressRoute circuits that you want use. You can enable ExpressRoute Global Reach between the private peerings of any two ExpressRoute circuits, as long as they're located in the supported countries/regions and were created at different peering locations.
3939

4040
* If your subscription owns both circuits, you can choose either circuit to run the configuration in the following sections.
4141
* If the two circuits are in different Azure subscriptions, you need authorization from one Azure subscription. Then you pass in the authorization key when you run the configuration command in the other Azure subscription.

0 commit comments

Comments
 (0)