Merge pull request #268225 from code-sidd/replica_al

al replica limitation

Author: prmerger-automator[bot]

articles/mysql/flexible-server/concepts-accelerated-logs.md

@@ -36,20 +36,18 @@ Database servers with mission-critical workloads demand robust performance, requ
 
 ## Limitations
 
-- New primary servers created under the Business Critical service tier created after *November 14* are eligible to use the accelerated logs feature. The accelerated logs feature is only available for the Business Critical service tier.
-
 - During the preview phase,  you can't enable the accelerated logs feature on servers that have the following features enabled.
     - [High Availability](./concepts-high-availability.md) (HA) servers.
-    - [Read Replica](./concepts-read-replicas.md) servers.
+    - Primary servers with [Read Replica](./concepts-read-replicas.md) servers created. 
     - Servers enabled with [Customer Managed Keys](./concepts-customer-managed-key.md)  (CMK).
-    - Servers enabled with [Microsoft Entra ID](./concepts-azure-ad-authentication.md) authentication.
 
 - Performing a [major version upgrade](./how-to-upgrade.md) on your Azure Database for MySQL flexible server instance with the accelerated logs feature enabled is **not supported**. Suppose you wish to proceed with a major version upgrade. In that case, you should temporarily [disable](#disable-accelerated-logs-feature-preview) the accelerated logs feature, carry out the upgrade, and re-enable the accelerated logs feature once the upgrade is complete.
 
 - Accelerated logs feature in preview is currently available only in specific regions. [Learn more about supported regions](#the-accelerated-logs-feature-is-available-in-the-following-regions).
 
 - After the accelerated logs feature is activated, any previously configured value for the ["binlog_expire_seconds"](https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_binlog_expire_logs_seconds) server parameter will be disregarded and not considered.
 
+
 ## The accelerated logs feature is available in the following regions
 
 - Australia East

articles/mysql/flexible-server/whats-new.md

@@ -26,6 +26,17 @@ This article summarizes new releases and features in Azure Database for MySQL fl
 
 ## February 2024
 
+
+- **Accelerated Logs is now available for exisiting servers and available in three new regions.**
+    
+  Accelerated Logs, previously limited to servers created after November 14th, is now accessible for all existing Business Critical tier's **standalone** servers in preview phase. Accelerated logs now also supports [Microsoft Entra ID](./concepts-azure-ad-authentication.md). Additionally, this feature has been extended to include three new regions: Japan East, Korea Central, and Poland Central. [Learn more.](./concepts-accelerated-logs.md) 
+
+
+- **Known Issues**
+
+  Due to a technical issue in this month's deployment, primary servers with read-replica are temporarily restricted from enabling the [accelerated logs](./concepts-accelerated-logs.md) feature. Users are advised to disable accelerated logs feature before creating a replica server. If you require assistance with accelerated logs and replica creation, please open a [support ticket](https://azure.microsoft.com/support/create-ticket) for assistance. [Learn more](./concepts-accelerated-logs.md#limitations).
+
+
 - **Audit logs now supports wild card entries**
 
   The server parameters now supports wildcards in `audit_log_include_users` and `audit_log_exclude_users`, enhancing flexibility for specifying user inclusions and exclusions in audit logs. [Learn more](./concepts-audit-logs.md#configure-audit-logging)