You can now use the Azure CDN to access blobs with custom domains over HTTPS. See the following article for instructions on how to do so: https://docs.microsoft.com/en-us/azure/storage/storage-https-custom-domain-cdn. Having talked to a number of customers, we concluded that this solution addresses many scenarios where the need for HTTPS access to blobs with custom domains exists.
Native Azure Storage support for using SSL to access blobs at custom domains is still on our backlog. We would love to hear about your scenarios where using the Azure CDN is not an acceptable solution, either by posting on this thread or sending us an email at email@example.com.
It's been 5 years since this idea was created!!!
Dear Storage Team,
This is getting ridiculous. Please implement >:(
I second the SAS link issue. This is NOT "completed".
Let's get this done, come on already!
This is so sorely needed!
This is a good idea. We’ll look at this later when we’re ready to start adding more bindings (likely after we GA).
This is really needed. More importantly a caching mechanism is required so that keyvault does not get overwhelmed with requests when function infinitely scales. (see discussion here: https://github.com/Azure/azure-webjobs-sdk/issues/746)
Renaming resource groups is treated like a resource move behind the scenes. We will address this feature request once resource move is broadly supported across the various services. We would not want to release a rename feature where some resources ended up in the “renamed” resource group, while others were left behind.
This work item is on our list.
Daria, Azure FunctionsDimka M shared this idea ·
I’m happy to share that work has officially started to enable HTTP/2 for App Service. We will share a more concrete timeline as it becomes available, but we are hoping for sometime later this year. We really appreciate your patience as we work through multiple dependencies that have to be met before we can fully support HTTP/2.
Yes, HTTP/2 would be very nice finally.