Merge pull request #284802 from cherylmc/basic-sku

Basic SKU

Author: Jill Grant

articles/vpn-gateway/create-gateway-basic-sku-powershell.md

@@ -5,7 +5,7 @@ description: Learn how to create a Basic SKU virtual network gateway for a VPN c
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 07/17/2024
+ms.date: 08/15/2024
 ms.author: cherylmc 
 ms.custom: devx-track-azurepowershell
 ---
@@ -14,18 +14,19 @@ ms.custom: devx-track-azurepowershell
 
 This article helps you create a Basic SKU Azure VPN gateway using PowerShell. The VPN gateway you create can be either RouteBased, or PolicyBased, depending on your connection requirements. A VPN gateway is used when creating a VPN connection to your on-premises network. You can also use a VPN gateway to connect VNets.
 
+> [!IMPORTANT]
+> The Basic SKU has certain feature and performance limitations and shouldn't be used for production purposes. For more information about SKUs, see [About gateway SKUs](about-gateway-skus.md).
+
 :::image type="content" source="./media/create-gateway-basic-sku/gateway-diagram.png" alt-text="Diagram that shows a virtual network and a VPN gateway." lightbox="./media/create-gateway-basic-sku/gateway-diagram-expand.png":::
 
 * The left side of the diagram shows the virtual network and the VPN gateway that you create by using the steps in this article.
 * You can later add different types of connections, as shown on the right side of the diagram. For example, you can create [site-to-site](tutorial-site-to-site-portal.md) and [point-to-site](point-to-site-about.md) connections. To view different design architectures that you can build, see [VPN gateway design](design.md).
 
 The steps in this article create a virtual network, a subnet, a gateway subnet, and a VPN gateway (virtual network gateway) using the Basic SKU. The article steps specify a **RouteBased** VPN type. You can also specify a **PolicyBased** VPN type using the steps in this article. Once the gateway creation completes, you can then create connections. If you want to create a gateway using a SKU other than the Basic SKU, see the [Portal article](tutorial-create-gateway-portal.md).
 
-Basic SKU VPN gateways have limitations. For more information about SKUs and Basic SKU limitations, see [About gateway SKUs](about-gateway-skus.md). A few of the limitations that affect the settings used in this article are:
+The Basic SKU has certain feature and performance limitations and shouldn't be used for production purposes. Some of the limitations of the Basic SKU are:
 
-* A Basic SKU VPN gateway must use the Dynamic allocation method for public IP address, not Static.
-* A Basic SKU VPN gateway uses a Basic SKU public IP address, not Standard.
-* You can't create a Basic SKU VPN gateway using the Azure portal.
+[!INCLUDE [Basic SKU limitations](../../includes/vpn-gateway-basic-sku-limitations.md)]
 
 ## Before you begin
 

includes/vpn-gateway-basic-sku-limitations.md

@@ -0,0 +1,13 @@
+---
+ms.author: cherylmc
+author: cherylmc
+ms.date: 08/15/2024
+ms.service: azure-vpn-gateway
+ms.topic: include
+---
+
+* A Basic SKU VPN gateway uses a Basic SKU public IP address, not Standard.
+* The public IP address allocation method for a Basic SKU VPN gateway must be Dynamic, not Static.
+* The Basic SKU can only be configured using PowerShell or Azure CLI.
+* The Basic SKU doesn't support IPv6.
+* The Basic SKU doesn't support RADIUS authentication.

includes/vpn-gateway-sku-resize-restrictions.md

@@ -1,13 +1,13 @@
 ---
 author: cherylmc
 ms.author: cherylmc
-ms.date: 08/06/2024
+ms.date: 08/15/2024
 ms.service: azure-vpn-gateway
 ms.topic: include
 ---
 
 * You can't resize to downgrade a SKU.
-* You can't resize a legacy SKU to one of the newer Azure SKUs (VpnGw1, VpnGw2AZ etc.) Legacy SKUs for the Resource Manager deployment model are: Basic, Standard, and High Performance. You must instead, change the SKU.
+* You can't resize a legacy SKU to one of the newer Azure SKUs (VpnGw1, VpnGw2AZ etc.) Legacy SKUs for the Resource Manager deployment model are: Standard, and High Performance. You must instead, change the SKU.
 * You can resize a gateway SKU as long as it is in the same generation, except for the Basic SKU.
 * You can change a Basic SKU to another SKU.
 * When you change from a legacy SKU to a new SKU, you'll have connectivity downtime.