Azure Database for MariaDB server stuck in “Stopping” — can’t start or delete

Andriy Kravchuk 0 Reputation points
2025-05-28T14:03:53.12+00:00

Hi all,

I’m encountering a control-plane issue with an Azure Database for MariaDB (Single Server) instance.

I manually pressed Stop on the server via Azure Portal. Since then, the server has been stuck in:

"userVisibleState": "Stopping"

  1. It's been over 2 hours.
  2. The Start and Delete buttons are greyed out.
  3. I confirmed the state via Azure CLI: az mariadb server show --name iam-db --resource-group iam --query userVisibleState

What I’ve tried:

  • Waited >2 hours
  • CLI confirms "Stopping" state
  • Attempted deletion from CLI and Portal — both blocked
  • Confirmed this is not an InnoDB recovery issue — the DB was idle and healthy before the stop
  • Cannot open a technical support ticket (basic plan)

Is there any way to force-complete this lifecycle transition or escalate to backend support without a paid plan?

Alternatively:

Does deleting the entire resource group help bypass the stuck state?

Any Microsoft-side remediation path for this known control-plane bug?


Thanks in advance. Open to workarounds or references to existing incident IDs.


Let me know if you're posting on Microsoft Q&A, GitHub, or Twitter — I can tweak tone/form for each platform.

Azure Database for MariaDB
Azure Database for MariaDB
An Azure managed MariaDB database service for app development and deployment.
64 questions
{count} votes

Your answer

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