Skip to main content
Last updated on

Connect your Git provider to Databricks

This page explains how to configure a user's Git credentials in Databricks so you can connect remote repositories using Git folders. Choose your Git provider below and follow the authentication steps.

Configure Git credentials for a service principal

You can also configure Git credentials for a Databricks service principal. Service principals are the recommended choice for jobs, CI/CD pipelines, and other automated workflows that shouldn't be associated with a user.

To authorize a Databricks service principal to access your workspace's Git folders, see Authorize a service principal to access Git folders.

GitHub​

This section covers GitHub and GitHub Advanced Enterprise.

For hosted GitHub accounts, Databricks recommends using the Databricks GitHub app for authentication instead of personal access tokens (PATs). The GitHub app uses OAuth 2.0 with encrypted repository traffic, renews tokens automatically, and lets you scope access to specific repositories.

note
  • GitHub Enterprise Server doesn't support linking your GitHub account. Use a personal access token instead.
  • Enterprise Managed Users can't install GitHub Apps on their user accounts. Use a personal access token instead, which works with both organization and personal repositories.

To link your GitHub account with the Databricks GitHub app:

  1. Click your user icon and select Settings.

  2. Click the Linked accounts tab.

  3. Click Add Git credential.

  4. Set your provider to GitHub, select Link Git account, and click Link.

    Link GitHub account in Databricks

  5. On the Databricks GitHub app authorization page, click Authorize Databricks to authorize the app. This allows Databricks to perform Git operations on your behalf, such as cloning repositories. See Authorizing GitHub Apps in the GitHub documentation.

  6. Install the Databricks GitHub app on repositories that you want to access from Git folders:

    1. Open the Databricks GitHub app installation page. You must be the account owner to install the app.
    2. Select the account that owns the repositories you want to access.
    3. Optionally, choose Only select repositories to limit access to specific repositories.
    4. Click Install.

    For more information, see About installing GitHub Apps.

Databricks stores your access and refresh tokens following standard OAuth 2.0 integration. GitHub manages all other access control. Access tokens expire after 8 hours. Refresh tokens expire after 6 months of inactivity, requiring you to reconfigure your credentials. You can optionally encrypt tokens using customer-managed keys.

Classic personal access token​

To create a classic personal access token in GitHub:

  1. Click your user icon, then click Settings.
  2. Click Developer settings.
  3. Click Personal access tokens > Tokens (classic).
  4. Click Generate new token (classic).
  5. Enter a note to indicate the purpose of the token.
  6. Select the repo scope. If your repository uses GitHub Action workflows, also select the workflow scope.
  7. Click Generate token.
  8. Copy the token and enter it in Databricks under Settings > Linked accounts.

For single sign-on, see Authorizing a personal access token for use with single sign-on.

Fine-grained personal access token​

Fine-grained PATs grant access only to the specific resources you need. To create one in GitHub:

  1. Click your user icon, then click Settings.

  2. Click Developer settings.

  3. Click Personal access tokens > Fine-grained tokens.

  4. Click Generate new token.

  5. Configure the token:

  6. Click Generate token.

  7. Copy the token and enter it in Databricks under Settings > Linked accounts.

GitLab​

To create a personal access token in GitLab:

  1. Click your user icon and select Preferences.
  2. Click Personal access tokens in the sidebar.
  3. Click Add new token.
  4. Enter a name for the token.
  5. Select the scopes for your desired permission levels. See Personal access token scopes in the GitLab documentation.
  6. Click Create token.
  7. Copy the token and enter it in Databricks under Settings > Linked accounts.

For fine-grained access to a specific project, use project access tokens.

AWS CodeCommit​

To create HTTPS Git credentials in AWS CodeCommit:

  1. Create HTTPS Git credentials following the AWS CodeCommit documentation. The associated IAM user must have read and write permissions for the repository.
  2. Copy the password and enter it in Databricks under Settings > Linked accounts.

Azure DevOps Services​

Personal access token​

Use a personal access token when your Databricks and Azure DevOps repositories aren't in the same Microsoft Entra ID tenancy.

The Microsoft Entra ID service endpoint must be accessible from both the private and public subnets of the Databricks workspace. For more information, see Enable Private Service Connect for your workspace.

To create a personal access token in Azure DevOps:

  1. Go to dev.azure.com and sign in to the DevOps organization containing your repository.
  2. Click the user settings icon and select Personal Access Tokens.
  3. Click + New Token.
  4. Configure the token:
    • Enter a name for the token.
    • Select the organization (repository name).
    • Set an expiration date.
    • Choose the required scope, such as Full access.
  5. Copy the access token.
  6. In Databricks, go to Settings > Linked accounts and enter the token.
  7. In Git provider username or email, enter the email address you use to sign in to the DevOps organization.

For more information about Azure DevOps personal access tokens, see the Azure DevOps documentation.

Bitbucket​

Databricks supports Bitbucket authentication using API tokens, access tokens, and app passwords. Databricks recommends using API tokens for users and access tokens for service principals.

To generate a scoped Bitbucket API token, follow the Bitbucket documentation.

The token must have read:repository:bitbucket and write:repository:bitbucket scopes.

Select bitbucket API scopes

Add the token in Databricks under Settings > Linked accounts.

Access token​

Bitbucket access tokens provide scoped authentication to repositories, projects, or workspaces. They're designed for CI/CD and are recommended for service principals. To create an access token, see the Bitbucket documentation on access tokens.

To configure access tokens for a Databricks service principal, see Authorize a service principal to access Git folders.

App password​

App password deprecation

Atlassian is deprecating app passwords for Bitbucket, with full deprecation scheduled for June 9, 2026. After this date, app passwords won't work. Databricks recommends migrating to API tokens, which provide enhanced security and admin control. For more information, see Bitbucket Cloud transitions to API tokens.

When adding an app password in Databricks, you must enter your Bitbucket username in the Git provider username field under Settings > Linked accounts.

Other Git providers​

If your Git provider isn't listed, try selecting GitHub and entering the PAT from your provider. This approach often works but isn't guaranteed.