What characterizes the branch-to-branch topology in an Azure virtual WAN?

In Azure Virtual WAN, enabling branch-to-branch connectivity lets every site build only a single

VPN/ExpressRoute link to its regional Virtual WAN hub. Azure then automatically provides

any-to-any traffic flow across Microsoft’s backbone, so additional branches can be on-boarded

without creating new peerings or tunnels between existing sites. This managed, cloud-transit

model therefore chiefly distinguishes itself by giving very large and rapidly growing branch

footprints the ability to scale simply and quickly.

A. Concerns hub redundancy; branch-to-branch is about inter-site scale, not multiple hub links.

B. Centralized security (e.g., Azure Firewall) is a hub feature, not the defining trait of

branch-to-branch.

C. Architecture is simplified, but reliance on hubs is not reduced—traffic still transits the hub, so

statement is inaccurate.

1. Microsoft Learn – “About Azure Virtual WAN,” section “Branch-to-branch traffic flows”

https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about

2. Microsoft Learn – “Azure Virtual WAN design considerations,” subsection “Scalability benefits of

branch-to-branch connectivity”

https://learn.microsoft.com/en-us/azure/virtual-wan/design-guide#branch-to-branch-scalability