Sign In Failure for Azure Resources Sign In #899
Comments
rosh2020
changed the title
|
Have you set any proxy related settings in VS Code? My other request is that you share the Microsoft Authentication extension logs (on trace or debug log level) with us. Set the log level with the "Developer: Set Log Level..." command. Then view the logs using the "Developer: Show Logs..." command and selecting "Microsoft Authentication". |
|
alexweininger The proxy setting is blank and so are the relevant HTTP_PROXY and HTTPS_PROXY env variables. I set the log level to Debug but it's still only providing info level: |
|
Any more logs if you set the log level to trace? Also by not setting the proxy settings and proxy env variables I'm assuming that means the proxy (corporate?) was disabled, is that correct? |
|
alexweininger logs with trace: |
|
Ok, thanks for providing those logs. |
|
For reference, I am experiencing the exact same issue. No proxy settings set, identical output. |
|
I'm unfortunately not able to downgrade to 7.1 due to a dependency loop: Earliest version I can downgrade to is 8.0, where the error still occurs |
|
I have the same issue with the same scenario. |
|
Could you retry sign in with the following setting enabled? 
|
alexweininger
added
🐛bug
|
Hello I am having this same issue with pretty much the same scenario. I tried to use MSAL and it still failed. |
|
@Rodion0 could you provide the information that I requested from the original poster from this comment? #899 (comment) |
|
Issue: I am using Azure Resources extension v0.9.4 and I have unable to sign in to azure in order to use the extension. Details: I have been able to use this for the past week or so with no issue. However yesterday (9/9/24) I noticed that when I went to the Azure Resources tab within vscode, it was hanging for a long time. So I decided to log out. Unfortunately I have been unable to log back in. It allows me to authenticate but once it says I am signed in and can close that window, it hangs for a couple minutes and then says there was a network failure. I am not using any proxy settings. Attempts at troubleshooting:
Logs: I set the log level to trace and recorded the logs from Microsoft Authentication. 2024-09-10 15:37:58.254 [info] [email https://management.core.windows.net/.default offline_access openid profile] Got 0 sessions |
|
I am also not using any proxy settings Logs with MSAL: |
|
I don't see a msal option alexweininger, or a Microsoft extension section within Settings. Only relevant extensions in settings are "Azure" and "Microsoft Sovereign Cloud". |
|
Ok, the Msal option might be in a newer build of stable VS Code or perhaps insiders. I'm wondering if this issue popped up because of a VS Code update because all of our authentication is built-in and owned by VS Code itself. I know it's a lot of work, but it would help us and the VS Code team if you could confirm that going back to an older version of VS Code fixes the issue. I would try going to VS Code 1.91.0, two major versions ago. If we can confirm that this is an issue introduced by a recent update then it's much easier for me to take this to the VS Code team and get it fixed ASAP |
|
This would unfortunately not be possible for me |
|
Exactly the same issue with 1.92.2. Rolled back to 1.85.2 and it works fine again. There is clearly a bug in the later version causing Azure Account signin to fail. I'd have thought this issue will be issue to replicate. |
Thanks for confirming this. We believe it's related to this change microsoft/vscode#221736 in VS Code and we're hoping to get a fix out in the next stable VS Code release. |
|
Any estimate on when that would be? |
|
Early October, the next stable release of VS Code. |
Thankss :). This solved my problem... that i was having for the past three months!! |
|
@alexweininger I'm unable to roll back to an earlier version of vs code but looks like this will be fixed soon. Looking forward to hearing when the fix is pushed/when the new update is pushed. Thank you for the help. And thanks others for contributing to the thread |
|
@rosh2020 you can download it here https://code.visualstudio.com/updates/v1_85. Also make sure to update your vscode settings to disable auto update, so that you won't update it to the latest one after you close your 1.85.2 version of vscode. To turn off the auto update: |
|
I downloaded the new version of VSCode 1.94 and am still experiencing the issue. Any advice? |
|
I also cannot roll back to 1.85 |
|
It's weird because I can log in with the Azure Accounts but not with this extension |
|
This prevents Azure Machine learning VSCode Extension from working and Azure Functions from deploying. Please fix this |
@hmrc87 could you file a separate issue and provide details about your setup? Please include logs from the Azure Resources extension. There are many variables at play that can cause sign in failures so I want to make sure we can address your issue. See #899 (comment) for how to get logs. |
|
@Rodion0 the new version of VS Code has been released with the fix. Is it working now for you? |
|
@alexweininger I'm also still not able to access resources. Here are my logs for microsoft authentication: |
|
@alexweininger It is still not working for me even with the update, same errors. |
|
@rosh2020, @keanughorbanian-sb could you enable the |
|
@alexweininger Seems like it works now! Only issue was it was a two step process. I sign in to my Azure account through VS Code and then VS Code asks me to "Sign in to directory" and then I sign in again and then it works. |
|
Ok, then that's working as intended I think. Basically we have to sign in to a general endpoint then list your tenants. And if we can't automatically sign in to your tenants we need to ask you to sign in again. Glad you got it working |
|
OH MY GOD I AM BLIND. I had to click on the actual text "Sign in to directory" after the first sign in - which does not look like a button at all in order for it to work. That's so stupid :( - or am I? :) |
|
Yes, it's a button. Hmm, I wonder if many users are not realizing it's a button, it doesn't really standout as a button. We can probably fix that. |
|
Maybe it's possible to style it as a blue button like the first Sign-In Button, that would help for sure! |
Do you have a screenshot of this? I don't think the Azure Resources extension has a blue sign in button? For me it shows |
|
FYI you can sign out like so: |
|
And also, does everyone understand that tenants == directories? We are trying to decide if we should use directory or tenant in our UI. |
|
Regarding directory or tenant: Just use both :) "Sign in to Tenant (Directory)" Regarding the button: after signing out and signing in again I did not have to choose the directory again. I think adding the same Icon next to the "Sing in to directory"-text as the "Sign in to Azure..." text should do the trick for the blind-eyed people like me and @rosh2020 :) |
|
Thanks. That's helpful feedback. I'm experimenting with this too (will be updating the wording): |
Yeah, once signed in to a tenant in the browser it will automatically grant access next time unless you sign out everywhere and close the browser, etc. No worries. |
Issue: Network Failure error occurs when trying to Sign In with the Azure Resource Groups extension latest version (0.9.1).
Details: The interactive login does pop up and allows me to authenticate with my username/password and MFA and looks successful on the browser. But in VS Code it loads for a long time and eventually ends with a Network Failure. Proxy seems to work for everything else (ie AZ CLI). Our network engineer said the only thing getting dropped from the proxy perspective due to bad SSL handshake is default.exp-tas.com. The domain itself is permitted, it's just a bad handshake. All other parts of the transaction seem to go through so doesn't appear to be a problem on the corporate side.
Workaround: Currently using v0.7.1 which uses the "Azure Account" extension. But this extension will be deprecated soon.
Attempts at Solutioning: Turned all extensions (including the Microsoft Auth provider built-in extension) off and on. Deleted Azure Account Extension. Reinstalled all extensions. Turned off VS Code telemetry setting. Changed proxy env variable. Used both the Sign In command and the GUI.
Please advise.
The text was updated successfully, but these errors were encountered: