Azure DevOps Git API returns Failed access to the Git repository

Question

Azure DevOps Git API returns Failed access to the Git repository

TomOrdonez-0470 20

We use an external integration to Azure DevOps repositories to fetch branches so that we can deploy a project. This was working fine until last week. Today we started getting the error. Updated the credentials. Tried again same error "Failed to access the Git Repository. Operation fetch is not permitted by server for origin. https://dev.azure.com/...our_repo"

Tejaswini Billakurthi 250 Reputation points Microsoft External Staff Moderator

2026-09-03T07:10:59.3066667+00:00

Hello

Greetings!

I wanted to follow up and check whether you've had an opportunity to review the suggested solution for your query. Please feel free to let us know if you have any questions or require any additional assistance. We're happy to help.

Answer accepted by question author

Tejaswini Billakurthi 250 Microsoft External Staff Moderator

@TomOrdonez-0470 I hope you're doing well!

Greetings from Microsoft Q&A!

The behavior you're experiencing indicates that the connection is successfully reaching the Azure DevOps Git repository endpoint; however, the Git fetch/read operation is not being permitted for the identity used by the external integration.

The error message:

"Failed to access the Git Repository. Operation fetch is not permitted by server for origin."

typically indicates that the integration is unable to perform Git fetch operations against the Azure DevOps repository. This may be caused by repository permission changes, authentication issues, repository access restrictions, or changes affecting the account or token used by the integration.

As a next step, we recommend validating the following:

Verify that the account or service identity used by the integration still has the required access to the Azure DevOps repository.
Review whether any repository permissions, branch permissions, project security settings, or service connection configurations have changed recently.
Confirm the authentication method used by the integration and ensure the configured credentials remain valid.
Validate that the configured repository URL and repository settings remain unchanged.

For reference, Microsoft documentation related to Azure DevOps repository permissions and authentication:

Azure DevOps Git repository permissions: https://learn.microsoft.com/azure/devops/repos/git/set-git-repository-permissions
Azure DevOps branch permissions: https://learn.microsoft.com/azure/devops/repos/git/branch-permissions
Azure DevOps authentication guidance: https://learn.microsoft.com/azure/devops
Personal Access Tokens (PATs): https://learn.microsoft.com/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

0 comments

1 additional answer

Your answer

Tejaswini Billakurthi 250 Reputation points Microsoft External Staff Moderator

2026-09-03T07:10:59.3066667+00:00

Hello

Greetings!

I wanted to follow up and check whether you've had an opportunity to review the suggested solution for your query. Please feel free to let us know if you have any questions or require any additional assistance. We're happy to help.

Answer 1

TomOrdonez-0470 20

If it helps others, this is what I did to solve it. I changed from PAT to OAuth and that solved issues with Azure policies blocking access from the external integration.

0 comments