Configure Databricks Service Principal and Client Secret

Service principals provide a secure way to authenticate without exposing personal credentials. This guide walks you through creating or managing a service principal in your Databricks workspace, generating a client secret, and safely storing it for future use. By following these steps, you’ll ensure that your integrations remain secure, reliable, and compliant with best practices.

1. Log in to your Databricks Workspace.
2. At the top-right corner of the page, click your username > Settings .
3. Go to the Identity and access tab > Service principals > Manage .
4. Select an existing service principal or create a new one.
5. In the Secrets tab, click Generate secret , set a lifetime , and click Generate .
6. Copy the Client ID and Client Secret and enter them in the respective fields.

Follow these instructions to provide sufficient access for the created service principal:

1. Log in to your Databricks Workspace.
2. At the top-right corner of the page, click your username > Settings .
3. Go to the Identity and access tab > Service principals > Manage .
4. Navigate to the Groups tab under Identity and access section.
5. In the existing groups, click admins .
6. Click Add Members in Members tab of admins .
7. In the pop-up window, use the Select members drop-down menu to select the service principal associated with Site24x7 (created in previous section).
8. Click Add .

The client secret is shown only once and cannot be retrieved after leaving the page. Store it in a secure location before proceeding.

Granting Admin access to the service principal eliminates the need to manually provide sufficient access every time a new Job is added. Contact Site24x7 support team for instructions to provide granular permissions manually.

• Related Articles

• Why does it show "The Client Secret is invalid" in Site24x7 Azure monitoring?

  You may encounter the error message "Client Secret is invalid" in the Site24x7 web client while configuring or updating your Azure monitoring setup. Cause: This error typically occurs when the client secret used to authenticate the Azure application ...

• How to derive the Client Secret value from the Azure portal

  Use the below steps to create the Client Secret value from the Azure portal: 1. Log in to the Microsoft Azure portal. 2. Search and navigate to the application you have created for monitoring. If you are unsure about the application name, you can ...

• Updating the Client Secret (Application Secret) value provided for Azure monitoring

  To update the Client Secret value provided while adding an Azure monitor, follow these steps: Log in to Site24x7 and go to Azure > Service View. Hover over the hamburger icon at the top and click Edit. On the Edit Azure Monitor page, click Update ...

• What should I do if Service Health data collection in Microsoft 365 monitor is not happening?

  Your Microsoft 365 monitor's Service Health data collection may have stopped because of the recently updated Microsoft 365 Service Communications API policy. Follow the steps below if Service Health data collection in your Microsoft 365 monitor is ...

• Configure gMSA Permissions for Secure SQL Monitoring in Site24x7

  The Site24x7 App Monitoring Agent can be configured to monitor a Microsoft SQL Server instance. During setup via the Agent Manager command-line interface, the agent's Windows service logon account must have the appropriate domain credentials to ...