Virtual WAN
Definition
Azure's networking service that provides optimized and automated branch-to-branch connectivity through Azure, improving network performance.
Use Cases
- NTT Ltd.: Managed SD-WAN and branch connectivity to Azure for distributed enterprise customers — Integrated its SD-WAN offering with Azure Virtual WAN so customer branch sites could connect into Virtual WAN hubs using automated provisioning and centralized routing/policy, then reach Azure VNets and shared services through the hub. (Faster branch onboarding and simplified operations by using a cloud-managed hub-and-spoke WAN model instead of building and maintaining many individual site-to-site VPN meshes.)
- VMware: Cloud-based SD-WAN integration for enterprise branch-to-Azure connectivity — Enabled VMware SD-WAN (VeloCloud) integration with Azure Virtual WAN, allowing enterprises to connect branch edges to Virtual WAN hubs and use Azure as a transit for optimized routing to VNets and other sites. (Improved manageability and scalability for multi-branch connectivity by centralizing routing and leveraging automated hub deployment and partner integration.)
- Cisco: Connecting SD-WAN branches to Azure applications with centralized policy — Used Cisco SD-WAN integration with Azure Virtual WAN so branches establish connectivity to Virtual WAN hubs, then route to Azure workloads and shared services with consistent policy and simplified connectivity management. (Reduced complexity compared to maintaining many separate VPN connections and improved consistency of network policy across sites and cloud.)
Provider Equivalents
- AWS: AWS Cloud WAN
- Azure: Azure Virtual WAN
- GCP: Network Connectivity Center
- OCI: OCI Cloud WAN
Frequently Asked Questions
- What's the difference between Azure Virtual WAN and Azure VPN Gateway?
- Azure VPN Gateway is a gateway you deploy in a single virtual network (VNet) to provide VPN connectivity (site-to-site, point-to-site, or VNet-to-VNet). Azure Virtual WAN is a higher-level, managed WAN architecture that uses Virtual WAN hubs to connect many sites and many VNets together, often across regions, with centralized routing, automation, and optional integration with SD-WAN partners. In practice: VPN Gateway is a building block; Virtual WAN is the managed multi-site/multi-VNet connectivity framework that can use VPN gateways inside its hubs.
- When should I use Azure Virtual WAN?
- Use Virtual WAN when you need to connect multiple branch sites and multiple VNets (often across regions) and want centralized routing and simpler operations. It’s a good fit for hub-and-spoke at scale, hybrid networks with many sites, SD-WAN integration, or when you want Azure-managed hubs instead of designing and operating your own transit VNets and routing. If you only have one or a few connections, a standard VPN Gateway or ExpressRoute setup in a single hub VNet may be simpler.
- How much does Azure Virtual WAN cost?
- Pricing depends on several factors: the Virtual WAN hub type (Basic vs Standard), hub hourly charges, data processing/throughput charges through the hub, and the connectivity method (VPN, ExpressRoute, or partner SD-WAN) plus any underlying bandwidth/egress charges. Costs typically increase with the number of hubs, total traffic processed, and the number/type of connections (site-to-site VPN connections, ExpressRoute circuits, inter-hub traffic). For accurate estimates, use Azure Pricing for Virtual WAN and model expected traffic volumes and hub locations.
Category: networking
Difficulty: advanced
Related Terms
See Also