Skip to content

Commit aa8ea25

Browse files
authored
Merge pull request #112642 from cherylmc/patch-1
update links for Next Steps
2 parents 2b3a97b + 6905dc7 commit aa8ea25

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/expressroute/expressroute-global-reach.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: cherylmc
66

77
ms.service: expressroute
88
ms.topic: conceptual
9-
ms.date: 02/20/2020
9+
ms.date: 04/24/2020
1010
ms.author: cherylmc
1111

1212

@@ -48,9 +48,9 @@ ExpressRoute Global Reach currently is supported in the following places.
4848
Your ExpressRoute circuits must be created at the [ExpressRoute peering locations](expressroute-locations.md) in the above countries or region. To enable ExpressRoute Global Reach between [different geopolitical regions](expressroute-locations.md), your circuits must be Premium SKU.
4949

5050
## Next steps
51-
1. [Learn more about ExpressRoute Global Reach](expressroute-faqs.md)
52-
2. [How to enable ExpressRoute Global Reach](expressroute-howto-set-global-reach.md)
53-
3. [Link ExpressRoute circuit to Azure virtual network](expressroute-howto-linkvnet-arm.md)
51+
1. [View the Global Reach FAQ](expressroute-faqs.md#globalreach)
52+
2. [Learn how to enable Global Reach](expressroute-howto-set-global-reach.md)
53+
3. [Learn how to link an ExpressRoute circuit to your virtual network](expressroute-howto-linkvnet-arm.md)
5454

5555

5656
<!--Image References-->

0 commit comments

Comments
 (0)