Error TF30063: You are not authorized to access …

Question

I'm using TFS Preview (Team Foundation Service) with one of my projects with Visual Studio 2012. I'm also using an on-premises TFS server with most of my projects. When I use my on-premises TFS after using TFS preview and go back to using TFS preview, I get this error:

TF30063: You are not authorized to access MyProject\DefaultCollection.

If I go to Team → Disconnect TFS and then connect to TFS preview again, I'm able to see a "Loading identifiers" loading screen coming up, but in the end I don't get to enter my credentials to TFS preview (my Microsoft account) and as a result, the TF30063 error still occurs.

I suspect this has something to do with my Microsoft account (i.e. Live ID). I'm logged in to Windows with the same Microsoft account that I use at TFS preview. I have logged in to other sites (Windows Development Center, MSDN, etc.) with other Microsoft accounts, but I verified that if I log out of these services and re-login with the correct Microsoft account, I still get the TF30063 error when I try to log in to TFS preview from Visual Studio.

Answer 1

I had to "run as a different user" to get Visual Studio to connect using my TFS account. It seemed to be trying to use my Microsoft account instead.

Text and image from: https://www.visualstudio.com/en-us/docs/connect/connect-team-projects

To change accounts

To run Visual Studio under an account that is different from your logged on Windows account, open the context menu for devenv.exe to access your run as options.

You can locate the executable in the following folder: Drive:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE.

Answer 2

When I came accross this issue none of the provided answers solved this problem or if it did I didn't like recreating the project. The way I ended up solving the issue:

1. Clicking on the "Connect to Team Projects button" (The plug next to the home button in the Team Explorer tab)
2. Right click the project you are getting this issue on.
3. Click Connect.

I guess the "Remember me" cookie timed out but gave me a generic response for trying to push or pull any code.

Answer 3

Check the information in registry : HKEY_CURRENT_USER\SOFTWARE\Microsoft\VSCommon\Keychain\Accounts and delete the related keys under Accounts section.

Clear the cache in these paths:

• %localappdata%\Microsoft\TeamTest

• %localappdata%\Microsoft\Team Foundation

• %localappdata%\Microsoft\VisualStudio

• %appdata%\Roaming\Microsoft\VisualStudio

Hope this will work.

Note: By doing this may clear all the cookies and caches and load the Visual Studio New.

Answer 4

In VS 2015 it can be achieved by Team Explorer > Connect > Manage Connections and selecting the team project again. In case of there exist more than one account in VS, Team Explorer asks for which account to use to connect to the team project.

Answer 5

I finally found the right answer for me on the web.

For me it happened after I changed my password and Windows cached the TFS password. It is require to be updated manually. This is one way to do it:

Solution found at: developercommunity.visualstudio.com

CREDIT: Lavente Nagy! Thanks so much!

Fix Summary:

I found a solution, and it works on Windows 7/Windows 10 too. The steps are the same:

Close Visual Studio. Go to Control Panel (with small icon view) → User Accounts → Manage your credentials (on the left column) → Select "Windows Credentials" → Scroll down to the "Generic Credentials" section and look for your TFS server connection. Expand the pull down and click "Edit". Enter in new network password. Reopen Visual Studio and everything should work again.

Answer 6

This happens to me regularly, and none of the solutions described above works every time. Most of the times the solution where you use the "Connect to Team Projects button" works fine, but sometimes nothing happens when I do this.

Other times I simply have to re-login to http://tfs.visualstudio.com using the Visual Studio built-in browser (Ctrl+Alt+R) or via Internet Explorer.

(As suggested in some of the other answers, for my part this is not caused by multiple live-ids)