Skip to content

Commit d9ca7c7

Browse files
authored
Merge pull request #113784 from skishen525/patch-31
Update virtual-wan-global-transit-network-architecture.md
2 parents 1f952fc + 7bebbd0 commit d9ca7c7

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/virtual-wan/virtual-wan-global-transit-network-architecture.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,11 @@ Branches can be connected to an Azure virtual WAN hub using ExpressRoute circuit
9696

9797
This option lets enterprises leverage the Azure backbone to connect branches. However, even though this capability is available, you should weigh the benefits of connecting branches over Azure Virtual WAN vs. using a private WAN.
9898

99+
### Disabling Branch-to-Branch Connectivity in Virtual WAN
100+
Virtual WAN can be configured to disable Branch-to-Branch connectivity. This configuation will block route propagation between VPN (S2S and P2S) and Express Route connected sites. This configuration will not affect branch-to-Vnet and Vnet-to-Vnet route propogation and connectivity.
101+
102+
In the Azure Portal, under Virtual WAN Configuration menu, Choose Setting: Branch-to-Branch -> Disabled.
103+
99104
### Remote User-to-VNet (c)
100105

101106
You can enable direct, secure remote access to Azure using point-to-site connection from a remote user client to a virtual WAN. Enterprise remote users no longer have to hairpin to the cloud using a corporate VPN.

0 commit comments

Comments
 (0)