Merge pull request #246655 from cherylmc/vwan-fresh3

freshness update

Author: v-regandowner

articles/vpn-gateway/reset-gateway.md

@@ -5,7 +5,7 @@ description: Learn how to reset a gateway or a gateway connection to reestablish
 author: cherylmc
 ms.service: vpn-gateway
 ms.topic: how-to
-ms.date: 06/13/2022
+ms.date: 07/28/2023
 ms.author: cherylmc 
 ---
 # Reset a VPN gateway or a connection
@@ -45,35 +45,41 @@ Before you reset your gateway, verify the key items listed below for each IPsec
 Verify the following items before resetting your gateway:
 
 * The Internet IP addresses (VIPs) for both the Azure VPN gateway and the on-premises VPN gateway are configured correctly in both the Azure and the on-premises VPN policies.
-* The pre-shared key must be the same on both Azure and on-premises VPN gateways.
+* The preshared key must be the same on both Azure and on-premises VPN gateways.
 * If you apply specific IPsec/IKE configuration, such as encryption, hashing algorithms, and PFS (Perfect Forward Secrecy), ensure both the Azure and on-premises VPN gateways have the same configurations.
 
 ### <a name="portal"></a>Azure portal
 
-You can reset a Resource Manager VPN gateway using the Azure portal. If you want to reset a classic gateway, see the PowerShell steps for the [Classic deployment model](#resetclassic).
+You can reset a Resource Manager VPN gateway using the Azure portal.
 
 [!INCLUDE [portal steps](../../includes/vpn-gateway-reset-gw-portal-include.md)]
 
 ### <a name="ps"></a>PowerShell
 
-#### Resource Manager deployment model
-
-[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
-
 The cmdlet for resetting a gateway is **Reset-AzVirtualNetworkGateway**. Before performing a reset, make sure you have the latest version of the [PowerShell Az cmdlets](/powershell/module/az.network). The following example resets a virtual network gateway named VNet1GW in the TestRG1 resource group:
 
 ```azurepowershell-interactive
 $gw = Get-AzVirtualNetworkGateway -Name VNet1GW -ResourceGroupName TestRG1
 Reset-AzVirtualNetworkGateway -VirtualNetworkGateway $gw
 ```
 
-Result:
+When you receive a return result, you can assume the gateway reset was successful. However, there's nothing in the return result that indicates explicitly that the reset was successful. If you want to look closely at the history to see exactly when the gateway reset occurred, you can view that information in the [Azure portal](https://portal.azure.com). In the portal, navigate to **'GatewayName' -> Resource Health**.
+
+### <a name="cli"></a>Azure CLI
+
+To reset the gateway, use the [az network vnet-gateway reset](/cli/azure/network/vnet-gateway) command. The following example resets a virtual network gateway named VNet5GW in the TestRG5 resource group:
+
+```azurecli-interactive
+az network vnet-gateway reset -n VNet5GW -g TestRG5
+```
 
 When you receive a return result, you can assume the gateway reset was successful. However, there's nothing in the return result that indicates explicitly that the reset was successful. If you want to look closely at the history to see exactly when the gateway reset occurred, you can view that information in the [Azure portal](https://portal.azure.com). In the portal, navigate to **'GatewayName' -> Resource Health**.
 
-#### <a name="resetclassic"></a>Classic deployment model
+### <a name="resetclassic"></a>Reset a classic gateway
 
-The cmdlet for resetting a gateway is **Reset-AzureVNetGateway**. The Azure PowerShell cmdlets for Service Management must be installed locally on your desktop. You can't use Azure Cloud Shell. Before performing a reset, make sure you have the latest version of the [Service Management (SM) PowerShell cmdlets](/powershell/azure/servicemanagement/install-azure-ps#azure-service-management-cmdlets). When using this command, make sure you're using the full name of the virtual network. Classic VNets that were created using the portal have a long name that is required for PowerShell. You can view the long name by using 'Get-AzureVNetConfig -ExportToFile C:\Myfoldername\NetworkConfig.xml'.
+The cmdlet for resetting a classic gateway is **Reset-AzureVNetGateway**. The Azure PowerShell cmdlets for Service Management must be installed locally on your desktop. You can't use Azure Cloud Shell. Before performing a reset, make sure you have the latest version of the [Service Management (SM) PowerShell cmdlets](/powershell/azure/servicemanagement/install-azure-ps#azure-service-management-cmdlets).
+
+When using this command, make sure you're using the full name of the virtual network. Classic VNets that were created using the portal have a long name that is required for PowerShell. You can view the long name by using 'Get-AzureVNetConfig -ExportToFile C:\Myfoldername\NetworkConfig.xml'.
 
 The following example resets the gateway for a virtual network named "Group TestRG1 TestVNet1" (which shows as simply "TestVNet1" in the portal):
 
@@ -92,14 +98,6 @@ RequestId      : 9ca273de2c4d01e986480ce1ffa4d6d9
 StatusCode     : OK
 ```
 
-### <a name="cli"></a>Azure CLI
-
-To reset the gateway, use the [az network vnet-gateway reset](/cli/azure/network/vnet-gateway) command. The following example resets a virtual network gateway named VNet5GW in the TestRG5 resource group:
+## Next steps
 
-```azurecli-interactive
-az network vnet-gateway reset -n VNet5GW -g TestRG5
-```
-
-Result:
-
-When you receive a return result, you can assume the gateway reset was successful. However, there's nothing in the return result that indicates explicitly that the reset was successful. If you want to look closely at the history to see exactly when the gateway reset occurred, you can view that information in the [Azure portal](https://portal.azure.com). In the portal, navigate to **'GatewayName' -> Resource Health**.
+For more information about VPN Gateway, see the [VPN Gateway FAQ](vpn-gateway-vpn-faq.md).

articles/vpn-gateway/vpn-gateway-about-point-to-site-routing.md

@@ -5,7 +5,7 @@ description: Learn about Azure Point-to-Site VPN routing for different operating
 author: cherylmc
 ms.service: vpn-gateway
 ms.topic: article
-ms.date: 12/03/2021
+ms.date: 07/28/2023
 ms.author: cherylmc
 
 ---
@@ -25,7 +25,7 @@ There are a number of different diagrams in this article. Each section shows a d
 
 ## <a name="isolatedvnet"></a>One isolated VNet
 
-The Point-to-Site VPN gateway connection in this example is for a VNet that is not connected or peered with any other virtual network (VNet1). In this example, clients can access VNet1.
+The Point-to-Site VPN gateway connection in this example is for a VNet that isn't connected or peered with any other virtual network (VNet1). In this example, clients can access VNet1.
 
 :::image type="content" source="./media/vpn-gateway-about-point-to-site-routing/isolated.jpg" alt-text="Isolated VNet routing" lightbox="./media/vpn-gateway-about-point-to-site-routing/isolated.jpg":::
 
@@ -49,7 +49,7 @@ The Point-to-Site VPN gateway connection in this example is for a VNet that is n
 
 In this example, the Point-to-Site VPN gateway connection is for VNet1. VNet1 is peered with VNet2. VNet 2 is peered with VNet3. VNet1 is peered with VNet4. There is no direct peering between VNet1 and VNet3. VNet1 has “Allow gateway transit” and VNet2 and VNet4 have “Use remote gateways” enabled.
 
-Clients using Windows can access directly peered VNets, but the VPN client must be downloaded again if any changes are made to VNet peering or the network topology. Non-Windows clients can access directly peered VNets. Access is not transitive and is limited to only directly peered VNets.
+Clients using Windows can access directly peered VNets, but the VPN client must be downloaded again if any changes are made to VNet peering or the network topology. Non-Windows clients can access directly peered VNets. Access isn't transitive and is limited to only directly peered VNets.
 
 :::image type="content" source="./media/vpn-gateway-about-point-to-site-routing/multiple.jpg" alt-text="Multiple peered VNets" lightbox="./media/vpn-gateway-about-point-to-site-routing/multiple.jpg":::
 
@@ -77,7 +77,7 @@ Clients using Windows can access directly peered VNets, but the VPN client must
 
 ## <a name="multis2s"></a>Multiple VNets connected using an S2S VPN
 
-In this example, the Point-to-Site VPN gateway connection is for VNet1. VNet1 is connected to VNet2 using a Site-to-Site VPN connection. VNet2 is connected to VNet3 using a Site-to-Site VPN connection. There is no direct peering or Site-to-Site VPN connection between VNet1 and VNet3. All Site-to-Site connections are not running BGP for routing.
+In this example, the Point-to-Site VPN gateway connection is for VNet1. VNet1 is connected to VNet2 using a Site-to-Site VPN connection. VNet2 is connected to VNet3 using a Site-to-Site VPN connection. There is no direct peering or Site-to-Site VPN connection between VNet1 and VNet3. All Site-to-Site connections aren't running BGP for routing.
 
 Clients using Windows, or another supported OS, can only access VNet1. To access additional VNets, BGP must be used.
 
@@ -133,7 +133,7 @@ Clients using Windows, or another supported OS, can access all VNets that are co
 
 ## <a name="vnetbranch"></a>One VNet and a branch office
 
-In this example, the Point-to-Site VPN gateway connection is for VNet1. VNet1 is not connected/ peered with any other virtual network, but is connected to an on-premises site through a Site-to-Site VPN connection that is not running BGP.
+In this example, the Point-to-Site VPN gateway connection is for VNet1. VNet1 isn't connected/ peered with any other virtual network, but is connected to an on-premises site through a Site-to-Site VPN connection that isn't running BGP.
 
 Windows and non-Windows clients can only access VNet1.
 
@@ -159,9 +159,9 @@ Windows and non-Windows clients can only access VNet1.
 
 ## <a name="vnetbranchbgp"></a>One VNet and a branch office (BGP)
 
-In this example, the Point-to-Site VPN gateway connection is for VNet1. VNet1 is not connected or peered with any other virtual network, but is connected to an on-premises site (Site1) through a Site-to-Site VPN connection running BGP.
+In this example, the Point-to-Site VPN gateway connection is for VNet1. VNet1 isn't connected or peered with any other virtual network, but is connected to an on-premises site (Site1) through a Site-to-Site VPN connection running BGP.
 
-Windows clients can access the VNet and the branch office (Site1), but the routes to Site1 must be manually added to the client. Non-Windows clients can access the VNet as well as the on-premises branch office.
+Windows clients can access the VNet and the branch office (Site1), but the routes to Site1 must be manually added to the client. Non-Windows clients can access the VNet and the on-premises branch office.
 
 :::image type="content" source="./media/vpn-gateway-about-point-to-site-routing/branch-bgp.jpg" alt-text="Routing with a VNet and a branch office - BGP" lightbox="./media/vpn-gateway-about-point-to-site-routing/branch-bgp.jpg":::
 

articles/vpn-gateway/vpn-gateway-vpn-faq.md

@@ -4,7 +4,7 @@ description: Learn about frequently asked questions for VPN Gateway cross-premis
 author: cherylmc
 ms.service: vpn-gateway
 ms.topic: conceptual
-ms.date: 01/30/2023
+ms.date: 07/28/2023
 ms.author: cherylmc
 ---
 

includes/vpn-gateway-reset-gw-portal-include.md

@@ -2,10 +2,10 @@
  author: cherylmc
  ms.service: vpn-gateway
  ms.topic: include
- ms.date: 09/14/2022
+ ms.date: 07/28/2023
  ms.author: cherylmc
 ---
 
 1. In the portal, go to the virtual network gateway that you want to reset.
-1. On the **Virtual network gateway** page, in the left pane, scroll down to the **Support + Troubleshooting** section and select **Reset**.
+1. On the **Virtual network gateway** page, in the left pane, scroll down to **Reset**.
 1. On the **Reset** page, click **Reset**. Once the command is issued, the current active instance of the Azure VPN gateway is rebooted immediately. Resetting the gateway will cause a gap in VPN connectivity, and may limit future root cause analysis of the issue.