Skip to content

Commit a631560

Browse files
Merge pull request #300568 from halkazwini/vwan-connect
VWAN connectivity: Introduction tweak
2 parents 5b0079d + 3d444a4 commit a631560

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

articles/virtual-wan/virtual-wan-connectivity.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,21 @@
11
---
2-
title: Virtual WAN to Virtual WAN connectivity
2+
title: Virtual WAN to Virtual WAN Connectivity
33
description: Learn about the different available options for connecting your Azure Virtual WAN to another Virtual WAN.
44
author: halkazwini
55
ms.author: halkazwini
66
ms.service: azure-virtual-wan
7-
ms.topic: how-to
8-
ms.date: 05/08/2025
7+
ms.topic: concept-article
8+
ms.date: 05/29/2025
99
---
1010

1111
# Virtual WAN to Virtual WAN connectivity options
1212

13-
In this article, you learn about the various connection options available to connect multiple Virtual WAN environments.
13+
In some enterprise environments, there might be a need to connect one Azure Virtual WAN to another. Common scenarios include:
14+
15+
- Mergers and acquisitions
16+
- Decentralized business units requiring interconnectivity
17+
18+
In this article, you learn about the various connection options available to link multiple Virtual WAN environments.
1419

1520
## IPsec tunnels using virtual network gateways
1621

@@ -44,7 +49,7 @@ This option is ideal if you want to connect two Virtual WANs using SD-WAN NVAs.
4449

4550
This option is similar to the previous one, except you place the SD-WAN NVA in a spoke virtual network that is peered to the virtual hub, rather than deploying it in the virtual hub. This setup allows you to configure BGP peering between the SD-WAN NVA and the virtual hub route server.
4651

47-
This approach is suitable for scenarios where SD-WAN NVAs can't be deployed into Virtual WAN hubs but still support BGP. As in the second option, you must replace ASNs 65520 and 65515 with those used by your SD-WAN to avoid BGP loop prevention.
52+
This approach is suitable for scenarios where SD-WAN NVAs can't be deployed into Virtual WAN hubs but still support BGP. As in the second option, you must replace ASNs 65520 and 65515 with the ones used by your SD-WAN to avoid BGP loop prevention.
4853

4954
:::image type="content" source="./media/virtual-wan-connectivity/vwan-connectivity-using-spoke-sdwan.png" alt-text="Diagram shows Virtual WAN connectivity using SD-WAN devices in spoke virtual networks." lightbox="./media/virtual-wan-connectivity/vwan-connectivity-using-spoke-sdwan.png":::
5055

0 commit comments

Comments
 (0)