Open lbimsft opened 1 month ago
@lbimsft Thank you for bringing this to our attention. I've delegated this to content author, who will review it and offer their insightful opinions.
Hi @TPavanBalaji @lbimsft,
The Seamless Gateway Migration tool today, will only support PowerShell and it does hold both the old prefix and the new prefix. Due to this being a known issue, the ExpressRoute Gateway team is currently working on a fix/enhancement where customers will no longer need to create a second prefix, enabling a seamless migration with just a single prefix. Our current ETA for this enhancement will be end of Sept.
Hello Team,
Regarding to expressroute gateway migration doc: https://learn.microsoft.com/en-us/azure/expressroute/expressroute-howto-gateway-migration-portal
Currently it only provide ps command to add second prefix on gateway subnet. do we have any plan to do it from portal? Also this new added second prefix is not visible and only observe old first prefix on gateway subnet from portal. do we have any plan to make it visible from portal?
The old expressroute gateway is deleted after click "commit migration“. but the old first prefix still exist on gateway subnet and from portal it still showing the old first prefix on gateway subnet. could you please update the doc to provide the ps commands how to remove this old first prefix on gateway subnet? or we can integrate this step to "commit migration" stage? or we still need to keep both prefixes?
Best Regards, Vincent
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.