Merge pull request #4872 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-20 17:11 UTC

Author: learn-build-service-prod[bot]

articles/mysql/concepts-version-policy.md

@@ -24,10 +24,10 @@ Azure Database for MySQL currently supports the following major and minor versio
 
 | Version | Current minor version | Release status |
 | --- | --- | --- |
-| MySQL Version 5.7 | [5.7.44](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html) | GA |
-| MySQL Version 8.0 | [8.0.42](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-42.html) | GA |
-| MySQL Version 8.4 | [8.4.5](https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-5.html) | GA |
-| MySQL Version 9.3 | [9.3.0](https://dev.mysql.com/doc/relnotes/mysql/9.1/en/news-9-3-0.html) | Public Preview |
+| MySQL Version 5.7 | [5.7.44](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html) | GA (Retired) |
+| MySQL Version 8.0 | [8.0.44](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-44.html) | GA |
+| MySQL Version 8.4 | [8.4.7](https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-7.html) | GA |
+| MySQL Version 9.5 | [9.5.0](https://dev.mysql.com/doc/relnotes/mysql/9.6/en/news-9-5-0.html) | Public Preview ([Innovation Release](#innovation-release-version-support)) |
 
 Read the version support policy for retired versions in [version support policy documentation.](concepts-version-policy.md#retired-mysql-engine-versions-not-supported-in-azure-database-for-mysql)
 
@@ -61,7 +61,7 @@ During the Extended Support period, Microsoft prioritizes the service's availabi
 
 ## Innovation release version support
 
-The MySQL Innovation Release versions are provided to enable access to the latest MySQL features and capabilities. Support for these versions includes core functionalities but excludes advanced features such as High Availability (HA), replicas, and automated backups. Innovation Release support is limited to the most current version, with previous versions not retained to ensure users have access to the newest advancements. Each Innovation Release server has a 30-day lifecycle from the date of creation, after which it's automatically removed. No monthly maintenance updates are applied during the lifecycle of these versions.
+The MySQL Innovation Release versions are provided to enable access to the latest MySQL features and capabilities. Support for these versions includes core functionalities but excludes advanced features such as High Availability (HA), replicas, and automated backups. Innovation Release support is limited to the most current version, with previous versions not retained to ensure users have access to the newest advancements. Each Innovation Release server has a 30-day lifecycle from the date of creation, after which it's automatically removed. No monthly maintenance updates are applied during the lifecycle of these versions. The Innovation Release track does not go GA.
 
 > [!NOTE]  
 > Innovation Release versions are intended for early access and experimentation. As such, they don't qualify for customer support cases, and no direct support assistance is provided. Users are encouraged to refer to documentation and community resources for troubleshooting and guidance.

articles/mysql/flexible-server/concept-performance-best-practices.md

@@ -82,7 +82,7 @@ While partitioning has its benefits, it also has some limitations, such as the l
 
 Most applications primarily read from the database, with only a small percentage of the interactions involving writes. The number of active connections on the primary database we calculated for the connection pools likely includes read traffic. Offloading as many queries to read replicas as possible and conserving access to the primary writable instance increases the amount of overall database activity performed by the application servers without increasing the load on the primary database. If you aren't already accessing read replicas at least for longer running queries such as reports, you should consider immediately moving reporting or analytics to read replicas.
 
-Wider scale use of read replicas might require more careful consideration, as replicas lag slightly behind the primary because of the asynchronous nature of replication. Find as many areas of the application as possible that can be served with reads from the replicas with minor code changes. You should also apply this method at higher levels concerning caching - serve more of the read only or slowly changing content from a dedicated caching tier such as [Azure Cache for Redis](https://azure.microsoft.com/services/cache/).
+Wider scale use of read replicas might require more careful consideration, as replicas lag slightly behind the primary because of the asynchronous nature of replication. Find as many areas of the application as possible that can be served with reads from the replicas with minor code changes. You should also apply this method at higher levels concerning caching - serve more of the read only or slowly changing content from a dedicated caching tier such as [Azure Managed Redis](/azure/redis/overview).
 
 ## Write scaling and sharding