Skip to content

Commit 31cfb61

Browse files
authored
Update concepts-customer-managed-key.md
1 parent 42fa97f commit 31cfb61

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,9 @@ When you configure data encryption with a CMK in Key Vault, continuous access to
105105

106106
- 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_.
107107
- 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_.
108-
- 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_.
108+
109+
> [!NOTE]
110+
> If the key vault had expired, server will still be accessible.
109111
110112
## Accidental key access revocation from Key Vault
111113

0 commit comments

Comments
 (0)