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

 Don't Use Use Instead

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