This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 67%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
I am experiencing an issue where my Azure Cosmos DB for MongoDB (with vCore architecture) cluster remains in the 'Stopped' state even after I paid the outstanding bill and reactivated my Azure subscription. The cluster does not start automatically, and the 'Start' button is not available in the Azure portal. I want to understand why this is happening and how to resolve it.
Azure Cosmos DB for MongoDB (M50 tier, 8 vCores, 32 GiB RAM) cluster, region not specified in the case information.
I paid the outstanding bill and reactivated my Azure subscription. I checked the cluster in the portal, but it remained stopped with no automatic restart. I reviewed the available self-help documentation, but there was no manual start performed. No diagnostic logs, activity logs, or error messages were available. I did not attempt to start the cluster manually in the portal.
Currently, the cluster remains stopped despite subscription reactivation, and I am seeking guidance on how to manually start the cluster or troubleshoot the reason for its inactivity.
An Azure NoSQL database service for app development.
I think Billing Support is the next step. If ur subscription is Enabled but the cluster is still Stopped after 30 minutes, check it with az documentdb mongocluster show --ids "<resource-id>". There's no CLI start command for MongoDB vCore, and u don't have a Start button in the portal either.
Send the resource ID, command output and reactivation time to support. Stopped alone doesn't tell why it hasn't come back.