We have just released integration with API management as there is a consumption plan. Please review https://docs.microsoft.com/en-us/azure/azure-functions/functions-openapi-definition to see if this meets your needs.
3 votes0 comments · Azure Monitor- Alert Management » API and Integrations · Flag idea as inappropriate… · Admin →
We don’t have plans for this currently, but please keep the votes coming!
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.Bjørn commented
Once support for SSL and custom domains have been added, we also need automatic redirect from any http requests to https to provide the best possible experience for users that access static web sites hosted in storage (or the option to turn it on)
For any questions, please reach out to us at AskCosmosDB@microsoft.comBjørn commented
In App Service Plan it is possible to configure auto scaling. I would like the same capability in CosmosDB. I.e. I could set a lower and upper RU/s and if throttling was about to occur, Cosmos DB could instead increase RU/s until the upper limit was reached or throughput was met. And Cosmos would also automatically lower RU/s if traffic is low.
Push to web is on our roadmap and we will update once we have a more concrete ETA.
This is not on our roadmap and we have no plans for it long term.
Thank you for your suggestion.
This is currently not on our roadmap. However, we will continue to review this item in the future as we prioritize future releases.
Thank you for your suggestion and for the comments.
At this point our recommendation is to move resources into a new Resource Group with the new name.