Merge pull request #251677 from cherylmc/patch-2

Update vpn-gateway-gwsku-include.md

Author: prmerger-automator[bot]

includes/vpn-gateway-gwsku-include.md

@@ -5,7 +5,7 @@
  author: cherylmc
  ms.service: vpn-gateway
  ms.topic: include
- ms.date: 06/27/2023
+ ms.date: 09/15/2023
  ms.author: cherylmc
  ms.custom: include file
 ---
@@ -33,7 +33,7 @@ The new VPN gateway SKUs streamline the feature sets offered on the gateways:
 
 (*) 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](../articles/vpn-gateway/vpn-gateway-connect-multiple-policybased-rm-ps.md) for details.
 
-(\*\*) The Basic SKU is considered a legacy SKU. The Basic SKU has certain feature limitations. You can't resize a gateway that uses a Basic SKU to another SKU, you must instead change to a new SKU, which involves deleting and recreating your VPN gateway. You can't deploy a Basic SKU to a VNet that uses IPv6 address space.
+(\*\*) The Basic SKU is considered a legacy SKU. The Basic SKU has certain feature limitations. You can't resize a gateway that uses a Basic SKU to another SKU, you must instead change to a new SKU, which involves deleting and recreating your VPN gateway. You can't deploy a Basic SKU to a VNet that uses IPv6 address space. The Basic SKU can only be configured using PowerShell or Azure CLI.
 
 ###  <a name="workloads"></a>Gateway SKUs - Production vs. Dev-Test Workloads