Azure Cosmos Mongodb: Cluster Remains Stopped After Subscription Reactivation - Manual Restart Required

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 (M50 tier, 8 vCores, 32 GiB RAM) 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.