VS2022 loses DevOps authorization with error TFS30063 - but only after a while

Viewed 5973

I'm noticing this repeatedly with VS2022. Everything starts off well but eventually it seems to lose my authorization on my Azure DevOps project.

I open a solution and VS 2022 connects to Azure Devops. Maybe I make a commit or two and type the little hashtag ('#') symbol in the comment box and sure enough, the list of available work-items appears for me to associate with the checkin. Things are great.

But eventually, that stops working. Nothing appears when I hit the hashtag. So I go to the Team Explorer window and I see this message at the top:

TF30063: You are not authorized to access dev.azure.com/<mycompanyname>.

I try reconnecting through Team Explorer but it doesn't do anything. But if I restart Visual Studio, I'm all connected again. For a while until it happens again.

Anyone have this or know how to fix it? It does not happen to me with VS2019

5 Answers

Experienced the same problem was well. By accident I switched VS 2022 from the embeded to the system browser (Options->Accounts) and after restarting VS 2022 it worked well, however it can be a coincidence:

enter image description here

Just to put a bookend on this, Dan Schulte of Microsoft has officially responded in this thread (see his Dec 14 reply) that they've found the root cause of this problem and have created a fix for it but that the fix won't be released until January.

Apparently it was pretty low level and very hairy and affected not just VS2022 but also previous version. It was something that none of the lists workarounds could truly fix. So I wouldn't bother running repair on your VS install or any of that. It won't fix it.

I had same problem and solved by following this:

  • restart OS;
  • open Visual Studio Installer;
  • on Visual Studio 2022 item, click "Other" button, then "Repair".

that's all.

after updating the version to 17.0.5 its problem was solved.

None of the other methods above worked for me. I tried this in visual studio 2022 and it worked.

Open the Developer PowerShell (search for PowerShell) and type in the following:

TF vc permissions

This will bring up a login screen and allow you to log in. After that you should have permission.

Related