Skip to content

Commit d01caae

Browse files
Merge pull request #272429 from dileepraotv-github/041724_AE_Updates
Message to include full key identifier
2 parents 056b8e2 + 0ede749 commit d01caae

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/cosmos-db/how-to-always-encrypted.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -149,6 +149,8 @@ Creating a new data encryption key is done by calling the `CreateClientEncryptio
149149
- The `type` defines the type of key resolver (for example, Azure Key Vault).
150150
- The `name` can be any friendly name you want.
151151
- The `value` must be the key identifier.
152+
> [!IMPORTANT]
153+
> Once the key is created, browse to its current version, and copy its full key identifier: `https://<my-key-vault>.vault.azure.net/keys/<key>/<version>`. If you omit the key version at the end of the key identifier, the latest version of the key is used.
152154
- The `algorithm` defines which algorithm shall be used to wrap the key encryption key with the customer-managed key.
153155

154156
```csharp
@@ -173,6 +175,8 @@ Creating a new data encryption key is done by calling the `createClientEncryptio
173175
- The `type` defines the type of key resolver (for example, Azure Key Vault).
174176
- The `name` can be any friendly name you want.
175177
- The `value` must be the key identifier.
178+
> [!IMPORTANT]
179+
> Once the key is created, browse to its current version, and copy its full key identifier: `https://<my-key-vault>.vault.azure.net/keys/<key>/<version>`. If you omit the key version at the end of the key identifier, the latest version of the key is used.
176180
- The `algorithm` defines which algorithm shall be used to wrap the key encryption key with the customer-managed key.
177181

178182
```java

0 commit comments

Comments
 (0)