Merge pull request #3140 from MicrosoftDocs/main

Auto Publish – main to live - 2025-09-21 17:00 UTC

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

articles/mysql/flexible-server/concepts-customer-managed-key.md

@@ -105,7 +105,9 @@ When you configure data encryption with a CMK in Key Vault, continuous access to
 
 - If you delete the key vault, the Azure Database for MySQL flexible server instance is unable to access the key and moves to _Inaccessible_ state. Recover the [key vault](/azure/key-vault/general/key-vault-recovery) and revalidate the data encryption to make the Azure Database for MySQL flexible server instance _Available_.
 - If you delete the key from the key vault, the Azure Database for MySQL flexible server instance is unable to access the key and moves to _Inaccessible_ state. Recover the [key](/azure/key-vault/general/key-vault-recovery) and revalidate the data encryption to make the Azure Database for MySQL flexible server instance _Available_.
-- If the key stored in Azure Key Vault expires, the key becomes invalid, and the Azure Database for MySQL flexible server instance transitions into _Inaccessible_ state. Extend the key expiry date using [CLI](/cli/azure/keyvault/key#az-keyvault-key-set-attributes) and then revalidate the data encryption to make the Azure Database for MySQL flexible server instance _Available_.
+
+> [!NOTE]
+> If the key vault had expired, server will still be accessible.
 
 ## Accidental key access revocation from Key Vault
 

articles/mysql/flexible-server/concepts-high-availability.md

@@ -143,9 +143,6 @@ Keep the following considerations in mind when you use high-availability:
 - Restarting the primary database server to apply static parameter changes also restarts the standby replica.
 - The solution turns on GTID mode because it uses GTID. Check whether your workload has [restrictions or limitations on replication with GTIDs](https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html).
 
-> [!NOTE]  
-> To enable same-zone HA after creating the server, make sure the server parameters `enforce_gtid_consistency` and ["gtid_mode"](./concepts-read-replicas.md#global-transaction-identifier-gtid) are set to `ON` before enabling HA.
-
 > [!NOTE]  
 > Storage autogrow is enabled by default for a high-availability configured server and can't be disabled.