Azure Database for MySQL January 2026 version release notes

The January 2026 version of Azure Database for MySQL Flexible Server is now available. Starting January 22, 2026, all new servers automatically use this version. Existing servers upgrade during their next scheduled maintenance. To upgrade your servers earlier, enroll in the Virtual Canary Program.

This version introduces new features and enhancements, resolves known problems, and includes important security patches to ensure optimal performance and security.

Maintenance scheduling considerations

For Azure Database for MySQL instances in China regions, the certificate that the current Certificate Authority (CA) issued will expire after the Spring Festival in 2026. After the certificate expires, client connections to the server fail, resulting in service unavailability.

To assess whether your server is affected, verify the certificate expiration date from a client environment by using the following command:openssl s_client -starttls mysql -connect <server_dns>:3306. For affected servers, the maintenance reschedule window is limited and can't be freely postponed, as further delay increases the risk of certificate expiration and client connection failures. In some cases, if the server was restarted recently, the certificate is automatically refreshed. If you believe this condition applies to your server, open an Azure Support case.

During this maintenance cycle, there are major global events that might limit our ability to fully honor all customers' Custom Maintenance Window (CMW) preferences during initial scheduling. As a result, some servers with CMW enabled might be assigned a maintenance date outside of their preferred window. You can still reschedule the maintenance in the Azure portal to better align with these event periods or your original CMW preference.

Engine version changes

This version doesn't include any engine version changes.

Features

This version doesn't introduce any new features.

Improvements

  • Improved the error message that's shown when you attempt to enable HA on a VNET-based instance that still has Accelerated Logs enabled.
  • Added TLS 1.3 support for Azure MySQL 5.7 version.

Known issues fixes

  • Fixed an issue where enabling geo backup caused subsequent GTID reset operations to fail.
  • Fixed an issue where certain HA servers behind a dedicated SLB couldn't enable a private endpoint.