Azure Database for MySQL 5.7 end of life (EOL) date and support status
End of life End of life since 2026-09-30 (8 days ago)
Upgrade: Azure Database for MySQL 5.7 no longer receives fixes. Supported cycles: 8.4, 8.0.
| Product | Azure Database for MySQL |
|---|---|
| Version cycle | 5.7 |
| Status | End of life |
| Released | 2018-03-20 |
| Active support until | — |
| End of life | 2026-09-30 |
| Latest version | — |
| Last verified | 2026-10-08 |
All Azure Database for MySQL versions → · Source: endoflife.date
Frequently asked questions
Is Azure Database for MySQL 5.7 end of life?
Yes. End of life since 2026-09-30 (8 days ago). It no longer receives security or bug fixes.
When does Azure Database for MySQL 5.7 reach end of life?
Azure Database for MySQL 5.7 reached end of life on 2026-09-30.
When was Azure Database for MySQL 5.7 released?
Azure Database for MySQL 5.7 was first released on 2018-03-20.
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
For agents
GET https://vigia.coredls.cloud/v1/eol/azure-database-for-mysql/5.7