Depending on the average amount of incomming requests/ required RU's, (or other parameters,)
I would like to autoscale the througput(RU/s) of a collection.1,851 votes
We have now released autoscale for general availability.
Thank you everyone for your comments and votes. We are very excited to release this feature for all of you.
It would be great if we could deploy sprocs from visualstudio.com as we can with Azure Functions or Azure Web Sites.79 votes
This is now complete. Customers can deploy Cosmos DB stored procedures, triggers and UDF’s from an ARM template. For an example see here.
When looking to migrate our alerting (deployed in ARM templates) to the new alerting platform the throttled request metric is not available when configuring an alert for Cosmos DB resources, we currently have a classic alert using this metric. I have attempted to use an alert based on 'Total Requests' filtering for response code 429 but this doesn't seem to behave the same as the existing Classic alert (maybe due to the only available setting for 'timeAggregation' being 'Count'). Having logged a support request it was suggested I make a request here.24 votes
Marking as completed with the response below.
We can enable locks at Resource level to make sure Cosmos DB is not deleted. Currently it will still allow the admin to delete the Database and delete the collection under the db. It will be nice to lock the DB and Collection as well. So in Production Environment we can enable these locks to make sure they are not deleted by anyone.11 votes
Update on this.
We do currently support this capability, even down to database and container level resources. This capability is available in CLI or PoweShell. To enable this you need to include the full resource URI for the resource to be locked.
Below is a sample for how to enable this using CLI.
Lock a database resource (using MongoDB API as an example).
az lock create —name myDatabaseLock —lock-type CanNotDelete —resource-type Microsoft.DocumentDB/databaseAccounts —parent databaseAccounts/mycosmosaccount —resource mydatabase —resource-group myResourceGroup
Lock a collection level resource (also MongoDB API example).
az lock create —name myCollectionLock —lock-type CanNotDelete —resource-type Microsoft.DocumentDB/databaseAccounts —parent databaseAccounts/mycosmosaccount —resource myDatabase/collections/myCollection —resource-group myResourceGroup
Thank you and hope this is helpful.
When a PCI scan was run on our public cosmos end point it raised an exception since TLS 1.0 has not been decommissioned.
Can there be a button on the portal to only support TLS 1.2?
This feature is now available to customers. We are currently rolling this out.
We will be making a public announcement around this support.
Customers using TLS 1.1 will continue to do so but customers may opt-in to enforcing TLS 1.2. To do so customers will need to contact support.
Customers wishing for this can do so today.
Please add feature that can check the time when container created, when auto back up stored, when auto back up will be stored.
Please add feature that can check the time when container created, when auto back up stored, when auto back up will be stored.1 vote
Customers now have the ability to get diagnostic logs on Control Plane requests. Please see this article for details.
- Don't see your idea?