freshness graphics updates

cherylmc · cherylmc · commit 67a8b6b35229 · 2024-03-12T13:34:30.000-04:00
diff --git a/articles/vpn-gateway/active-active-portal.md b/articles/vpn-gateway/active-active-portal.md
@@ -5,7 +5,7 @@ description: Learn how to configure active-active virtual network gateways using
 author: cherylmc
 ms.service: vpn-gateway
 ms.topic: how-to
-ms.date: 07/22/2021
+ms.date: 03/12/2024
 ms.author: cherylmc
 
 ---
@@ -17,20 +17,20 @@ This article helps you create highly available active-active VPN gateways using
 To achieve high availability for cross-premises and VNet-to-VNet connectivity, you should deploy multiple VPN gateways and establish multiple parallel connections between your networks and Azure. See [Highly Available cross-premises and VNet-to-VNet connectivity](vpn-gateway-highlyavailable.md) for an overview of connectivity options and topology.
 
 > [!IMPORTANT]
-> The active-active mode is available for all SKUs except Basic or Standard. For more information, see [Configuration settings](vpn-gateway-about-vpn-gateway-settings.md#gwsku).
+> The active-active mode is available for all SKUs except Basic or Standard. See [About Gateway SKUs](about-gateway-skus.md) article for the latest information about gateway SKUs, performance, and supported features.
 >
 
-The steps in this article help you configure a VPN gateway in active-active mode. There are a few differences between active-active and active-standby modes. The other properties are the same as the non-active-active gateways. 
+The steps in this article help you configure a VPN gateway in active-active mode. There are a few differences between active-active and active-standby modes. The other properties are the same as the non-active-active gateways.
 
 * Active-active gateways have two Gateway IP configurations and two public IP addresses.
 * Active-active gateways have active-active setting enabled.
 * The virtual network gateway SKU can't be Basic or Standard.
 
 If you already have a VPN gateway, you can [Update an existing VPN gateway](#update) from active-standby to active-active mode, or from active-active to active-standby mode.
 
-## <a name="vnet"></a>Create a VNet
+## <a name="vnet"></a>Create a virtual network
 
-If you don't already have a VNet that you want to use, create a VNet using the following values:
+If you don't already have a virtual network (VNet) that you want to use, create a VNet using the following values:
 
 * **Resource group:** TestRG1
 * **Name:** VNet1
@@ -67,7 +67,7 @@ You can see the deployment status on the Overview page for your gateway. After t
 
 ## <a name ="update"></a> Update an existing VPN gateway
 
-This section helps you change an existing Azure VPN gateway from active-standby to active-active mode, and from active-active to active-standby mode. When you change an active-standby gateway to active-active, you create another public IP address, then add a second gateway IP configuration. 
+This section helps you change an existing Azure VPN gateway from active-standby to active-active mode, and from active-active to active-standby mode. When you change an active-standby gateway to active-active, you create another public IP address, then add a second gateway IP configuration.
 
 ### Change active-standby to active-active
 
@@ -77,22 +77,20 @@ Use the following steps to convert active-standby mode gateway to active-active
 
 1. On the left menu, select **Configuration**.
 
-1. On the **Configuration** page, configure the following settings: 
+1. On the **Configuration** page, configure the following settings:
 
    * Change the Active-active mode to **Enabled**.
-   * Click **Create another gateway IP configuration**.
+   * Click **Add new** to add another public IP address. If you already have an IP address that you previously created that's available to dedicate to this resource, you can instead select it from the **SECOND PUBLIC IP ADDRESS** dropdown.
 
-   :::image type="content" source="./media/active-active-portal/configuration.png" alt-text="Screenshot shows the Configuration page.":::
+   :::image type="content" source="./media/active-active-portal/active-active.png" alt-text="Screenshot shows the Configuration page with active-active mode enabled." lightbox="./media/active-active-portal/active-active.png":::
 
-1. On the **Choose public IP address** page and either specify an existing public IP address that meets the criteria, or select **+Create new** to create a new public IP address to use for the second VPN gateway instance.
-
-1. On the **Create public IP address** page, select the **Basic** SKU, then click **OK**.
+1. On the **Choose public IP address** page and either specify an existing public IP address that meets the criteria, or select **+Create new** to create a new public IP address to use for the second VPN gateway instance. After you've specified the second public IP address, click **OK**.
 
 1. At the top of the **Configuration** page, click **Save**. This update can take about 30-45 minutes to complete.
 
 > [!IMPORTANT]
 > If you have BGP sessions running, be aware that the Azure VPN Gateway BGP configuration will change and two newly assigned BGP IPs will be provisioned within the Gateway Subnet address range. The old Azure VPN Gateway BGP IP address will no longer exist. This will incur downtime and updating the BGP peers on the on-premises devices will be required. Once the gateway is finished provisioning, the new BGP IPs can be obtained and the on-premises device configuration will need to be updated accordingly. This applies to non APIPA BGP IPs. To understand how to configure BGP in Azure, see [How to configure BGP on Azure VPN Gateways](bgp-howto.md).
-> 
+>
 
 ### Change active-active to active-standby
 
@@ -108,7 +106,7 @@ Use the following steps to convert active-active mode gateway to active-standby
 
 > [!IMPORTANT]
 > If you have BGP sessions running, be aware that the Azure VPN Gateway BGP configuration will change from two BGP IP addresses to a single BGP address. The platform generally assigns the last usable IP of the Gateway Subnet. This will incur downtime and updating the BGP peers on the on-premises devices will be required. This applies to non APIPA BGP IPs. To understand how to configure BGP in Azure, see [How to configure BGP on Azure VPN Gateways](bgp-howto.md).
-> 
+>
 
 ## Next steps
 
diff --git a/articles/vpn-gateway/media/active-active-portal/active-active.png b/articles/vpn-gateway/media/active-active-portal/active-active.png
diff --git a/includes/media/vpn-gateway-add-gw-pip-active-portal/pip-details.png b/includes/media/vpn-gateway-add-gw-pip-active-portal/pip-details.png
diff --git a/includes/vpn-gateway-add-gw-pip-active-portal-include.md b/includes/vpn-gateway-add-gw-pip-active-portal-include.md
@@ -1,24 +1,20 @@
 ---
- title: include file
- description: include file
- services: vpn-gateway
  author: cherylmc
  ms.service: vpn-gateway
  ms.topic: include
- ms.date: 07/16/2021
+ ms.date: 03/12/2024
  ms.author: cherylmc
- ms.custom: include file
 ---
-4. Specify in the values for **Public IP address**. These settings specify the public IP address object that gets associated to the VPN gateway. The public IP address is dynamically assigned to this object when the VPN gateway is created. For gateways that are not [zone-redundant](../articles/vpn-gateway/about-zone-redundant-vnet-gateways.md), the only time the Public IP address changes is when the gateway is deleted and re-created. It doesn't change across resizing, resetting, or other internal maintenance/upgrades of your VPN gateway.
+4. Specify in the values for **Public IP address**. These settings specify the public IP address object that gets associated to the VPN gateway. The public IP address is dynamically assigned to this object when the VPN gateway is created. For gateways that aren't [zone-redundant](../articles/vpn-gateway/about-zone-redundant-vnet-gateways.md), the only time the Public IP address changes is when the gateway is deleted and re-created. It doesn't change across resizing, resetting, or other internal maintenance/upgrades of your VPN gateway.
 
    :::image type="content" source="./media/vpn-gateway-add-gw-pip-active-portal/pip-details.png" alt-text="Screenshot of public IP address field.":::
 
      * **Public IP address**: Leave **Create new** selected.
      * **Public IP address name**: In the text box, type a name for your public IP address instance.
-     * **Assignment**: VPN gateway supports only Dynamic.
+     * **Assignment**: Static is selected automatically.
      * **Enable active-active mode**: Select **Enabled**.
      * **Second Public IP Address**: Select **Create new**.
      * **Public IP address name**: Name the second Public IP address.
-     * Leave **Configure BGP** as **Disabled**, unless your configuration specifically requires this setting. If you do require this setting, the default ASN is 65515, although this can be changed.
+     * Leave **Configure BGP** as **Disabled**, unless your configuration specifically requires this setting. If you do require this setting, the default ASN is 65515, but other ASNs can be used.
 5. Select **Review + create** to run validation.
 6. Once validation passes, select **Create** to deploy the VPN gateway.
diff --git a/includes/vpn-gateway-add-gw-portal-include.md b/includes/vpn-gateway-add-gw-portal-include.md
@@ -2,7 +2,7 @@
  author: cherylmc
  ms.service: vpn-gateway
  ms.topic: include
- ms.date: 01/17/2024
+ ms.date: 03/12/2024
  ms.author: cherylmc
 ---
 
diff --git a/includes/vpn-gateway-basic-vnet-rm-portal-include.md b/includes/vpn-gateway-basic-vnet-rm-portal-include.md
@@ -3,7 +3,7 @@ author: cherylmc
 ms.author: cherylmc
 ms.service: vpn-gateway
 ms.topic: include
-ms.date: 08/08/2023
+ms.date: 03/12/2024
 ---
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
