Cannot Sign in to Azure using new 'Azure Resources' from Visual Studio Code.

[Vijay-Koganti]

I could sign in last week without any issues. Now its a nightmare. I get a popup saying "The extension 'Azure Resources' wants to sign in using Microsoft". I click 'Allow'. It opens a popup. I select 'my windows ID' displayed there and nothing happens. I tried uninstalling the extension, then uninstalling and re-installing Visual Studio Code. Really struggling with this updated 'Azure Resources'. I tried about 20 to 30 different things including opening the Visual Studio Code as 'admin' but nothing works.

[Vijay-Koganti]

I get an error called 'Unexpected: (pii)'. Please see attached screenshot.

[alexweininger]

Hi Vijay, VS Code had a major release last week that changed the authentication implementation. Can you confirm what version of VS Code you're using?

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. You can try setting the microsoft-authentication.implementation to classic and restarting VS Code. Keep in mind that this setting won't be around for much longer. If we can confirm that this is what's causing the issue then we can forward it to the VS Code team.

[Vijay-Koganti]

Hi Thanks for that tip. I tried the 'classic' route and I could login within seconds. I spent a frustrating 4 hours doing everything I can but the 'sign-in' link would stay on and on. I've taken screenshots and attached of the problem. Basically I start of by clicking on 'Sign in to Azure' and then I click 'Allow' on the popup that appears with the question: 'The extension 'Azure Resources' wants to sign in using Microsoft'. I am then taken to a popup where it presents me with the various logins I have on different azure subscriptions. I pick the one that I am currently logged in as 'Windows User' as it's the same user account. And the popup disappears. Then instead of being being signed in I notice that it asks me to sign in again. Sometimes it shows the first popup a second time. But the end result in the same. I am unable to login. Please do not disable 'classic' until this is fixed. It's a major issue. I have to deploy several key bicep files urgently. ***@***.*** Kind Regards, Vijay Koganti Head of Development and DevOps Bromcom Computers PLC www.bromcom.com<http://www.bromcom.com/> From: Alex Weininger ***@***.***> Sent: 10 February 2025 15:39 To: microsoft/vscode-azureresourcegroups ***@***.***> Cc: Vijay Koganti ***@***.***>; Author ***@***.***> Subject: Re: [External] [microsoft/vscode-azureresourcegroups] Cannot Sign in to Azure using new 'Azure Resources' from Visual Studio Code. (Issue #1039) [https://members.ironscales.com/static/webapp/images/iron_icon_color_7_2021.png] IRONSCALES couldn't recognize this email as this is the first time you received an email from this sender notifications @ github.com Hi Vijay, VS Code had a major release last week that changed the authentication implementation. Can you confirm what version of VS Code you're using? See here https://code.visualstudio.com/updates/v1_97#_microsoft-account-now-uses-msal-with-wam-support-on-windows<https://urldefense.proofpoint.com/v2/url?u=https-3A__code.visualstudio.com_updates_v1-5F97-23-5Fmicrosoft-2Daccount-2Dnow-2Duses-2Dmsal-2Dwith-2Dwam-2Dsupport-2Don-2Dwindows&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=kO-MpmZwZPyFf0Py2j101FkdNyiqDeAobmaA7oHI0UTCaOfhYu0Dw1mq3J5hAXsB&s=FCa3pX0MHADEWWz7VuiVYvfg6xJ7rjrc5bjTM_-058U&e=> for information on the new implementation. You can try setting the microsoft-authentication.implementation to classic and restarting VS Code. Keep in mind that this setting won't be around for much longer. If we can confirm that this is what's causing the issue then we can forward it to the VS Code team. - Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_microsoft_vscode-2Dazureresourcegroups_issues_1039-23issuecomment-2D2648429398&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=kO-MpmZwZPyFf0Py2j101FkdNyiqDeAobmaA7oHI0UTCaOfhYu0Dw1mq3J5hAXsB&s=R-B-3EO6w8kqx7SJ7l7ts1Ne4IO93Wf-IqLcirzw91k&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_A4HCVQEBLNNJKEGZ2TPRG7D2PDBX3AVCNFSM6AAAAABW2TIL3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBYGQZDSMZZHA&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=kO-MpmZwZPyFf0Py2j101FkdNyiqDeAobmaA7oHI0UTCaOfhYu0Dw1mq3J5hAXsB&s=FhRp4917RYdn8yU3c_qaawaU95wwbqSmXuChLgo_3BE&e=>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> This email, its contents and any files transmitted with it is confidential and may also be privileged. If you are not the intended recipient please notify the sender using the email reply option and then delete it; you should not copy the email or use it for any purpose or disclose its contents to any other person. Unless expressly stated otherwise no content herein may be held binding upon Bromcom Computers Plc or any associated company unless confirmed by the issuance of a formal contractual document or purchase order. Any statements made, opinions or intentions expressed may not necessarily reflect the view of Bromcom Computers Plc or any associated company. No responsibility is assumed for changes made to this email after it was sent. Any electronic voice communications to or from the company or associated companies may be recorded for quality control purposes or for the purposes of general record keeping. This includes but is not limited to telephone calls, conference calls and online seminars. Registered Office: Bromcom Computers Plc, Rutland House, 44 Masons Hill, Bromley, Kent, BR2 9JG Registered in England No: 2040690

