Custom Domain with My Own Certificate on Azure Premium Verizon CDN still serving *.azureedge.net Certificate

Question

I rebuilt my CDN Endpoints from ADN to General Web Delivery yesterday, and reapplied my Custom Domain and My Own Certificate from our keyvault secrets.

This as rolled out successfully according to the portal, and is showing as "Completed", however browsing to the site shows an Invalid Certificate Error as the CDN is still sending the original *.azureedge.net certificate even 12 hours after the deployment.

I've tried purging the content, but this doesn't seem to have affected the certificate being served. Is there anything else I can try?

This is on an Azure Premium Verizon CDN endpoint, using General Web Delivery.

Answer 1

After waiting for another 6 hours, and having some other issues with our CSP support team, I gave up, removed the custom certificate and domain name, waited another 6 hours, re-added the domain name, waited another 6 hours and re-added the certificate.

All now seems to be back in working order. Moral of the story: patience is a virtue.