Merge pull request #291899 from cherylmc/images7

freshness

Author: v-dirichards

articles/virtual-wan/media/virtual-wan-custom-ipsec-portal/locate.png

@@ -68,7 +68,7 @@ The effective routes in hub 2 will be similar:
 
 :::image type="content" source="./media/routing-deep-dive/virtual-wan-routing-deep-dive-scenario-2-er-hub-2.png" alt-text="Screenshot of effective routes in Virtual hub 2 with Global Reach and routing preference ExpressRoute." lightbox="./media/routing-deep-dive/virtual-wan-routing-deep-dive-scenario-2-er-hub-2-expanded.png":::
 
-The routing preference can be changed to VPN or AS-Path as explained in [Virtual hub routing preference][virtual-wan-hrp]. For example, you can set the preference to VPN as shown in this image:
+The routing preference can be changed to VPN or AS-Path as explained in [Virtual hub routing preference][virtual-wan-hrp]. For example, you can set the preference to VPN.
 
 :::image type="content" source="./media/routing-deep-dive/virtual-wan-routing-deep-dive-scenario-2-set-hrp-vpn.png" alt-text="Screenshot of how to set hub routing preference in Virtual WAN to V P N." lightbox="./media/routing-deep-dive/virtual-wan-routing-deep-dive-scenario-2-set-hrp-vpn.png":::
 
