What Microsoft actually announced
Microsoft's Ignite Book of News says the offering will extend Azure DocumentDB to hybrid and multicloud environments and is now in preview. The Azure DocumentDB team's Ignite post is more specific. It describes the preview as a way to deploy open-source DocumentDB on supported Azure Arc-enabled Kubernetes clusters across on-premises, edge and multicloud environments. It says teams can use MongoDB-compatible APIs and tools, with Azure Arc handling management and governance of the underlying Kubernetes infrastructure.
A few details are easy to miss:
- The engine is open-source DocumentDB. It is not the fully managed Azure DocumentDB service moved onto your hardware.
- Arc governs the Kubernetes layer. The announcement doesn't say Arc manages every database-level operation.
- The cluster must be supported. Microsoft hasn't published a list of supported Kubernetes distributions or versions in the material I reviewed.
Where this fits in the DocumentDB family
Azure DocumentDB is Microsoft's MongoDB-compatible document database powered by the open-source DocumentDB engine governed by the Linux Foundation. Microsoft Learn describes the managed service as built on that engine. It says the same engine can run on-premises or on any cloud with the DocumentDB Kubernetes operator. The Arc preview packages that hybrid story around Azure's management plane.
Microsoft announced a sibling preview in the same post, DocumentDB on Azure Local. That one targets customer-owned infrastructure powered by Azure Local, such as datacenters, retail locations and industrial sites. The two options are separate:
| Option | Target | Status |
|---|---|---|
| DocumentDB enabled by Azure Arc | Supported Arc-enabled Kubernetes clusters (on-premises, edge, multicloud) | Public preview |
| DocumentDB on Azure Local | Customer-owned infrastructure running Azure Local | Public preview |
Microsoft's database roundup frames both as ways to run MongoDB compatible workloads on supported Kubernetes clusters or customer-owned infrastructure, including on-premises and edge environments.
Preview means preview
Azure's own status definitions say "In preview" means the feature is available to Azure customers for non-production use and testing. Don't plan production databases on this yet. There is no general-availability date, service-level commitment or support statement in the material I reviewed.
What Microsoft hasn't said
The announcement leaves several practical questions open. I found no answers in the sources I reviewed:
- Supported Kubernetes distributions and versions
- Minimum cluster resources
- Installation steps and Azure Arc prerequisites
- Pricing and regional availability
- Backup and restore, high availability, upgrades and monitoring integration for Arc-hosted deployments
- How the preview signs up or enables
The managed-service figures on Microsoft Learn shouldn't be assumed to carry over. Those include 99.03% operator compatibility, MongoDB versions 4.0 through 8.0, and a 99.995% availability SLA. They describe the managed Azure service, and the Arc announcement doesn't repeat them for this deployment. Compatibility is the biggest unknown for anyone planning a migration.
Who should pay attention
This is most relevant if you are in one of these groups:
- Hybrid and edge teams that need document data close to applications for latency or data-location reasons.
- Platform teams already running Arc-enabled Kubernetes that want a Microsoft-aligned MongoDB-compatible option under the same governance model.
- Teams weighing MongoDB alternatives, who can use the preview to see how the open-source DocumentDB engine behaves outside Azure.
A sensible way to evaluate it
This is general guidance, not Microsoft's documented procedure:
- Inventory which workloads can't move to a public cloud and why.
- Check your Arc-enabled Kubernetes clusters against Microsoft's preview documentation once it lists supported platforms.
- Test in a non-production environment with a copy of representative data.
- Run your MongoDB drivers and queries against it and note any unsupported operators.
- Hold off on backup, failover and upgrade conclusions until Microsoft documents them for this deployment.
The bottom line
The Arc preview gives teams another option for running MongoDB-compatible workloads where public cloud isn't an option. The main limit is the lack of public detail on supported clusters, operations and pricing. Until that appears, treat it as something to test, not deploy.
References
- (In preview) Public Preview: DocumentDB enabled by Azure Arc Azure Updates · 2026-11-17T20:00:32Z
- What is Azure DocumentDB (with MongoDB compatibility)? - Azure DocumentDB | Microsoft Learn learn.microsoft.com
- Azure DocumentDB at Microsoft Ignite 2026: What's New devblogs.microsoft.com