Skip to content

Commit 855dde3

Browse files
authored
Merge pull request #210619 from jlichwa/patch-24
Update best-practices.md
2 parents 17310fc + 64dfedf commit 855dde3

File tree

1 file changed

+13
-17
lines changed

1 file changed

+13
-17
lines changed

articles/key-vault/general/best-practices.md

Lines changed: 13 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -34,35 +34,31 @@ Suggestions for controlling access to your vault are as follows:
3434
- Use the principle of least privilege access to grant access.
3535
- Turn on firewall and [virtual network service endpoints](overview-vnet-service-endpoints.md).
3636

37-
## Backup
38-
39-
Make sure you take regular backups of your vault. Backups should be performed when you update, delete, or create objects in your vault.
40-
41-
### Azure PowerShell backup commands
42-
43-
* [Backup certificate](/powershell/module/azurerm.keyvault/Backup-AzureKeyVaultCertificate)
44-
* [Backup key](/powershell/module/azurerm.keyvault/Backup-AzureKeyVaultKey)
45-
* [Backup secret](/powershell/module/azurerm.keyvault/Backup-AzureKeyVaultSecret)
46-
47-
### Azure CLI backup commands
37+
## Turn on data protection for your vault
4838

49-
* [Backup certificate](/cli/azure/keyvault/certificate#az-keyvault-certificate-backup)
50-
* [Backup key](/cli/azure/keyvault/key#az-keyvault-key-backup)
51-
* [Backup secret](/cli/azure/keyvault/secret#az-keyvault-secret-backup)
39+
Turn on purge protection to guard against malicious or accidental deletion of the secrets and key vault even after soft-delete is turned on.
5240

41+
For more information, see [Azure Key Vault soft-delete overview](soft-delete-overview.md)
5342

5443
## Turn on logging
5544

5645
[Turn on logging](logging.md) for your vault. Also, [set up alerts](alert.md).
5746

58-
## Turn on recovery options
47+
## Backup
48+
49+
Purge protection prevents malicious and accidental deletion of vault objects for up to 90 days. In scenarios when purge protection is not a possible option, we recommend backup vault objects, which can't be recreated from other sources like encryption keys generated within the vault.
5950

60-
- Turn on [soft-delete](soft-delete-overview.md).
61-
- Turn on purge protection if you want to guard against force deletion of the secrets and key vault even after soft-delete is turned on.
51+
For more information about backup, see [Azure Key Vault backup and restore](backup.md)
6252

6353
## Multitenant solutions and Key Vault
6454

6555
A multitenant solution is built on an architecture where components are used to serve multiple customers or tenants. Multitenant solutions are often used to support software as a service (SaaS) solutions. If you're building a multitenant solution that includes Key Vault, review [Multitenancy and Azure Key Vault](/azure/architecture/guide/multitenant/service/key-vault).
6656

57+
## Frequently Asked Questions:
58+
### Can I use Key Vault role-based access control (RBAC) permission model object-scope assignments to provide isolation for application teams within Key Vault?
59+
No. RBAC permission model allows to assign access to individual objects in Key Vault to user or application, but any administrative operations like network access control, monitoring, and objects management require vault level permissions which will then expose secure information to operators across application teams.
60+
6761
## Learn more
6862
- [Best practices for secrets management in Key Vault](../secrets/secrets-best-practices.md)
63+
64+

0 commit comments

Comments
 (0)