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
Copy file name to clipboardExpand all lines: articles/purview/register-scan-azure-databricks.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: jingwang
6
6
ms.service: purview
7
7
ms.subservice: purview-data-map
8
8
ms.topic: how-to
9
-
ms.date: 01/09/2023
9
+
ms.date: 01/30/2023
10
10
ms.custom: template-how-to
11
11
---
12
12
@@ -59,6 +59,10 @@ This connector brings metadata from Databricks metastore. Comparing to scan via
59
59
60
60
*[Generate a personal access token](/azure/databricks/dev-tools/auth#--azure-databricks-personal-access-tokens), and store it as a secret in Azure Key Vault.
61
61
*[Create a cluster](/azure/databricks/clusters/create-cluster). Note down the cluster ID - you can find it in Azure Databricks workspace -> Compute -> your cluster -> Tags -> Automatically added tags -> `ClusterId`.
62
+
* Make sure the user has the following [permissions](/azure/databricks/security/access-control/cluster-acl) so as to connect to the Azure Databricks cluster:
63
+
64
+
***Can Attach To** permission to connect to the running cluster.
65
+
***Can Restart** permission to automatically trigger the cluster to start if its state is terminated when connecting.
0 commit comments