Switch custom domain from one Frontdoor to another using afdverify

Question

I'm currently trying to transfer a custom domain (e.g. abc.constco.com) from a front door instance hosted in one subscription of my company to a different front door instance in a different subscription due to cost rollup reporting.

Following https://learn.microsoft.com/en-us/azure/frontdoor/front-door-custom-domain#map-the-temporary-afdverify-subdomain which talks about how to use a temporary afdverify subdomain when migrating to frontdoor to have 0 downtime, i've tried to a custom subdomain of 'afdverify.abc.constco.com' and the front door UI designer will not be able to find a DNS mapped to the frontdoor instance, and if I try to add the custom domain to the 2nd instance directly, it says there is another frontdoor instance already using that custom domain (which is accurate).

Is there any way to transfer that custom domain ownership between frontdoor instances with 0 downtime for a production level service?

Answer 1

@tyler morris , Appreciate your patience. The doc you were referring to states about adding custom domain to your FrontDoor that has been configured with CNAME to external registers like GoDaddy. As FrontDoor is globally available there should be unique frontend domain name across servers else it would result in a domain name conflict. AFAIK, there is no other method that can be implemented here to avoid zero downtime for migration of CD between FrontDoors. Migration and Propagation time are expected.

----------

Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.