Just as a follow up - it seems to be behaving correctly consistently now (18-24 hours later) - I'm assuming the CDN takes time to propogate the right certificate to all endpoints, or something similar?
Inconsistent/invalid certificate sometimes being returned for custom sub domain on Aure CDN
I've recently set up the following on Azure:
Storage as a static web site (which uses a z33.....windows.net address to access it).
Azure CDN (which uses a <mysite>.azureedge.net address to access it)
Added a custom sub domain to the CDN (mysite.mydomain.org), with the CNAME mapped to the azureedge.net domain, and HTTPS is enabled with the CDN managed certificate option.
I'm having a problem when accessing the site over HTTPS using my custom sub domain, the certificate is often returned as the certificate for the *....windows.net domains instead of mysite.mydomain.org, and the browser obviously flags this as insecure because they don't match.
But if I leave it a few minutes and refresh the page, the correct certificate often then gets used and I can access the site without problems.
Accessing via the azure CDN or storage addresses always seems to return the right certificate - it's only the custom domain that has a problem.
Is there something I've missed setting this up?
If you need more details or there is any specific troubleshooting I can carry out, please let me know.