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!


SourceTree 3: Connecting to VSTS

I'm trying to connect to my to my VSTS remote repo using the new version of Sourcetree (3.0.8). I have the chosen "Visual Studio Team Services" and put in the Host url (https://{organisation}
The only option is to "Refresh Personal Access Token". This gives me a pop up requesting username and password. This fails with not authorised and the username field is not filled in. If I instead use a PAT for the password, the username field is now populated with my username but is still not authorised and says I don't have access to ""

What am I doing wrong?

4 answers

Also looking for an answer to this question, however I may be even more out of luck -- I'm trying to connect to a locally-hosted instance of azure devops. Would love a fix or workaround.

The hosting URL works for but not for the new URL system that devops uses/recommends

Get the token from in Azure Devops in the Create Token area.

Okaay, so 30 mins later, I'm ready to go...

It is very weird but, after entering the PAT for couple of times it did work. 

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 26, 2018


In principle you are doing the right thing.

I have noticed on occasions you need to enter the PAT twice, at this stage I don't know why. After the first failure if you try and enter the PAT again, you might find the username information pre-filled, enter the PAT and click OK and you should find it works.

I have the same problem, I've spent hours and hours and tried different URL for host and different UserName but still no success. 
The most closed way to put credential is like this : 

You better put as Host URL and your email as username and your token as the password. but still getting this error : 



I wish there was a tutorial from sourceTree team how we can work with AzueDevOps. Even when we choose Visual Studio Team Service as Hosting Service, The Username field is disabled and you cannot put any value. The way I worked around was I chose BitBucket server, then username field was active, I put my email and then changed to VSTS otherwise there is no way to put username.
It's a pity such a great tool has this big and obvious problem and lack of document.

Like # people like this

Same problem here...

Like # people like this

I finally got it to work.  here is what I did. 

1. Select "Visual Studio Team Services" as Hosting Service.

2. For host name, use https://[yourname or org name]

3. Click on Refresh Personal Access Token, and type in your MS account user name.  For password, enter the token that you have generated from Azure DevOps.

- To generate a token, login to Azure Dev Ops.  On the top right menu, click on the circle with your initials and select "Security".  Generate a new one token.  Give it a name, e.g. SourceTree (not important), and copy the token to be used with SourceTree.

4. Here is the tricky part -- On SourceTree, I tried several times and it kept saying authenticated failed.  I finally (through random frustration) clicked on the error message itself and it refreshed and say "Authenticated".  Definitely buggy.  Good luck.

Like # people like this
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 11, 2019

Interesting, thanks for the update.

The error message isn't actually an active element, just a textbook, I'd guess there was just a log between old error messages and the new success coming through and being  shown.

I followed Lhkengs instructions:


I am on the new         domain

This uri is not accepted via sourcetree as constantly unable to verify

If i revert back to the old address of  and use same credentials it is successful.

Then when i go into clone a repository:

I get This is not a valid source path / URI[repository]



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events