How to use Databricks CLI as a service principal?

[AlbertWang]

Hi all,

I have a question about how to use Databricks CLI on my local environment as a service principal?

I have installed Databricks CLI and configured the file `.databrickscfg` as shown below.

[DEFAULT]
host      = https://adb-123123123.1.azuredatabricks.net
auth_type = databricks-cli

[devsp]
host                = https://adb-123123123.1.azuredatabricks.net
azure_tenant_id     = <my-azure-tenant-id>
azure_client_id     = <my-ms-entra-id-service-principal-client-id>
azure_client_secret = <my-ms-entra-id-service-principal-client-secret>

I use Microsoft Entra ID service principal and added the service principal to the Databricks workspace.

However, when I run the command `databricks current-user me -p devsp`, I still see my personal user information. When I run the command `databricks tokens create -p devsp`, I still create a PAT for my personal user.

Any help will be appreciated!

Regards,

Albert

[Stefan-Koch]

I assume, you want to connect for account-level operation, then the configuration in your .databrickscfg file looks like this:

[<some-unique-configuration-profile-name>]
host          = <account-console-url>
account_id    = <account-id>
client_id     = <service-principal-client-id>
client_secret = <service-principal-oauth-secret>

 For workspace-level commands, set the following values in your .databrickscfg file:

[<some-unique-configuration-profile-name>]
host          = <workspace-url>
client_id     = <service-principal-client-id>
client_secret = <service-principal-oauth-secret>

See also: https://learn.microsoft.com/en-us/azure/databricks/dev-tools/cli/authentication 

[AlbertWang]

Thank you for your reply. However, I refer to this Authentication for the Databricks CLI - Azure Databricks | Microsoft Learn - Microsoft Entra ID serv.... This is for authentication using Microsoft Entra ID's client id and secret.

The one you mentioned is Authentication for the Databricks CLI - Azure Databricks | Microsoft Learn - OAuth machine-to-machin... As I understand, this is for authentication using Databricks Service Principal client id and secret.