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

Question

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

Parthiv Patel 0

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.

4 answers

Your answer

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:

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.
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.
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.
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:

Answer 2

Adam Zachary 2,025

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:

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

Parthiv Patel 0 Reputation points

2025-11-28T03:34:26.0766667+00:00

Thanks, but I can confirm that I have sufficient vCores available in the East US region as well. The error message I mentioned relates specifically to a resource creation issue in East US. I’m also able to reproduce the same error when attempting to create the resource in the South Central US region. To be more specific Azure Resource I am creating is Azure DocumentDB (with MongoDB compatibility). https://learn.microsoft.com/en-us/azure/documentdb/quickstart-portal

{
"code": "bad_request",
"message": "Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details,\nLocation: southcentralus,\nSubscription: xxxxxxx-2075-xxxx-863a-xxxxxxxxxxxx,\nCurrent Limit: 0,\nCurrent Usage: 0,\nAdditional Required: 2,\n(Minimum) New Limit Required: 2.\nPlease open a support ticket."
}
Adam Zachary 2,025 Reputation points

2025-11-28T04:53:16.08+00:00

You are right, my first reply missed the mark here, I treated it like a normal Compute vCPU or paired region issue and that was wrong.

In your case the error is coming from the separate “Total Regional Cores” quota that Azure DocumentDB or Cosmos DB Mongo vCore uses in each region, which is often zero by default, even if Microsoft Compute vCPU shows 20. The JSON you posted for southcentralus with Current Limit 0 and Additional Required 2 is that vCore quota, not the VM quota.

I think the practical fix is to Create a support request from the portal, and ask to increase the “Total Regional Cores” quota for Azure DocumentDB or Cosmos DB Mongo vCore in southcentralus from 0 to at least the number in your error and paste the exact error message in the ticket
VRISHABHANATH PATIL 1,820 Reputation points Microsoft External Staff Moderator

2025-11-28T07:31:16.46+00:00

Hi @Parthiv Patel

Thank you for your patience and for sharing the context around your deployment scenario. I completely understand how important it is for you to provision staging slots within the same region, and I realize the current limitation in the East US region is impacting your deployment.

Currently, there’s no confirmed ETA for restoration of provisioning capabilities in East US region, but our engineering team is actively working on resolving the issue and restoring full functionality as soon 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.
Parthiv Patel 0 Reputation points

2025-11-28T07:40:07.5766667+00:00

Thanks @VRISHABHANATH PATIL
I can reproduce a similar error in the South Central US region too. Is this limitation applicable there as well? If so, is any support available to mitigate it?
VRISHABHANATH PATIL 1,820 Reputation points Microsoft External Staff Moderator

2025-11-28T08:26:50.8533333+00:00

Hi @Parthiv Patel

Please refer to the following knowledge base article for details on regional availability - https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/table

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.
VRISHABHANATH PATIL 1,820 Reputation points Microsoft External Staff Moderator

2025-12-01T07:04:51.1633333+00:00

Hi @Parthiv Patel

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
VRISHABHANATH PATIL 1,820 Reputation points Microsoft External Staff Moderator

2025-12-02T11:10:59.4866667+00:00

Hi @Parthiv Patel

Just checking in to see if you had any questions. We are happy to assist and continue the discussion whenever you are ready.
Parthiv Patel 0 Reputation points

2025-12-02T11:59:11.5233333+00:00

Hi @VRISHABHANATH PATIL
I don’t have any questions right now, but let me know when this issue is resolved or where I can track the status of this specific DocumentDB related problem.
VRISHABHANATH PATIL 1,820 Reputation points Microsoft External Staff Moderator

2025-12-04T06:28:36.7366667+00:00

Hi @Parthiv Patel

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Answer 3

VRISHABHANATH PATIL 1,820 Microsoft External Staff Moderator

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.

VRISHABHANATH PATIL 1,820 Reputation points Microsoft External Staff Moderator

2025-12-05T03:50:17.78+00:00

Hi @Parthiv patel

If this solution helped resolve your issue, please consider clicking ‘Accept Answer’ or giving it an upvote to help others find it easily.
Parthiv Patel 0 Reputation points

2025-12-05T05:44:04.3233333+00:00

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.

Answer 4

Parthiv Patel 0

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.

Share via

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

4 answers

Your answer