Depoyment failure when creating cosmo db with mongo support on azure

Question

Depoyment failure when creating cosmo db with mongo support on azure

Harmeet Kamboj 0

I am getting an error when I am trying to create Cosmos MongoDB service in Azure.

Mahesh Kurva 5,025 Reputation points Microsoft External Staff Moderator

2025-06-13T14:26:28.76+00:00

Hi Harmeet Kamboj,

Greetings!!

Could you please share the complete error message while you're creating Cosmos MongoDB service in Azure.
Harmeet Kamboj 0 Reputation points

2025-06-14T04:46:00.9833333+00:00
Mahesh Kurva 5,025 Reputation points Microsoft External Staff Moderator

2025-06-16T09:33:21.4633333+00:00
Hi Harmeet Kamboj,

Thanks for the response.

Try deploying the resource in a different Azure region. This is the most common workaround for this issue.

Review your Azure subscription quotas and ensure you're not exceeding limits.

Azure Cosmos DB supports MongoDB wire protocol versions 3.2, 3.6, and 4.0

Confirm that the Cosmos DB account name you want to create is unique globally.

Temporary service issues or outages in the Cosmos DB backend. Wait a few minutes and retry the deployment.

Try creating an Azure Cosmos DB account with MongoDB API using the Azure CLI.

https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/error-codes-solutions

https://learn.microsoft.com/en-us/cli/azure/cosmosdb/mongodb/collection?view=azure-cli-latest#az-cosmosdb-mongodb-collection-create

I hope this information helps. Please do let us know if you have any further queries.
Mahesh Kurva 5,025 Reputation points Microsoft External Staff Moderator

2025-06-17T09:48:28.32+00:00

Hi Harmeet Kamboj,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Taduturu Balaji 80 Reputation points Microsoft External Staff Moderator

2025-06-17T10:58:50.37+00:00

Hi @Harmeet Kamboj ,

From your first screenshot, the error indicates that the Cosmos DB account name you chose is already in use. Try creating the account with a globally unique name.

From your second screenshot, the error shows that the resource write operation failed and reached the terminal provisioning state 'Failed'. Means a previous attempt to create a Cosmos DB account with the same name has failed that deployment may still be causing a conflict.

For more information on Azure Cosmos Mongo DB refer to the below article,

https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/troubleshoot-common-issues
Taduturu Balaji 80 Reputation points Microsoft External Staff Moderator

2025-06-18T04:01:45.8+00:00

Hi @Harmeet Kamboj ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

1 answer

Your answer

Mahesh Kurva 5,025 Reputation points Microsoft External Staff Moderator

2025-06-13T14:26:28.76+00:00

Hi Harmeet Kamboj,

Greetings!!

Could you please share the complete error message while you're creating Cosmos MongoDB service in Azure.
Harmeet Kamboj 0 Reputation points

2025-06-14T04:46:00.9833333+00:00
Mahesh Kurva 5,025 Reputation points Microsoft External Staff Moderator

2025-06-16T09:33:21.4633333+00:00

Hi Harmeet Kamboj,

Thanks for the response.

Try deploying the resource in a different Azure region. This is the most common workaround for this issue.

Review your Azure subscription quotas and ensure you're not exceeding limits.

Azure Cosmos DB supports MongoDB wire protocol versions 3.2, 3.6, and 4.0

Confirm that the Cosmos DB account name you want to create is unique globally.

Temporary service issues or outages in the Cosmos DB backend. Wait a few minutes and retry the deployment.

Try creating an Azure Cosmos DB account with MongoDB API using the Azure CLI.

https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/error-codes-solutions

https://learn.microsoft.com/en-us/cli/azure/cosmosdb/mongodb/collection?view=azure-cli-latest#az-cosmosdb-mongodb-collection-create

I hope this information helps. Please do let us know if you have any further queries.
Mahesh Kurva 5,025 Reputation points Microsoft External Staff Moderator

2025-06-17T09:48:28.32+00:00

Hi Harmeet Kamboj,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Taduturu Balaji 80 Reputation points Microsoft External Staff Moderator

2025-06-17T10:58:50.37+00:00

Hi @Harmeet Kamboj ,

From your first screenshot, the error indicates that the Cosmos DB account name you chose is already in use. Try creating the account with a globally unique name.

From your second screenshot, the error shows that the resource write operation failed and reached the terminal provisioning state 'Failed'. Means a previous attempt to create a Cosmos DB account with the same name has failed that deployment may still be causing a conflict.

For more information on Azure Cosmos Mongo DB refer to the below article,

https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/troubleshoot-common-issues
Taduturu Balaji 80 Reputation points Microsoft External Staff Moderator

2025-06-18T04:01:45.8+00:00

Hi @Harmeet Kamboj ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Answer 1

Hi @Harmeet Kamboj ,

From your first screenshot, the error indicates that the Cosmos DB account name you chose is already in use. Try creating the account with a globally unique name.

From your second screenshot, the error shows that the resource write operation failed and reached the terminal provisioning state 'Failed'. Means a previous attempt to create a Cosmos DB account with the same name has failed that deployment may still be causing a conflict.

Try with the below code to create Azure Cosmos DB with Mongo using Powershell:

It will create provisioned throughput (RU/s) account, as we use -Kind MongoDB with New-AzCosmosDBAccount.


>>$resourceGroup = "*******"

>> $location = "East US"

>> $accountName = "mycosmosmongotest"  

>>

>> New-AzResourceGroup -Name $resourceGroup -Location $location

>>

>> New-AzCosmosDBAccount `

>>     -ResourceGroupName $resourceGroup `

>>     -Name $accountName `

>>     -Location $location `

>>     -ApiKind MongoDB `

>>     -DefaultConsistencyLevel "Session"

Output:


ResourceGroupName : *********

Location          : eastus

ProvisioningState : Succeeded

Tags              :

ResourceId        : /subscriptions/**********/resourceGroups/*********

For more information on Azure Cosmos Mongo DB refer to the below articles,

Taduturu Balaji 80 Reputation points Microsoft External Staff Moderator

2025-06-19T05:54:57.71+00:00

Hi @Harmeet Kamboj ,

Please do not forget to click "Accept the Answer” and Yes wherever the information provided helps you, this can be beneficial to other community members.

If you have any other questions or still running into more issues, let me know in the "comments" and I would be happy to help you.
Taduturu Balaji 80 Reputation points Microsoft External Staff Moderator

2025-06-20T06:05:38.8633333+00:00

Hi @Harmeet Kamboj ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

Depoyment failure when creating cosmo db with mongo support on azure

1 answer

Your answer