There is no "Sign in to Azure..." command under the "Accounts & Tenants" section when no accounts are signed in

[v-chenzha]

OS: All
Build Version: 20250213.1

Repro Steps:

1. Make sure the account signed out.
2. Open the "Accounts & Tenants" section.

Expect:
There is a "Sign in to Azure..." command under the "Accounts & Tenants" section.

Actual:
There is no "Sign in to Azure..." command under the "Accounts & Tenants" section.

More Info:

1. Refresh can fix this issue.
2. This issue doesn't reproduce when setting "Microsoft-authentication: Implementation" to "classic".

[linkmckinney]

I get the constant you are not logged in message.

Steps to reproduce:

1. Click + in Accounts & Tenants from the Azure Resources Extension
2. Click the Allow button when you get the popup "**The extension 'Azure Resources wants to sign in using Microsoft. **"
   This drops down my email accounts that I can sign into at the top in VS code.
3. I select my main account and immediately get this message in the lower right-hand corner.

I have rebooted, restarted, I have not uninstalled yet, that will be my next course of action.

[alexweininger]

@linkmckinney as a workaround, you can set the "Microsoft-authentication: Implementation" setting to "classic". If this doesn't work please let me know.

[KelsonMartins]

@alexweininger Your recommended workaround, did just the trick. Thank you. 😄

[alexweininger]

There's also this fix that was suggested in this VS Code thread: microsoft/vscode#240307 (comment) which allows you to keep using the MSAL setting.

• Delete the directory: %userprofile%\AppData\Local\Microsoft\IdentityCache
• Try signing in with msal again

See here https://code.visualstudio.com/updates/v1_97#_microsoft-account-now-uses-msal-with-wam-support-on-windows for information on the new implementation. Keep in mind that the classic setting won't be around for much longer. If we can confirm that this is what's causing the issue then I encourage you to file an issue on the VS Code repo. https://github.com/microsoft/vscode/issues

Also there's a fix hopefully coming soon for this entire issue: microsoft/vscode#243290 (comment)