
Introduction
An Azure Virtual Network Gateway gives you managed connectivity between an Azure virtual network and other networks. Its cost is separate from the virtual network itself. Creating a VNet is free. Deploying a gateway in it is not.
Your total spend depends on gateway type, SKU, region, availability design, data transfer, tunnel or client counts, and related resources. Teams often budget for traffic and miss the hourly gateway charge entirely.
This guide covers current US pricing, recurring and usage-based charges, cost drivers, a budgeting process, and common mistakes. Rates in this guide reflect Microsoft pricing as of November 18, 2026. Confirm every rate against Microsoft's pricing page and the Azure Pricing Calculator before you commit.
Key Takeaways
- Expect an hourly gateway charge plus data transfer, connection, public IP, logging, and ExpressRoute costs.
- SKU and connectivity model drive most of the bill.
- Basic and low-tier SKUs fit dev, test, and modest workloads.
- Pick the lowest SKU that meets throughput, availability, and compliance needs.
How Much Does Azure Virtual Network Gateway Cost? (Pricing Overview)
There is no single price. VPN Gateway and ExpressRoute Gateway use different models, and rates vary by SKU, region, and configuration.
Three misunderstandings cause most budget surprises:
- Assuming the VNet includes the gateway at no extra cost
- Comparing a VPN Gateway to an ExpressRoute gateway while ignoring the circuit and connectivity provider
- Budgeting for traffic only and overlooking the recurring hourly charge
Typical Cost Range
Microsoft's VPN Gateway pricing page shows East US rates from $0.04 per hour for Basic up to $4.02 per hour for VpnGw5AZ. Monthly figures assume 730 hours.
| SKU | Hourly | Monthly (730 hrs) |
|---|---|---|
| Basic | $0.04 | $26.28 |
| VpnGw1 | $0.19 | $138.70 |
| VpnGw2 | $0.49 | $357.70 |
| VpnGw3 | $1.25 | $912.50 |
| VpnGw1AZ | $0.21 | $153.30 |
| VpnGw2AZ | $0.54 | $394.20 |
| VpnGw5AZ | $4.02 | $2,934.60 |

These East US estimates reflect rates as of November 18, 2026. Microsoft stopped allowing new non-AZ VpnGw1-5 deployments on November 1, 2025, so new builds should plan on AZ SKUs. Basic is not retiring.
The gateway line excludes data transfer, public IPs, logging, point-to-site overages, ExpressRoute circuits, and provider fees.
Price Range 1: Entry-Level or Development Configuration
Basic is the floor at roughly $26 a month. It supports 100 Mbps aggregate throughput and up to 10 route-based site-to-site tunnels.
It has no BGP, active-active, OpenVPN, RADIUS, or IPv6 support, and policy-based Basic allows one tunnel and no point-to-site.
Microsoft recommends Basic for dev-test and proof-of-concept work, not production. Use it for labs and pilots. Don't put a workload with strict availability or performance needs on it.
Price Range 2: Standard Production VPN Gateway
VpnGw1 through VpnGw3 (and their AZ versions) cover most small and medium production needs, from about $139 to $1,007 a month. Aggregate throughput runs from 650 Mbps to 2.5 Gbps depending on SKU and generation, with up to 30 site-to-site tunnels. They support BGP and active-active.
Good fits: branch connectivity, hybrid applications, and remote-user access without a dedicated circuit. Remember that aggregate throughput is a benchmark. A single connection can achieve far less.
Price Range 3: High-Capacity, Zone-Redundant, or ExpressRoute-Based Design
VpnGw4 and VpnGw5 (and AZ variants) reach 5 to 10 Gbps and up to 100 tunnels, at roughly $1,533 to $2,935 a month. ExpressRoute gateways run separately:
| ExpressRoute gateway | Hourly (East US) |
|---|---|
| Standard | $0.19 |
| High Performance | $0.49 |
| Ultra Performance | $1.87 |
| ErGw1AZ | $0.361 |
| ErGw2AZ | $0.632 |
| ErGw3AZ | $2.151 |
This is the Azure-side gateway charge only. The circuit has its own port fee, metered or unlimited data plan, and often a provider charge. Neither an unlimited plan nor a provider contract removes the gateway fee.
Choose this tier for high-throughput, mission-critical, multi-region, or compliance-sensitive workloads.
Key Factors That Affect the Cost of Azure Virtual Network Gateway
Gateway Type and Connectivity Model
VPN Gateway sends encrypted IPsec/IKE traffic over the public internet. You pay hourly SKU compute plus egress. ExpressRoute Gateway exchanges routes and traffic over private connectivity, so you pay the hourly gateway plus the circuit and provider.
SKU, Throughput, and Connection Capacity
The SKU sets hourly price, aggregate throughput, tunnel limits, and feature support. Upgrade paths are limited:
- Basic cannot be upgraded in place
- Same-generation upgrades are supported
- Gen1 to Gen2 AZ is a migration
- ExpressRoute upgrades stay within the same SKU family
Anything else means deleting and recreating the gateway, with downtime.
Region and Availability Design
East US, Central US, and West US 2 list identical VpnGw1AZ, VpnGw2AZ, and VpnGw5AZ rates. Confirm pricing for your actual region and agreement, since not every US region matches those figures.
Active-active carries the same gateway charge as active-standby, but requires two Standard static public IPs instead of one. Enabling point-to-site on active-active needs a third.
Data Transfer and Connection Usage
- Inbound data is free
- Same-region VNet-to-VNet over VPN is free in both directions
- Cross-region VNet-to-VNet bills egress at $0.035/GB from Zone 1, which includes the named US regions
- Internet egress from North America: first 100 GB per month free, then $0.087/GB up to 10 TB

