Skip to content

Commit 2f2e43c

Browse files
author
gerardori
committed
Updated title
1 parent 385eed5 commit 2f2e43c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/key-vault/general/azure-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ When enforcing a policy, you can determine its effect over the resulting evaluat
4444

4545
Predetermined policies, referred to as 'built-ins', facilitate governance over your Key Vaults so you don't have to write custom policies in JSON format to enforce commonly used rules associated with best security practices. Even though built-ins are predetermined, certain policies require you to define parameters. For example, by defining the effect of the policy, you can audit the Key Vault and its objects before enforcing a deny operation to prevent outages. Current built-ins for Azure Key Vault are categorized in four major groups: key vault, certificates, keys, and secrets management. Within each category, policies are grouped towards driving specific security goals.
4646

47-
### [Key Vault Management](#tab/keyvault)
47+
### [Key Vault](#tab/keyvault)
4848

4949

5050
#### Network Access

0 commit comments

Comments
 (0)