Azure Cosmos DB: Cluster Remains Stopped After Subscription Reactivation — Manual Start Required

DG-9429 0 Reputation points
2026-10-09T10:27:54.42+00:00

Problem description

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.

Environment

Azure Cosmos DB for MongoDB (vCore) cluster, region not specified in the case information.

What I've already tried

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.

Current status

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.

Azure Cosmos DB
Azure Cosmos DB

An Azure NoSQL database service for app development.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alex Burlachenko 25,530 Reputation points MVP Volunteer Moderator
    2026-10-09T11:15:44.6866667+00:00

    Hi DG-9429 & thx for join me at Q&A platform,

    so ... subscription reactivation issue rather than something wrong with ur MongoDB cluster configuration. Paying the outstanding balance reactivates the subscription, but it doesn't necessarily mean every suspended service will immediately recover its previous state.

    One important detail Cosmos DB for MongoDB vCore doesn't have the same Start/Stop controls as Cosmos DB for PostgreSQL. So if u can't find a Start button, that's not necessarily a portal bug. Don't use the PostgreSQL cluster start commands here, bc they don't apply to MongoDB vCore. I'd first confirm the subscription is fully Active, Microsoft.DocumentDB is registered, and check the cluster's actual provisioningState and clusterStatus using az cosmosdb mongocluster show. Also check the Activity Log for any failed operations around the subscription reactivation.

    If the cluster still reports Stopped and there's no supported way to start it, this is likely a backend recovery/state-sync issue. I'd open a Cosmos DB support case and ask the engineering team to check why the MongoDB vCore cluster wasn't restored after billing reactivation. Include the cluster resource ID, payment/reactivation time, and current resource state.

    I wouldn't delete or recreate the cluster rn. U don't wanna risk losing data over what may just be a stuck service-side recovery operation

    rgds,

    Alex

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.