Skip to content

Commit 6428424

Browse files
authored
Update secrets-best-practices.md
1 parent de82571 commit 6428424

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ For more information about best practices for Key Vault, see [Best practices to
3131

3232
## Configuration and storing
3333

34-
Store the dynamic parts of credentials, which are generated during rotation, as values. Examples include client application secrets, passwords, and access keys. Any related static attributes and identifiers, like usernames, application IDs, and service URLs, should be stored as secret tags and copied to the new version of a secret during rotation.
34+
Store credential information required to access database or service in secret value. In the case of compound credentials like username/password, it can be stored as a connection string or JSON object. Other information required for management should be stored in tags, i.e., rotation configuration.
3535

3636
For more information about secrets, see [About Azure Key Vault secrets](about-secrets.md).
3737

0 commit comments

Comments
 (0)