Skip to content

Latest commit

 

History

History
100 lines (60 loc) · 6.6 KB

about-gateway-skus.md

File metadata and controls

100 lines (60 loc) · 6.6 KB
Raw
title description author ms.service ms.topic ms.date ms.author
About gateway SKUs
Learn about VPN Gateway SKUs.
cherylmc
vpn-gateway
conceptual
01/23/2024
cherylmc

About gateway SKUs

When you create a VPN Gateway virtual network gateway, you specify the gateway SKU that you want to use. This article describes the factors that you should take into consideration when selecting a gateway SKU. If you're looking for information about ExpressRoute gateway SKUs, see Virtual network gateways for ExpressRoute. For Virtual WAN gateways, see Virtual WAN gateway settings.

When you configure a virtual network gateway SKU, select the SKU that satisfies your requirements based on the types of workloads, throughput, features, and SLAs. The following sections show the relevant information that you should use when deciding.

Gateway SKUs by tunnel, connection, and throughput

[!INCLUDE Aggregated throughput by SKU]

(*) If you need more than 100 S2S VPN tunnels, use Virtual WAN instead of VPN Gateway.

Additional information

  • Because Basic SKU public IP addresses are announced to retire September 30, 2025, we're no longer permitting new gateways to be created using Basic SKU public IP addresses. Starting December 1, 2023, when you create a new VPN gateway, you must use a Standard SKU public IP address. This limitation doesn't apply to new gateways that you create using the VPN Gateway Basic gateway SKU. You can still create a Basic SKU VPN gateway that uses a Basic SKU public IP address.

  • The Basic gateway SKU doesn't support IPv6 and can only be configured using PowerShell or Azure CLI. Additionally, the Basic gateway SKU doesn't support RADIUS authentication.

  • These connection limits are separate. For example, you can have 128 SSTP connections and also 250 IKEv2 connections on a VpnGw1 SKU.

  • If you have numerous P2S connections, it can negatively impact your S2S connections. The Aggregate Throughput Benchmarks were tested by maximizing a combination of S2S and P2S connections. A single P2S or S2S connection can have a much lower throughput.

  • See the Pricing page for pricing information.

  • See the SLA page for SLA (Service Level Agreement) information.

  • All benchmarks aren't guaranteed due to Internet traffic conditions and your application behaviors.

Gateway SKUs by performance

[!INCLUDE Performance by SKU]

Gateway SKUs by feature set

SKU Features
Basic (**) Route-based VPN: 10 tunnels for S2S/connections; no RADIUS authentication for P2S; no IKEv2 for P2S
Policy-based VPN: (IKEv1): 1 S2S/connection tunnel; no P2S
All Generation1 and Generation2 SKUs except Basic Route-based VPN: up to 100 tunnels (*), P2S, BGP, active-active, custom IPsec/IKE policy, ExpressRoute/VPN coexistence

(*) You can configure "PolicyBasedTrafficSelectors" to connect a route-based VPN gateway to multiple on-premises policy-based firewall devices. Refer to Connect VPN gateways to multiple on-premises policy-based VPN devices using PowerShell for details.

(**) The Basic SKU is considered a legacy SKU. The Basic SKU has certain feature and performance limitations and should not be used for production purposes. Verify that the feature that you need is supported before you use the Basic SKU. The Basic SKU doesn't support IPv6 and can only be configured using PowerShell or Azure CLI. Additionally, the Basic SKU doesn't support RADIUS authentication.

Gateway SKUs - Production vs. Dev-Test workloads

Due to the differences in SLAs and feature sets, we recommend the following SKUs for production vs. dev-test:

Workload SKUs
Production, critical workloads All Generation1 and Generation2 SKUs, except Basic
Dev-test or proof of concept Basic (**)

(**) The Basic SKU is considered a legacy SKU. The Basic SKU has certain feature and performance limitations and should not be used for production purposes. Verify that the feature that you need is supported before you use the Basic SKU. The Basic SKU doesn't support IPv6 and can only be configured using PowerShell or Azure CLI. Additionally, the Basic SKU doesn't support RADIUS authentication.

If you're using the old SKUs (legacy), the production SKU recommendations are Standard and HighPerformance. For information and instructions for old SKUs, see Gateway SKUs (legacy).

About legacy SKUs

For information about working with the legacy gateway SKUs (Basic, Standard, and High Performance), including SKU deprecation, see Managing legacy gateway SKUs.

Specify a SKU

You specify the gateway SKU when you create your VPN Gateway. See the following article for steps:

Change or resize a SKU

Note

If you're working with a legacy gateway SKU (Basic, Standard, and High Performance), see Managing Legacy gateway SKUs.

[!INCLUDE changing vs. resizing]

Considerations

There are many things to consider when moving to a new gateway SKU. This section outlines the main items and also provides a table that helps you select the best method to use.

[!INCLUDE resize SKU restrictions]

The following table helps you understand the required method to move from one SKU to another.

[!INCLUDE resize SKU methods table]

Next steps

For more information about available connection configurations, see About VPN Gateway.