Alternate credentials stop working for existing Visual Studio Online account users
This article helps you resolve a problem where alternate credentials don't work for existing Visual Studio Online account users that are connected to Microsoft Entra ID.
Original product version: Azure DevOps Services Premium
Original KB number: 2991274
Symptoms
Assume that you have applications or tools that work outside the browser (including Team Explorer Everywhere command-line client and the git-tf utility) that requires basic authentication credentials to connect to your Visual Studio Online accounts. When an existing Visual Studio Online account is connected to Microsoft Entra ID, alternate credentials stop working for that account.
For Microsoft accounts, the same alternate credentials can be used to access all your Visual Studio Online accounts.
For organizational accounts, alternate credentials are scoped to Microsoft Entra ID. And alternate credentials can be used to access Visual Studio Online accounts that are connected to that directory.
Workaround
To work around the issue, reset your alternate credentials for that account to resume access for your applications or tools. Follow these steps:
By using a web browser; sign in to the Visual Studio Online account that was connected to Microsoft Entra ID, or the account for which your alternate credentials stop working by typing its address:
https://<youraccountname>.visualstudio.com
Open your profile.
Enable alternate credentials for this account.
Set a password and optionally a secondary user name that isn't an email account if @ is not supported by your application.
Note
If you are member of multiple Visual Studio Online accounts, you will have one set of alternate credentials that can be used to access all your Visual Studio Online accounts associated with your Microsoft Account, and another set for all the accounts connected to each Microsoft Entra directory.
References
For more information, see Visual Studio Online.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for