Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
ExpressRoute gateways created or connected to circuits before 2017 have limitations that affect performance. This guide provides step-by-step instructions to migrate from legacy gateway connections. These limitations include restricted bandwidth, inability to upgrade to higher bandwidth SKUs, and inability to migrate to zone-redundant gateways. Converting to newer connections is recommended to avoid lower throughput and potential connectivity loss.
To begin the conversion, you need to delete all existing connections associated with the identified gateway.
Sign in to the Azure portal.
Navigate to the virtual network gateway with legacy connections.
Identify and delete all existing connections. If you have multiple connections, delete each one individually, ensuring the previous connection is fully deleted before proceeding to the next.
Important
Ensure all connections are removed before recreating new connections.
For more information on how to delete connections, see Link a virtual network to ExpressRoute circuits (Portal, PowerShell, and CLI).
After deleting the connections, you can proceed to recreate them.
Create new connections from the ExpressRoute virtual network gateway.
Configure the new ExpressRoute connections based on the resiliency model of your previous connections.
Validate the new connections to ensure they're functioning correctly. Perform tests to verify that the connections are established and traffic is flowing as expected.
For more information on how to create connections, see Link a virtual network to ExpressRoute circuits (Portal, PowerShell, and CLI).
Note
ExpressRoute gateway connections that aren't converted by February 28, 2025, might experience potential connectivity loss.
To learn more about ExpressRoute redundant gateways, see About zone redundant virtual network gateway.