We’re working on a solution for auth extensibility. We’ll provide some more detail once we have something more concrete to share.
- Matthew, Azure Functions team
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 email@example.com.
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.
This work is in progress, tooling is currently in Preview. See https://aka.ms/functionsvstools for more!
Our apologies for not updating this ask earlier. Static websites is on our backlog. This feature will include more detailed error messages as well as support for a default Storage Blob. As soon as we have updates to share on Static Websites we will do so. For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.
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
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.
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!