Skip to content

Commit dc333b2

Browse files
authored
Merge pull request #114322 from jlichwa/patch-14
Update about-secrets.md
2 parents 28b4950 + 3200790 commit dc333b2

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/key-vault/secrets/about-secrets.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,10 @@ For highly sensitive data, clients should consider additional layers of protecti
2323

2424
Key Vault also supports a contentType field for secrets. Clients may specify the content type of a secret to assist in interpreting the secret data when it's retrieved. The maximum length of this field is 255 characters. There are no pre-defined values. The suggested usage is as a hint for interpreting the secret data. For instance, an implementation may store both passwords and certificates as secrets, then use this field to differentiate. There are no predefined values.
2525

26+
## Encryption
27+
28+
All secrets in your Key Vault are stored encrypted. This encryption is transparent, and requires no action from the user. The Azure Key Vault service encrypts your secrets when you add them, and decrypts them automatically when you read them. The encryption key is unique to each key vault.
29+
2630
## Secret attributes
2731

2832
In addition to the secret data, the following attributes may be specified:

0 commit comments

Comments
 (0)