Skip to content

Commit 07ea996

Browse files
msmbaldwinCopilot
andcommitted
Strengthen service-offline warning in secure-key-vault.md
Co-authored-by: Copilot <[email protected]>
1 parent 03be391 commit 07ea996

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/key-vault/general/secure-key-vault.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ Regular backups ensure business continuity and protect against data loss from ac
125125

126126
- **Test backup and recovery procedures**: To verify the effectiveness of backup processes, regularly test the restoration of Key Vault secrets, keys, and certificates. See [Azure Key Vault backup](backup.md).
127127

128-
- **Understand backup copy independence**: A key restored from a backup to another vault is fully independent of the original. Disabling, deleting, or purging the original key does not affect any restored copies. If a key is suspected compromised, rotate to a new key and migrate dependent services before disabling the old one. For full details, see [Backup security considerations](backup.md#security-considerations) and [Key compromise response](../keys/secure-keys.md#key-compromise-response).
128+
- **Understand backup copy independence**: A key restored from a backup to another vault is fully independent of the original. Disabling, deleting, or purging the original key does not affect any restored copies. Disabling or deleting the key also takes all dependent data services offline (for example, SQL TDE databases become inaccessible and Storage accounts with customer-managed keys return errors). If a key is suspected compromised, rotate to a new key and migrate dependent services before disabling the old one. For full details, see [Backup security considerations](backup.md#security-considerations) and [Key compromise response](../keys/secure-keys.md#key-compromise-response).
129129

130130
## Related security articles
131131

0 commit comments

Comments
 (0)