Azure MySQL Flexible Server stuck in "Updating" state – cannot delete or access it

Riad Ahmod 0 Reputation points
2025-12-05T04:22:00.7166667+00:00

Hi there,

I have a MySQL Flexible Server that is currently stuck in the updating state and cannot be deleted via the portal or CLI. I have already removed all associated VNets, subnets, and private endpoints, so there are no visible network dependencies blocking deletion.

I have tried deleting the server using the Azure CLI, but the deletion fails and the server remains in updating and my bill keep increasing.

Guidance on any further steps I need to take to resolve this would also be appreciated.

Thank you for your help.

Azure Database for MySQL
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. VRISHABHANATH PATIL 1,820 Reputation points Microsoft External Staff Moderator
    2025-12-05T07:49:59.54+00:00

    Hey Riad! It sounds like you're having a frustrating issue with your Azure MySQL Flexible Server being stuck in the "updating" state and are unable to delete it. Here are a few steps you can try that might help resolve the situation:

    Error Logs: First, enable the error logs for the MySQL server. This might provide insights into what's causing the update to hang.

    Resource Health: Check the resource health of your server in the Azure portal to see if there are any service issues reported that could be affecting your server.

    Self-Healing: Consider leveraging the Self-Healing functionality offered by Azure Database for MySQL. This can help independently resolve common server problems.

    Resource Locks: Verify that there are no resource locks preventing you from deleting the server.

    Azure CLI: When attempting to delete the server via Azure CLI, ensure you're using the correct syntax. The command would look something like this:

    az mysql flexible-server delete --resource-group myResourceGroup --name myServerName
    

    Make sure to replace myResourceGroup and myServerName with your actual resource group and server name.

    If none of these steps work, you might need to reach out to Azure support for further assistance, as they can take deeper actions on the backend.

    To help diagnose the issue better, here are a few follow-up questions:

    • What specific error messages, if any, are you receiving when trying to delete the server?
    • Have you made any recent changes to the configuration of the server before it became stuck?
    • Are there any specific logs or metrics you've already reviewed?
    • Is your subscription status active, just to rule out any access issues?

    Hope these suggestions help you get your MySQL server back in working order! If you have any more questions, feel free to ask.

    0 comments No comments

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.