What is the limit of collection in Azure Cosmos DB for MongoDB (vCore) ?

Hugo MENDES ADMAZ 0 Reputation points
2025-04-09T15:09:48.1466667+00:00

According to the official documentation for Azure Cosmos DB for MongoDB vCore (https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/limits), there is a stated limit of 1000 collection per cluster. However, in my current setup (Cluster tier : M30 tier, 2 vCores, 8 GiB RAM), I have successfully created 1500 collections, and the system has not raised any errors or performance issues (so far).

This seems to contradict the documented limitation, so I’m wondering:

What is the actual limit on the number of collections per cluster in MongoDB vCore?

Is the 1000 collection limit outdated or lifted dynamically ?

And should I expect any performance or stability issues if I continue creating more collections?

Azure Cosmos DB
Azure Cosmos DB
An Azure NoSQL database service for app development.
1,843 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Adithya Prasad K 740 Reputation points Microsoft External Staff
    2025-04-11T04:21:11.5233333+00:00

    HI Hugo MENDES ADMAZ,
    The documented limit of 1000 collections per cluster in Azure Cosmos DB for MongoDB vCore is a general guideline rather than a strict enforcement. Here's what you need to know:

    1. Actual Limit

    • While the documentation states a limit of 1000 collections, your ability to create 1500 collections without errors suggests that the limit may be dynamically adjusted based on your cluster tier and workload.
      • Azure Cosmos DB is designed to be flexible, and some limits may evolve over time as the service improves.

    2. Outdated or Dynamic Limit

    • The 1000 collection limit might be outdated or not strictly enforced for certain configurations. It's possible that higher-tier clusters (like M30) allow more collections due to increased resources.

    3. Performance and Stability Considerations

    • Exceeding the recommended limit could lead to:
      • Increased latency for queries and operations.
      • Higher memory and CPU usage, especially if collections have large indexes or frequent transactions.
      • Challenges with scaling or managing the cluster.
    • Monitor your cluster's metrics (e.g., CPU, memory, and throughput) to ensure stability as you add more collections.

    Recommendations:

    • Monitor Performance: Use Azure Monitor to track resource utilization and identify bottlenecks.
    • Plan for Scaling: If you anticipate needing more collections, consider upgrading to a higher-tier cluster or exploring sharding strategies.

    I would request you to refer the below mentioned links for more information
    1.Service Limits in Azure Cosmos DB for MongoDB vCore
    2.Azure Cosmos DB service quotas
    3.MicrososftDoc
    I hope this information helps. Please do let us know if you have any further queries. 


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.