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.Itay Shakury commented
Thanks for making the suggestion.
This can be done by either opening a port on your VNET, using a Service Bus Relay endpoint, or installing Hybrid Connector.
This is on the roadmap. We want to carefully design this to make sure data is not deleted accidentally.
We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.
After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.
We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.
Thanks for your continued feedback,
-Adam (Azure Billing Team)
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Azure Search Product Team
This item has been marked as Started by mistake. We don’t have a short-term plan to deliver this feature but it is on our roadmap.
We have recently added support for OSS APIs like MongoDB and Gremlin, so that you have the freedom of choice among cloud providers and programming APIs, while taking advantage of Azure Cosmos DB’s capabilities like SLAs, global distribution, and predictable performance.