Merge pull request #298620 from duongau/patch-24

ExpressRoute - Migration (add tip box)

Author: prmerger-automator[bot]

articles/expressroute/expressroute-howto-gateway-migration-portal.md

@@ -7,7 +7,7 @@ author: duongau
 ms.service: azure-expressroute
 ms.custom: ignite-2023, devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 03/31/2025
+ms.date: 04/22/2025
 ms.author: duau
 ---
 
@@ -20,6 +20,9 @@ When creating an ExpressRoute virtual network gateway, you must select a [gatewa
 - 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.
 
+> [!TIP]
+> You can now deploy two ExpressRoute gateways within the same virtual network. To do this, create a second ExpressRoute gateway with its admin state set to **disabled**. Once the second gateway is deployed, initiate the *Prepare* step in the migration tool. This step will establish the connection without redeploying the gateway, as it is already in place. Finally, run the *Migrate* step, which will change the new gateway's admin state to **_enabled_**, completing the migration process. This method minimizes the migration or maintenance window, significantly reducing downtime when transitioning from a non-zonal to a zone-redundant gateway.
+
 ## Steps to migrate to a new gateway in Azure portal
 
 Follow these steps to migrate to a new gateway using the Azure portal: