Azure Database for MySQL: MySQL 8.0 end of extended support

After the extended support period ends, no further security or support updates are provided for MySQL 8.0 on servers still running it.

• Azure cannot patch the retired database engine, and support for engine-related issues is no longer available.
• Azure continues periodic maintenance and patching for the host, OS, containers and other service-related components.
• New database servers cannot be created for the retired version. Point-in-time recoveries and read replicas for existing servers remain possible.
• If an engine vulnerability in the retired version seriously threatens the service, Azure might stop the compute node of the server and ask for an upgrade before bringing it online.
• Uptime SLAs apply only to service-related issues, not to downtime caused by database engine bugs.

1. Upgrade to a supported major version. Upgrade read replicas that use an older MySQL version before upgrading the primary server.
2. Check schema compatibility with the target version using the Validate feature in the Azure portal. Validation locks tables, and the page directs large-scale production environments to Oracle's client-side upgrade checker tool. Verify deprecated sql_mode values and remove or deselect them in the Server Parameters pane before upgrading, to avoid deployment failure.
3. Ensure there are no active or pending XA transactions on the database. Ongoing XA transactions can cause the upgrade to fail.
4. Trigger an on-demand backup before the major version upgrade of a production server.
5. Perform the upgrade first on a restored server copy rather than on production directly.
6. In the Azure portal, open the server, and on the Overview page select Upgrade. The major version upgrade is irreversible. Burstable SKU servers use a separate workflow that first upgrades the compute tier to a General-Purpose SKU. See Major version upgrade in Azure Database for MySQL.