Skip to content

Commit a364f44

Browse files
Merge pull request #268947 from halkazwini/rs-multi
Freshness
2 parents f777863 + e7a261b commit a364f44

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

articles/route-server/multiregion.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,12 @@ title: Multi-region designs with Azure Route Server
33
description: Learn how Azure Route Server enables multi-region designs.
44
services: route-server
55
author: halkazwini
6-
ms.service: route-server
7-
ms.topic: conceptual
8-
ms.date: 03/31/2023
96
ms.author: halkazwini
10-
ms.custom: template-concept, engagement-fy23
7+
ms.service: route-server
8+
ms.topic: concept-article
9+
ms.date: 03/13/2024
10+
11+
#CustomerIntent: As an Azure administrator, I want to use Azure Route Server in a multi-region topology where I have hub and spokes in each region and the Route Server exchange routes with NVAs and dynamically adapt to any topology changes.
1112
---
1213

1314
# Multi-region networking with Azure Route Server
@@ -45,7 +46,7 @@ The cross-region tunnels between the NVAs are required because otherwise a routi
4546

4647
If UDRs are an option, you could disable BGP route propagation in the NVAs' subnets, and configure static UDRs instead of an overlay, so that Azure can route traffic to the remote spoke VNets.
4748

48-
## Next steps
49+
## Related content
4950

50-
* Learn more about [Azure Route Server support for ExpressRoute and Azure VPN](expressroute-vpn-support.md)
51-
* Learn how to [Configure peering between Azure Route Server and network virtual appliance](tutorial-configure-route-server-with-quagga.md)
51+
- Learn more about [Azure Route Server support for ExpressRoute and Azure VPN](expressroute-vpn-support.md).
52+
- Learn how to [Configure peering between Azure Route Server and network virtual appliance](tutorial-configure-route-server-with-quagga.md).

0 commit comments

Comments
 (0)