Merge pull request #297335 from cherylmc/freshness3

freshness review 2

Author: prmerger-automator[bot]

articles/vpn-gateway/about-site-to-site-tunneling.md

@@ -5,7 +5,7 @@ titleSuffix: Azure VPN Gateway
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
-ms.date: 09/22/2023
+ms.date: 03/31/2025
 ms.author: cherylmc
 ---
 
@@ -38,7 +38,7 @@ You can configure forced tunneling by setting the Default Site for your route-ba
 
 By default, all Internet-bound traffic goes directly to the Internet if you don't have forced tunneling configured. When forced tunneling is configured, all Internet-bound traffic is sent to your on-premises location.
 
-In some cases, you may want Internet-bound traffic only from certain subnets (but not all subnets) to traverse from the Azure network infrastructure directly out to the Internet, rather than to your on-premises location. This scenario can be configured using a combination of forced tunneling and virtual network custom user-defined routes (UDRs). For steps, see [Route Internet-bound traffic for specific subnets](site-to-site-tunneling.md#udr).
+In some cases, you might want Internet-bound traffic only from certain subnets (but not all subnets) to traverse from the Azure network infrastructure directly out to the Internet, rather than to your on-premises location. This scenario can be configured using a combination of forced tunneling and virtual network custom user-defined routes (UDRs). For steps, see [Route Internet-bound traffic for specific subnets](site-to-site-tunneling.md#udr).
 
 ## Next steps
 

articles/vpn-gateway/about-zone-redundant-vnet-gateways.md

@@ -5,7 +5,7 @@ titleSuffix: Azure VPN Gateway
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 12/04/2023
+ms.date: 03/31/2025
 ms.author: cherylmc 
 ---
 # About zone-redundant virtual network gateway in Azure availability zones

articles/vpn-gateway/monitor-vpn-gateway.md

@@ -1,7 +1,7 @@
 ---
 title: Monitor Azure VPN Gateway
 description: Start here to learn how to monitor Azure VPN Gateway by using Azure Monitor metrics and resource logs.
-ms.date: 07/26/2024
+ms.date: 03/31/2025
 ms.custom: horz-monitor
 ms.topic: conceptual
 author: cherylmc

articles/vpn-gateway/packet-capture.md

@@ -5,7 +5,7 @@ description: Learn about packet capture functionality that you can use on VPN ga
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 08/24/2023
+ms.date: 03/31/2025
 ms.author: cherylmc
 ---
 

articles/vpn-gateway/vpn-gateway-download-vpndevicescript.md

@@ -5,7 +5,7 @@ titleSuffix: Azure VPN Gateway
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 03/18/2024
+ms.date: 03/31/2025
 ms.author: cherylmc 
 ms.custom: devx-track-azurepowershell
 

articles/vpn-gateway/vpn-gateway-ipsecikepolicy-rm-powershell.md

@@ -5,7 +5,7 @@ description: Learn how to configure IPsec/IKE custom policy for S2S or VNet-to-V
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 05/29/2024
+ms.date: 03/31/2025
 ms.author: cherylmc 
 ms.custom: devx-track-azurepowershell
 
@@ -100,7 +100,7 @@ $LNGIP6        = "131.107.72.22"
 
 #### 2. Create the virtual network, VPN gateway, and local network gateway
 
-The following samples create the virtual network, TestVNet1, with three subnets, and the VPN gateway. When substituting values, it's important that you always name your gateway subnet specifically GatewaySubnet. If you name it something else, your gateway creation fails. It can take 45 minutes or more for the virtual network gateway to create. During this time, if you are using Azure Cloud Shell, your connection may time out. This doesn't affect the gateway create command.
+The following samples create the virtual network, TestVNet1, with three subnets, and the VPN gateway. When substituting values, it's important that you always name your gateway subnet specifically GatewaySubnet. If you name it something else, your gateway creation fails. It can take 45 minutes or more for the virtual network gateway to create. During this time, if you're using Azure Cloud Shell, your connection might time out. This doesn't affect the gateway create command.
 
 ```azurepowershell-interactive
 New-AzResourceGroup -Name $RG1 -Location $Location1
@@ -119,7 +119,7 @@ $gw1ipconf1 = New-AzVirtualNetworkGatewayIpConfig -Name $GW1IPconf1 -Subnet $sub
 New-AzVirtualNetworkGateway -Name $GWName1 -ResourceGroupName $RG1 -Location $Location1 -IpConfigurations $gw1ipconf1 -GatewayType Vpn -VpnType RouteBased -GatewaySku VpnGw1
 ```
 
-Create the local network gateway. You may need to reconnect and declare the following variables again if Azure Cloud Shell timed out.
+Create the local network gateway. You might need to reconnect and declare the following variables again if Azure Cloud Shell timed out.
 
 Declare variables.
 
@@ -172,7 +172,7 @@ You can optionally add "-UsePolicyBasedTrafficSelectors $True" to the create con
 > Once an IPsec/IKE policy is specified on a connection, the Azure VPN gateway will only send or accept
 > the IPsec/IKE proposal with specified cryptographic algorithms and key strengths on that particular
 > connection. Make sure your on-premises VPN device for the connection uses or accepts the exact
-> policy combination, otherwise the S2S VPN tunnel will not establish.
+> policy combination, otherwise the S2S VPN tunnel won't establish.
 
 ## <a name ="vnet2vnet"></a>Create a VNet-to-VNet connection with IPsec/IKE policy
 
@@ -229,7 +229,7 @@ It can take about 45 minutes or more to create the VPN gateway.
 
 ### Step 2: Create a VNet-toVNet connection with the IPsec/IKE policy
 
-Similar to the S2S VPN connection, create an IPsec/IKE policy, then apply the policy to the new connection. If you used Azure Cloud Shell, your connection may have timed out. If so, re-connect and state the necessary variables again.
+Similar to the S2S VPN connection, create an IPsec/IKE policy, then apply the policy to the new connection. If you used Azure Cloud Shell, your connection might have timed out. If so, re-connect and state the necessary variables again.
 
 ```azurepowershell-interactive
 $GWName1 = "VNet1GW"
@@ -270,7 +270,7 @@ New-AzVirtualNetworkGatewayConnection -Name $Connection21 -ResourceGroupName $RG
 > Once an IPsec/IKE policy is specified on a connection, the Azure VPN gateway will only send or accept
 > the IPsec/IKE proposal with specified cryptographic algorithms and key strengths on that particular
 > connection. Make sure the IPsec policies for both connections are the same, otherwise the
-> VNet-to-VNet connection will not establish.
+> VNet-to-VNet connection won't establish.
 
 After you complete these steps, the connection is established in a few minutes, and you'll have the following network topology as shown in the beginning:
 
@@ -287,7 +287,7 @@ The last section shows you how to manage IPsec/IKE policy for an existing S2S or
 The same steps apply to both S2S and VNet-to-VNet connections.
 
 > [!IMPORTANT]
-> IPsec/IKE policy is supported on *Standard* and *HighPerformance* route-based VPN gateways only. It does not work on the Basic gateway SKU or the policy-based VPN gateway.
+> IPsec/IKE policy is supported on *Standard* and *HighPerformance* route-based VPN gateways only. It doesn't work on the Basic gateway SKU or the policy-based VPN gateway.
 
 ### 1. Show an IPsec/IKE policy for a connection
 

articles/vpn-gateway/vpn-profile-intune.md

@@ -5,7 +5,7 @@ description: Learn how to create an Intune custom profile to deploy Azure VPN cl
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 07/28/2023
+ms.date: 03/31/2025
 ms.author: cherylmc
 
 ---

articles/vpn-gateway/work-remotely-support.md

@@ -5,7 +5,7 @@ description: Learn how you can use VPN Gateway point-to-site connections in orde
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
-ms.date: 07/10/2024
+ms.date: 03/31/2025
 ms.author: cherylmc
 
 ---