Merge pull request #291954 from cherylmc/images9

freshness

Author: v-shils

articles/vpn-gateway/media/vpn-gateway-howto-always-on-device-tunnel/cleanup.png

@@ -5,7 +5,7 @@ description: Learn how to use gateways with Windows 10 or later Always On to est
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 07/28/2023
+ms.date: 12/13/2024
 ms.author: cherylmc
 
 ---
@@ -27,7 +27,9 @@ Configure the VPN gateway to use IKEv2 and certificate-based authentication usin
 
 To remove the profile, run the following command:
 
-![Screenshot shows a PowerShell window that runs the command Remove-VpnConnection -Name MachineCertTest.](./media/vpn-gateway-howto-always-on-device-tunnel/cleanup.png)
+```azurepowershell-interactive
+Remove-VpnConnection -Name MachineCertTest
+```
 
 ## Next steps
 

articles/vpn-gateway/media/vpn-gateway-howto-aws-bgp/create-gw-bgp.png

@@ -6,7 +6,7 @@ author: cherylmc
 ms.author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: tutorial
-ms.date: 10/15/2024
+ms.date: 12/13/2024
 
 ---
 
@@ -49,9 +49,9 @@ You can use the following values for your BGP APIPA configuration throughout the
 | **AWS Tunnel 1 to Azure Instance 1** | 169.254.21.6 | 169.254.21.5 | 169.254.21.4/30 |
 | **AWS Tunnel 2 to Azure Instance 1** | 169.254.22.6 | 169.254.22.5 | 169.254.22.4/30 |
 
-You can also set up your own custom APIPA addresses. AWS requires a /30 **Inside IPv4 CIDR** in the APIPA range of **169.254.0.0/16** for each tunnel. This CIDR must also be in the Azure-reserved APIPA range for VPN, which is from **169.254.21.0** to **169.254.22.255**. AWS will use the first IP address of your /30 inside CIDR and Azure will use the second. This means you need to reserve space for two IP addresses in your AWS /30 CIDR.
+You can also set up your own custom APIPA addresses. AWS requires a /30 **Inside IPv4 CIDR** in the APIPA range of **169.254.0.0/16** for each tunnel. This CIDR must also be in the Azure-reserved APIPA range for VPN, which is from **169.254.21.0** to **169.254.22.255**. AWS uses the first IP address of your /30 inside CIDR and Azure uses the second. This means you need to reserve space for two IP addresses in your AWS /30 CIDR.
 
-For example, if you set your AWS **Inside IPv4 CIDR** to be **169.254.21.0/30**, AWS will use the BGP IP address **169.254.21.1** and Azure will use the IP address **169.254.21.2**.
+For example, if you set your AWS **Inside IPv4 CIDR** to be **169.254.21.0/30**, AWS uses the BGP IP address **169.254.21.1** and Azure uses the IP address **169.254.21.2**.
 
    > [!IMPORTANT]
    > * Your APIPA addresses must not overlap between the on-premises VPN devices and all connected Azure VPN gateways.
@@ -65,7 +65,9 @@ You must have both an Azure account and AWS account with an active subscription.
 
 ### Create a VNet
 
-Create a virtual network with the following values. You can refer to the steps in the [Site-to-site Tutorial](tutorial-site-to-site-portal.md).
+Create a virtual network. You can refer to the [Site-to-site Tutorial](tutorial-site-to-site-portal.md) for steps. 
+
+For this exercise, we use the following example values:
 
 * **Subscription**: If you have more than one subscription, verify that you're using the correct one.
 * **Resource group**: TestRG1
@@ -77,7 +79,9 @@ Create a virtual network with the following values. You can refer to the steps i
 
 ### Create an active-active VPN gateway with BGP
 
-Create a VPN gateway using the following values:
+In this section, you create active-active VPN gateway. You can refer to the [Site-to-site Tutorial](tutorial-site-to-site-portal.md) for steps. 
+
+For this exercise, we use the following example values:
 
 * **Name**: VNet1GW
 * **Region**: East US
@@ -94,29 +98,24 @@ Create a VPN gateway using the following values:
 * **SECOND PUBLIC IP ADDRESS**: Create new
 * **Public IP address 2 name**: VNet1GWpip2
 * **Availability zone**: Zone-redundant
-* **Configure BGP**: Enabled
-* **Autonomous system number (ASN)**: 65000
-* **Custom Azure APIPA BGP IP address**: 169.254.21.2, 169.254.22.2
-* **Second Custom Azure APIPA BGP IP address**: 169.254.21.6, 169.254.22.6
+* **BGP values**: When you configure BGP, pay attention to the following settings:
+
+  * Select **Enabled** for **Configure BGP** to show the BGP configuration section.
+  * Fill in a **ASN (Autonomous System Number)**. This ASN must be different than the ASN used by AWS.
 
-1. In the Azure portal, navigate to the **Virtual network gateway** resource from the Marketplace, and select **Create**.
-1. Fill in the parameters as shown in the following examples.
+    * **Example:** 65000
 
