diff --git a/articles/expressroute/expressroute-howto-gateway-migration-portal.md b/articles/expressroute/expressroute-howto-gateway-migration-portal.md
index b1a122d6b4009..7e144d781e35b 100644
--- a/articles/expressroute/expressroute-howto-gateway-migration-portal.md
+++ b/articles/expressroute/expressroute-howto-gateway-migration-portal.md
@@ -43,7 +43,6 @@ Follow these steps to migrate to a new gateway using the Azure portal:
     |--|--|
     | **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]
     > During this process, your existing virtual network gateway is locked, preventing the creation or modification of connections.
@@ -66,4 +65,4 @@ Follow these steps to migrate to a new gateway using the Azure portal:
 ## Next steps
 
 * Learn more about [designing for high availability](designing-for-high-availability-with-expressroute.md).
-* Plan for [disaster recovery](designing-for-disaster-recovery-with-expressroute-privatepeering.md) and [using VPN as a backup](use-s2s-vpn-as-backup-for-expressroute-privatepeering.md).
\ No newline at end of file
+* Plan for [disaster recovery](designing-for-disaster-recovery-with-expressroute-privatepeering.md) and [using VPN as a backup](use-s2s-vpn-as-backup-for-expressroute-privatepeering.md).