Connection Cost in Azure Virtual WAN

Understanding the cost structure of Virtual WAN connections helps you design cost‑effective, high‑performance network topologies. This page outlines the primary components that contribute to connection costs, explains billing metrics, and provides guidance on optimizing spend.

Cost Components

ComponentDescriptionPricing Model
Hub‑to‑Hub Transfer Data transferred between hubs in the same Virtual WAN. Per GB outbound traffic
Branch‑to‑Hub Connection Traffic between on‑premises sites (branch VPN) and the hub. Per GB inbound/outbound traffic
Site‑to‑Site (S2S) VPN Standard IPsec VPN tunnels to the hub. Fixed hourly charge per tunnel + data usage
ExpressRoute to Hub Private dedicated connectivity from an ExpressRoute circuit to a hub. Metered data (per GB) or Unlimited (fixed fee)
Hub‑to‑VNet Peering Traffic between the hub and peered VNets. Per GB VNet inbound/outbound traffic
Data Processing (Security, Acceleration) Optional services like Azure Firewall, Azure DDoS, and WAN Optimizer. Service‑specific hourly rates

Billing Metrics

Cost‑Optimization Tips

  1. Consolidate hubs where possible to reduce hub‑to‑hub traffic.
  2. Enable traffic steering to route high‑volume workloads through ExpressRoute (metered) instead of VPN.
  3. Use Azure Cost Management alerts to monitor unexpected spikes.
  4. Evaluate unlimited data plans for ExpressRoute if your traffic regularly exceeds 5 TB/month.
  5. Leverage Azure Firewall Manager policies to avoid redundant security services.

Sample Pricing (USD, East US)

ComponentRateNotes
Hub‑to‑Hub Transfer$0.02/GBTiered after 10 TB
Branch‑to‑Hub (VPN)$0.008/GBIncludes 1 GB free per month per tunnel
VPN Tunnel$0.025/hrPer active tunnel
ExpressRoute (Metered)$0.025/GBUnlimited option available
Hub‑to‑VNet Peering$0.01/GBBoth inbound & outbound
Azure Firewall$1.25/hrPlus data processing fee
All rates are subject to change. Verify current pricing on the Azure Pricing Calculator.