From 07373c1a3de95d8848ffb34cb62439341a5f6d0b Mon Sep 17 00:00:00 2001 From: Mikal S Date: Wed, 8 Sep 2021 21:44:57 +0200 Subject: [PATCH] Update azure-keyvault-managed-identity.md Fix 'fully qualified ID' to 'fully qualified resource ID' --- .../supported-secret-stores/azure-keyvault-managed-identity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-secret-stores/azure-keyvault-managed-identity.md b/daprdocs/content/en/reference/components-reference/supported-secret-stores/azure-keyvault-managed-identity.md index 721524125..3302feb90 100644 --- a/daprdocs/content/en/reference/components-reference/supported-secret-stores/azure-keyvault-managed-identity.md +++ b/daprdocs/content/en/reference/components-reference/supported-secret-stores/azure-keyvault-managed-identity.md @@ -150,7 +150,7 @@ The above example uses secrets as plain strings. It is recommended to use a loca azureIdentity: [your managed identity name] selector: [your managed identity selector] ``` - where the value `resourceID: [your managed identity id]` is the fully qualified ID of the managed identity. It can be retrieved by running + where the value `resourceID: [your managed identity id]` is the fully qualified resource ID of the managed identity. It can be retrieved by running ``` az identity show -g [your resource group] -n [managed identity name] --query id ```