How to move custom domain from classic Azure Frontdoor to new Frontdoor Standard/Premium

Question

We have a classic Frontdoor where we have mapped a custom domain. We have now created a new Frontdoor Premium where we would like to move this custom domain.

I was hoping that I could just add this domain to the new Frontdoor, verify it by adding TXT records to our dns, and then changing the CName to point to the new Frontdoor. Unfortunately when I try to the add the domain we get the following error:

How can we

1. Find out what the actual problem is?
2. Is there a guide on how to migrate domains?

Answer 1

@Mathias Rönnlund Thank you for reaching out to Microsoft Q&A. I understand that you are having issues migrating your custom domain to the new Frontdoor i.e., Standard/premium from your old classic FD and have issues with the same. Can you confirm if you had deleted the older FD before you tried to configure the above? You cannot have 2 endpoints with the same domain name.

Please let us know if you have any further questions and we will be glad to assist you further. Thank you!

Remember:

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

Want a reminder to come back and check responses? Here is how to subscribe to a notification.

Answer 2

The current Front door is a production system so we cannot delete it before we have it setup in a new Front door.

This is the setup that is needed and how it's done if we can create the custom domain:

1. Create custom domain in new Front door Premium
2. Get the key/value from Front door needed for TXT record needed for validation
3. Add the TXT record to our dns
4. Validate the domain in new Front Door
5. Add the new custom domain to the needed routes in new Front door
6. Change the current DNS record by changing the cname record to point to the new Front door instead of the old

With the above steps we can move a domain without any downtime.

Answer 3

@Mathias Rönnlund

One of the limitations of Front Door currently is that a host cannot be added to the new Frontdoor if it already exists in the old.
The only way to move a host without downtime currently, is to route the traffic to the origin or another CDN, delete the host from old frontdoor and add it to the new frontdoor. Once Frontdoor Standard/Premium goes available (since it is currently in preview), we'd support a migration workflow to migrate from Microsoft CDN or Frontdoor Classic to Frontdoor Standard/Premium without downtime.

Hope this helps. Please let us know if you have any further questions and we will be glad to assist you further. Thank you!

Remember:

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

Want a reminder to come back and check responses? Here is how to subscribe to a notification.

Answer 4

Following up on this now that Premium is GA. What is the migration path to move a domain from FD Classic to an EXISTING FD Premium instance. The current implementation will not allow pre-configuration of the domain as long as it is still attached to the old FD Classic.

This is a big problem for us as we migrate away from classic and consolidate FD instances. Is there a better solution if we migrate the classic instance to premium (in place migration)... premium -> existing premium migration of a domain? I think we run into the same problem no matter what.

Re-routing directly to the host remove the SSL/TLS cert provided by FD. Any suggestions or possible solutions for how to manage this migration?