Skip to content

Commit 5844ed9

Browse files
authored
Clarify that Databricks OAuth setup requires an account admin (DataDog#22593)
1 parent d8e4cb0 commit 5844ed9

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

databricks/README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,9 @@ First, [connect a new Databricks workspace](#connect-to-a-new-databricks-workspa
3232
<!-- xxx tab "Use a Service Principal for OAuth" xxx -->
3333
<div class="alert alert-warning">New workspaces must authenticate using OAuth. Workspaces integrated with a Personal Access Token continue to function and can switch to OAuth at any time. After a workspace starts using OAuth, it cannot revert to a Personal Access Token.</div>
3434

35-
1. In your Databricks account, click on **User Management** in the left menu. Then, under the **Service principals** tab, click **Add service principal**.
35+
<div class="alert alert-info">The following steps must be performed by a Databricks account admin. A workspace admin alone does not have sufficient permissions to create service principals at the account level.</div>
36+
37+
1. In your Databricks account console, click **User Management** in the left menu. Then, under the **Service principals** tab, click **Add service principal**.
3638
2. Under the **Credentials & secrets** tab, click **Generate secret**. Set **Lifetime (days)** to the maximum value allowed (730), then click **Generate**. Take note of your client ID and client secret. Also take note of your account ID, which can be found by clicking on your profile in the upper-right corner. (You must be in the account console to retrieve the account ID. The ID will not display inside a workspace.)
3739
3. Click **Workspaces** in the left menu, then select the name of your workspace.
3840
4. Go to the **Permissions** tab and click **Add permissions**.

0 commit comments

Comments
 (0)