Merge pull request #283713 from cherylmc/legacy-basic

VPN Gateway legacy

Author: Stacyrch140

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

@@ -50,7 +50,7 @@ When you configure a virtual network gateway SKU, select the SKU that satisfies
 
 (*) 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](vpn-gateway-connect-multiple-policybased-rm-ps.md) 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.
+(\*\*) 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.
 
 ## <a name="workloads"></a>Gateway SKUs - Production vs. Dev-Test workloads
 
@@ -62,7 +62,7 @@ Due to the differences in SLAs and feature sets, we recommend the following SKUs
 | **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.
+(\*\*) 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)](vpn-gateway-about-skus-legacy.md).
 
@@ -82,7 +82,7 @@ You specify the gateway SKU when you create your VPN Gateway. See the following
 ## <a name="resizechange"></a>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](vpn-gateway-about-skus-legacy.md).
+> 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)]
 

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

@@ -5,7 +5,7 @@ description: Learn how to change a gateway SKU.
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 10/24/2023
+ms.date: 08/06/2024
 ms.author: cherylmc
 
 ---

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

@@ -1,10 +1,10 @@
 ---
 title: VPN Gateway legacy SKUs
-description: How to work with the old virtual network gateway SKUs; Basic, Standard, and High Performance.
+description: How to work with the old virtual network gateway SKUs; Standard, and High Performance.
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: article
-ms.date: 12/20/2023
+ms.date: 08/06/2024
 ms.author: cherylmc 
 ---
 # Working with VPN Gateway legacy SKUs

includes/vpn-gateway-gwsku-legacy-include.md

@@ -2,19 +2,15 @@
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: include
-ms.date: 11/29/2023
+ms.date: 08/06/2024
 ms.author: cherylmc
 ---
 The legacy (old) VPN Gateway SKUs are:
 
-* Default (Basic)
 * Standard
 * High Performance
 
 When working with the legacy SKUs, consider the following:
 
-* If you want to use a PolicyBased VPN type, you must use the Basic SKU. PolicyBased VPNs (previously called Static Routing) aren't supported on any other SKU.
-* BGP isn't supported on the Basic SKU.
-* ExpressRoute-VPN Gateway coexist configurations aren't supported on the Basic SKU.
 * Active-active S2S VPN Gateway connections can be configured on the High Performance SKU only.
 * VPN Gateway doesn't use the UltraPerformance gateway SKU. For information about the UltraPerformance SKU, see the [ExpressRoute](../articles/expressroute/expressroute-about-virtual-network-gateways.md) documentation.

includes/vpn-gateway-sku-about-change-resize.md

@@ -1,7 +1,7 @@
 ---
 author: cherylmc
 ms.author: cherylmc
-ms.date: 11/28/2023
+ms.date: 08/06/2024
 ms.service: azure-vpn-gateway
 ms.topic: include
 ---

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

@@ -1,7 +1,7 @@
 ---
 author: cherylmc
 ms.author: cherylmc
-ms.date: 11/28/2023
+ms.date: 08/06/2024
 ms.service: azure-vpn-gateway
 ms.topic: include
 ---

includes/vpn-gateway-table-gwtype-legacy-aggtput-include.md

@@ -5,7 +5,7 @@
  author: cherylmc
  ms.service: azure-vpn-gateway
  ms.topic: include
- ms.date: 03/21/2018
+ ms.date: 08/06/2024
  ms.author: cherylmc
  ms.custom: include file
 ---

includes/vpn-gateway-table-requirements-legacy-sku-include.md

@@ -5,7 +5,7 @@
  author: cherylmc
  ms.service: azure-vpn-gateway
  ms.topic: include
- ms.date: 03/21/2018
+ ms.date: 08/06/2024
  ms.author: cherylmc
  ms.custom: include file
 ---