How do I change Azure CDN from Verizon to Microsoft without downtime?

Question

I'm on the Azure CDN from Verizon. I want to move to Microsoft's CDN offering, because Verizon doesn't handle brotli compression properly.

I need to keep using the same domain. So my Verizon CDN is currently on the domain cdn.mydomain.com, and I want to set up a Microsoft CDN using that same domain.

I've set up a Microsoft CDN in Azure. If I try to add "cdn.mydomain.com", it complains that it cant find a the expected CNAME record for that domain. Of course, the current CNAME record points to the Verizon CDN.

If I go ahead and change the CNAME record for "cdn.mydomain.com" to point the Microsoft CDN, there will be effectively be a downtime from the time I change the CNAME record to the time the Microsoft CDN has been able to verify the ownership of the domain. Last time I tried, this verification process can took about 30 minutes, from what I read it can take up to an hour. If it takes 1 hour, that's 1 hour of downtime.

How can I work around this so I avoid the downtime? Are there alternative ways of verifying that I own the domain, other than changing the CNAME record?

Answer 1

@Lars , You should be able to achieve this using "cdnverify.<custom-domain-name>". Here is a doc explaining about mapping the temporary cdnverify subdomain with our production custom domain.

Add this CNAME entry into your domain registerer list,

Once you've added this, you'll have to wait for some time due to DNS propagation before you verify your custom domain. If done with all the configuration and verification needed for your new CDN endpoint, that's where you can now point the actual CNAME record of your DNS to your new CDN hostname that will be used in production. Once you do this, it's now safe to delete the CNAME record with cdnverify subdomain.

----------

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