{
  "slug": "azure-mysql-5-7-end-of-support",
  "title": "Azure Database for MySQL: MySQL 5.7 end of standard support",
  "summary": "Azure Standard Support End Date for MySQL 5.7 on Azure Database for MySQL: 30 Sep 2026. After that date, servers still running the version are automatically enrolled in Extended Support and charged for it.",
  "cloud": "azure",
  "service": "Azure Database for MySQL",
  "service_slug": "mysql",
  "category": "database",
  "type": "end_of_support",
  "announced_date": null,
  "effective_date": "2026-09-30",
  "effective_precision": "day",
  "impact": "After the Standard Support end date, servers running MySQL 5.7 are automatically enrolled in Extended Support and automatically charged for it.\n\n- Extended Support provides critical security updates for up to three years after the end of Standard Support.\n- New features and minor version upgrades might not be guaranteed.\n- The charge is billed per vCore per hour, so read replicas and HA-enabled servers are billed for the additional vCores they consume.\n- Servers in stopped state are not charged for Extended Support.",
  "migration_path": "1. Choose a target MySQL version that is still within Standard Support. Upgrading to it avoids Extended Support charges.\n2. Upgrade read replicas that use an older MySQL version before upgrading the primary server.\n3. Check schema compatibility with the target version using the Validate feature in the Azure portal. Validation locks tables, and the page directs large-scale production environments to Oracle's client-side upgrade checker tool. Verify deprecated sql_mode values and remove or deselect them in the Server Parameters pane before upgrading, to avoid deployment failure.\n4. Ensure there are no active or pending XA transactions on the database. Ongoing XA transactions can cause the upgrade to fail.\n5. Trigger an on-demand backup before the major version upgrade of a production server, and perform the upgrade first on a restored server copy rather than on production directly.\n6. In the Azure portal, open the server, and on the Overview page select Upgrade. The major version upgrade is irreversible. Burstable SKU servers use a separate workflow that first upgrades the compute tier to a General-Purpose SKU. See [Major version upgrade in Azure Database for MySQL](https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-upgrade).",
  "replacement": null,
  "affected_versions": [
    "5.7"
  ],
  "source_url": "https://learn.microsoft.com/azure/mysql/concepts-version-policy",
  "extra_source_urls": [
    "https://endoflife.date/azure-database-for-mysql"
  ],
  "vendor_ref": "azure-database-for-mysql@5.7",
  "last_checked_at": "2026-11-12T09:55:37.239Z",
  "created_at": "2026-11-13T13:36:44.208Z",
  "updated_at": "2026-11-13T13:36:44.208Z",
  "url": "https://eolwatch.dev/items/azure-mysql-5-7-end-of-support",
  "short_url": "https://eolwatch.dev/i/y",
  "markdown_url": "https://eolwatch.dev/items/azure-mysql-5-7-end-of-support.md",
  "json_url": "https://eolwatch.dev/items/azure-mysql-5-7-end-of-support.json",
  "estate_check": {
    "resource_types": [
      "microsoft.dbformysql/flexibleservers",
      "azurerm_mysql_flexible_server"
    ],
    "fields": [
      "pgversion",
      "version"
    ],
    "inputs": [
      "Azure Resource Graph export (CSV or JSON)",
      "Terraform state or plan (JSON)",
      "ARM template"
    ]
  },
  "source_note": null
}