[alexweininger]

Hi Vijay, could you re-file this issue on the VS Code repository? https://github.com/microsoft/vscode/issues

[Vijay-Koganti]

Hi, Thanks. I have done that. Here is the link: microsoft/vscode#240350 I suspect this issue is happening because I have multiple Windows login accounts on my laptop. To test this theory I am going to remove extra logins and only retain the main login today and try again. In many cases the coder expects the windows login to be a single piece of string whereas the actual windows logins is an array of logins available on the local laptop. Sometimes some developers take the array[0] the element. In my case it is the array[2] login that is the one I use. This is just my suspicion at the moment. I will find out more today and will keep this bug updated with my findings. Thanks. Kind Regards, Vijay Koganti Head of Development and DevOps Bromcom Computers PLC www.bromcom.com<http://www.bromcom.com/> From: Alex Weininger ***@***.***> Sent: 10 February 2025 20:37 To: microsoft/vscode-azureresourcegroups ***@***.***> Cc: Vijay Koganti ***@***.***>; Author ***@***.***> Subject: Re: [External] [microsoft/vscode-azureresourcegroups] Cannot Sign in to Azure using new 'Azure Resources' from Visual Studio Code. (Issue #1039) Hi Vijay, could you re-file this issue on the VS Code repository? https://github.com/microsoft/vscode/issues<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_microsoft_vscode_issues&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=8y44KSuXHYuIySfzOvd-IPIKAlcQYwbkay0lr_J6nrGz0D_HcWD1rzNc6DRdj4Ap&s=K-QGVj8n-hsE1EhTWGx3HWw35JxWPgMcAQPhze75xlg&e=> — Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_microsoft_vscode-2Dazureresourcegroups_issues_1039-23issuecomment-2D2649177822&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=8y44KSuXHYuIySfzOvd-IPIKAlcQYwbkay0lr_J6nrGz0D_HcWD1rzNc6DRdj4Ap&s=8kZwWpPsJNh3KSEKx2pvnYLK8kIxu8S3pZ1Td22CqnI&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_A4HCVQAPNZKRNSKCTLAY73D2PEEVRAVCNFSM6AAAAABW2TIL3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBZGE3TOOBSGI&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=8y44KSuXHYuIySfzOvd-IPIKAlcQYwbkay0lr_J6nrGz0D_HcWD1rzNc6DRdj4Ap&s=YrvevBhn-Y8C8NdzUPAwhndawP0PIWHLLNwB3oIRBqM&e=>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> This email, its contents and any files transmitted with it is confidential and may also be privileged. If you are not the intended recipient please notify the sender using the email reply option and then delete it; you should not copy the email or use it for any purpose or disclose its contents to any other person. Unless expressly stated otherwise no content herein may be held binding upon Bromcom Computers Plc or any associated company unless confirmed by the issuance of a formal contractual document or purchase order. Any statements made, opinions or intentions expressed may not necessarily reflect the view of Bromcom Computers Plc or any associated company. No responsibility is assumed for changes made to this email after it was sent. Any electronic voice communications to or from the company or associated companies may be recorded for quality control purposes or for the purposes of general record keeping. This includes but is not limited to telephone calls, conference calls and online seminars. Registered Office: Bromcom Computers Plc, Rutland House, 44 Masons Hill, Bromley, Kent, BR2 9JG Registered in England No: 2040690

[Vijay-Koganti]

