Azure vWAN hub connection pricing

Srivatsa J 0 Reputation points
2026-11-20T08:01:50.05+00:00

We have an Azure VNet in our subscription. A customer has an Azure Virtual WAN hub in their own subscription and tenant. We create a cross-tenant hub virtual network connection from their vWAN hub to our VNet, with the connection resource residing in the customer's subscription.

What charges are incurred by our subscription for this architecture, specifically:

  1. Is there an hourly charge for the cross-tenant hub virtual network connection?
  2. Are VNet peering/data-transfer charges incurred on both our VNet and customer VNet sides?
  3. Is traffic processed by the customer's vWAN hub charged only to the customer?
  4. What are the applicable inbound and outbound data-transfer charges for traffic between the two VNets?
  5. Are there any additional charges specifically associated with cross-tenant VNet-to-vWAN hub connectivity?

Referred these links but unsure if its applicable to our usecase:

https://azure.microsoft.com/en-gb/pricing/details/virtual-network/

https://azure.microsoft.com/en-gb/pricing/details/virtual-wan/

Azure Virtual WAN
Azure Virtual WAN

An Azure virtual networking service that provides optimized and automated branch-to-branch connectivity.


1 answer

Sort by: Newest
  1. Eber Daniel Perez 165 Reputation points
    2026-11-20T15:54:47.6966667+00:00

    Hi Srivatsa,

    Short version: there's no extra charge just because the connection is cross-tenant. You pay for your VNet's traffic, the customer pays for their hub. Here's how it breaks down:

    1. Hourly charge for the hub virtual network connection: no. In Virtual WAN, connection units only apply to on-premises/non-Microsoft endpoints (S2S branches, P2S users, ExpressRoute circuits). A VNet connection isn't one of them. The hourly costs (Standard hub deployment hour, gateway scale units, routing infrastructure units) belong to the hub, so they're billed in the customer's subscription.
    2. VNet peering charges: yes, on your side. The docs say peering charges apply when a VNet connected to a vWAN hub sends or receives data. So your VNet pays peering outbound for what it sends and peering inbound for what it receives. The customer's spoke VNets pay their own peering the same way.
    3. Hub data processing: this applies to VNet-to-VNet transit through a Standard hub, and it's charged on the hub router, so it lands with the hub owner (the customer). It doesn't apply to VNet-to-branch traffic through the same hub.
    4. Inbound/outbound between the two VNets: if both VNets and the hub are in the same region, a VNet-to-VNet flow is basically peering out (source VNet) + hub data processing + peering in (destination VNet). That's scenario 5 in the pricing doc. If the hub and your VNet are in different regions, add inter-region data transfer for the traffic leaving the hub.
    5. Anything specific to cross-tenant: I don't see any cross-tenant surcharge in the Virtual WAN or Virtual Network pricing docs. The cross-tenant setup is just about permissions (Contributor on your VNet subscription for the hub admin) and it's managed via PowerShell/CLI only.

    One exception worth knowing: traffic to private endpoints in a VNet connected to the hub doesn't pay peering, it's billed as Private Link data processing instead.

    The docs don't spell out invoice attribution for the cross-tenant case specifically, so I'd confirm it with Cost Analysis in your subscription after a few days of traffic (filter by your VNet and look at the VNet Peering meters).

    Docs:

    Hope this helps!

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.