We’re excited to announce that we are making this a lot easier with our preview of Autopilot. With Autopilot, Azure Cosmos DB will automatically manage and scale the RU/s of your containers based on the usage. This eliminates the need for custom scripting to change RU/s and makes it easier to handle bursty, unpredictable workloads.
You can try out Autopilot in your Cosmos accounts by going to the Azure Portal and enabling the feature in the “Preview Features” blade.
Thanks for your suggestion. Currently, we don’t have anything planned in changing our billing meter from hour to minute. But will leave this request open and will include this in future planning discussions for our roadmap.
Thank you for your suggestion.Anonymous commented
1. Pricing Granularity per Minute instead of per Hour
2. GROUP BY is a MUST!!!
there are my two top reasons I am not using CosmosDB
For this we recommend using Azure Search. This is not on our roadmap. If that ever changes we will reopen this item.
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
We are evaluating this feature ask. However, it is not on our immediate roadmap.
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.Anonymous commented
"Static websites is on our backlog" up to now I am waiting 7 years for default object and 404Error return custom object when not exists!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.
I have 14 years until I got my pension.
Hope I do one project with Azure, I have already with Rackspace and Amazon
This is an interesting idea. The ask is currently on our backlog and will be prioritized accordingly. It is unlikely to happen in the coming year due to other priorities, however we will update when the status changes.
Thank you for your feedback. Providing this functionality is on our backlog but there is no ETA we can share at this time. We will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.
While this feature is under review, Shared Access Signatures (http://blogs.msdn.com/b/windowsazurestorage/archive/2012/06/12/introducing-table-sas-shared-access-signature-queue-sas-and-update-to-blob-sas.aspx) can be used to specify exact permissions for a table, partition, or entity, and distribute those to calling applications. Using this can reduce the risk of accidental deletions.
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.