Check a VPN Gateway SKU against your throughput and tunnel needs, then cost the gateway and its egress data.
VPN Gateway throughput is an aggregate across every tunnel on the gateway, so ten branches sharing a VpnGw1 share its 650 Mbps rather than each getting it. Tunnel limits step from 10 on Basic to 30 on VpnGw1–3 and 100 on VpnGw4–5, and changing SKU family requires recreating the gateway. A gateway that is one SKU too small shows up as unexplained packet loss during backup windows rather than a clean error, and outbound data through the tunnel is billed at normal internet egress rates — confirm the SKU prices and egress bands for your region in the Azure pricing calculator.
Azure VPN Gateway
Each SKU has a fixed aggregate throughput and tunnel count; monthly = SKU hourly rate × 730 + outbound GB × egress price, with utilisation = required Mbps ÷ SKU throughput.
Each SKU has a fixed aggregate throughput and tunnel count; monthly = SKU hourly rate × 730 + outbound GB × egress price, with utilisation = required Mbps ÷ SKU throughput. VPN Gateway throughput is an aggregate across every tunnel on the gateway, so ten branches sharing a VpnGw1 share its 650 Mbps rather than each getting it. Tunnel limits step from 10 on Basic to 30 on VpnGw1–3 and 100 on VpnGw4–5, and changing SKU family requires recreating the gateway.
A gateway that is one SKU too small shows up as unexplained packet loss during backup windows rather than a clean error, and outbound data through the tunnel is billed at normal internet egress rates — confirm the SKU prices and egress bands for your region in the Azure pricing calculator.
This calculator takes 7 inputs: Gateway SKU, VpnGw1 reference rate, Aggregate throughput required, IPsec tunnels required, Outbound data through the tunnels, Outbound data price per GB, Billed hours per month. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.