Hi, I removed the 2 additional windows account. I then reverted back from ‘classic’ to ‘msal’. This time I saw only 1 account in the popup – then I clicked SignIn and then clicked ‘Allow’. I cannot however signin. In the end I had to revert back from ‘msal’ to ‘classic’ to be able to sign in. So the problem is still unresolved. Please don’t disable classic till these issues are resolved. ***@***.*** Kind Regards, Vijay Koganti Head of Development and DevOps Bromcom Computers PLC www.bromcom.com<http://www.bromcom.com/> From: Vijay Koganti ***@***.***> Sent: 11 February 2025 08:51 To: microsoft/vscode-azureresourcegroups ***@***.***>; microsoft/vscode-azureresourcegroups ***@***.***> Cc: Author ***@***.***> Subject: RE: [External] [microsoft/vscode-azureresourcegroups] Cannot Sign in to Azure using new 'Azure Resources' from Visual Studio Code. (Issue #1039) Hi, Thanks. I have done that. Here is the link: microsoft/vscode#240350 I suspect this issue is happening because I have multiple Windows login accounts on my laptop. To test this theory I am going to remove extra logins and only retain the main login today and try again. In many cases the coder expects the windows login to be a single piece of string whereas the actual windows logins is an array of logins available on the local laptop. Sometimes some developers take the array[0] the element. In my case it is the array[2] login that is the one I use. This is just my suspicion at the moment. I will find out more today and will keep this bug updated with my findings. Thanks. Kind Regards, Vijay Koganti Head of Development and DevOps Bromcom Computers PLC www.bromcom.com<http://www.bromcom.com/> From: Alex Weininger ***@***.******@***.***>> Sent: 10 February 2025 20:37 To: microsoft/vscode-azureresourcegroups ***@***.******@***.***>> Cc: Vijay Koganti ***@***.******@***.***>>; Author ***@***.******@***.***>> Subject: Re: [External] [microsoft/vscode-azureresourcegroups] Cannot Sign in to Azure using new 'Azure Resources' from Visual Studio Code. (Issue #1039) Hi Vijay, could you re-file this issue on the VS Code repository? https://github.com/microsoft/vscode/issues<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_microsoft_vscode_issues&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=8y44KSuXHYuIySfzOvd-IPIKAlcQYwbkay0lr_J6nrGz0D_HcWD1rzNc6DRdj4Ap&s=K-QGVj8n-hsE1EhTWGx3HWw35JxWPgMcAQPhze75xlg&e=> — Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_microsoft_vscode-2Dazureresourcegroups_issues_1039-23issuecomment-2D2649177822&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=8y44KSuXHYuIySfzOvd-IPIKAlcQYwbkay0lr_J6nrGz0D_HcWD1rzNc6DRdj4Ap&s=8kZwWpPsJNh3KSEKx2pvnYLK8kIxu8S3pZ1Td22CqnI&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_A4HCVQAPNZKRNSKCTLAY73D2PEEVRAVCNFSM6AAAAABW2TIL3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBZGE3TOOBSGI&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=8y44KSuXHYuIySfzOvd-IPIKAlcQYwbkay0lr_J6nrGz0D_HcWD1rzNc6DRdj4Ap&s=YrvevBhn-Y8C8NdzUPAwhndawP0PIWHLLNwB3oIRBqM&e=>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> This email, its contents and any files transmitted with it is confidential and may also be privileged. If you are not the intended recipient please notify the sender using the email reply option and then delete it; you should not copy the email or use it for any purpose or disclose its contents to any other person. Unless expressly stated otherwise no content herein may be held binding upon Bromcom Computers Plc or any associated company unless confirmed by the issuance of a formal contractual document or purchase order. Any statements made, opinions or intentions expressed may not necessarily reflect the view of Bromcom Computers Plc or any associated company. No responsibility is assumed for changes made to this email after it was sent. Any electronic voice communications to or from the company or associated companies may be recorded for quality control purposes or for the purposes of general record keeping. This includes but is not limited to telephone calls, conference calls and online seminars. Registered Office: Bromcom Computers Plc, Rutland House, 44 Masons Hill, Bromley, Kent, BR2 9JG Registered in England No: 2040690

[MCorreia456]

I had a similar issue. Switching to classic solved my problem as well. Logged my issue here: microsoft/vscode#240439

[alexweininger]

I had a similar issue. Switching to classic solved my problem as well. Logged my issue here: microsoft/vscode#240439

Thank you!

[yueyuanlucy]

Hi I also had a similar issue and got stuck on it for 5 hours, like we need to sign in using an incognito window, but the current program does not allow to open the incognito for signing in, which is really not convenient. The only way is to switch to classic option, which will be deprecated soon? Don't know what users can do after that. I think this is really a BIG problem for microsoft or vs code that should be addressed pretty immediately.

