Azure Database for MySQL version support policy

APPLIES TO: Azure Database for MySQL - Single Server Azure Database for MySQL - Flexible Server

This page describes the Azure Database for MySQL versioning policy, and is applicable to Azure Database for MySQL - Single Server and Azure Database for MySQL - Flexible Server (Preview) deployment modes.

Supported MySQL versions

Azure Database for MySQL has been developed from MySQL Community Edition, using the InnoDB storage engine. The service supports all the current major version supported by the community namely MySQL 5.6, 5.7 and 8.0. MySQL uses the X.Y.Z naming scheme where X is the major version, Y is the minor version, and Z is the bug fix release. For more information about the scheme, see the MySQL documentation.

Azure Database for MySQL currently supports the following major and minor versions of MySQL:

Version Single Server
Current minor version
Flexible Server
Current minor version
MySQL Version 5.6 5.6.47(Retired) Not supported
MySQL Version 5.7 5.7.32 5.7.37
MySQL Version 8.0 8.0.15 8.0.28


In the Single Server deployment option, a gateway is used to redirect the connections to server instances. After the connection is established, the MySQL client displays the version of MySQL set in the gateway, not the actual version running on your MySQL server instance. To determine the version of your MySQL server instance, use the SELECT VERSION(); command at the MySQL prompt. If your application has a requirement to connect to specific major version say v5.7 or v8.0, you can do so by changing the port in your server connection string as explained in our documentation here.


MySQL v5.6 is retired on Single Server as of February 2021. Starting from September 1st 2021, you will not be able to create new v5.6 servers on Azure Database for MySQL - Single Server deployment option. However, you will be able to perform point-in-time recoveries and create read replicas for your existing servers.

Read the version support policy for retired versions in version support policy documentation.

Major version support

Each major version of MySQL will be supported by Azure Database for MySQL from the date on which Azure begins supporting the version until the version is retired by the MySQL community, as provided in the versioning policy.

Minor version support

Azure Database for MySQL automatically performs minor version upgrades to the Azure preferred MySQL version as part of periodic maintenance.

Major version retirement policy

The table below provides the retirement details for MySQL major versions. The dates follow the MySQL versioning policy.

Version What's New Azure support start date Retirement date
MySQL 5.6 Features March 20, 2018 February 2021
MySQL 5.7 Features March 20, 2018 October 2023
MySQL 8 Features) December 11, 2019 April 2026

Retired MySQL engine versions not supported in Azure Database for MySQL

After the retirement date for each MySQL database version, if you continue running the retired version, note the following restrictions:

  • As the community will not be releasing any further bug fixes or security fixes, Azure Database for MySQL will not patch the retired database engine for any bugs or security issues or otherwise take security measures with regard to the retired database engine. However, Azure will continue to perform periodic maintenance and patching for the host, OS, containers, and any other service-related components.
  • If any support issue you may experience relates to the MySQL database, we may not be able to provide you with support. In such cases, you will have to upgrade your database in order for us to provide you with any support.
  • You will not be able to create new database servers for the retired version. However, you will be able to perform point-in-time recoveries and create read replicas for your existing servers.
  • New service capabilities developed by Azure Database for MySQL may only be available to supported database server versions.
  • Uptime SLAs will apply solely to Azure Database for MySQL service-related issues and not to any downtime caused by database engine-related bugs.
  • In the extreme event of a serious threat to the service caused by the MySQL database engine vulnerability identified in the retired database version, Azure may chose to stop the compute node of your database server to secure the service first. You will be asked to upgrade the server before bringing the server online. During the upgrade process, your data will always be protected using automatic backups performed on the service which can be used to restore back to the older version if desired.

Next steps