Azure Cosmos DB: Resource Stuck in Updating State — Unable to Complete Region Move

Question

Azure Cosmos DB: Resource Stuck in Updating State — Unable to Complete Region Move

ViBenderest-3341 0

Problem description

I am facing an issue where my Azure Cosmos DB for MongoDB (vCore) resource, ', has been stuck in the 'Updating' provisioning state since August 16, 2026. Attempts to move the resource to West Europe region have failed, and the resource remains in an indefinite 'Updating' status.

Also the CPU hangs on 100%

Environment

Azure Cosmos DB for MongoDB (vCore) account in a Europe region, running under a Developer subscription, provisioned with vCore-based compute and managed storage.

What I've already tried

On August 16, 2026, I initiated an update operation on the resource, which has not completed but it stays in 'Updating' with no progress. I have checked the Deployment blade and activity logs, but no successful state transition or error details are available. I also deleted a failed job related to this resource, but it did not resolve the issue.

Current status

I am seeking guidance on how to clear the stuck update operation and successfully move or reset the resource to a stable state.

Jose Benjamin Solis Nolasco 12,201 Reputation points Volunteer Moderator

2026-08-25T19:59:33.0166667+00:00

@ViBenderest-3341 I hope you are doing well,

I'm going to scale this thread so MS can take a look if the issues probably on backend

Thanks

1 answer

Your answer

Jose Benjamin Solis Nolasco 12,201 Reputation points Volunteer Moderator

2026-08-25T19:59:33.0166667+00:00

@ViBenderest-3341 I hope you are doing well,

I'm going to scale this thread so MS can take a look if the issues probably on backend

Thanks

Answer 1

Hello @ViBenderest-3341

Azure Cosmos DB for MongoDB (vCore) does not support a direct move to another Azure Resource Manager region, since the Microsoft.DocumentDB/mongoClusters resource type lists Region move: No in Microsoft's resource move support matrix.

The fact that the cluster has been updating since August 16th suggests the update operation itself may be stuck at the service/backend level, so it would be advisable to avoid any further update or move operations while it remains in this state.

I suggest:

Look at the Resource Health and Activity Log for the cluster and note the failed operation or correlation ID.
Check the current state using the Azure CLI or REST API rather than relying solely on the portal.
If the 'Updating' message continues to appear, open an Azure Support request for Cosmos DB for MongoDB (vCore) and include the resource ID, correlation ID, timestamp of the original operation, and that CPU consistently reaches 100%. Microsoft might then have to clear or investigate the backend operation.
Once the cluster is stable, do not attempt to move an ARM region. If the requirement is West Europe, plan to migrate or replicate to a cluster in that region using a supported approach. Microsoft has specifically provided migration guidance for vCore-based Cosmos DB for MongoDB.

The 100% CPU usage should also be covered by the support package, since it could indicate a separate workload or capacity issue, or it might be related to the incomplete operation.

Sharing these references with you:

Azure resource move support – Microsoft.DocumentDB

Migrate to vCore-based Azure Cosmos DB for MongoDB

Please "Accept the Answer" if this information helped you. This will help us and others in the community.