Merge pull request #249278 from cherylmc/fresh5

prmerger-automator[bot] · web-flow · commit 5cfa716488cc · 2023-08-24T20:27:04.000Z
freshness review
diff --git a/articles/virtual-wan/about-vpn-profile-download.md b/articles/virtual-wan/about-vpn-profile-download.md
@@ -6,7 +6,7 @@ author: cherylmc
 
 ms.service: virtual-wan
 ms.topic: how-to
-ms.date: 02/08/2021
+ms.date: 08/24/2023
 ms.author: cherylmc
 
 ---
diff --git a/articles/virtual-wan/howto-always-on-device-tunnel.md b/articles/virtual-wan/howto-always-on-device-tunnel.md
@@ -7,7 +7,7 @@ author: cherylmc
 
 ms.service: virtual-wan
 ms.topic: how-to
-ms.date: 05/26/2021
+ms.date: 08/24/2023
 ms.author: cherylmc
 
 ---
diff --git a/articles/virtual-wan/nat-rules-vpn-gateway-powershell.md b/articles/virtual-wan/nat-rules-vpn-gateway-powershell.md
@@ -7,15 +7,15 @@ author: cherylmc
 ms.service: virtual-wan
 ms.custom: devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 04/11/2022
+ms.date: 08/24/2023
 ms.author: cherylmc
 ---
 
 # Configure NAT Rules for your Virtual WAN VPN gateway using PowerShell
 
 You can configure your Virtual WAN VPN gateway with static one-to-one NAT rules. A NAT rule provides a mechanism to set up one-to-one translation of IP addresses. NAT can be used to interconnect two IP networks that have incompatible or overlapping IP addresses. A typical scenario is branches with overlapping IPs that want to access Azure VNet resources.
 
-This configuration uses a flow table to route traffic from an external (host) IP Address to an internal IP address associated with an endpoint inside a virtual network (virtual machine, computer, container, etc.). In order to use NAT, VPN devices need to use any-to-any (wildcard) traffic selectors. Policy Based (narrow) traffic selectors are not supported in conjunction with NAT configuration.
+This configuration uses a flow table to route traffic from an external (host) IP Address to an internal IP address associated with an endpoint inside a virtual network (virtual machine, computer, container, etc.). In order to use NAT, VPN devices need to use any-to-any (wildcard) traffic selectors. Policy Based (narrow) traffic selectors aren't supported in conjunction with NAT configuration.
 
 ## Prerequisites
 
diff --git a/articles/virtual-wan/point-to-site-ipsec.md b/articles/virtual-wan/point-to-site-ipsec.md
@@ -6,7 +6,7 @@ services: virtual-wan
 author: wellee
 ms.service: virtual-wan
 ms.topic: conceptual
-ms.date: 02/24/2021
+ms.date: 08/24/2023
 ms.author: wellee
 #Customer intent: As a Virtual WAN software-defined connectivity provider, I want to know the IPsec policies for point-to-site VPN
 ---
diff --git a/articles/virtual-wan/scenario-365-expressroute-private.md b/articles/virtual-wan/scenario-365-expressroute-private.md
@@ -7,7 +7,7 @@ author: floklaffenbach
 
 ms.service: virtual-wan
 ms.topic: conceptual
-ms.date: 04/08/2022
+ms.date: 08/24/2023
 ms.author: flofox
 
 ---
diff --git a/articles/virtual-wan/virtual-wan-point-to-site-powershell.md b/articles/virtual-wan/virtual-wan-point-to-site-powershell.md
@@ -8,7 +8,7 @@ author: cherylmc
 ms.service: virtual-wan
 ms.custom: devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 07/05/2022
+ms.date: 08/24/2023
 ms.author: cherylmc
 ---
 # Create a P2S User VPN connection using Azure Virtual WAN - PowerShell
diff --git a/articles/virtual-wan/vpn-profile-intune.md b/articles/virtual-wan/vpn-profile-intune.md
@@ -6,7 +6,7 @@ author: cherylmc
 
 ms.service: virtual-wan
 ms.topic: how-to
-ms.date: 02/04/2021
+ms.date: 08/24/2023
 ms.author: cherylmc
 
 ---