-   :::image type="content" source="./media/vpn-gateway-howto-aws-bgp/gateway-basics.png" alt-text="Screenshot shows top part of the virtual network gateway screen." lightbox="./media/vpn-gateway-howto-aws-bgp/gateway-basics.png" :::
-  
-1. Configure both Public IP addresses and enable active-active mode. The public IP address objects created here are associated to the VPN gateway. The public IP address is dynamically assigned to the object when the VPN gateway is created.
+  * Add two addresses to **Custom Azure APIPA BGP IP address**. Include the IP addresses for **AWS Tunnel 1 to Azure Instance 0** and **AWS Tunnel 2 to Azure Instance 0** from the [APIPA configuration you chose](#apipa-config). The second input will only appear after you add your first APIPA BGP IP address.
 
-   :::image type="content" source="./media/vpn-gateway-howto-aws-bgp/public-ip.png" alt-text="Screenshot shows PIP setting." lightbox="./media/vpn-gateway-howto-aws-bgp/public-ip.png" :::
+    * **Example:** 169.254.21.2, 169.254.22.2
 
-1. Configure BGP.
+  * Add two addresses to **Second Custom Azure APIPA BGP IP address**. Include the IP addresses for **AWS Tunnel 1 to Azure Instance 1** and **AWS Tunnel 2 to Azure Instance 1** from the [APIPA configuration you chose](#apipa-config). The second input will only appear after you add your first APIPA BGP IP address.
 
-    :::image type="content" source="./media/vpn-gateway-howto-aws-bgp/create-gw-bgp.png" alt-text="Screenshot shows BGP setting." lightbox="./media/vpn-gateway-howto-aws-bgp/create-gw-bgp.png" :::
+    * **Example:** 169.254.21.6, 169.254.22.6
 
-    * Select **Enabled** for **Configure BGP** to show the BGP configuration section.
-    * Fill in a **ASN (Autonomous System Number)**. This ASN must be different than the ASN used by AWS.
-    * Add two addresses to **Custom Azure APIPA BGP IP address**. Include the IP addresses for **AWS Tunnel 1 to Azure Instance 0** and **AWS Tunnel 2 to Azure Instance 0** from the [APIPA configuration you chose](#apipa-config). The second input will only appear after you add your first APIPA BGP IP address.
-    * Add two addresses to **Second Custom Azure APIPA BGP IP address**. Include the IP addresses for **AWS Tunnel 1 to Azure Instance 1** and **AWS Tunnel 2 to Azure Instance 1** from the [APIPA configuration you chose](#apipa-config). The second input will only appear after you add your first APIPA BGP IP address.
-1. Select **Review + create** to run validation. Once validation passes, select **Create** to deploy the VPN gateway. Creating a gateway can often take 45 minutes or more, depending on the selected gateway SKU. You can see the deployment status on the Overview page for your gateway.
+Select **Review + create** to run validation. Once validation passes, select **Create** to deploy the VPN gateway. Creating a gateway can often take 45 minutes or more, depending on the selected gateway SKU. You can see the deployment status on the **Overview** page for your gateway.
+
+To view the public IP addresses that are assigned to your gateway, go to your virtual network gateway in the portal and navigate to **Settings -> Properties**.
 
 ## <a name ="part-2"></a> Part 2: Connect to your VPN gateway from AWS
 
@@ -220,16 +219,12 @@ Repeat these instructions to create each local network gateway.
 1. Leave **IP Address** as the value for **Endpoint**.
 1. For **IP Address**, enter the **Outside IP Address** (from AWS) for the tunnel you're creating.
 1. Leave **Address Space** as blank and select **Advanced**.
-
-   :::image type="content" source="./media/vpn-gateway-howto-aws-bgp/create-lng.png" alt-text="Screenshot shows local network gateway basics page." :::
 1. On the **Advanced** tab, configure the following settings:
 
    * Select **Yes** for **Configure BGP settings**.
    * For **Autonomous system number (ASN)**, enter the ASN for your AWS Virtual Private Network. Use the ASN **64512** if you left your ASN as the AWS default value.
    * For **BGP peer IP address**, enter the AWS BGP Peer IP Address based on the [APIPA configuration you chose](#apipa-config).
 
-   :::image type="content" source="./media/vpn-gateway-howto-aws-bgp/lng-bgp.png" alt-text="Screenshot shows values for your local network gateway BGP settings." :::
-
 ### <a name ="create-azure-connections"></a> Create connections
 
 Repeat these steps to create each of the required connections.

articles/vpn-gateway/media/vpn-gateway-howto-aws-bgp/create-lng.png

@@ -22,7 +22,7 @@ You might experience the problem that a new or existing Microsoft Azure Site-to-
 Check the type of Azure  virtual network gateway:
 
 1. Go to [Azure portal](https://portal.azure.com).
-2. Check the **Overview** page of the virtual network gateway for the type information.
+2. Check the **Overview** page of the virtual network gateway to verify the **Type**. Example: Route-based.
 
     ![The overview of the gateway](media/vpn-gateway-troubleshoot-site-to-site-disconnected-intermittently/gatewayoverview.png)