Azure Database for MySQL 8.0 — lifecycle date eolFrom is now 2027-01-31
For Azure Database for MySQL 8.0, product is azure-database-for-mysql; field changed is eolFrom; previous value is 2026-12-31; new value is 2027-01-31; detected is 2026-09-14, verified against its source on 2026-09-14.
- Product
- azure-database-for-mysql verified
- Product label
- Azure Database for MySQL verified
- Release cycle
- 8.0 verified
- Field changed
- eolFrom verified
- Previous value
- 2026-12-31 verified
- New value
- 2027-01-31 verified
- Detected
- 2026-09-14 verified
What the source says
{"name":"8.0","codename":null,"label":"8.0","releaseDate":"2019-12-11","isLts":false,"ltsFrom":null,"isEol":false,"eolFrom":"2027-01-31"
— endoflife.date, retrieved 2026-09-14
Source
- endoflife.datehttps://endoflife.date/api/v1/products/azure-database-for-mysql
This one changes, and we watch it.Software end-of-life date changes — which dates moved and what they were before is re-read on a schedule and every change is dated. Subscribe: Atom feed · JSON · what has changed so far.