Merge pull request #270186 from xboxeer/patch-24

Create april-2024.md

Author: PMEds28

articles/mysql/TOC.yml

@@ -31,6 +31,8 @@
             href: flexible-server/release-notes/january-2024.md
           - name: February 2024
             href: flexible-server/release-notes/february-2024.md
+          - name: April 2024
+            href: flexible-server/release-notes/april-2024.md            
       - name: Compute and storage
         href: flexible-server/concepts-service-tiers-storage.md
   - name: Quickstarts

articles/mysql/flexible-server/release-notes/april-2024.md

@@ -0,0 +1,32 @@
+---
+title: Release notes for Azure Database for MySQL Flexible Server - April 2024
+description: Learn about the release notes for Azure Database for MySQL Flexible Server April 2024.
+author: xboxeer
+ms.author: yuzheng1
+ms.date: 03/26/2024
+ms.service: mysql
+ms.subservice: flexible-server
+ms.topic: conceptual
+---
+
+# Azure Database For MySQL Flexible Server April 2024 Maintenance
+
+We're pleased to announce the April 2024 maintenance for Azure Database for MySQL Flexible Server. This maintenance incorporates several new features and improvement, along with known issue fix, minor version upgrade, and security patches.
+
+## Engine version changes
+All existing engine version server upgrades to 8.0.36 engine version.
+
+To check your engine version, run `SELECT VERSION();` command at the MySQL prompt
+
+## Features
+- Support for Azure Defender for Azure DB for MySQL Flexible Server
+
+## Improvement
+- Expose old_alter_table for 8.0.x.
+
+## Known Issues Fix
+- Fixed the issue where `GTID RESET` operation's retry interval was excessively long.
+- Fixed the issue that data-in HA failover stuck because of system table corrupt
+- Fixed the issue that in point-in-time restore that database or table starts with special keywords may be ignored
+- Fixed the issue where, if there's replication failure, the system now ignores the replication latency metric instead of displaying a '0' latency value.
+- Fixed the issue where under certain circumstances MySQL RP does not correctly get notified of a "private dns zone move operation". The issue will cause the server to be showing incorrect ARM resource ID of the associated private dns zone resource.