I’ve gotten a few questions about this item recently, so I just wanted to give a more detailed status. We still have this on the backlog; it hasn’t been forgotten. But we don’t have a clear timeline for when we would get to it right now. The “unplanned” status just means that it can’t be tied to a timeline, but we do think this is a valid request that we would like to have in the product.
Sortof agree with this, but simply validating tokens issued by my applications is fairly straight forward in a function, as long as the function has a signing key. -with RSA that should even just be a public key, so not that bad.
What would be really neat would be something like asp.net identity, only with bearer tokens and tablestorage, where i simply supply a few basic settings and configuration of endpoints (change password, password reset, get token, the usual account management stuff that we usually dont need to touch)
Rolling my own isnt really difficult, just tedius and not as easily reusable. (mostly because of the way we deploy to Functions right now, which for me has been writing code directly in the browser)
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 firstname.lastname@example.org.
Agree wholeheartedly with the last few comments, I also have a SPA and an API on Functions, and hope "BACKLOG" actually means it's a priority feature.
Putting a static site on App Service seems like a waste of money, but hopefully it will do OK with Cloudflare and an agressive caching strategy until this feature is ready.
Thank you for your feedback. We are currently in public preview of static website hosting for Azure Storage to enable this scenario. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview. The feature set includes support for default documents and custom error documents for HTTP status code 404.
For any further questions, or to discuss your specific scenario, send us an email at email@example.com.
This is simply a necessary feature for costeffective hosting of singlepage applications. unless ofcourse we like **** routes like [blobaddress]/index.html/#/[Something]/[SomethingElse]
Considering it's there in Google Cloud Storage AND Amazon AWS S3 it should make sense to make it here too.
I did in fact look into altertative ways to get the functionality (through a CDN) but no luck.
I guess there is no problem in hosting the singlepage application from Amazon or Google with a backend somewhere in Azure, but it just shouldn't be necessary
We are looking at options to enable this.
I actually bought one of those insanely overpriced App Service Certificates...
It doesnt work, I get a "Guest User Error" when i go to import it to a KeyVault. - their support person wasted my time (3 remote sessions where he just wanted me to run the same Powershell commands and email him the output.. 3 times... I didnt bother to keep entertaining that idiot.)
Just make them obsolete already and support a great service that will eventually make the internet a more secure place!
We understand this is a top customer ask and as such it is currently on our backlog to be prioritized. We will update when the status changes.
Hope the secondary index is still coming.
Azure Table Storage is an immensely powerful platform, and is already an exceptionally cost effective NoSQL database for certain kinds of applications.
Being able to add a secondary index would drastically reduce the complexity and the amount of redundant data in certain scenarios and would make an already awesome platform relevant for even more projects.
I too have used index tables to get secondary indicies and sometimes that would still be necessary to allow for efficient partitioning, but having a second index still seems like it would be very useful!