An Azure virtual networking service that provides optimized and automated branch-to-branch connectivity.
Your subscription should budget for the Virtual WAN connection’s VNet-side ingress and egress charges, while the subscription containing the customer-managed hub bears the hub deployment and other hub-resident charges; the exact total then depends on whether traffic comes from a branch, another VNet, another region, or a secured hub.
Charges attributable to your subscription
For the VNet in your tenant:
- The VNet itself has no hourly charge.
- A VNet connected to a Virtual WAN hub incurs VNet peering-style per-GB charges when it sends or receives traffic.^1^
- Consequently, traffic:
- From your VNet toward the hub incurs the applicable outbound VNet charge.
- From the hub into your VNet incurs the applicable inbound VNet charge.
- Resources already running in your VNet—VMs, private endpoints, load balancers, public IPs, and similar services—retain their normal independent charges.
The published Virtual Network pricing page confirms that VNet connections are billed by transferred ingress and egress volume; a VNet itself is free.^2^
Cross-tenant attachment is a supported Virtual WAN operation. It changes the identity and permission workflow, but the available pricing documentation does not specify a separate cross-tenant connection surcharge.^3^
Charges attributable to the customer’s hub subscription
Because the customer owns the Virtual WAN and virtual hub, its subscription ordinarily receives the hub-side charges:
- Standard Virtual WAN hub deployment hours
- Standard hub data processing, where applicable
- VPN, ExpressRoute, NVA, routing infrastructure, or connection units used by the hub
- Azure Firewall deployment and processing charges if this is a secured hub
- Inter-hub or inter-region transfer charged on the hub side where traffic leaves a region
These are the cost components listed on the Virtual WAN pricing page.^4^
There is no documented “VNet connection unit” hourly fee comparable to a VPN branch or ExpressRoute connection unit. Connection units apply to on-premises/non-Microsoft endpoints such as branches, remote users, and ExpressRoute circuit connections.^1^
Apply the matching traffic pattern
Customer branch → hub → your VNet
Your side incurs inbound VNet traffic. For VNet-to-branch traffic through the same hub, Standard hub router data-processing charges do not apply; other VPN or ExpressRoute and outbound-transfer charges may still apply on the customer’s side.^1^
Return traffic from your VNet incurs outbound VNet traffic, plus any applicable customer-side branch connectivity charge.
Customer VNet → hub → your VNet, using one hub
This is VNet-to-VNet transit. The pricing model contains:
- Outbound VNet charge at the source
- Inbound VNet charge at the destination
- Standard virtual hub data-processing charge
Microsoft’s same-hub example calculates these as outbound plus inbound VNet charges and hub processing.^1^ Your subscription should therefore expect its direction-specific VNet charge; the customer’s subscriptions receive the source-VNet and hub charges according to resource ownership.
Traffic crosses regions or hubs
Add inter-region transfer for traffic leaving the source hub. Microsoft documents no charge for traffic entering the destination hub, although VNet ingress/egress and hub-processing components can still apply.^1^ Current inter-region rates depend on the source and destination geography.^5^
Traffic targets a private endpoint
Traffic destined for a private endpoint connected through Virtual WAN is excluded from VNet peering charges. It is billed using the Private Link resource’s inbound or outbound data-processing meters instead.^1^
Estimate your monthly amount
For each traffic direction, calculate:
Your monthly network cost =
GB sent from your VNet × applicable VNet outbound rate
+ GB received by your VNet × applicable VNet inbound rate
+ charges for resources owned in your subscription
+ Private Link processing, if the destination is a private endpoint
Use the regions of your VNet and the customer hub, estimated monthly GB in each direction, and whether the destination is a private endpoint. Pricing pages show estimates rather than contractual prices, so use the Azure Pricing Calculator under your own agreement and currency for the final amount.^2^
Cross-tenant connections must be managed through locally installed Azure CLI or PowerShell rather than the portal or portal Cloud Shell. The hub administrator also needs Contributor access to the remote VNet subscription for creation and management.^3^
References