Skip to content

Commit 13681a0

Browse files
authored
Remove a note about Azure KeyVault and Service Principal from databricks_secret_scope troubleshooting guide (#2248)
1 parent 0227304 commit 13681a0

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

docs/guides/troubleshooting.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -111,8 +111,3 @@ You can get this error during provisioning of the Databricks workspace. It aris
111111
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.
112112
113113
1. Comment out the `deployment_name` parameter to create workspace with default URL: `dbc-XXXXXX.cloud.databricks.com`.
114-
115-
116-
## Azure KeyVault cannot yet be configured for Service Principal authorization
117-
118-
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.

0 commit comments

Comments
 (0)