cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Azure Devops Git sync failed in Azure Databricks

ackerman_chris
New Contributor III

Hello,

I am currently attempting to setup a Git Repo within Azure Devops to use on my Azure Databricks Workspace environment for various notebooks. I went through the process of creating a Personal Access Token (PAT) on Devops, and have inputted the token in the Git Integration settings in Databricks using the same email used under Devops.

However, when I attempt to select "Git Repo" to link the Repo to the one I created in my project, I get the error below.

Error while syncing Git history: Response from Azure DevOps Services: status code: 500, reason phrase: {"$id":"1","innerException":null,"message":"Unable to complete authentication for user due to looping logins","typeName":"Microsoft.VisualStudio.Services.Identity.IdentityLoopingLoginException, Microsoft.VisualStudio.Services.WebApi","typeKey":"IdentityLoopingLoginException","errorCode":0,"eventId":4207}

1 ACCEPTED SOLUTION

Accepted Solutions

Kaniz
Community Manager
Community Manager

Hi @Christopher Ackermanโ€‹, This error message usually occurs when there is an issue with authentication between Azure Databricks and Azure DevOps. One possible reason for this error is that the token was not granted the necessary permissions to access the Azure DevOps repository.

To resolve this issue, you can try the following steps:

Verify that the token has the necessary permissions to access the Azure DevOps repository. To do this, you can check the token's scope in Azure DevOps and ensure it has the required permissions.

If the issue persists, you may need to contact Azure support for further assistance.

View solution in original post

1 REPLY 1

Kaniz
Community Manager
Community Manager

Hi @Christopher Ackermanโ€‹, This error message usually occurs when there is an issue with authentication between Azure Databricks and Azure DevOps. One possible reason for this error is that the token was not granted the necessary permissions to access the Azure DevOps repository.

To resolve this issue, you can try the following steps:

Verify that the token has the necessary permissions to access the Azure DevOps repository. To do this, you can check the token's scope in Azure DevOps and ensure it has the required permissions.

If the issue persists, you may need to contact Azure support for further assistance.