Skip to content

Commit cc69311

Browse files
Update articles/azure-app-configuration/concept-customer-managed-keys.md
Co-authored-by: Maud <[email protected]>
1 parent ebe8b6c commit cc69311

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-app-configuration/concept-customer-managed-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ After these resources are configured, use the following steps so that the Azure
108108
The command uses system-assigned managed identity to do authentication with the key vault by default.
109109
110110
> [!NOTE]
111-
> When using a user-assigned managed identity to access the managed key, you can specify its client id explicitly by adding `--identity-client-id <client id of your user assigned identity>` to the command.
111+
> When using a user-assigned managed identity to access the managed key, you can specify its client ID explicitly by adding `--identity-client-id <client ID of your user assigned identity>` to the command.
112112
113113
Your Azure App Configuration instance is now configured to use a customer-managed key stored in Azure Key Vault.
114114

0 commit comments

Comments
 (0)