Merge pull request #301726 from MicrosoftDocs/release-vpn-sku

Release vpn SKU -> main -- 06/24

Author: Albertyang0

.openpublishing.redirection.json

@@ -2434,6 +2434,16 @@
       "redirect_url": "/previous-versions/azure/vpn-gateway/vpn-gateway-about-vpn-gateway-settings",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/vpn-gateway/gateway-sku-change.md",
+      "redirect_url": "/azure/vpn-gateway/gateway-sku-upgrade",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/vpn-gateway/gateway-sku-resize.md",
+      "redirect_url": "/azure/vpn-gateway/gateway-sku-upgrade",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/vpn-gateway/vpn-gateway-about-forced-tunneling.md",
       "redirect_url": "/previous-versions/azure/vpn-gateway/vpn-gateway-about-forced-tunneling",

articles/vpn-gateway/TOC.yml

@@ -54,17 +54,13 @@
     items:
     - name: About gateway SKUs
       href: about-gateway-skus.md
-    - name: Gateway SKU consolidation & migration
-      items:
-      - name: About SKU consolidation & migration
-        href: gateway-sku-consolidation.md
-    - name: Resize a gateway SKU
-      href: gateway-sku-resize.md
-    - name: Change a gateway SKU
-      href: gateway-sku-change.md
+    - name: About gateway SKU consolidation & migration
+      href: gateway-sku-consolidation.md
+    - name: Upgrade a gateway SKU
+      href: gateway-sku-upgrade.md
     - name: Manage legacy gateway SKUs
       href: vpn-gateway-about-skus-legacy.md
-  - name: Public IP addresses
+  - name: Public IP address SKUs
     items:
     - name: About Basic SKU public IP address migration
       href: basic-public-ip-migrate-about.md
@@ -96,10 +92,6 @@
       href: about-gateway-skus.md
     - name: Gateway SKU consolidation
       href: gateway-sku-consolidation.md
-    - name: Resize a gateway SKU
-      href: gateway-sku-resize.md
-    - name: Change a gateway SKU
-      href: gateway-sku-change.md
     - name: Manage legacy gateway SKUs
       href: vpn-gateway-about-skus-legacy.md
   - name: Migrate classic gateways to Resource Manager

articles/vpn-gateway/about-gateway-skus.md

@@ -4,7 +4,7 @@ description: Learn about VPN Gateway SKUs.
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
-ms.date: 03/31/2025
+ms.date: 06/23/2025
 ms.author: cherylmc 
 
 ---
@@ -63,7 +63,6 @@ Due to the differences in SLAs and feature sets, we recommend the following SKUs
 | **Production, critical workloads** | All Generation1 and Generation2 SKUs, except Basic|
 | **Dev-test or proof of concept**   | Basic (**)             |
 
-
 (\*\*) The Basic SKU has certain feature and performance limitations and shouldn't 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)](vpn-gateway-about-skus-legacy.md).
@@ -81,23 +80,13 @@ You specify the gateway SKU when you create your VPN Gateway. See the following
 * [PowerShell](create-gateway-powershell.md)
 * [Azure CLI](create-routebased-vpn-gateway-cli.md)
 
-## <a name="resizechange"></a>Change or resize a SKU
+## <a name="resizechange"></a>Upgrade a SKU
+
+For most VPN gateways, you can upgrade a gateway SKU. For more information, see [Upgrade a VPN Gateway SKU](gateway-sku-upgrade.md).
 
 > [!NOTE]
 > If you're working with a legacy gateway SKU (Standard and High Performance), see [Managing Legacy gateway SKUs](vpn-gateway-about-skus-legacy.md).
 
-[!INCLUDE [changing vs. resizing](../../includes/vpn-gateway-sku-about-change-resize.md)]
-
-### 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](../../includes/vpn-gateway-sku-resize-restrictions.md)]
-
-The following table helps you understand the required method to move from one SKU to another.
-
-[!INCLUDE [resize SKU methods table](../../includes/vpn-gateway-sku-resize-methods-table.md)]
-
 ## Next steps
 
 For more information about available connection configurations, see [About VPN Gateway](vpn-gateway-about-vpngateways.md).

articles/vpn-gateway/basic-public-ip-migrate-about.md

@@ -6,7 +6,7 @@ author: raboilla
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
 ms.custom: references_regions
-ms.date: 06/10/2025
+ms.date: 06/23/2025
 ms.author: cherylmc
 ---
 
@@ -18,7 +18,7 @@ This article explains the migration process from a Basic SKU public IP address t
 
 To migrate your gateway, you first need to validate whether your resource is capable of migration. Here are some common situations to be aware of:
 
