Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
APPLIES TO: 
NoSQL
This article only shows Azure Resource Manager template examples for API for NoSQL accounts. You can also find template examples for Cassandra, Gremlin, MongoDB, and Table APIs.
API for NoSQL
| Template | Description |
|---|---|
| Create an Azure Cosmos DB account, database, container with autoscale throughput | This template creates a API for NoSQL account in two regions, a database and container with autoscale throughput. |
| Create an Azure Cosmos DB account, database, container with analytical store | This template creates a API for NoSQL account in one region with a container configured with Analytical TTL enabled and option to use manual or autoscale throughput. |
| Create an Azure Cosmos DB account, database, container with standard (manual) throughput | This template creates a API for NoSQL account in two regions, a database and container with standard throughput. |
| Create an Azure Cosmos DB account, database and container with a stored procedure, trigger and UDF | This template creates a API for NoSQL account in two regions with a stored procedure, trigger and UDF for a container. |
| Create an Azure Cosmos DB account with Microsoft Entra identity, Role Definitions and Role Assignment | This template creates a API for NoSQL account with Microsoft Entra identity, Role Definitions and Role Assignment on a Service Principal. |
| Create a private endpoint for an existing Azure Cosmos DB account | This template creates a private endpoint for an existing Azure Cosmos DB for NoSQL account in an existing virtual network. |
| Create a free-tier Azure Cosmos DB account | This template creates an Azure Cosmos DB for NoSQL account on free-tier. |
See Azure Resource Manager reference for Azure Cosmos DB page for the reference documentation.
Next steps
Trying to do capacity planning for a migration to Azure Cosmos DB? You can use information about your existing database cluster for capacity planning.
- If all you know is the number of vcores and servers in your existing database cluster, read about estimating request units using vCores or vCPUs
- If you know typical request rates for your current database workload, read about estimating request units using Azure Cosmos DB capacity planner