@@ -80,7 +80,7 @@ The previous image shows that the route to `10.4.2.0/24` has now a next hop of `
 
 :::image type="content" source="./media/routing-deep-dive/virtual-wan-routing-deep-dive-scenario-2-vpn-hub-2.png" alt-text="Screenshot of effective routes in Virtual hub 2 with Global Reach and routing preference V P N." lightbox="./media/routing-deep-dive/virtual-wan-routing-deep-dive-scenario-2-vpn-hub-2.png":::
 
-However, traffic between hubs is still preferring the routes coming via ExpressRoute. To use the more efficient direct connection between the virtual hubs, the  route preference can be set to "AS Path" on both hubs:
+However, traffic between hubs is still preferring the routes coming via ExpressRoute. To use the more efficient direct connection between the virtual hubs, the  route preference can be set to "AS Path" on both hubs.
 
 :::image type="content" source="./media/routing-deep-dive/virtual-wan-routing-deep-dive-scenario-2-set-hrp-aspath.png" alt-text="Screenshot that shows how to set hub routing preference in Virtual WAN to A S Path." lightbox="./media/routing-deep-dive/virtual-wan-routing-deep-dive-scenario-2-set-hrp-aspath.png":::
 

articles/virtual-wan/media/virtual-wan-site-to-site-portal/edit-gateway.png

@@ -6,7 +6,7 @@ author: cherylmc
 
 ms.service: azure-virtual-wan
 ms.topic: how-to
-ms.date: 02/02/2023
+ms.date: 12/12/2024
 ms.author: cherylmc
 
 ---
@@ -21,15 +21,16 @@ You can configure a custom IPsec policy for a Virtual WAN VPN connection in the
 ## Configure a policy
 
 1. **Locate the virtual hub**. In the Azure portal, go to your Virtual WAN resource and locate the virtual hub that your VPN site is connected to.
-2. **Select the VPN site**. From the hub overview page, click **VPN (Site to site)** and select the VPN Site for which you want to set up a custom IPsec policy.
 
-   ![select](./media/virtual-wan-custom-ipsec-portal/locate.png)
-3. **Edit the VPN connection**. From the **Context menu** **...**, select **Edit VPN Connection**.
+1. **Select the VPN site**. From the hub overview page, click **VPN (Site to site)** and select the VPN Site for which you want to set up a custom IPsec policy.
 
-   ![edit](./media/virtual-wan-custom-ipsec-portal/contextmenu.png)
-4. **Configure the settings**. On the **Edit VPN connection** page, change the IPsec setting from default to custom and customize the IPsec policy. Select **Save** to save your settings.
+1. **Edit the VPN connection**. From the **Context menu** **...**, select **Edit VPN Connection**.
 
-   ![configure and save](./media/virtual-wan-custom-ipsec-portal/edit.png)
+   :::image type="content" source="./media/virtual-wan-custom-ipsec-portal/contextmenu.png" alt-text="Screenshot shows how to use the context menu to edit the policy." lightbox="./media/virtual-wan-custom-ipsec-portal/contextmenu.png":::
+
+1. **Configure the settings**. On the **Edit VPN connection** page, change the IPsec setting from default to custom and customize the IPsec policy. Select **Save** to save your settings.
+
+   :::image type="content" source="./media/virtual-wan-custom-ipsec-portal/edit.png" alt-text="Screenshot shows how to configure and save the policy." lightbox="./media/virtual-wan-custom-ipsec-portal/edit.png":::
 
 ## Next steps
 

articles/virtual-wan/routing-deep-dive.md

@@ -4,7 +4,7 @@ description: In this tutorial, learn how to use Azure Virtual WAN to create Expr
 author: cherylmc
 ms.service: azure-virtual-wan
 ms.topic: tutorial
-ms.date: 04/28/2023
+ms.date: 12/12/2024
 ms.author: cherylmc
 # Customer intent: As someone with a networking background, I want to connect my corporate on-premises network(s) to my VNets using Virtual WAN and ExpressRoute.
 ---
@@ -141,7 +141,7 @@ By default, VNet to Virtual WAN traffic is disabled over ExpressRoute. You can e
 
 :::image type="content" source="./media/virtual-wan-expressroute-portal/allow-non-virtual-wan-traffic.png" alt-text="Azure portal Screenshot of Virtual Hub Edit with ExpressRoute toggle for allowing traffic from non Virtual WAN networks." lightbox="./media/virtual-wan-expressroute-portal/allow-non-virtual-wan-traffic.png":::
 
-It is recommended to keep these toggles disabled and instead create a Virtual Network connection between the standalone virtual network and Virtual WAN hub. This offers better performance and lower latency, as conveyed in our [FAQ.](virtual-wan-faq.md#when-theres-an-expressroute-circuit-connected-as-a-bow-tie-to-a-virtual-wan-hub-and-a-standalone-vnet-what-is-the-path-for-the-standalone-vnet-to-reach-the-virtual-wan-hub)
+We recommend that you keep these toggles disabled and instead create a Virtual Network connection between the standalone virtual network and Virtual WAN hub. This offers better performance and lower latency, as conveyed in our [FAQ.](virtual-wan-faq.md#when-theres-an-expressroute-circuit-connected-as-a-bow-tie-to-a-virtual-wan-hub-and-a-standalone-vnet-what-is-the-path-for-the-standalone-vnet-to-reach-the-virtual-wan-hub)
 
 ## <a name="cleanup"></a>Clean up resources
 

articles/virtual-wan/virtual-wan-custom-ipsec-portal.md

@@ -6,7 +6,7 @@ services: virtual-wan
 author: cherylmc
 ms.service: azure-virtual-wan
 ms.topic: tutorial
-ms.date: 08/09/2023
+ms.date: 12/12/2024
 ms.author: cherylmc
 
 ---
@@ -84,19 +84,16 @@ Once you have finished configuring your client, you can connect.
 
 ## <a name="connect-vnet"></a>Connect VNet to hub
 
-In this section, you create a connection between your virtual hub and your VNet. For this tutorial, you don't need to configure the routing settings.
+In this section, you create a connection between your virtual hub and your virtual network. For this tutorial, you don't need to configure the routing settings.
 
 [!INCLUDE [Connect virtual network](../../includes/virtual-wan-connect-vnet-hub-include.md)]
 
 ## <a name="viewwan"></a>Point to site sessions dashboard
 
 1. To view your active point to site sessions, click on **Point-to-site Sessions**. This will show you all active point to site users that are connected to your User VPN gateway.
-  :::image type="content" source="../../includes/media/virtual-wan-p2s-sessions-dashboard/point-to-site-sessions-button.png" alt-text="Screenshot shows point to site blade in Virtual WAN." lightbox="../../includes/media/virtual-wan-p2s-sessions-dashboard/point-to-site-sessions-button.png":::
 
 1. To disconnect users from the User VPN gateway, click the ... context menu and click "Disconnect".	
 
- :::image type="content" source="../../includes/media/virtual-wan-p2s-sessions-dashboard/point-to-site-sessions-disconnect.png" alt-text="Screenshot shows point to site sessions dashboard." lightbox="../../includes/media/virtual-wan-p2s-sessions-dashboard/point-to-site-sessions-disconnect.png":::
-
 ## Modify settings
 
 ### <a name="address-pool"></a>Modify client address pool

articles/virtual-wan/virtual-wan-expressroute-portal.md

@@ -5,7 +5,7 @@ description: Learn how to use Azure Virtual WAN to create a site-to-site VPN con
 author: cherylmc
 ms.service: azure-virtual-wan
 ms.topic: tutorial
-ms.date: 01/31/2024
+ms.date: 12/12/2024
 ms.author: cherylmc
 # Customer intent: As someone with a networking background, I want to connect my local site to my VNets using Virtual WAN and I don't want to go through a Virtual WAN partner.
 ---
@@ -226,7 +226,7 @@ The device configuration file contains the settings to use when configuring your
 
 ### <a name="vpn-device"></a>Configuring your VPN device
 
->[!NOTE]
+> [!NOTE]
 > If you are working with a Virtual WAN partner solution, VPN device configuration automatically happens. The device controller obtains the configuration file from Azure and applies to the device to set up connection to Azure. This means you don't need to know how to manually configure your VPN device.
 >
 
@@ -253,8 +253,6 @@ On the **Edit VPN Gateway** page, you can see the following settings:
 * **Default BGP IP Address**: Assigned by Azure.
 * **Custom BGP IP Address**: This field is reserved for APIPA (Automatic Private IP Addressing). Azure supports BGP IP in the ranges 169.254.21.* and 169.254.22.*. Azure accepts BGP connections in these ranges but will dial connection with the default BGP IP. Users can specify multiple custom BGP IP addresses for each instance. The same custom BGP IP address shouldn't be used for both instances. 
 
-   :::image type="content" source="media/virtual-wan-site-to-site-portal/edit-gateway.png" alt-text="Screenshot shows the Edit VPN Gateway page with the Edit button highlighted." lightbox="media/virtual-wan-site-to-site-portal/edit-gateway.png":::
-
 ## <a name="cleanup"></a>Clean up resources
 
 When you no longer need the resources that you created, delete them. Some of the Virtual WAN resources must be deleted in a certain order due to dependencies. Deleting can take about 30 minutes to complete.

articles/virtual-wan/virtual-wan-point-to-site-portal.md

@@ -1,7 +1,7 @@
 ---
 author: cherylmc
 ms.author: cherylmc
-ms.date: 06/14/2023
+ms.date: 12/12/2024
 ms.service: azure-virtual-wan
 ms.topic: include
 
@@ -12,8 +12,6 @@ ms.topic: include
 1. On the **Virtual network connections** page, select **+ Add connection**.
 1. On the **Add connection** page, configure the connection settings. For information about routing settings, see [About routing](../articles/virtual-wan/about-virtual-hub-routing.md).
 
-   :::image type="content" source="./media/virtual-wan-connect-vnet-hub/connection.png" alt-text="Screenshot of the Add connection page." lightbox="./media/virtual-wan-connect-vnet-hub/connection.png":::
-
    * **Connection name**: Name your connection.
    * **Hubs**: Select the hub you want to associate with this connection.
    * **Subscription**: Verify the subscription.
@@ -25,5 +23,5 @@ ms.topic: include
    * **Static routes**: Configure static routes, if necessary. Configure static routes for Network Virtual Appliances (if applicable). Virtual WAN supports a single next hop IP for static route in a virtual network connection. For example, if you have a separate virtual appliance for ingress and egress traffic flows, it would be best to have the virtual appliances in separate VNets and attach the VNets to the virtual hub.
    * **Bypass Next Hop IP for workloads within this VNet**: This setting lets you deploy NVAs and other workloads into the same VNet without forcing all the traffic through the NVA. This setting can only be configured when you're configuring a new connection. If you want to use this setting for a connection you've already created, delete the connection, then add a new connection.
    * **Propagate static route**: This setting is currently being rolled out. This setting lets you propagate static routes defined in the **Static routes** section to route tables specified in **Propagate to Route Tables**. Additionally, routes will be propagated to route tables that have labels specified as **Propagate to labels**. These routes can be propagated inter-hub, except for the default route 0/0. **This feature is in the process of rolling out. If you need this feature enabled please open a support case**
-   * 
+   
 1. Once you've completed the settings you want to configure, click **Create** to create the connection.