-* If your current gateway subnet is /28 or smaller, the migration tool may error out. You can use this to [add multiple prefixes for subnet](https://learn.microsoft.com/azure/virtual-network/how-to-multiple-prefixes-subnet?tabs=powershell) to /27 or larger before you can proceed with migration.
+* If your current gateway subnet is /28 or smaller, the migration tool may error out. You can use this to [add multiple prefixes for subnet](../virtual-network/how-to-multiple-prefixes-subnet.md) to /27 or larger before you can proceed with migration.
 
 * Before your initiate migration for your VPN gateway, verify that your gateway subnet has at least *three* available IP addresses in your current prefix.
 
@@ -55,7 +55,7 @@ The Standard SKU public IP address parameter for the VPN Gateway Basic SKU is cu
 
 ### Can I change to a Standard SKU public IP address manually?
 
-Yes, you can. If you choose to do this manually, you'll need to delete the old gateway and then create a new gateway in your virtual network. When you create a new gateway, your gateway will automatically use a Standard SKU public IP address. However, if you choose to use this process, you'll incur downtime while the old gateway is deleted and the new gateway is created. For more information, see [Change a gateway SKU](gateway-sku-change.md).
+Yes, you can. If you choose to do this manually, you'll need to delete the old gateway and then create a new gateway in your virtual network. When you create a new gateway, your gateway will automatically use a Standard SKU public IP address. However, if you choose to use this process, you'll incur downtime while the old gateway is deleted and the new gateway is created.
 
 ### If I delete and re-create my gateway, will my IP address change?
 

articles/vpn-gateway/gateway-sku-change.md

@@ -0,0 +1,65 @@
+---
+title: Upgrade a VPN Gateway SKU
+titleSuffix: Azure VPN Gateway
+description: Learn how to upgrade a VPN Gateway SKU in Azure.
+author: cherylmc
+ms.service: azure-vpn-gateway
+ms.topic: how-to
+ms.date: 06/23/2025
+ms.author: cherylmc
+
+#customer intent: As an Azure network engineer, I want to understand the workflow for upgrading a VPN Gateway SKU so that I can plan properly and minimize downtime.
+
+---
+# Upgrade a VPN Gateway SKU
+
+This article helps you upgrade a VPN Gateway virtual network gateway SKU. Upgrading a gateway SKU is a relatively fast process with minimal downtime (approximately 45 minutes). You can upgrade a SKU easily in the Azure portal, or by using PowerShell or Azure CLI. When you upgrade a SKU, the public IP address assigned to your gateway SKU doesn't change and you don't need to reconfigure your VPN device or your P2S clients.
+
+## Considerations
+
+There are many things to consider when upgrading to a new gateway SKU. The following table helps you understand the required method to move from one SKU to another. Notice that not all gateway SKUs are eligible to be upgraded directly. Some SKUs require you to delete the existing gateway and create a new one.
+
+| Starting SKU | Target SKU | Eligible for SKU upgrade| Delete/Recreate only |
+| --- | --- |--- | --- |
+| Basic SKU | Any other SKU | No | Yes  |
+| Generation 1 SKU | Generation 1 SKU | Yes| No |
+| Generation 1 SKU | Generation 1 AZ SKU | No |Yes |
+| Generation 1 AZ SKU | Generation 1 AZ SKU |Yes | No |
+| Generation 1 AZ SKU | Generation 2 AZ SKU | No | Yes |
+| Generation 2 SKU | Generation 2 SKU | Yes | No |
+| Generation 2 SKU | Generation 2 AZ SKU | No |Yes |
+| Generation 2 AZ SKU | Generation 2 AZ SKU | Yes | No |
+
+For gateway SKU throughput and connection limits, see [About gateway SKUs](about-gateway-skus.md#benchmark).
+
+## Limitations and restrictions
+
+* You can't upgrade a Basic SKU to a new SKU. You must delete the gateway, and then create a new one.
+* You can't downgrade a SKU without deleting the gateway and creating a new one.
+* Legacy gateway SKUs (Standard and High Performance) can't be upgraded to the new SKU families. You must delete the gateway and create a new one. For more information about working with legacy gateway SKUS, see [VPN Gateway legacy SKUs](vpn-gateway-about-skus-legacy.md)
+
+## Upgrade a gateway SKU using the Azure portal
+
+Upgrading a gateway SKU takes about 45 minutes to complete.
+
+1. Go to the **Configuration** page for your virtual network gateway.
+1. On the right side of the page, click the dropdown arrow to show a list of available SKUs. The options listed are based on the starting SKU and SKU Generation. Select the SKU from the dropdown.
+1. **Save** your changes to begin the SKU upgrade. It takes about 45 minutes for the gateway SKU upgrade to complete.
+
+## Workflow for SKUs that can't be upgraded
+
+For SKUs that can't be directly upgraded (Basic and legacy gateway SKUs), you must delete the existing gateway and create a new one. This process incurs downtime. The public IP address assigned to your gateway SKU changes. You must also reconfigure your VPN device and P2S clients.
+
+The high level workflow is:
+
+1. Remove any connections to the virtual network gateway.
+1. Delete the old VPN gateway.
+1. Create the new VPN gateway.
+1. Update your on-premises VPN devices with the new VPN gateway IP address (for site-to-site connections).
+1. Update the gateway IP address value for any VNet-to-VNet local network gateways that connect to this gateway.
+1. Download new client VPN configuration packages for point-to-site clients connecting to the virtual network through this VPN gateway.
+1. Recreate the connections to the virtual network gateway.
+
+## Next steps
+
+For more information about gateway SKUs, see [About gateway SKUs](about-gateway-skus.md).