Connect Azure Devops Account

[Amir Barzilay]

Hi there,

so, im having trouble with the subject with Sourcetree 3.0.1. 

A few months ago, I cloned the project using a username&Token url. 

As it seems the Token has expired and so i've created a new one and tried adding the account to sourcetree. 

I'm typing in the username (tried primary and secondary) & token as described in my account in  https://dev.azure.com.

The only thing i'm baffled about is the host i should be using, tried:

1. https://dev.azure.com/MYHOSTNAME

2. my git url. 

keep getting: 

We couldn't connect to Azure DevOps with your ('MyUserName') credentials. Check your username and try the password again.

What am i missing? 

[Edwin Klesman]

I got this working via the following steps:

1. Create a PAT in azure DevOps (https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops)
2. Make sure you copy the generated PAT as you won't be able to view it again
3. On Source Tree, go to add account and select Azure DevOps
4. for the host, I used https://{organisation}.visualstudio.com as the new URL format for azure DevOps didn't work
5. enter the generated PAT as username
6. use the PAT you just generated for the password as well

If somehow your Sourcetree doesn't seem to be using the right PAT credentials when you try to clone your repo, force Sourcetree to use the credentials by prefixing the URL with them:

1. Get the URL from the Azure DevOps Repo, ie: https://{organisation}.visualstudio.com/{projectname}/_git/{projectname}
2. Add the token as username and password in the URL of the repo, ie:
   https://{token}:{token}@{organisation}.visualstudio.com/{projectname}/_git/{projectname}

Using these steps, SourceTree will force using the PAT as credentials for the repo and you can clone and work on the repo directly.

PS: Somehow, I couldn't get the username - PAT as a password combination working. I found out this route and it works for me.

I hope it saves you some time!

[psundareshan]

this worked for me! thanks Edwin.

[Edwin Klesman]

Glad it helped you @psundareshan 

[Christian Wölke]

@Edwin Klesman @psundareshan The issue is solved in the newest release 3.4.3.0


https://jira.atlassian.com/browse/SRCTREEWIN-10800

[Edwin Klesman]

Good to read that! I know that connections like this can be a little fragile, but what I understand from MS is that the current setup will last for the upcoming period. 

Thanks for the update @Christian_Wölke 

[TK]

I can't seem to get this working, plus I have an issue. When I enter the host url (for ex: https://tfs.mydomain.com/), no matter what I enter, it won't accept it. I believe this, because I'm unable to enter a username in the username box. The only way I can get some sort of prompt for credentials, is by clicking on 'Refresh Personal Access Token'. However, even when I do that, it doesn't work.

Please see the attachment:

This is also from Sourcetree. I am using version 3.4.8.

Any ideas?

[Cu Thi Phuong Thao]

Thank you so much. I have faced this issue over 3 days before, and your contribution works for me. God bless you!!!

[Amir Barzilay]

So.. adding an account didn't work for me, but i managed to solve the problem by changing the repository url to include the new token 

Sourcetree -> repository -> repository settings -> remotes

Hope it helps someone... 

[amrud]

doesn't work for me. the repository settings option is disabled

[jay.n]

did you solve this?

[Amila Udayanga]

I managed to get this sorted by doing the following.

1. Create a PAT in azure devops (https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops)
2. Make sure you copy the generated PAT as you won't be able to view it again
3. On Source Tree, go to add account and select Azure DevOps
4. for host, I used https://{organisation}.visualstudio.com as the new url format for azure devops didn't work
5. enter username that you use
6. use the PAT you just generated for the password

Hope this helps

-----UPDATE-----

above works for adding the account, but gets an error when trying to clone a repo from DevOps as the git url is in the old format. 

[Craig Haydon]

@Amila Udayanga .. did you resolve the cloning issue. If so... how did you fix?

[David Connor]

@Craig Haydon I managed to get it working using his/her instructions. Step 4 is the important one then it's just a matter of logging in.

[Armando]

Hello,

for me works to add an Account using the URL

https://{organisation}.visualstudio.com/

Username: Your PAT

Passwort: Your PAT

HTTPS

How to create a PAT (Personal Authentication Token):

https://docs.microsoft.com/de-de/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&viewFallbackFrom=vsts&tabs=preview-page

Then all works fine!

Kind Regards

Armando

[jeevasusej]

It is really working. 

[Christian Wölke]

There is still a bug open for that topic, since one year. Please vote for it, to solve it asap.

Authentication fails when using Azure DevOps URL

Regards

Christian

[sinekhaya brian ntuli]

Operating from the original server's account workspace is by the court of law that it had ruled over all. To mean, any candidate who had been voted out by participate due to unnecessary conditions, is requested to resume systems maintenance from the actual service providers area of monitor. Currently this malfunction is not monitored!

[Christian Wölke]

@Amir Barzilay @ou can close that issue as it is solved
https://jira.atlassian.com/browse/SRCTREEWIN-10800

[Christian Wölke]

Hi Guys

A few of you are describing an workaround with using the visualstudio URL. But the main problem is, that the new azure URL does not work.

This needs to be fixed please.

Regards
Christian

[Edwin Klesman]

It seems to be different depending on unknown factors.

When I open up my projects (even one I created this January (2020), and go to the repo to find the clone URL it says:

https://<myorganisation>.visualstudio.com/<projectname>/_git/<projectname>

So I use that. I didn't bother checking if the new URL format works since the tool shows me that URL. 

If there are people that see the new URL format as "clone url" for their repo and that is not working, you're right: it should be fixed. But it needs to be fixed by Microsoft

What I find troublesome is the lack of documentation stating on how to get access to the repo correct (PAT as username and as password?)... This takes a lot of time for people.

[Christian Wölke]

Hi Edwin

Thanks for the answer.

I already mentioned that problem posted a bug also in the Microsoft community. https://developercommunity.visualstudio.com/content/problem/815239/new-organization-url-for-git-url-with-prefix.html

For me it is not clear where the bug needs to be fixed. Maybe you can also contribute on that bug.

Regards

Christian

[Amair Mohammed]

@Amila Udayanga

I w as able to log in and clone the repo successfully. Thanks for the instructinos.!

[Amila Udayanga]

Glad it helped :)