[alexweininger]

Hi I also had a similar issue and got stuck on it for 5 hours, like we need to sign in using an incognito window, but the current program does not allow to open the incognito for signing in, which is really not convenient. The only way is to switch to classic option, which will be deprecated soon? Don't know what users can do after that. I think this is really a BIG problem for microsoft or vs code that should be addressed pretty immediately.

Hi @yueyuanlucy, have you filed an issue on the VS Code repository? If not, please file an issue and detail your situation and they can help. https://github.com/microsoft/vscode/issues

[glloyd2010f]

Hi Vijay, VS Code had a major release last week that changed the authentication implementation. Can you confirm what version of VS Code you're using?

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. You can try setting the microsoft-authentication.implementation to classic and restarting VS Code. Keep in mind that this setting won't be around for much longer. If we can confirm that this is what's causing the issue then we can forward it to the VS Code team.

Was unable to login to any Azure Extension while microsoft-authentication.implementation was set to msal within VSCode. Switch this setting back to classic and everything logged in.

In summary when doing with with the browser window everything worked as expected.

[Vijay-Koganti]

Hi, Here are the details of my VS setup – Also additional info: I uninstalled and re-installed Visual Studio code and that has not made any difference. Whilst installing I chose ‘current user’ setup route. Version: 1.97.1 (user setup) Commit: e249dada235c2083c83813bd65b7f4707fb97b76 Date: 2025-02-10T13:13:58.153Z Electron: 32.2.7 ElectronBuildId: 10660205 Chromium: 128.0.6613.186 Node.js: 20.18.1 V8: 12.8.374.38-electron.0 OS: Windows_NT x64 10.0.19045 Kind Regards, Vijay Koganti Head of Development and DevOps Bromcom Computers PLC www.bromcom.com<http://www.bromcom.com/> From: glloyd2010f ***@***.***> Sent: 14 February 2025 21:01 To: microsoft/vscode-azureresourcegroups ***@***.***> Cc: Vijay Koganti ***@***.***>; Author ***@***.***> Subject: Re: [External] [microsoft/vscode-azureresourcegroups] Cannot Sign in to Azure using new 'Azure Resources' from Visual Studio Code. (Issue #1039) Hi Vijay, VS Code had a major release last week that changed the authentication implementation. Can you confirm what version of VS Code you're using? See here https://code.visualstudio.com/updates/v1_97#_microsoft-account-now-uses-msal-with-wam-support-on-windows<https://urldefense.proofpoint.com/v2/url?u=https-3A__code.visualstudio.com_updates_v1-5F97-23-5Fmicrosoft-2Daccount-2Dnow-2Duses-2Dmsal-2Dwith-2Dwam-2Dsupport-2Don-2Dwindows&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=PtoZOZ2X1S7p1G__yq3dMnPd1ykB83wvTfV5wSFF3l9VbPbXjhfqBm6KKkgxrB_P&s=o7ly-TcejYYnLz6EI8nF62W8g0PSAP6ZA2gpfZmvPaI&e=> for information on the new implementation. You can try setting the microsoft-authentication.implementation to classic and restarting VS Code. Keep in mind that this setting won't be around for much longer. If we can confirm that this is what's causing the issue then we can forward it to the VS Code team. Was unable to login to any Azure Extension while microsoft-authentication.implementation was set to msal within VSCode. Switch this setting back to classic and everything logged in. In summary when doing with with the browser window everything worked as expected. — Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_microsoft_vscode-2Dazureresourcegroups_issues_1039-23issuecomment-2D2660261351&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=PtoZOZ2X1S7p1G__yq3dMnPd1ykB83wvTfV5wSFF3l9VbPbXjhfqBm6KKkgxrB_P&s=VdlqgzatSc_WlzV97HX-Kdt5HSAS0gqbBbWz02SYv8A&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_A4HCVQH3HEDSM6HF6DYUYDT2PZKSFAVCNFSM6AAAAABW2TIL3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGI3DCMZVGE&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=PtoZOZ2X1S7p1G__yq3dMnPd1ykB83wvTfV5wSFF3l9VbPbXjhfqBm6KKkgxrB_P&s=31ROFr8jLv2zZmtHzDtIlocYoWAbz9ecjXShQjZ1VQQ&e=>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> [glloyd2010f]glloyd2010f left a comment (microsoft/vscode-azureresourcegroups#1039)<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_microsoft_vscode-2Dazureresourcegroups_issues_1039-23issuecomment-2D2660261351&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=PtoZOZ2X1S7p1G__yq3dMnPd1ykB83wvTfV5wSFF3l9VbPbXjhfqBm6KKkgxrB_P&s=VdlqgzatSc_WlzV97HX-Kdt5HSAS0gqbBbWz02SYv8A&e=> Hi Vijay, VS Code had a major release last week that changed the authentication implementation. Can you confirm what version of VS Code you're using? See here https://code.visualstudio.com/updates/v1_97#_microsoft-account-now-uses-msal-with-wam-support-on-windows<https://urldefense.proofpoint.com/v2/url?u=https-3A__code.visualstudio.com_updates_v1-5F97-23-5Fmicrosoft-2Daccount-2Dnow-2Duses-2Dmsal-2Dwith-2Dwam-2Dsupport-2Don-2Dwindows&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=PtoZOZ2X1S7p1G__yq3dMnPd1ykB83wvTfV5wSFF3l9VbPbXjhfqBm6KKkgxrB_P&s=o7ly-TcejYYnLz6EI8nF62W8g0PSAP6ZA2gpfZmvPaI&e=> for information on the new implementation. You can try setting the microsoft-authentication.implementation to classic and restarting VS Code. Keep in mind that this setting won't be around for much longer. If we can confirm that this is what's causing the issue then we can forward it to the VS Code team. Was unable to login to any Azure Extension while microsoft-authentication.implementation was set to msal within VSCode. Switch this setting back to classic and everything logged in. In summary when doing with with the browser window everything worked as expected. — Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_microsoft_vscode-2Dazureresourcegroups_issues_1039-23issuecomment-2D2660261351&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=PtoZOZ2X1S7p1G__yq3dMnPd1ykB83wvTfV5wSFF3l9VbPbXjhfqBm6KKkgxrB_P&s=VdlqgzatSc_WlzV97HX-Kdt5HSAS0gqbBbWz02SYv8A&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_A4HCVQH3HEDSM6HF6DYUYDT2PZKSFAVCNFSM6AAAAABW2TIL3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGI3DCMZVGE&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=apr_Gjf7w_3x6fEbQHAHJ7qeSbtmpgdP9glcG_Qw9o8&m=PtoZOZ2X1S7p1G__yq3dMnPd1ykB83wvTfV5wSFF3l9VbPbXjhfqBm6KKkgxrB_P&s=31ROFr8jLv2zZmtHzDtIlocYoWAbz9ecjXShQjZ1VQQ&e=>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> This email, its contents and any files transmitted with it is confidential and may also be privileged. If you are not the intended recipient please notify the sender using the email reply option and then delete it; you should not copy the email or use it for any purpose or disclose its contents to any other person. Unless expressly stated otherwise no content herein may be held binding upon Bromcom Computers Plc or any associated company unless confirmed by the issuance of a formal contractual document or purchase order. Any statements made, opinions or intentions expressed may not necessarily reflect the view of Bromcom Computers Plc or any associated company. No responsibility is assumed for changes made to this email after it was sent. Any electronic voice communications to or from the company or associated companies may be recorded for quality control purposes or for the purposes of general record keeping. This includes but is not limited to telephone calls, conference calls and online seminars. Registered Office: Bromcom Computers Plc, Rutland House, 44 Masons Hill, Bromley, Kent, BR2 9JG Registered in England No: 2040690

[mikedice]

I agree with one of the posters above. Sign in has become a nightmare in vs code. The MSAL option for sign in does not work. With that enabled I get a very annoying popup that asks me to sign in but when I type in the account name I get red error messages in the same dialog that says my account cannot be accessed. Thats funny, I can access my account from:

• az login
• the browser
• VS Code if I switch MSAL mode back to classic mode

You see those errors and you go down the path of 'gee what did I do wrong?' and waste a couple of precious hours trying to figure it out if you ever get it figured out.

Please disable or remove MSAL mode. It doesn't work.

Version: 1.97.2 (user setup)
Commit: e54c774e0add60467559eb0d1e229c6452cf8447
Date: 2025-02-12T23:20:35.343Z
Electron: 32.2.7
ElectronBuildId: 10982180
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.26100

Sorry, I have a million Azure plugins installed. Maybe the most relevant one is Azure Resources 0.10.6. If you need verison of infor for more let me know

[alexweininger]

@mikedice Hi Mike, sorry for the troubles. Please file an issue on VS Code https://github.com/microsoft/vscode/issues detailing that it doesn't work with MSAL enabled, and only works with classic mode. cc: @TylerLeonhardt