@danbord Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

I must be missing something, if I navigate to [mystaticwebcdn].azureedge.net I get an error:

InvalidQueryParameterValue
Value for one of the query parameters specified in the request URI is invalid. RequestId:75f0f848-601e-0013-6123-a4aff5000000 Time:2019-01-04T11:52:05.9894406Z
comp

I have to add the explicit file to the url: [mystaticwebcdn].azureedge.net$web/default.html

It doesn't seem to respect the index page and 404 page I set in the azure config.

I was able to fix this by going into my CDN endpoint and updating the origin type from "Storage" to "Custom Origin" and setting my origin hostname and origin host header to my x.z.web.core.windows.net URL instead of the x.blob.core.windows.net URL.

Nice one @awickham10 that was the trick, thanks.
As @danbord said, it took a while to propagate, but it seems to work fine.

@awickham10 Having the same problem. In your example x.z.web.core.windows.net which part is your custom domain? Is it x.z.web or just x.z? Thanks

I used the Custom Origin option and the hostname from the Storage Account > Static Website > Primary Endpoint which is x.z.web.core.windows.net instead of the x.blob.core.windows.net URL you get when using an origin type of Storage.

Hopefully that helps.

Did the trick for me too. Thanks

@danbord @awickham10 @bjthomson @smithsson68 @Djiit - Thanks for your feedback. We'll investigate this further and update the article as needed.

please-close

Why did you close the issue if it hasn't been resolved?

@awickham10 I just re-opened the case, i'll provide some feedback to the CDN team to update the documentation as appropriate.

@mdgattuso Would you be able to help with this issue ?

Thanks,
Adam

It looks like this documentation is owned by the storage team, so it needs to be assigned to someone from there.

However, you don't need to use the premium tier in order to use SSL. You can bring your own SSL cert on Azure CDN from Microsoft Standard, or use the CDN managed cert on any of the other tiers.

Setting Origin type and Origin host was indeed a bit vague in the docs. Took me a while to learn which values I had to use.

I used this page: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-https-custom-domain-cdn
The page mentions the Origin type setting, but doesn't mention the proper value of Origin host.

@normesta - FYI

Is microsoft planning to update the document?
Is azure testing the document they publish ?
It is not the firt time the they document are out of date even it is preview, actually does not work as the document.

I have add this configuration in godaddy provider,

Type Name Value
CNAME * urlstaticlorenzo.azureedge.net
CNAME cdnverify.www.lorenzo.com cdnverify.urlstaticlorenzo.azureedge.net
CNAME www urlstaticlorenzo.azureedge.net

The step in order to add ssl, is not as the document describes, but actually already was able to add https, but I have not been able to reach www.lorenzobrito.com

@lorenzobrito - Yes, we are working on updating the document, thanks for your feedback.

Thanks, all, for your feedback and your patience. I have updated the doc and hopefully it is more clear now. Please don't hesitate to open another issue if you encounter problems.

@normesta - FYI

please-close

Looks good!

Regarding to map to custom domain , i have follow the custom configuration and still not working.

@lorenzobrito Can you please open a new issue as we believe the original issue was resolved. This will help us to ensure we give the issue you are encountering the visibility that it deserves.

@danbord We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.