You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Create an Azure Key Vault-backed secret scope using the UI" steps listed on this page only work if the AKV is configured to use Access Policies to manage authorisation. If the AKV uses RBAC then an additional step of assigning the "Key Vault Secret User" role to the AzureDatabricks enterprise app needs to be performed otherwise users will not be able to list secrets via Databricks CLI.
Refer to the content in this Microsoft QandA discussion,, some of this content probably should be added to this page.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 810a218a-80a5-2da0-b540-26347f9ef908
Version Independent ID: 41c2a12f-99b6-0faa-500b-3e4308cd00de
@pnarsi Thanks for the feedback! I have assigned the issue to the content author to evaluate and add the details on how to connect using RBAC role in the document.
Thanks for your dedication to our documentation. Unfortunately, we have been unable to review your issue and apologize for the delayed response. The requested updates have not yet been made. The timeline for resolution varies based on resourcing. We've created an internal work item (DOC-7063) to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
"Create an Azure Key Vault-backed secret scope using the UI" steps listed on this page only work if the AKV is configured to use Access Policies to manage authorisation. If the AKV uses RBAC then an additional step of assigning the "Key Vault Secret User" role to the AzureDatabricks enterprise app needs to be performed otherwise users will not be able to list secrets via Databricks CLI.
Refer to the content in this Microsoft QandA discussion,, some of this content probably should be added to this page.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: