Today in Visual Studio I tried to clone a repository and I got :
Git failed with a fatal error: repository ‘xyz’ not found
After a bit of trial and error, I found that the git command line was giving me the same error message

Quite quickly I figured out that Visual Studio is using my company account (as with the above command prompt) rather than the Microsoft account that I’m logged in with. In my case mu company account uses a stakeholder licence within Visual Studio online and stakeholder by default don’t have access to code.
So then I made my stakeholder account a project administrator:

And as soon as I’ve done this my repository can be cloned:

Then I tried the same within 3 versions of Visual Studio.
15.2 (26430.16) doesn’t require my windows account to be included in the project permissions.
15.3.3 and 15.4.4 do require my windows account to have project admin rights. So it looks like something was broken after 15.2
Discover more from SharePains
Subscribe to get the latest posts sent to your email.
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like.
I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide.
For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions.
SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/
Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/
You can contact me using contact@sharepains.com
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like.
I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide.
For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions.
SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/
Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/
You can contact me using contact@sharepains.com
Thank you
Pieter – thank you for this article – I came across this issue too (I am using VS2017 v15.6.4). I would add that my company account needed to have at least Basic level access to VSTS in addition to permissions on the Project & Git Repo. I was getting errors because my company account originally had only Stakeholder access.
Thanks for your comment David. I’ve got the feeling that something has recently changed in this area.