← ← Back to all products
Azure Database for MySQL
Active
OtherLatest Version: 8.4Latest Release: N/A
Support summary
Azure Database for MySQL currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
Dec 31, 2026
Azure Database for MySQL 8.0 · 132 days left
Supported cycles
2
0 lts
Versions
3
Latest Version
8.4
Active Support
2
EOL
1
Lifecycle Timeline
Today ↓
8.4
8.4
8.0
8.0
5.7
5.7
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 8.4 | Sep 1, 2025 | Yes | No | 8.4 | No | Active |
| 8.0 | Dec 11, 2019 | Yes | Dec 31, 2026 | 8.0 | No | Active |
| 5.7 | Mar 20, 2018 | No | Jul 31, 2026 | 5.7 | No | EOL |
Data sources
Frequently Asked Questions
Which versions of Azure Database for MySQL have reached end of life?
The following Azure Database for MySQL versions have reached end of life and no longer receive security updates: 5.7. It is recommended to upgrade to a supported version.
Is it safe to continue using Azure Database for MySQL 5.7?
Azure Database for MySQL 5.7 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Azure Database for MySQL?
The latest version of Azure Database for MySQL is 8.4, released in the 8.4 release cycle.
How many versions of Azure Database for MySQL are currently supported?
Azure Database for MySQL currently has 2 actively supported version(s): 8.4, 8.0.
When does Azure Database for MySQL 8.4 reach end of life?
Azure Database for MySQL 8.4 does not have a specific end-of-life date announced yet.
What should I do when Azure Database for MySQL reaches end of life?
When a Azure Database for MySQL version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.