Architecture and Related Resources
Related resources add separate line items:
- Standard static IPv4 costs $0.005 per IP-hour, billed whether or not the attached resource is busy
- Diagnostic logs add cost only once you route them somewhere
- Log Analytics in East US costs $2.30/GB, with the first 5 GB per month per billing account free
- On-premises VPN devices, ExpressRoute circuits, and provider fees sit outside Azure's gateway line
Azure Virtual Network Gateway Cost Breakdown: Low-Cost vs High-Cost Setups
Gateway Compute Charges
Recurring. VPN billing is based on provisioned availability, not traffic, and partial hours bill as full hours. Monthly estimate: hourly rate × hours deployed. A VpnGw1AZ running 730 hours costs $0.21 × 730, or about $153.30.
Data Transfer Charges
Recurring and usage-based. Use this framework: monthly GB × applicable rate, with free paths (inbound, same-region VNet-to-VNet) at zero.
For example, 2 TB (about 2,000 GB) of cross-region VNet-to-VNet egress at $0.035/GB is roughly $70. Use your own workload volume, not a universal figure.

Point-to-Site and Connection-Related Charges
Recurring or usage-based. The first 10 site-to-site tunnels and 128 point-to-site connections are included. Beyond that:
- Site-to-site tunnels 11 and up: $0.015 per tunnel-hour (up to 30 on VpnGw1-3, up to 100 on VpnGw4-5)
- Point-to-site connections 129 and up: $0.01 per connection-hour
User count, session length, and full-tunnel versus split-tunnel routing all change the total. Full-tunnel sends all user traffic through Azure, raising egress.
Supporting Infrastructure and Operational Costs
| Item | Status |
|---|---|
| Gateway runtime | Required |
| Standard public IP(s) | Required, extra for active-active |
| Diagnostic logging | Optional |
| On-premises VPN device | Architecture-dependent |
| ExpressRoute circuit and provider | Architecture-dependent |
The gateway is rarely the whole hybrid connectivity bill.
Low-Cost vs High-Cost Gateway Designs
Lower-cost setups usually mean:
- Basic or VpnGw1 SKUs
- Few tunnels and standard availability
- Light traffic volumes
They are simple to run, with limited headroom.
Higher-cost setups usually mean:
- VpnGw4/5 or AZ SKUs
- Active-active or multi-region deployment
- Heavy traffic, often with ExpressRoute
You get more resilience and throughput, and more to manage.
Pay more when downtime risk, performance, compliance, or continuity demands it. Don't pay for capacity that sits unused.
How to Estimate the Right Budget for Azure Virtual Network Gateway and Avoid Common Mistakes
Follow this process:
- Define the pattern: site-to-site, point-to-site, VNet-to-VNet, ExpressRoute, or multi-region.
- Record inputs: US region, gateway type, SKU, hours, throughput, tunnels, P2S concurrency, outbound volume, redundancy, and monitoring.
- Split line items: gateway hours, data transfer, connection charges, public IPs, logging, and circuit or provider costs.
- Model three scenarios: low, expected, and peak traffic.
- Compare options: the lowest suitable SKU against a resilient alternative.

In the calculator, use the VPN Gateway module for gateway hours (Microsoft's example uses 720 hours for 30 days) and the ExpressRoute module for circuits.
Common mistakes:
- Ignoring idle charges. A retained ExpressRoute gateway keeps billing after you delete its circuit.
- Using internet egress assumptions for cross-region traffic
- Assuming Basic works for production
- Skipping resize constraints. Basic can't be upgraded in place.
- Forgetting extra public IPs for active-active
If you're reviewing the whole Azure bill, gateway charges are separate from block storage. Lucidity's AutoScaler supports Azure, AWS, and Google Cloud and can cut cloud block storage costs by up to 70%. It doesn't change Azure Virtual Network Gateway pricing, but it addresses a different line on the same invoice.
Conclusion
Gateway type, SKU, region, usage, resilience model, and related resources set the price, not one universal rate. A reliable budget separates fixed gateway charges from data transfer and architecture-dependent costs. Use those figures to match the design to real performance, availability, and business needs.
Frequently Asked Questions
How much does Azure virtual network cost?
Creating the VNet is free. The Virtual Network Gateway is billed separately, along with data transfer and public IPs. Check Microsoft's US pricing pages for current rates.
How much does an Azure VPN Gateway cost?
It bills hourly by SKU. In East US that ranges from $0.04 (Basic) to $4.02 (VpnGw5AZ), plus data transfer and connection charges. Exact cost depends on SKU and region.
What is the difference between Azure Virtual Network and Virtual Network Gateway pricing?
A VNet is the private network holding your resources. The gateway connects it to other networks or users. Budget for gateway hours, egress, extra tunnels or connections, public IPs, and logging.
Does Azure VPN Gateway charge when idle?
Yes. VPN billing is based on provisioned, available time, not traffic. Only data transfer and connection meters vary with usage.
Which factors affect Azure Virtual Network Gateway pricing?
Gateway type, SKU, region, throughput, tunnel or client counts, data transfer, zone redundancy, active-active design, and supporting resources such as public IPs, logs, and circuits.
How can I estimate Azure Virtual Network Gateway costs?
List your workload inputs, then use the Azure Pricing Calculator with separate lines for gateway hours, transfer, connections, IPs, and logging. Add ExpressRoute circuit and provider costs where relevant, and verify against Microsoft's pricing pages.