Skip to content

Commit 9973616

Browse files
author
benijake
committed
improve key vault roles explanation
1 parent 100804e commit 9973616

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The secret value will appear on the screen. Do not leave the page before recordi
2626
Create an Azure Key Vault in the same region
2727
![azure-keyvault](./databricks/CreateKeyVault.png)
2828

29-
Assign yourself and the Azure Databricks application the Key Vault Secrets Officer role. (Databricks will access the key vault referenced in your secrets scope using the Databricks application's own service principal, which is unique to your tenant. You might expect a Unity Catalog-enabled workspace to use the workspace's managed identity to connect to the key vault, but unfortunately that's not the case.)
29+
Assign yourself the [Key Vault Secrets Officer](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/security#key-vault-secrets-officer) role and the Azure Databricks application the [Key Vault Secrets User](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/security#key-vault-secrets-user) role. (Databricks will access the key vault referenced in your secrets scope using the Databricks application's own service principal, which is unique to your tenant. You might expect a Unity Catalog-enabled workspace to use the workspace's managed identity to connect to the key vault, but unfortunately that's not the case.)
3030
![add-role](./databricks/AddKeyVaultRole.png)
3131
![secrets-officer](./databricks/KVSecretsOfficerRole.png)
3232
![azure-databricks](./databricks/AssignDatabricksAppRBAC.png)

0 commit comments

Comments
 (0)