Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Visual Studio: User account you used to sign in is not supported for this application

Tags:

I use to sign-in to server explorer & query AzureTable entities. However since I have updated to Visual Studio Update 4, I have not been able to login.

I tried using same credentials on azure portal & they work perfectly fine.

Visual Studio

Sorry, but we're having trouble signing you in

User account you used to sign in is not supported for this application. Please use a different account to sign in.

To my surprise, Google did not return any relevant search result for this error.

P.S. I have double checked my Microsoft account credentials & they are working. This issue has been happening with other team members on different PCs as well.

like image 978
Abhijeet Avatar asked Dec 15 '14 05:12

Abhijeet


People also ask

Can you use Visual Studio without signing in?

Login is required per Microsoft Docs after the trial period. VS Community is free (if you meet the license terms), but you do need to login to renew the license. If you just want to use the Visual C++ compiler from the command-line, then look at the Build Tools for Visual Studio 2019 release.


2 Answers

I have learned to live with this error. This is definitely a bug in VS-2013 Update 4 which Microsoft should look into.

  1. I use to sign-out from current subscription in Azure
  2. Right click Azure in server explorer
  3. Click Connect to Microsoft Azure Subscription

It works for one and only time. Next time repeat the process 1 to 3 again.

like image 71
Abhijeet Avatar answered Sep 30 '22 17:09

Abhijeet


I believe I've had the exact same issue. Here's how I resolved it:

In the log-in page that "pops up" from Visual Studio I deleted the Microsoft account id that I usually sign in with and entered a different account ID that I own.

As soon as I finished typing the account id in, the page was refreshed and I was redirected to a Microsoft account log-in page. In that log-in page I made sure to type in the correct Microsoft account ID (the one I use for Azure) and its password. Having successfully signed in there, I was able to continue working as usual.

This was roughly based on guidance I found in this Microsoft Technet discussion.

like image 25
urig Avatar answered Sep 30 '22 17:09

urig