Updating the Azure Database for MySQL Flexible Server for WordPress for Azure

Question

I received an email titled Important notice: Billing for extended support for MySQL begins 1 August 2026 . I went looking for the server to upgrade based on this how-to: https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-upgrade

In the portal, I have no such servers.

I suspect that the server I'm getting the notice for is managed by Azure, itself, based on this documentation: https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress#manage-the-mysql-flexible-server-username-or-password-optional

Since I can't open a support request to Microsoft, without paying more money, how do I get them to upgrade the server, themselves, so I don't end-up with higher costs for support - and I can't manage the server[s], myself?

Answer 1

Hello ohn Bailey,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are updating the Azure Database for MySQL Flexible Server for WordPress for Azure.

1. From experience, the only best practice for an Azure Database for MySQL Flexible Server stuck in “Updating” is opening an Azure Support ticket, because backend engineers must manually resync the provisioning state inside Azure’s orchestration layer - https://learn.microsoft.com/azure/mysql/.
2. Before escalating, Azure recommends validating the server’s reported state, attempting a single wait operation, and reviewing activity logs, using the commands below for triage consistency - https://techcommunity.microsoft.com/

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

      az mysql flexible-server wait </span>
        --resource-group <rg> </span>
        --name <server> </span>
        --updated </span>
        --timeout 3600
   

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

3. If your deployment uses Customer-Managed Keys, Azure recommends revalidating the key configuration because unsynchronized encryption metadata can prevent the server from exiting the Updating state - https://learn.microsoft.com/azure/mysql/.

      az mysql flexible-server encryption update </span>
        --resource-group <rg> </span>
        --name <server> </span>
        --cmk-uri <key-uri>
   

4. If the issue persists beyond ~30 minutes or blocks all management actions, you must contact Azure Support under the MySQL Flexible Server platform category so engineers can clear orphaned tasks and forcibly reset the provisioned state - https://learn.microsoft.com/azure/mysql/.

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Answer 2

Hello John Bailey

It looks like the MySQL server you got the “extended support billing” notice for is the platform-managed Flexible Server that App Service spins up for you when you use the WordPress quick start. Because it lives in App Service’s own resource group, it won’t show up in your “Azure Database for MySQL flexible servers” blade and you can’t directly kick off a major-version upgrade on that instance.

Microsoft handles its patching and will bill the extended-support fees once community support ends in August 2026.

If you want full control over upgrades (and avoid any surprise extended-support charges), your best bet is to:

Provision your own Azure Database for MySQL – Flexible Server in your subscription (you’ll see this in the portal or via AZ CLI).

Dump and restore your WordPress database into that new server (this is the recommended way to do a major-version upgrade).

Reconfigure your WordPress site to point at your new server.

From then on you manage patch schedules, major-version upgrades, and you only pay the standard Flexible Server rates.
https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress

Kindly please share the details requested in the private message for further troubleshooting.