Not able to create Azure DocumentDB (with MongoDB compatibility) resource in South Central US region.

Question

Deployment fails with the error message says "Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details,\nLocation: southcentralus,\nSubscription: xxxxxxxx-2075-xxxx-863a-xxxxxxxxxxxx,\nCurrent Limit: 0,\nCurrent Usage: 0,\nAdditional Required: 1,\n(Minimum) New Limit Required: 1.\nPlease open a support ticket." but in the portal I can see that my Total Regional vCPU quota is 20.

Answer 1

It seems that you are encountering a quota issue when trying to create an Azure DocumentDB resource in the South Central US region. The error message indicates that your operation cannot be completed because it exceeds the approved Total Regional Cores quota, despite seeing a Total Regional vCPU quota of 20 in the portal.

Here are a few steps you can take to resolve this issue:

1. Check Quota Limits: Verify that your Total Regional Cores quota specifically for the South Central US region is not set to 0. Sometimes, quotas can vary by region, and you may have a limit in one region that is different from another.
2. Open a Support Ticket: Since the error message suggests opening a support ticket, it would be beneficial to do so. The Azure support team can provide specific insights into your subscription limits and help you adjust your quotas if necessary.
3. Consider Resource Group and Subscription: Ensure that you are creating the resource in the correct resource group and under the correct subscription that has the appropriate quotas.
4. Review Usage: Check if there are any existing resources consuming the cores in the South Central US region that you might not be aware of, which could be affecting your ability to create new resources.

If you continue to face issues, contacting Azure support will be the best course of action to get detailed assistance regarding your quota limits.

---

References:

• Frequently asked questions about Azure DocumentDB (with MongoDB compatibility)
• Create and use a replica cluster in another or the same Azure region in Azure DocumentDB

Answer 2

I’ve seen this a few times with Cosmos DB (Mongo API).

The error message is misleading because it talks about “vCPU quota,” but Cosmos DB is not using your VM regional core quota at all. What’s actually happening is this:

Cosmos DB for Mongo is failing over to a backup region (East US) during deployment, and your subscription has a core quota of 0 in that region. Even though you selected South Central US, the deployment pipeline internally validates the paired region, which for SCUS is East US.

If the quota in the paired region is zero, the create operation fails.

This is why the portal shows 20 vCPUs in South Central US, but the error says:

Location: eastus  
Current Limit: 0  
Required: 1  

To fix This:

1. Increase the vCPU quota for East US, not South Central US. Go to: Azure Portal --> Subscriptions --> Quotas --> Compute --> East US --> Increase “Standard vCPUs”.

Once the East US quota is at least 1, retry creating the Cosmos DB Mongo resource in South Central US. The deployment will succeed.

If your organization doesn’t want to increase East US quota, create the Cosmos DB resource in a region whose paired region quota is not zero.

This quota mismatch between primary region and paired region is the real cause, not an actual shortage in SCUS

Answer 3

Hi @Parthiv Patel

At this time, we do not have a confirmed ETA for restoring provisioning capabilities, but please be assured that our engineering team is working diligently to resolve the issue and restore full functionality as quickly as possible.

If services cannot be created there right now, it unfortunately means you would need to consider relocating your entire deployment to a region where this functionality is fully supported.

Below are few KB article documents which can help you on specific DocumentDB related problem.

• https://learn.microsoft.com/en-us/azure/documentdb/how-to-monitor-diagnostics-logs
• https://learn.microsoft.com/en-us/azure/documentdb/troubleshoot-common-issues
• https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/documentdb/troubleshoot-common-issues.md

Answer 4

The issue has been resolved through the Microsoft Support ticket. Azure Cosmos DB team confirmed that subscription needed to be explicitly allowed from their backend to enable resource creation. Once Microsoft enabled this permission on their side, the deployment began working as expected.