Azure DocumentDB, a fully managed MongoDB-compatible database service based on the open-source DocumentDB governed by the Linux Foundation, is now generally available. It was formerly known as vCore-based Azure Cosmos DB for MongoDB.
Azure DocumentDB gives developers a multi-cloud, first-party document database on Azure that preserves MongoDB skills and tooling, improves portability through open source, and delivers clear cost control with a simple compute and storage-based model.
At Ignite, we announced the AI-powered Index Advisor, Premium storage v2 disks, and the VS Code migration extension. All these enhancements help you develop your enterprise applications faster on Azure.
Multicloud Through Open Source
DocumentDB began as an open-source, MongoDB compatible document database under a permissive MIT license. Foundation on the MIT license speeds up onboarding and eliminates database vendor lock-in. With the project now owned by the Linux Foundation, multiple vendors participate and align on a common, MongoDB-compatible path.
Multi-cloud is the natural result: the same open engine runs locally and across providers, and the ecosystem is converging. The DocumentDB Kubernetes Operator is used to deploy, run and manage clusters across Azure, AWS, GCP, and on-premises. A Microsoft-built open-source DocumentDB VS Code extension supports any DocumentDB or MongoDB cluster and simplifies deploying open-source clusters for hybrid or multi-cloud applications. Azure DocumentDB is the first-party managed service for this open technology.
Predictable TCO and enterprise ready
Azure DocumentDB uses a simple compute and storage-based pricing model, with independent scaling for each, at highly competitive rates and no additional cost for backup or restore. This transparency makes spend easy to forecast and align to your MongoDB workload growth.
As a genuine first-party Azure service, Azure DocumentDB provides unified billing, Microsoft support, native Entra ID authentication, customer-managed keys (CMK), and the operational guardrails enterprises expect across the Azure platform. If your organization standardizes on Azure, Azure DocumentDB fits seamlessly and gives you a familiar MongoDB-compatible experience to develop faster.
Easy migration and first-party simplicity
No matter which MongoDB or DocumentDB service you use, whether on-premises, managed, or in other clouds, you can move to Azure DocumentDB using the built-in Azure migration flow or standard MongoDB tools. The goal is simple: a predictable path, familiar commands, and a supported landing zone backed by Azure, with a full-stack 99.995% SLA that does not exclude compute, data centers, and networking.
Customers can also test locally with the open-source DocumentDB project before deploying managed clusters on Azure. That flexibility shortens proof-of-concept cycles and builds confidence ahead of cutover.
What’s Available Today
You can now provision Azure DocumentDB clusters in the Azure portal, choose cluster tiers that match your performance needs, and scale vertically and horizontally as your application grows.
The former vCore-based Azure Cosmos DB for MongoDB offering is now Azure DocumentDB. Existing clusters automatically adopt the new name in the Azure portal with no changes required.
Get started
Create a cluster in the Azure portal, check out the new product page, review pricing, and follow the migration guidance to migrate your MongoDB workloads. Teams can evaluate DocumentDB locally using the open-source project, then move to managed clusters on Azure when ready. We’re excited to see what you build.
About Azure DocumentDB
Azure DocumentDB is a fully managed enterprise-grade MongoDB-compatible database and vector database for modern app development, including AI applications. With its predictable low costs, Open-source project, as well as 99.03% MongoDB compatibility, it is ideal for any MongoDB application running on Azure.
Microsoft truly is the number 1 company with the worst product naming in history. So DocumentDB was rebranded to CosmosDB some years back, and now we have this new Azure DocumentDB. What does that mean for CosmosDB? Is this the same? How does it relate? Should I adjust to the new naming, or will we go around one more time and rebrand to "CosmosDB v2 for Azure" in a couple years? The DocumentDB FAQs doesn't mention the word "Cosmos" even once.
It is hell for developers to work in the Azure ecosystem, because every service just contains a vague high-level...
Thanks for raising this, Martin. Your feedback is fair. Azure DocumentDB is the new name for what was previously the vCore-based Azure Cosmos DB for MongoDB service. We separated it out at Ignite to align with the open-source DocumentDB project (under the Linux Foundation) and to give it a clearer long-term identity. Cosmos DB remains its own service with its existing APIs; only the vCore-based Cosmos DB for MongoDB moved out. The rename brings some short-term friction, but the goal is long-term clarity. I’ve updated the FAQ (will be live shortly), and we’re updating our documentation over the next few...