Azure diagram showing an application granted access only to the Orders database’s orders collection, shielding unrelated data.
Azure DocumentDB now has a public preview of role-based access control scoped to individual databases and collections. The change is small to describe but matters for anyone running MongoDB-compatible workloads on Azure. It arrived with a bundle of Microsoft Ignite 2026 database announcements on November 17.

Azure diagram showing an application granted access only to the Orders database’s orders collection, shielding unrelated data. What Microsoft announced​

Microsoft's Ignite 2026 Book of News says Azure DocumentDB will let organizations scope custom roles and permissions to individual databases and collections. The stated aim is least-privilege access, so users and applications don't get broader cluster-level permissions than they need.

The Azure DocumentDB team's Ignite post, by Principal PM Manager Abinav Rameesh, puts it in the same terms. It says admins can define custom roles scoped to a database or collection "rather than relying only on cluster-level access." The post files the feature under "Scale with confidence" and labels it public preview.

The Azure Updates listing tags the item "In preview." The portal's general definition of that status is that the feature is available to all Azure customers for non-production use and testing. That is the portal's generic wording, not a statement about this feature's support terms.

Why scope matters​

Before this change, the access-control surfaces Microsoft documents for DocumentDB were:

  • Azure control-plane RBAC. Microsoft Learn describes this as fine-grained permissions for managing Azure DocumentDB clusters, databases, and collections, so only authorized users or services can perform administrative operations.
  • Native data-plane RBAC. Learn describes this as enforcing least-privilege access for querying, creating, and accessing items within DocumentDB collections.
  • Secondary users. Learn also describes assigning read-write or read-only privileges to secondary user clusters for more granular access control on a cluster's databases.

The new preview concerns data privileges scoped to a database or collection. In practice, a service that only reads one collection of product listings shouldn't be able to touch an unrelated billing collection in the same cluster. Scoped custom roles are the mechanism for that.

What Microsoft hasn't said​

The announcement material leaves several things unspecified, so treat these as open questions:

  • Which individual privileges can go into a custom role.
  • The exact setup steps, role syntax, or commands.
  • Which identities and authentication modes the preview supports. Learn's existing guidance covers Entra ID identities, but I can't confirm the new roles work with all of them.
  • Supported regions, cluster versions or tiers, and any preview limitations.
  • Whether the preview carries an SLA. The listing only gives the generic non-production guidance.

It is also unclear how the new roles map onto the existing control-plane and data-plane RBAC and secondary-user models. Don't assume they replace any of them.

Practical advice for admins​

  1. Inventory current access. List which applications and users have cluster-level access today, and why.
  2. Identify over-privileged accounts. Look for services that touch only one database or collection but hold wider rights.
  3. Test in a non-production cluster. That matches Azure's own preview guidance. Check that your applications still work with narrower roles.
  4. Read the feature documentation first. Do this before changing anything in production, and check supported privileges, identity compatibility, and limitations.
  5. Keep control-plane and data-plane identities separate. Learn already recommends this to reduce the risk of privilege escalation.

The rest of the Ignite DocumentDB announcements​

The same post covers other updates:

  • Generally available: the DocumentDB extension for Visual Studio Code, near-instant cluster provisioning for M10 through M30 tiers, and the ability to query from any node in multi-shard clusters.
  • Public preview: full-text search, DocumentDB enabled by Azure Arc, and DocumentDB on Azure Local.

The RBAC feature is the only one of these concerned with who can access what.

Analysis​

Cluster-wide access is convenient and risky. One leaked connection string or compromised app identity can expose every database in the cluster. Narrowing roles to a collection limits the damage from that kind of compromise. It also makes audits easier, because permissions can be mapped to workloads.

The caveat is that this is a preview with thin public detail. Teams with compliance obligations should evaluate it now but wait for general availability and full documentation before relying on it for production boundaries. That recommendation is my own judgment, not Microsoft guidance.

 

References

  1. (In preview) Public Preview: Fine-grained role-based access control for databases and collections in Azure DocumentDB Azure Updates 2026-11-17T20:00:32Z
  2. Azure DocumentDB at Microsoft Ignite 2026: What's New devblogs.microsoft.com
  3. Secure your cluster - Azure DocumentDB learn.microsoft.com