- Home
- Wide-Column Databases
- Azure Cosmos DB for NoSQL
Azure Cosmos DB for NoSQL
Azure Cosmos DB for NoSQL · Redmond, Washington, United States · founded 1975
What it is
Azure Cosmos DB for NoSQL is a fully managed cloud database built around schema-agnostic JSON documents and SQL-like queries. It supports global data distribution, writes in multiple regions, and automatic failover, alongside provisioned, autoscale, and serverless throughput options. Built-in vector and hybrid similarity search is listed for workloads such as RAG and AI agents. Developers can use SDKs for .NET, Java, JavaScript/Node.js, Python, Go, and Rust. Change feed supports event-driven architectures and streaming pipelines with Azure Functions and Spark; analytical workflows can use Azure Synapse Link or Fabric mirroring without an ETL step. The free tier includes 1,000 RU/s and 25 GB of storage for one account per Azure subscription. A separate 30-day trial is listed. Other options include hourly-billed standard provisioned throughput, autoscale with a minimum of 400 RU/s or 10% of maximum, and serverless billing based on request units and consumed storage. The service lists less than 10 millisecond read and write latency and 99.999 percent availability SLAs for NoSQL data. The selected compute pricing model and API cannot be changed after selection.
For and against
For
- Supports global distribution and multi-region writes.
- Includes vector and hybrid similarity search.
- Offers provisioned, autoscale, and serverless models.
- Free tier includes 1,000 RU/s and 25 GB.
- SDKs are listed for seven languages.
Against
- Compute pricing model and API cannot be changed later.
- Free tier is limited to one account per subscription.
- Autoscale minimum is 400 RU/s or 10% of maximum.
- Highly relational apps are identified as a poor fit.
The verdict
Azure Cosmos DB for NoSQL offers multiple throughput models, global distribution, and search capabilities for suitable NoSQL workloads. Review the account allowance and selection limits before choosing an API and compute model.
Who it suits
It suits developers building flexible-schema, latency-sensitive, elastic, high-throughput, or highly available mission-critical applications. The listed poor fits include analytical OLAP and highly relational applications.
Plans and prices
Free tier
1,000 RU/s · 25 GB storage · 1 free tier account per Azure subscription
Read 22 Sep 2026 · azure.microsoft.com
Standard provisioned throughput
Provisioned throughput billed by the hour · Available for the NoSQL API
Read 22 Sep 2026 · azure.microsoft.com
30-day free trial
30 days
Read 20 Sep 2026 · azure.microsoft.com
Autoscale provisioned throughput
Minimum 400 RU/s or 10% of maximum
Read 22 Sep 2026 · azure.microsoft.com
Serverless
Pay only for request units used and consumed storage · No minimum operations or capacity
Read 22 Sep 2026 · azure.microsoft.com
Azure Cosmos DB free tier
1,000 RU/s · 25 GB storage
Read 11 Oct 2026 · azure.microsoft.com
Azure Cosmos DB for NoSQL — standard provisioned throughput
Minimum 400 RU/s · storage and bandwidth billed separately
Read 11 Oct 2026 · azure.microsoft.com
On the record
- Analytics
- The service supports no-ETL analytical workflows through Azure Synapse Link or Fabric mirroring.learn.microsoft.com · read 11 Oct 2026
- Availability
- The product page states that NoSQL data has SLAs including less than 10 millisecond read and write latency and 99.999 percent availability.azure.microsoft.com · read 11 Oct 2026
- Developer SDKs
- Microsoft lists SDKs for .NET, Java, JavaScript/Node.js, Python, Go, and Rust.learn.microsoft.com · read 11 Oct 2026
- Free local development
- The Azure Cosmos DB emulator provides a no-cost local environment for development and testing on Windows or Linux.azure.microsoft.com · read 11 Oct 2026
- Global scale
- The service supports global data distribution, multi-region writes, and automatic failover.learn.microsoft.com · read 11 Oct 2026
- Integrations
- Change feed supports event-driven architectures and streaming pipelines using Azure Functions and Spark.learn.microsoft.com · read 11 Oct 2026
- Intended workloads
- Microsoft identifies flexible-schema, latency-sensitive, elastic, high-throughput, and highly available mission-critical apps as good fits, while describing analytical OLAP and highly relational apps as poor fits.learn.microsoft.com · read 11 Oct 2026
- Notable limits
- The pricing page says the selected compute pricing model and API cannot be changed after selection.azure.microsoft.com · read 11 Oct 2026
- Scaling
- Throughput options include standard provisioned, autoscale provisioned, and serverless models.azure.microsoft.com · read 11 Oct 2026
- Search
- It offers built-in vector and hybrid similarity search for workloads including RAG and AI agents.learn.microsoft.com · read 11 Oct 2026
- Security
- Microsoft recommends private endpoints, disabling public network access, and client-side encryption with Always Encrypted for sensitive data.learn.microsoft.com · read 11 Oct 2026
- Vector search
- Yesazure.microsoft.com · read 22 Sep 2026
- What it does
- Azure Cosmos DB for NoSQL is a fully managed cloud database using a schema-agnostic JSON document model with SQL-like querying.azure.microsoft.com · read 11 Oct 2026
The review
Overview
Azure Cosmos DB for NoSQL is a managed cloud database for schema-agnostic JSON data, queried through a SQL-like interface. It is best suited to applications that need elastic throughput, low-latency access across regions, or vector search. Its breadth is compelling, but teams must choose an API and compute model carefully because those selections cannot later be changed.
Key features
The flexible JSON document model suits applications whose data shape may evolve without a fixed schema. Documents can be up to 2.0 MB, and transactions and configurable consistency provide options for handling related updates and consistency behavior. Horizontal scaling and global distribution, including multi-region writes and automatic failover, make the service relevant to applications serving users across regions. Microsoft states SLAs for NoSQL data that include read and write latency under 10 milliseconds and 99.999 percent availability.
Built-in vector and hybrid similarity search supports retrieval-augmented generation and AI-agent workloads, a useful distinction for teams building search into AI applications. The change feed can connect database updates to event-driven systems and streaming pipelines through Azure Functions and Spark. For analytics without a separate extract-transform-load process, the service supports Azure Synapse Link or Fabric mirroring.
Microsoft lists SDKs for .NET, Java, JavaScript/Node.js, Python, Go, and Rust. Security guidance recommends private endpoints, disabling public network access, and client-side encryption with Always Encrypted for sensitive data. The local emulator offers free development and testing on Windows or Linux. These tools broaden development options, but teams should account for security configuration rather than assume sensitive data is protected by default.
One important constraint is that the API and compute pricing model are fixed after selection. That makes early workload assessment consequential: the service is a stronger fit for flexible-schema, latency-sensitive, elastic, high-throughput, highly available applications than for highly relational systems or analytical OLAP workloads, which Microsoft identifies as poor fits.
Pricing
Cosmos DB for NoSQL uses a freemium model, with a free plan and a 30-day trial. The Free tier costs nothing and includes 1,000 RU/s, 25 GB of storage, and one free-tier account per Azure subscription. The similarly described Azure Cosmos DB free tier is billed Free each month for the life of one account per subscription, with 1,000 RU/s provisioned throughput and 25 GB storage. These allowances offer a practical starting point, but the single-account cap and fixed throughput and storage limit how far they can support growing workloads.
The 30-day free trial is billed Free for 30 days, and renewals are available. It is useful for evaluation, but it is time-limited rather than a substitute for selecting a sustainable production model. The Standard provisioned throughput option is billed hourly and is available for the NoSQL API; its price depends on region and configuration. Standard provisioned throughput has a minimum of 400 RU/s, with storage and bandwidth billed separately, so usage planning needs to include more than throughput alone.
Autoscale provisioned throughput has a minimum of 400 RU/s or 10% of the maximum, making it an option to consider when demand varies but still imposing a floor. Serverless charges for request units used and consumed storage, with no minimum operations or capacity; that pay-for-use structure suits workloads that do not need reserved capacity. Prices are custom pricing for these options; compare the billing model and minimums against expected demand before committing, since the choice cannot be changed later.
Platforms
The product is a managed cloud service, with API and self-hosted platforms listed. Its deployment model is cloud, so the self-hosted label should not be read as evidence that this database itself can be deployed on a customer's own infrastructure. The emulator does provide a no-cost local environment for development and testing on Windows or Linux.
Who it's for
Choose Cosmos DB for NoSQL when an application needs a flexible document model, global availability, elastic throughput, or built-in vector search, especially when change-feed integrations or analytics mirroring fit the architecture. Look elsewhere for highly relational applications or OLAP analytics, which are poor matches for the service's intended workload profile.
Pros and cons
- Pro: Global distribution, multi-region writes, automatic failover, and stated latency and availability SLAs make it suited to demanding multi-region applications.
- Pro: Vector and hybrid similarity search, plus integrations for event-driven processing and analytics, support AI and data-pipeline use cases within the same service.
- Pro: The free tier includes 1,000 RU/s and 25 GB, and the emulator supports local development at no cost.
- Con: The API and compute model cannot be changed after selection, raising the cost of an early mismatch.
- Con: The free tier is limited to one account per Azure subscription, and provisioned throughput has a 400 RU/s minimum with storage and bandwidth billed separately.
- Con: Highly relational and analytical OLAP workloads are identified as poor fits, narrowing its appeal for those database needs.
Alternatives
For a different database approach, compare Amazon Keyspaces, which offers on-demand capacity billed for reads and writes actually performed or provisioned capacity. Choose Apache Cassandra instead if an open-source, self-managed distributed NoSQL database is the priority; it costs nothing. Apache HBase is another free, open-source distributed database for teams prepared to configure and manage deployments. SWC-DB is a free GPLv3 option, with commercial-purpose licensing inquiries required for uses limited by that license.
Google Cloud Bigtable is another paid database alternative, with Enterprise at $0.65 a month and Enterprise Plus at $0.85 a month. Apache Accumulo offers a free, open-source sorted distributed key/value store under Apache License 2.0. Azure Application Insights is a paid alternative with a free plan and usage-based ingestion, including the first 5 GB/month per billing account free. Tencent Cloud API Gateway is a paid API gateway with a shared-instance allowance of the first 1 million API calls per month free during the first year.
Readers comparing database categories can also browse Document Databases, Wide-Column Databases, Multimodel Databases, Spatial Databases, and Database Software.
Verdict
Azure Cosmos DB for NoSQL is a strong choice for teams building flexible, latency-sensitive applications that need global distribution or vector search, with multiple throughput models to match demand. Its main appeal is combining those capabilities with managed operations and integration options; its main reason to look elsewhere is the irreversible API and compute-model decision, alongside a poor fit for relational and OLAP workloads.