![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 90%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Azure ExpressRoute
An Azure service that provides private connections between Azure datacenters and infrastructure, either on premises or in a colocation environment.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 15%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPB%3C/text%3E%3C/svg%3E)
Hello Sheik Mohamed Yasar
I understand you have some questions regarding express route migration timing. Please review the information below for further clarification:
After the migration commit, a new public IP will be assigned to the newly created ExpressRoute Gateway. Will this change be reflected on the Service Provider (ISP) end as well?
To complete the migration process, follow these four steps and also in this process new express riute gateway will create. First, select Validate to confirm that the gateway is ready for migration. Once validation is complete, move to the second step, which is Prepare. In this step, enter the gateway name and gateway SKU. No new public IP needs to be added; Microsoft will manage the public IP, so your production public IP and connectivity will not be affected.
Check the below screen shot and public document:
https://v4.hkg1.meaqua.org/en-us/azure/expressroute/expressroute-howto-gateway-migration-portal
The expected downtime is mentioned as 45 minutes for new deployment and 15 minutes for migration. Is there a possibility that it might exceed this estimated downtime?
No, there will be no downtime during the new gateway deployment. While the new gateway is being deployed, your existing gateway will be locked, which prevents creating or modifying connections. However, you will not experience any network connectivity issues during this process.
After deploying the new gateway, proceed to the migration stage and select the new gateway to transfer settings from your old gateway. All network traffic and data path connections will be moved. Click Migrate Traffic to begin; this process may take up to 5 minutes. According to the document, you should experience downtime for only 5 minutes and not longer than that.
What are the potential risks involved in this migration process?
If any issues arise during the migration, is it possible to revert to the previous state?
If you encounter any issues during the migration, you can revert to the previous state in the "Prepare" step. Choosing "Abort" will prompt Azure to remove the new gateway and connections, allowing you to return to the original setup. However, after committing the migration, rolling back is no longer possible.
Kindly check the below public document for more understanding:
https://v4.hkg1.meaqua.org/en-us/azure/expressroute/expressroute-howto-gateway-migration-portal
https://v4.hkg1.meaqua.org/en-us/azure/expressroute/gateway-migration
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you.