Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Database for MySQL provides a fully managed database service powered by the MySQL community edition, enabling developers to build and scale applications efficiently. This article outlines the version support policy for Azure Database for MySQL, detailing the lifecycle management, including version availability, updates, and end-of-support timelines. Customers can ensure their applications remain secure, performant, and aligned with the latest MySQL innovations while minimizing disruption during version transitions, by understanding this policy.
Supported MySQL versions
Azure Database for MySQL was developed from the MySQL Community Edition, using the InnoDB storage engine. The service supports the community's current major versions, namely MySQL 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 | Current minor version | Release status |
|---|---|---|
| MySQL Version 5.7 | 5.7.44 | GA |
| MySQL Version 8.0 | 8.0.41 | GA |
| MySQL Version 8.4 | 8.4.4 | Public Preview |
| MySQL Version 9.2 | 9.2.0 | Public Preview |
Read the version support policy for retired versions in version support policy documentation.
Major version support
Azure Database for MySQL supports each major version of MySQL from the date Azure begins supporting it until the MySQL community retires it, as provided in the versioning policy.
Major version retirement policy
The retirement details for MySQL major versions are listed in the following table. Dates shown follow the MySQL versioning policy.
| Version | What's New | Azure Support Start Date | Community Retirement Date | Azure Standard Support End Date | Azure Extended Support Start Date | Azure Extended Support End Date |
|---|---|---|---|---|---|---|
| MySQL 5.7 | Features | March 20, 2018 | October 31, 2023 | March 31, 2026 | April 1, 2026 | May 1, 2029 |
| MySQL 8 | Features | December 11, 2019 | April 30, 2026 | April 30, 2026 | June 1, 2026 | April 30, 2029 |
What happens after standard support ends?
To provide customers with sufficient time to decide whether to upgrade or be enrolled in Extended Support, the Extended Support plan officially begins sometime early 2026.
After the standard support end date, Azure Database for MySQL servers running on unsupported MySQL versions are automatically enrolled in Extended Support and are automatically charged for this service after a one-month grace period. Extended Support provides critical security updates for up to three years after the end of standard Support, allowing customers more time to plan and execute major version upgrades. To avoid Extended Support charges, you must upgrade your Azure Database for MySQL server to a MySQL version that is still within standard Support.
During the Extended Support period, Microsoft prioritizes the service's availability, reliability, and security. Essential modifications are implemented to ensure the service remains accessible and protected, but new features and minor version upgrades might not be guaranteed.
Note
Extended Support is automatically applied and charged to servers running on legacy MySQL versions after standard Support ends. To opt out of Extended Support and avoid charges, customers must upgrade to a supported major version of the software. For more information or to provide feedback, contact Ask Azure Database For MySQL.
Pricing is available on the pricing page later this year.
Innovation release version support
The MySQL Innovation Release versions are provided to enable access to the latest MySQL features and capabilities. Support for these versions includes core functionalities but excludes advanced features such as High Availability (HA), replicas, and automated backups. Innovation Release support is limited to the most current version, with previous versions not retained to ensure users have access to the newest advancements. Each Innovation Release server has a 30-day lifecycle from the date of creation, after which it's automatically removed. No monthly maintenance updates are applied during the lifecycle of these versions.
Note
Innovation Release versions are intended for early access and experimentation. As such, they don't qualify for customer support cases, and no direct support assistance is provided. Users are encouraged to refer to documentation and community resources for troubleshooting and guidance.
Minor version support
Azure Database for MySQL automatically performs minor version upgrades to the Azure-preferred version as part of periodic maintenance.
Retired MySQL engine versions not supported in Azure Database for MySQL
The following restrictions apply only after the extended pport period has ended, and your server is still running a retired MySQL version:
- No further security or support updates are provided for the retired version. Azure Database for MySQL can't patch the retired database engine for any bugs or security issues, and support for database engine-related issues are no longer be available. However, Azure continues performing periodic maintenance and patching for the host, OS, containers, and other service-related components.
- You can't create new database servers for the retired version. However, you can perform point-in-time recoveries and create read replicas for your existing servers. New service capabilities developed by Azure Database for MySQL might only be available for supported database server versions.
- Uptime S.L.A.s 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 might choose to stop the compute node of your database server from securing the service first. You're asked to upgrade the server before bringing it online. During the upgrade process, your data is always protected by automatic backups performed on the service, which can be used to restore it to an older version if desired.
Frequently asked questions (FAQ)
Q: What happens if I don't upgrade my Azure Database for MySQL server to a supported major version after standard support ends?
A: If you don't upgrade your Azure Database for MySQL server to a supported major version before the Azure extended support start date, your server is automatically enrolled in extended support, and you're charged for this service. To avoid extended support charges, you must upgrade your server to a MySQL version that is still within the standard support Period.
Q: What is the process for performing a major version upgrade on Azure Database for MySQL?
A: Azure Database for MySQL enables you to carry out in-place major version upgrades using the Major Version Upgrade (MVU) feature. Consult the Major version upgrade in Azure Database for MySQL Major version upgrade in Azure Database for MySQL document for more detailed information.
Q: Are there any expected downtime or performance impacts during a major version upgrade?
A: Yes, there's some downtime during the major version upgrade process. The specific duration varies depending on factors such as the size and complexity of the database. We recommend conducting a test upgrade in a nonproduction environment to assess the expected downtime and evaluate potential performance. To minimize downtime for your applications during the upgrade, you can explore the option of performing a minimal downtime major version upgrade using read replica.
Q: Can I roll back to a previous major version after upgrading?
A: While it's not recommended to downgrade to a previous major version after upgrading, we acknowledge that there might be specific scenarios where this flexibility becomes necessary. To ensure a smooth upgrade process and alleviate any potential concerns, it's advisable to adhere to best practices by performing a comprehensive on-demand backup, before proceeding with the upgrade.
This backup serves as a precautionary measure, allowing you to restore your database to its previous version on another new Azure Database for MySQL if needed.
Q: What are the main advantages of upgrading to a newer major version?
A: Newer major versions of MySQL come with a host of improvements, including enhanced performance, security, and new features. For details, refer to the relevant MySQL release notes.
Q: Are there any compatibility issues to be aware of when upgrading to a newer major version?
A: Changes in newer major versions might cause some compatibility issues. It's important to test your applications with the new version before upgrading the production database. Refer to MySQL's official documentation for a comprehensive list of compatibility issues.
Q: What support is available if I encounter issues during the upgrade process?
A: If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and you need technical help, create a support request.
Q: What happens to my data during the upgrade?
A: While your data remains unaffected during the upgrade process, it's highly advisable to create a backup before proceeding with the upgrade. This precautionary measure helps mitigate the risk of potential data loss due to any unforeseen complications.