Skip to content

Commit 932503f

Browse files
authored
Merge pull request #219189 from markingmyname/issues
[MySQL] Update articles from Issues
2 parents 05c3cec + 1581dce commit 932503f

File tree

2 files changed

+23
-23
lines changed

2 files changed

+23
-23
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ As you configure Key Vault to use data encryption using a customer-managed key,
8585
- Set a resource lock on Key Vault to control who can delete this critical resource and prevent accidental or unauthorized deletion.
8686
- Enable auditing and reporting on all encryption keys. Key Vault provides logs that are easy to inject into other security information and event management tools. Azure Monitor Log Analytics is one example of a service that's already integrated.
8787
- Keep a copy of the customer-managed key in a secure place or escrow it to the escrow service.
88-
- If Key Vault generates the key, create a key backup before using the key for the first time. You can only restore the backup to Key Vault. For more information about the backup command, see [Backup-AzKeyVaultKey](/powershell/module/az.keyVault/backup-azkeyVaultkey?view=azps-8.3.0).
88+
- If Key Vault generates the key, create a key backup before using the key for the first time. You can only restore the backup to Key Vault. For more information about the backup command, see [Backup-AzKeyVaultKey](/powershell/module/az.keyVault/backup-azkeyVaultkey).
8989

9090
## Inaccessible customer-managed key condition
9191

0 commit comments

Comments
 (0)