Allow domain verification without individual sub domain verification for HTTPS
Lets assume, I own company.com domain, it is a live website without CDN, and I have SSL certificate issued by some other company for www.company.com website. So it is live running somewhere else.
I would like to setup 'www.company.com'; CDN with HTTPS. There is no way I can do this without causing downtime to my already existing website because domain verification wants to map 'www.company.com'; to 'something.azureedge.net'. However, SSL on 'www.company.com'; will only be active after couple of hours or even days. Till the time all existing SSL connections to www.company.com will fail.
I should be able to verify my top level domain and I should be able to create www.company.com end point without actually mapping cname. Once I SSL is active on www.company.com I will then change my DNS zone to to point www.company.com to respective cname.
This scenario is already supported by using the intermediary “cdnverify” subdomain. See the following for information on this: https://docs.microsoft.com/en-us/azure/cdn/cdn-map-content-to-custom-domain#register-a-custom-domain-for-an-azure-cdn-endpoint-using-the-intermediary-cdnverify-subdomain