Frequently asked questions on Azure Cosmos DB for MongoDB in RU architecture

Yes, data residency is governed at the database account level, which is associated with one or more regions. Typically, you create a database account for each residency requirement. For example, if you have a requirement to store data in the US and EU, you would create two database accounts, one in the US and one in the EU.

Yes, documents as large as 16 MB are fully supported.

Yes, multi-field sort is supported. A compound index is required for the fields in the sort to ensure the operation is efficient and scalable.

In many cases, Azure Cosmos DB's costs scale better than linear. For example, if you read a 1-KB document, this operation equates to one Request Unit (RU). But if you read a 10-KB document, this larger operation still equates to roughly one RU. The capacity calculator can help you estimate your throughput needs.

Azure Cosmos DB for MongoDB (RU) supports Field Level Encryption.

Azure Cosmos DB for MongoDB (RU) offers three capacity modes: provisioned throughput, autoscale, and serverless. Autoscale instantaneously scales to meet your needs, and serverless only charges for the throughput you use.

Azure Cosmos DB for MongoDB (RU) supports a rich set of MongoDB features backed by Azure Cosmos DB's limitless scale architecture. These features include: Aggregation pipelines, Change streams, Indexes, Geospatial queries, and more. For more information, see feature support matrix.

Azure Cosmos DB for MongoDB (RU) is a cloud-native multitenant service and isn't available on-premises. Azure Cosmos DB offers an emulator for local development and testing.

The quickest way to connect to an Azure Cosmos DB for MongoDB (RU) database is to use the Quick Start feature within the resource's page in the Azure portal. The Quick Start includes code snippets preconfigured to connect to your database.

Azure Cosmos DB enforces strict security requirements and standards. Azure Cosmos DB accounts require authentication and secure communication via transport layer security (TLS). In any examples you build, use TLS version 1.2.

For more information, see Connect to your API for MongoDB RU database.

Along with the common MongoDB error codes, Azure Cosmos DB for MongoDB (RU) has its own specific error codes. For more information, see API for MongoDB (RU) troubleshooting guide.

Yes, you can use non-Microsoft MongoDB Open Database Connectivity (ODBC) drivers with Azure Cosmos DB for MongoDB (RU).

Azure portal support for role management isn't available. However, role-based access control can be enabled via the features tab in the Azure portal.

Update the user definition with the new password.

Versions 3.6 and higher support role-based access control.

• The number of users and roles you can create must equal less than 10,000.
• The commands listCollections, listDatabases, killCursors, and currentOp are excluded from role-based access control.
• Users and Roles across databases aren't supported.
• You can only set or reset a user's password through the Azure CLI or Azure PowerShell.
• Configuring Users and Roles is only supported through Azure CLI / PowerShell.
• Disabling primary/secondary key authentication isn't supported. We recommend rotating your keys to prevent access when you enable role-based access control.
• Role-based access control policies for Azure Cosmos DB for MongoDB aren't automatically reinstated after a restore operation. You need to reconfigure these policies after the restoration process completes.

Related content

• Frequently asked questions about Azure Cosmos DB for MongoDB vCore

• Get started with Azure Cosmos DB for MongoDB (RU) and Node.js

• Get started with Azure Cosmos DB for MongoDB (RU) and Python

• Get started with Azure Cosmos DB for MongoDB (RU) and Java

• Get started with Azure Cosmos DB for MongoDB (RU) and .NET

• Get started with Azure Cosmos DB for MongoDB (RU) and Go

Next step