Unknown cause for failing CosmoMongo DB

Question

Unknown cause for failing CosmoMongo DB

Cliff Eby 0

{
  "code": "DeploymentFailed",
  "target": "/subscriptions/f0f3c820-972e-4333-90ef-cf03c7007d4a/resourceGroups/BDay/providers/Microsoft.Resources/deployments/CosmosDB-MongoDB-rochdb-d358d4eb8eee43fa9166b3ef2933e4e4",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
  "details": [
    {
      "code": "ResourceDeploymentFailure",
      "target": "/subscriptions/f0f3c820-972e-4333-90ef-cf03c7007d4a/resourceGroups/BDay/providers/Microsoft.DocumentDB/mongoClusters/rochdb",
      "message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
    }
  ]
}

{
  "code": "UnprocessableEntity",
  "message": "An unknown error occurred for the operation. Tracking id: 197080d6-ceb0-41ae-bf6a-d37391a753f1."
}

Anonymous

2025-12-23T03:39:15.58+00:00

Hi @Cliff Eby

Thank you for reaching out to Microsoft QA and 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 specified region is impacting your deployment.

Currently, there’s no confirmed ETA for restoration of provisioning capabilities in 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.

Your answer

Anonymous

2025-12-23T03:39:15.58+00:00

Hi @Cliff Eby

Thank you for reaching out to Microsoft QA and 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 specified region is impacting your deployment.

Currently, there’s no confirmed ETA for restoration of provisioning capabilities in 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.