You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/expressroute/gateway-migration.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,9 @@ The guided gateway migration experience supports the following scenarios:
40
40
- Migrating from a non-Az-enabled SKU with a Basic IP to a non-Az-enabled SKU with a Standard IP.
41
41
- Migrating from a non-Az-enabled SKU with a Basic IP to an Az-enabled SKU with a Standard IP.
42
42
43
-
Learn how to [migrate using the Azure portal](expressroute-howto-gateway-migration-portal.md).
43
+
If you have a ExpressRoute gateway deployed in the same virtual network as a VPN Gateway, you can use the ExpressRoute Gateway migration tool. There is no expected impact to VPN Gateway traffic during this process.
44
+
45
+
Learn how to [migrate using the Azure portal](expressroute-howto-gateway-migration-portal.md).
44
46
Learn how to [migrate using PowerShell](expressroute-howto-gateway-migration-powershell.md).
45
47
46
48
For enhanced reliability and high availability, we recommend migrating to an Az-enabled SKU.
0 commit comments