BitBucket not working with Azure DevOps

Question

BitBucket not working with Azure DevOps

Dan Faulknor 50

Currently unable to set up BitBucket in Azure DevOps as Microsoft are using deprecated APIs.

{"$id":"1","innerException":null,"message":"Request failed. Bitbucket responded with result: 'CHANGE-2770 - Functionality has been deprecated'","typeName":"Microsoft.TeamFoundation.Build.WebApi.ExternalSourceProviderException, Microsoft.TeamFoundation.Build2.WebApi","typeKey":"ExternalSourceProviderException","errorCode":0,"eventId":3000}

https://developer.atlassian.com/cloud/bitbucket/changelog/#CHANGE-2770

Full removal is in a week, but we are currently in a brownout.

Is there a documented timeline for implementing the new APIs?

Pravallika KV 13,545 Reputation points Microsoft External Staff Moderator

2026-04-07T01:38:58.8066667+00:00
Hi @Dan Faulknor ,

Thanks for Reaching out to Microsoft Q&A.

Atlassian has deprecated the old “hooks & services” API that Azure Pipelines currently relies on for Bitbucket Cloud, and they’re planning full removal soon. Unfortunately, there isn’t a public ETA yet for when Azure DevOps Services (or Server) will switch over to the newer Bitbucket Cloud APIs.

In the meantime, here are a couple of things you can try:

Re-authenticate or recreate your Bitbucket service connection using OAuth (preferred) or an app-password

If you’re on Azure DevOps Server, check for any patches/upgrades that might include early support

As a stopgap, you can script your own Git check-outs in a pipeline task using your Bitbucket app-password
Aditya Kumar Choudhary 15 Reputation points

2026-04-08T07:05:17.4866667+00:00

Not able to authenticate.
Chris Brammer 15 Reputation points

2026-04-08T07:45:21.1866667+00:00

Same here, this is a major break for us as all code is hosted on Bitbucket.
Dan Faulknor 50 Reputation points

2026-04-08T09:51:50.5666667+00:00

No ETA really isn't acceptable when Atlassian announced these changes back in August 2025.

None of the suggestions are really that helpful when this is an advertised feature that should work.
Me Myself And I 5 Reputation points

2026-04-08T15:23:34.5766667+00:00

We are running into the same problem and have to move away from Azure DevOps with of our pipelines and workers in Azure if not solved within a week.

Changing all pipelines to do manual git checkout is not really an option as pipelines itself is a yaml in Bitbucket.
Pravallika KV 13,545 Reputation points Microsoft External Staff Moderator

2026-04-13T03:45:09.0533333+00:00

We are currently checking this with the DevOps team and will keep you updated as soon as we have more information

1 answer

Your answer

Pravallika KV 13,545 Reputation points Microsoft External Staff Moderator

2026-04-07T01:38:58.8066667+00:00

Hi @Dan Faulknor ,

Thanks for Reaching out to Microsoft Q&A.

Atlassian has deprecated the old “hooks & services” API that Azure Pipelines currently relies on for Bitbucket Cloud, and they’re planning full removal soon. Unfortunately, there isn’t a public ETA yet for when Azure DevOps Services (or Server) will switch over to the newer Bitbucket Cloud APIs.

In the meantime, here are a couple of things you can try:

Re-authenticate or recreate your Bitbucket service connection using OAuth (preferred) or an app-password

If you’re on Azure DevOps Server, check for any patches/upgrades that might include early support

As a stopgap, you can script your own Git check-outs in a pipeline task using your Bitbucket app-password
Aditya Kumar Choudhary 15 Reputation points

2026-04-08T07:05:17.4866667+00:00

Not able to authenticate.
Chris Brammer 15 Reputation points

2026-04-08T07:45:21.1866667+00:00

Same here, this is a major break for us as all code is hosted on Bitbucket.
Dan Faulknor 50 Reputation points

2026-04-08T09:51:50.5666667+00:00

No ETA really isn't acceptable when Atlassian announced these changes back in August 2025.

None of the suggestions are really that helpful when this is an advertised feature that should work.
Me Myself And I 5 Reputation points

2026-04-08T15:23:34.5766667+00:00

We are running into the same problem and have to move away from Azure DevOps with of our pipelines and workers in Azure if not solved within a week.

Changing all pipelines to do manual git checkout is not really an option as pipelines itself is a yaml in Bitbucket.
Pravallika KV 13,545 Reputation points Microsoft External Staff Moderator

2026-04-13T03:45:09.0533333+00:00

We are currently checking this with the DevOps team and will keep you updated as soon as we have more information

Answer 1

Eva Theodoridou 0 Microsoft Employee

If you were experiencing issues integrating with Bitbucket specifically through Azure App Service, we did identify a service-side problem on April 8 related to the Bitbucket API deprecation. Our team investigated and deployed a hotfix, and the App Service Bitbucket integration should now be working normally.

If you continue to see any unexpected behavior, please let us know and we’ll be happy to help investigate further.

Brendon 5 Reputation points

2026-04-10T18:54:12.6066667+00:00

I am still seeing an issue where the Azure endpoint (https://functions.azure.com/api/bitbucket/getRepositories) only returns 10 repositories.

Our Bitbucket workspace contains 132 repositories, but Azure App Service is only listing 10, and filtering does not return any additional results.

I don't believe this is a permissions issue. I have global admin access to all repositories, and when I call the new Bitbucket API directly (https://api.bitbucket.org/2.0/repositories/{workspace}?pagelen=100) using the same token Azure uses, all 132 repositories are returned as expected.

It appears the Azure endpoint is not correctly handling pagination.
Michael Ray 1 Reputation point

2026-04-13T23:02:48.26+00:00

I am having the exact same problem. Only a very small subset of our repositories are being returned, and it's not the ones I need, and filtering does nothing. Nor does re-authenticating, or creating a new app service.
Nick Giotta 5 Reputation points

2026-04-13T23:03:50.71+00:00

This is still hosed for us. It only displays a couple of (very old) repos for us and we have around 100. If you try to change your account, the window auto closes and the limited (and outdated) list of repos shows up with many duplicates.
Brendon 5 Reputation points

2026-04-15T13:24:31.4233333+00:00

As of this morning (April 15), I am seeing that a new API endpoint has been implemented in Azure, and that all repositories and branches are now being correctly fetched and rendered. I further validated with a code deployment, confirming the Bitbucket pipeline succeeded end-to-end. This now appears to be fully resolved.
Eva Theodoridou 0 Reputation points Microsoft Employee

2026-04-15T17:04:06.81+00:00

Hi Brendon, thank you for confirming! We just pushed another fix for this out yesterday evening.

Share via

BitBucket not working with Azure DevOps

1 answer

Your answer