Skip to content

Latest commit

 

History

History
118 lines (71 loc) · 6.9 KB

vpn-gateway-about-skus-legacy.md

File metadata and controls

118 lines (71 loc) · 6.9 KB
Raw
title description author ms.service ms.topic ms.date ms.author
VPN Gateway legacy SKUs
How to work with the old virtual network gateway SKUs; Standard, and High Performance.
cherylmc
azure-vpn-gateway
how-to
08/06/2024
cherylmc

Working with VPN Gateway legacy SKUs

This article contains information about the legacy (old) virtual network gateway SKUs. The legacy SKUs still work in both deployment models for VPN gateways that have already been created. Classic VPN gateways continue to use the legacy SKUs, both for existing gateways, and for new gateways. When creating new Resource Manager VPN gateways, use the new gateway SKUs. For information about the new SKUs, see About VPN Gateway.

Legacy gateway SKUs

[!INCLUDE Legacy gateway SKUs]

You can view legacy gateway pricing in the Virtual Network Gateways section, which is located on the ExpressRoute pricing page.

For SKU deprecation, see the SKU deprecation and SKU deprecation FAQs sections of this article.

Estimated aggregate throughput by SKU

The following table shows the gateway types and the estimated aggregate throughput by gateway SKU. This table applies to the Resource Manager and classic deployment models.

Pricing differs between gateway SKUs. For more information, see VPN Gateway Pricing.

The UltraPerformance gateway SKU isn't represented in this table. For information about the UltraPerformance SKU, see the ExpressRoute documentation.

VPN Gateway throughput (1) VPN Gateway max IPsec tunnels (2) ExpressRoute Gateway throughput VPN Gateway and ExpressRoute coexist
Standard SKU (3)(4) 100 Mbps 10 1000 Mbps Yes
High Performance SKU (3) 200 Mbps 30 2000 Mbps Yes

(1) The VPN throughput is a rough estimate based on the measurements between VNets in the same Azure region. It isn't a guaranteed throughput for cross-premises connections across the Internet. It's the maximum possible throughput measurement.

(2) The number of tunnels refer to RouteBased VPNs. A PolicyBased VPN can only support one Site-to-Site VPN tunnel.

(3) PolicyBased VPNs aren't supported for this SKU. They're supported for the Basic SKU.

(4) Active-active S2S VPN Gateway connections aren't supported for this SKU. Active-active is supported on the HighPerformance SKU.

Supported configurations by SKU and VPN type

[!INCLUDE Table requirements for old SKUs]

Resize, migrate, and change SKUs

Resize a gateway SKU

Resizing a gateway SKU incurs less downtime and fewer configuration changes than the process to change to a new SKU. However, there are limitations. You can only resize your gateway to a gateway SKU within the same SKU family (except for the Basic SKU).

For example, if you have a Standard SKU, you can resize to a High Performance SKU. However, you can't resize your VPN gateway between the old SKUs and the new SKU families. You can't go from a Standard SKU to a VpnGw2 SKU, or from a Basic SKU to VpnGw1 by resizing. For more information, see Resize a gateway SKU.

Resource Manager

You can resize a gateway for the Resource Manager deployment model using the Azure portal or PowerShell. For PowerShell, use the following command:

$gw = Get-AzVirtualNetworkGateway -Name vnetgw1 -ResourceGroupName testrg
Resize-AzVirtualNetworkGateway -VirtualNetworkGateway $gw -GatewaySku HighPerformance

Classic

To resize a gateway for the classic deployment model, you must use the Service Management PowerShell cmdlets. Use the following command:

Resize-AzureVirtualNetworkGateway -GatewayId <Gateway ID> -GatewaySKU HighPerformance

Migrate a gateway SKU

A gateway SKU migration process is similar to a resize. It requires fewer steps and configuration changes than changing to a new gateway SKU. At this time, gateway SKU migration isn't available. You can migrate a deprecated legacy gateway SKU December 2024 through September 30, 2025. We'll make a migration path available along with detailed documentation.

Change to the new gateway SKUs

Standard and High Performance SKUs will be deprecated September 30, 2025. The product team will make a migration path available for legacy SKUs. See the Legacy SKU deprecation section for more information. You can choose to change from a legacy SKU to one of the new SKUs at any point. However, changing to a new SKU requires more steps than migrating and incurs more downtime.

[!INCLUDE Change to the new SKUs]

SKU deprecation

The Standard and High Performance SKUs will be deprecated on September 30, 2025. The product team will make a migration path available for these SKUs by November 30, 2024. At this time, there's no action that you need to take.

When the migration path becomes available, you can migrate your legacy SKUs to the following SKUs:

  • Standard SKU: -> VpnGw1
  • High Performance SKU: -> VpnGw2

There are no price changes if you migrate to Standard (VpnGw1) and High Performance (VpnGw2) gateways. As a benefit, there's a performance improvement after migrating:

  • Standard SKU: 6.5x
  • High Performance SKU: 5x

If you don't migrate your gateway SKUs by September 30, 2025, your gateway will be automatically migrated and upgraded to an AZ gateway SKU:

  • Standard SKU: -> VpnGw1AZ
  • High Performance SKU: -> VpnGw2AZ

Important Dates:

  • December 1, 2023: No new gateway creations are possible using Standard or High Performance SKUs.
  • November 30, 2024: Begin migrating gateways to other SKUs.
  • September 30, 2025: Standard/High Performance SKUs will be retired and remaining deprecated legacy gateways will be automatically migrated and upgraded to AZ SKUs.

SKU deprecation FAQs

[!INCLUDE legacy SKU deprecation]

Next steps

For more information about the new Gateway SKUs, see Gateway SKUs.

For more information about configuration settings, see About VPN Gateway configuration settings.