Merge pull request #303331 from MekaylaMoore/patch-45

Update gateway-migration.md

Author: Stacyrch140

articles/expressroute/gateway-migration.md

@@ -99,6 +99,25 @@ You have up to 15 days to commit after migration preparation. Use this time to v
 
 Azure Advisor notifications will alert you if your gateway requires migration. Attempting to migrate an ineligible gateway will result in an error. For more details, see [Troubleshooting Gateway Migration](gateway-migration-error-messaging.md).
 
+### Can I roll back this change?
+Yes, until it is committed. The migration is composed of four major steps:​
+
+1. Validate – Confirms if your gateway is eligible for migration. ​
+No changes at this stage; nothing to roll back​
+
+2. Prepare – Creates a new Virtual Network Gateway with the desired configuration. ​
+The process can be aborted after step 2 and the new gateway will be deleted.​
+
+3. Migrate – Transfer the configuration from the existing gateway to the new one.​
+If needed, the configuration can be reverted to the existing gateway after step 3.​
+
+4. Commit – Finalize the migration by decommissioning the old gateway and its connections. ​
+Once the change has been committed, it can no longer be rolled back.
+
+### What is the traffic impact during migration? Is there packet loss or routing disruption?
+
+During the migration process, traffic is rerouted seamlessly. There is no expected packet loss or routing disruption under normal conditions.
+
 ## Next Steps
 
 - Troubleshoot migration  issues with [Troubleshooting Gateway Migration](gateway-migration-error-messaging.md).