Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove a note about Azure KeyVault and Service Principal from databricks_secret_scope troubleshooting guide #2248

Merged
merged 1 commit into from
May 1, 2023
Merged

Remove a note about Azure KeyVault and Service Principal from databricks_secret_scope troubleshooting guide #2248

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions docs/guides/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,8 +111,3 @@ You can get this error during provisioning of the Databricks workspace. It aris
1. Contact your Databricks representative, like Solutions Architect, Customer Success Engineer, Account Executive, or Partner Solutions Architect to set a deployment prefix for your account.

1. Comment out the `deployment_name` parameter to create workspace with default URL: `dbc-XXXXXX.cloud.databricks.com`.


## Azure KeyVault cannot yet be configured for Service Principal authorization

This is a well known limitation of the Azure Databricks - currently you cannot create Azure Key Vault-based secret scope because OBO flow is not supported yet for service principals on Azure Active Directory side. Use [azure-cli authentication](https://registry.terraform.io/providers/databrickslabs/databricks/latest/docs#authenticating-with-azure-cli) with user principal to create AKV-based secret scope.