Azure Database for MySQL flexible server stuck in "updating state"

Use the following steps to handle an Azure Database for MySQL Flexible Server that is stuck in the Updating state:

1. Wait and recheck status via CLI
   • Some operations (provisioning, scaling, maintenance) can legitimately take several minutes.
   • Use Azure CLI to poll the server state:

          az mysql flexible-server show \
            --resource-group <your-rg> \
            --name <your-server-name> \
            --query state -o tsv
     

   • Alternatively, use the built-in wait command to block until the provisioning state is Succeeded or a timeout is reached:

          az mysql flexible-server wait \
            --resource-group <your-rg> \
            --name <your-server-name> \
            --updated \
            --timeout 3600
     

     or, if the server was just created:

          az mysql flexible-server wait \
            --resource-group <your-rg> \
            --name <your-server-name> \
            --created
     

2. Check for CLI-level errors
   • If CLI commands fail with specific error codes (for example InvalidParameterValue, MissingSubscriptionRegistration, LocationNotAvailableForResourceType, ResourceGroupBeingDeleted), follow the documented mitigations, such as:
     • Registering the provider:

              az provider register --namespace Microsoft.DBMySQL
       

     • Verifying subscription and resource group:

              az account list --output table
              az group show --name <your-rg>
       

     • Validating parameter values against the CLI reference documentation.
3. Check activity logs for backend issues
   • If operations are hanging or failing with InternalServerError, inspect the activity log for the server using the correlation ID from any failed CLI/portal operation:

          az monitor activity-log list --correlation-id <correlation-id>
     

   • This can reveal backend or platform issues that keep the server in Updating.
4. Avoid management operations while stuck
   • When a Flexible Server is in a non-ready state (such as Updating), other management operations (scale, restart, stop/start, configuration changes) may be blocked until the current operation finishes or fails. Wait for the state to change back to Ready before attempting additional changes.
5. If the state persists, contact Microsoft support
   • If the server remains in Updating for an unusually long time (for example, significantly longer than similar operations in the same environment) and no clear error is visible in CLI or activity logs, open a support request so the platform team can inspect the backend operation:
     • In Azure portal, file a request via Help + support for Azure Database for MySQL – Flexible Server.

These steps align with the documented guidance for monitoring and troubleshooting Azure Database for MySQL Flexible Server operations and CLI errors. If the platform operation is stuck on the service side, only Microsoft support can force-complete or repair it.

References:

• Troubleshoot Azure Database for MySQL - Flexible Server CLI errors
• Tutorial: Deploy WordPress app on AKS with Azure Database for MySQL - Flexible Server
• Restart/stop/start an Azure Database for MySQL - Flexible Server instance using Azure CLI
• What is Azure Database for MySQL - Flexible Server?
• az mysql flexible-server wait