Error creating Git folder: Invalid Git provider credential although PAT is valid

[Fabi_DYM]

Hi everyone,

I’m getting this error when trying to create a Git folder in Databricks:

Error creating Git folder
Invalid Git provider credential for repository with URL [Placeholder].

How to fix
Please go to your remote Git provider to ensure that:

• You have entered the correct Git user email or username with your Git provider credentials.

• Your token has the correct repo access.

• Your token has not expired.

• If you have SSO enabled with your Git provider, be sure to authorize your token.

• Alternatively, select or create another git credential using git credential selector below.

Request ID: 6218650a-b143-XXX

What I already verified:

• My PATs are valid (not expired).

• PAT scopes/permissions are correct for repo access.

• Credentials (username/email + token) are correct.

• I can clone the same repositories successfully via other applications / CLI (no issues there).

• The problem appears only in Databricks.

Additional context:

• I already had this exact issue in December . At that time, it disappeared by itself after about 3 days, without any changes on my side (no credential changes, no permission changes, no config changes).

• Also had the same issue in February, after sharing the Problem here in der Forum, i got the Input to renew the Account Link in Databricks and it worked again but there also passed a few days.
• For a collague of mine, the same pocedure wasn't working but after a few days he tried again to renew the connection and is also started to work again

• The issue is not limited to creating new Git folders: in existing Databricks repos, I also cannot switch branches.

I also checked the solution suggestions from my previous post about the same Problem.

Hey Fabi_DYM

Thanks for reaching out. Here are a few troubleshooting suggestions: 

1. Authorize PAT for SAML SSO - Authorizing a personal access token for use with single sign-on

2. Verify Databricks Linked Account Settings - see docs here  

3. GitHub Enterprise Managed Users (EMU) - If you are an EMU, you cannot use the Databricks GitHub App and must use a PAT with specific naming conventions. See NOTE here.

4. Firewall and IP Access Lists - Databricks control plane IPs may need to be allowlisted in your GitHub Enterprise settings.

5. Service Principal Automation - If you are seeing this error in a job or workflow, standard PATs may not apply. You must link credentials to the Service Principal specifically. 

Please let me know if that helps.

Best,

Sarah

Is there beside the account-linking component also a time component? Like you have to wait a few days, than renew the Link in Databricks and than its working again? Is something like that even possible?

Could anyone share possible root causes I should check next?

Thanks in advance!

[NageshPatil]

1. Confirm HTTPS URL with .git suffix → no embedded credentials in URL

 Don't Use Use Instead

git@github.com:org/repo.git (SSH)	https://github.com/org/repo.git
https://github.com/org/repo (no .git)	https://github.com/org/repo.git
https://user@github.com/org/repo.git	https://github.com/org/repo.git (no embedded user)

2. If self-hosted Git → ask admin to register the host in Databricks Admin Console

• A Databricks admin must register the custom Git host:
  • Go to Admin Console → Settings → Git Integration
  • Add your custom Git host URL (e.g., https://gitlab.mycompany.com)
• Without this, Databricks silently fails auth even with valid credentials

3. Delete ALL saved Git credentials in Databricks → re-add one clean credential

Databricks stores Git credentials per user:

1. Go to Settings → Linked Accounts → Git Credentials
2. Confirm the credential is saved under your current logged-in user
3. If you have multiple Databricks accounts/workspaces, verify you're in the right workspace
4. Delete and re-add the credential fresh — sometimes a corrupted entry persists silent

4. If Azure DevOps → verify org name and URL format

If using Azure DevOps, this is a frequent Databricks-specific trap:

Correct URL format for Azure DevOps:

https://dev.azure.com/{organization}/{project}/_git/{repository}

Old format (may fail in Databricks):

https://{organization}.visualstudio.com/{project}/_git/{repository}

Also ensure your PAT was generated under the correct Azure DevOps Organization — a PAT from Org A won't work for Org B even with identical settings.

5. Regenerate PAT → re-save in Databricks

Some PATs contain characters (+, =, /, @) that Databricks may mishandle:

• Regenerate your PAT and check if the new one works
• If your provider allows it, regenerate until you get a token without special characters