review update

duongau · duongau · commit 8d889988cdf1 · 2025-03-31T14:06:46.000-07:00
diff --git a/articles/expressroute/expressroute-howto-gateway-migration-portal.md b/articles/expressroute/expressroute-howto-gateway-migration-portal.md
@@ -7,70 +7,58 @@ author: duongau
 ms.service: azure-expressroute
 ms.custom: ignite-2023, devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 04/26/2024
+ms.date: 03/31/2025
 ms.author: duau
 ---
 
 # Migrate to an availability zone-enabled ExpressRoute virtual network gateway in Azure portal
 
-When you create an ExpressRoute virtual network gateway, you need to choose the [gateway SKU](expressroute-about-virtual-network-gateways.md#gateway-types). If you choose a higher-level SKU, more CPUs and network bandwidth are allocated to the gateway. As a result, the gateway can support higher network throughput and more dependable network connections to the virtual network. 
-
-The following SKUs are available for ExpressRoute virtual network gateways:
-
-* Standard
-* HighPerformance
-* UltraPerformance
-* ErGw1Az
-* ErGw2Az
-* ErGw3Az
-* ErGwScale (Preview)
+When creating an ExpressRoute virtual network gateway, you must select a [gateway SKU](expressroute-about-virtual-network-gateways.md#gateway-types). Higher-level SKUs allocate more CPUs and network bandwidth, enabling the gateway to support higher throughput and more reliable connections to the virtual network.
 
 ## Prerequisites
 
-- Review the [Gateway migration](gateway-migration.md) article before you begin.
-- You must have an existing [ExpressRoute Virtual network gateway](expressroute-howto-add-gateway-portal-resource-manager.md) in your Azure subscription.
+- Review the [gateway migration](gateway-migration.md) article before starting.
+- Ensure you have an existing [ExpressRoute virtual network gateway](expressroute-howto-add-gateway-portal-resource-manager.md) in your Azure subscription.
 
-## Migrate to a new gateway in Azure portal
+## Steps to migrate to a new gateway in Azure portal
 
-Here are the steps to migrate to a new gateway in Azure portal.
+Follow these steps to migrate to a new gateway using the Azure portal:
 
+1. Navigate to your **Virtual Network Gateway** resource in the [Azure portal](https://portal.azure.com/).
 
-1. In the [Azure portal](https://portal.azure.com/), navigate to your Virtual Network Gateway resource.
+1. In the left-hand menu under **Settings**, select **Gateway SKU Migration**.
 
-1. the left-hand menu under *Settings*, select **Gateway SKU Migration**.
+1. Select **Validate** to check if the gateway is ready for migration. A list of prerequisites will be displayed. If any prerequisites are unmet, validation fails, and migration can't proceed.
 
-1. Select **Validate** to check if the gateway is ready for migration. You'll first see a list of prerequisites that must be met before migration can begin. If these prerequisites aren't met, validation fails and you can't proceed. 
+    :::image type="content" source="media/gateway-migration/validate-step.png" alt-text="Screenshot of the validate step for migrating a virtual network gateway." lightbox="media/gateway-migration/validate-step.png":::
 
-    :::image type="content" source="media/gateway-migration/validate-step.png" alt-text="Screenshot of the validate step for migrating a virtual network gateway."lightbox="media/gateway-migration/validate-step.png":::
+1. Once validation succeeds, proceed to the **Prepare** stage. A new virtual network gateway is created. Under **Virtual Network Gateway Details**, provide the following information:
 
-1. Once validation is successful, you enter the *Prepare* stage. Here, a new Virtual Network gateway is created. Under **Virtual Network Gateway Details**, enter the following information.
-    
-    :::image type="content" source="media/gateway-migration/gateway-prepare-stage.png" alt-text="Screenshot of the Prepare stage for migrating a virtual network gateway."lightbox="media/gateway-migration/gateway-prepare-stage.png":::
+    :::image type="content" source="media/gateway-migration/gateway-prepare-stage.png" alt-text="Screenshot of the Prepare stage for migrating a virtual network gateway." lightbox="media/gateway-migration/gateway-prepare-stage.png":::
 
-    | Setting | Value |
-    | --------| ----- |
-    | **Gateway Name** | Enter a name for the new gateway. |
-    | **Gateway SKU** | Select the SKU for the new gateway. |
-    | **Public IP Address** | Select **Add new**, then enter a name for the new public IP, select your availability zone, and select **OK** |
+    | Setting              | Value                                                                 |
+    |----------------------|-----------------------------------------------------------------------|
+    | **Gateway name**     | Enter a name for the new gateway.                                    |
+    | **Gateway SKU**      | Select the SKU for the new gateway.                                  |
+    | **Public IP address**| Select **Add new**, provide a name for the new public IP, choose an availability zone, and select **OK**. |
 
     > [!NOTE]
-    > Be aware that your existing Virtual Network gateway will be locked during this process, preventing any creation or modification of connections to this gateway.
-
-1. Select **Prepare** to create the new gateway. This operation could take up to 45 minutes.
+    > During this process, your existing virtual network gateway is locked, preventing the creation or modification of connections.
 
-1. After the new gateway is created, you'll proceed to the *Migrate* stage. Here, select the new gateway you created. In this example, it's **myERGateway_migrated**. This transfers the settings from your old gateway to the new one. All network traffic and data path connections from your old gateway will transfer without any interruptions. To start this process, select **Migrate Traffic**. This operation could take up to 5 minutes.
+1. Select **Prepare** to create the new gateway. This operation can take up to 45 minutes.
 
-    :::image type="content" source="media/gateway-migration/migrate-traffic-step.png" alt-text="Screenshot of migrating traffic for migrating a virtual network gateway."lightbox="media/gateway-migration/migrate-traffic-step.png":::
+1. After the new gateway is created, proceed to the **Migrate** stage. Select the new gateway (for example, **myERGateway_migrated**) to transfer settings from the old gateway to the new one. All network traffic and data path connections transfer without interruptions. Select **Migrate Traffic** to start the process. This step can take up to 5 minutes.
 
-1. After the traffic migration is finished, you'll proceed to the *Commit* stage. In this stage, you finalize the migration, which involves deleting the old gateway. To do this, select **Commit Migration**. This final step is designed to occur without causing any downtime. 
+    :::image type="content" source="media/gateway-migration/migrate-traffic-step.png" alt-text="Screenshot of migrating traffic for migrating a virtual network gateway." lightbox="media/gateway-migration/migrate-traffic-step.png":::
 
-    :::image type="content" source="media/gateway-migration/commit-step.png" alt-text="Screenshot of the commit step for migrating a virtual network gateway."lightbox="media/gateway-migration/commit-step.png":::
+1. Once traffic migration is complete, proceed to the **Commit** stage. Finalize the migration by deleting the old gateway. Select **Commit Migration** to complete this step without downtime.
 
+    :::image type="content" source="media/gateway-migration/commit-step.png" alt-text="Screenshot of the commit step for migrating a virtual network gateway." lightbox="media/gateway-migration/commit-step.png":::
 
->[!IMPORTANT]
-> - Before running this step, verify that the new virtual network gateway has a working ExpressRoute connection and validate if the traffic is flowing through the new connection.
-> - When migrating your gateway, you can expect possible interruption for a maximum of 30 seconds.
-> - Once committed, the connection name can't be changed and has to be deleted and recreated if you want to change the connection naming. Reach out to Azure support in case of any issues.
+> [!IMPORTANT]
+> - Before committing, verify that the new virtual network gateway has a working ExpressRoute connection and confirm traffic is flowing through the new connection.
+> - Expect a possible interruption of up to 30 seconds during migration.
+> - Once committed, the connection name can't be changed. To rename the connection, it must be deleted and recreated. Contact Azure support for assistance if needed.
 
 ## Next steps
 
