Unable to Create MongoDB User in Azure Cosmos DB for MongoDB vCore

Jonathan Allbritten 0 Reputation points
2025-08-08T22:49:51.23+00:00

Per title, I cannot create secondary native users in vCore mongo cluster.

EastUS region and M10 tier.

No UI exists (as mentioned in answer https://learn.microsoft.com/en-us/answers/questions/5513331/unable-to-create-mongodb-user-in-azure-cosmos-db-f).

No ability to create users via CLI tools (similar errors reported to those other users mentioned).

Official documentation/blog says that this entered general availability in July:

https://azure.microsoft.com/en-us/updates?id=470102

Which is supported by documentation here:

https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/compatibility?source=recommendations

And here

https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/secondary-users

Which all point to secondary user creation being supported via the mongosh cli and is the recommended path. No documentation points to UI for users (I assume this is a preview feature).

Is MSFT documentation out of sync with the current state of this feature? What is the exact criteria for user management?

Azure Cosmos DB
Azure Cosmos DB
An Azure NoSQL database service for app development.
{count} votes

1 answer

Sort by: Most helpful
  1. Vinodh247 36,031 Reputation points MVP Volunteer Moderator
    2025-08-09T14:44:56.6366667+00:00

    Hi ,

    Yes, you might be right. The ms doc is out of sync with the current implementation. While the feature is marked as generally available, until the CLI and mongosh commands truly work, portal UI remains the only reliable path to create secondary MongoDB users in CosmosDB vCore.

    Feature Limitations & Preview Notes:

    The UI based user management is still considered in a preview state and is subject to limitations:

    Max 100 users/roles per cluster

    updateuser only allows password changes

    roleinfo isn’t supported (use usersInfo instead)

    • Roles must be assigned cluster wide (no per/db granularity)

    This preview nature likely explains why CLI and mongosh support remain non functional or disabled despite documentation implying otherwise.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.