How can we improve Azure CDN?

Custom domain HTTPS support for Azure CDN from Verizon

Custom domain HTTPS supported for Azure CDN from Verizon profiles.

3,301 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Chris Pietschmann shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
completed  ·  Anton Kucer [MSFT] responded  · 

This is now generally available for Azure CDN from Verizon profiles. See the following blog post for details: https://azure.microsoft.com/en-us/blog/announcing-custom-domain-https-support-with-azure-cdn/.

Use the following request to vote for this support for Azure CDN from Akamai profiles – https://feedback.azure.com/forums/169397-cdn/suggestions/18013657-custom-domain-https-support-for-azure-cdn-from-aka.

180 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    The domain validation step is preposterous. My CNAME is already pointing to Verizon CDN - and still it's already almost 24 hours since it began verifying something - and still is. Verifying what exactly? Why can't I load my TLS certificate instead?

  • Anonymous commented  ·   ·  Flag as inappropriate

    Now I am stuck on the "Domain validation
    We have sent you an email asking you to validate the domain ownership. Waiting for your confirmation." May i know which email they will send to?

  • brendan commented  ·   ·  Flag as inappropriate

    This is NOT practical for production live environments. We should be able to bring our own SSL certificates instead of relying on a nebulous behind the curtains operation that takes up to 6 hours to execute. How am I supposed to cut over a CNAME record if I'm using it for another CDN already?? Azure requires you to create a custom domain within an endpoint before requesting for the SAN cert creation.... The problem with this is that custom domain creation requires a CNAME to point to the Azure CDN endpoint. This means I would have to cut over and experience downtime of up to 6 hours?! this is not well thought out one bit. Terrible.

  • RobDavey commented  ·   ·  Flag as inappropriate

    Thanks Nate. Mine seems to be enabled now too.

    Its seems like it takes around 12 hours to enable from the point when you verify the email.

    To all Please ensure you have access to admin@<yourdomain>.com before enabling so you can verify the email that is sent for verification.

    I think there needs to be some documentation for this from Microsoft.

  • Nate commented  ·   ·  Flag as inappropriate

    Mine is working this morning it seems. My registrar email owner must have taken care of it this morning! Woohoo! Seems like a weird process rather than just selecting a cert like in Web Apps? Oh well, seems to be good!

  • RobDavey commented  ·   ·  Flag as inappropriate

    I see this this has now been enabled. Has anyone managed to get this working. I received and confirmed my verification email but the request to enable is still processing several hours later.

  • Corey Deli commented  ·   ·  Flag as inappropriate

    Not sure why this isn't a thing or why no one seems to be giving any updates but this something that should have been shipped from the start.

  • Matt Hammond commented  ·   ·  Flag as inappropriate

    It is currently Q5 CY16. Would it be possible to at least get an updated date for this?

← Previous 1 3 4 5 8 9

Feedback and Knowledge Base