New in documentation for December 2020

Nikisha Reyes-Grange

Online technical documentation is regularly published and updated to help you get the most out of Azure Cosmos DB.  Here’s a round-up of the most recent releases, published in the last two months:

Resource locks

Admins can use PowerShell or Azure CLI to apply locks that stop users from changing or deleting resources in an account, database, or container. See documentation

Troubleshoot exceptions with Azure Cosmos DB Java SDK v4

  • Discover ways to diagnose and fix request timeout exceptions (the HTTP 408 error). See documentation
  • Find causes and solutions for service unavailable exceptions. See documentation.

Troubleshoot query issues for Azure Cosmos DB API for MongoDB

Find best practices to troubleshoot query issues when using the Azure Cosmos DB API for MongoDB, and performance tips to reduce latency and costs.  See documentation.


Create more complex string searches using metacharacters with the REGEXMATCH function. See documentation.

Plan and manage costs

Use built-in Cost Management features to set budgets and monitor the costs associated with your databases. By forecasting costs and monitoring trends, you’ll find opportunities to save and optimize your database spending.   See documentation.

Updates to service quotas

The minimum provisioned throughput (RU/s) required per database for shared throughput accounts has been changed.  See documentation.

Monitoring Azure Cosmos DB database operations

  • You can gather server-side metrics about the data stored in Azure Cosmos DB using tools in the Azure portal or Azure Monitor, or by using the .NET, Java, Python or Node.js SDKs. See documentation.
  • Performance and availability can also be monitored with a reference of log and metric data. See documentation.

Transactional batch operations with .NET SDK

Use the Azure Cosmos DB .NET SDK to define a group of point operations that must succeed or fail together in order to be committed. See documentation.

Migrate v1 .NET applications to v2 .NET SDK

The Azure Cosmos DB .NET SDK v1 will be retired. You can enjoy new features and functionality by migrating your applications to the Azure Cosmos DB v3 .NET SDK.  You can also move to v2 if you’d prefer. See documentation.

Use Databricks to migrate Cassandra data to Azure Cosmos DB

In a few short steps, you can migrate Apache Cassandra key spaces/tables to the fully-managed Azure Cosmos DB API for Cassandra using Azure Databricks. See documentation.


Find more


Discussion is closed. Login to edit/delete existing comments.

    • Nikisha Reyes-GrangeMicrosoft employee 1

      Hi, Ruben. Thanks for your comment. The documentation is in fact about migrating from v1 to v2. There are, however, a note and link about v3 migration on the page for people who are looking for that info.

Feedback usabilla icon