Error creating Git folder: Invalid Git provider credential although PAT is valid and cloning works o

[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).

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

Because of that, I suspect this may be Databricks-side configuration/integration related rather than a token issue itself.

Could anyone share possible root causes I should check next?

[sarahbhord · Accepted solution]

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

[Fabi_DYM]

Hello Sarah,

Thank you for your support. My issue was that the connection to Azure DevOps was visible under "Linked accounts," but it didn’t seem to work properly. After manually rebuilding the connection, it started working again.

Best regards,
Fabi

[saurabh18cs]

how are you doing it manually ? or during job deployment or during job execution? your own identity or servie principal identity?