Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Problems connecting Azure DevOps to BitBucket Cloud

Jon Starbird
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 08, 2022

Anyone have any success setting up Azure DevOps pipeline to connect to BitBucket Cloud? 

We can get it connected to see list of repos using grant access or basic auth with app password but once you select a particular repo it fails with:

Unable to get the path contents from the Bitbucket repository 'workspace/reponame' for the branch or source version 'master' and path ''. It is possible the specified path is a file. Error from Bitbucket: Forbidden

Permissions are set correctly. 

Also tried to use oauth consumer but was unable to find the proper callback url for azure devops anywhere on the net. 

I know  this may be Azure DevOps issue but since it's to use BitBucket Cloud I wanted to post here in case someone else has hit this same issue before. 


2 answers

We are facing the same issue.

I had to set-up pipelines for two repositories.

For the first one, no issue at all.

For the second one, I had the same error message. 
I found one comment on another thread :
Please add a Note to suggest not adding big binary... (

It seems to be linked with the fact the repository contains binary files, making the scan impossible.

Already tried the following workaround; create the pipeline with Azure DevOps REST API. But bitbucket pipeline are not supported with this approach.

The last solution is to change repository host service (to a concurrent one...)

Yes, we have these working, with both OAuth2 (grant) and Basic (app password).

I have tried to reproduce your error.

  • I have given inadequate permissions to the app password used in the Service Connection: this prevents creating the connection.
  • I have created a repo with only a nonstandard branch (default branch != 'main' or 'master): works fine.
  • I have removed the app password after creating the service connection: valid error, different to the one you report.

It seems ADO is handling everything correctly. We can go through how you create your Service Connection in more detail, if you like? And check how you've set up your repository and pipeline. Can you post the steps you go through for creating a Service Connection to a BitBucket Cloud repository?

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events