Closed evgeniylu closed 5 years ago
The above looks like the cmdlet returned - what are the characteristics of this 'hang' does it happen after successful login, or was the login above unsuccessful? Nan you log in wit the -UseDeviceCode switch more successfully?
Login is successful, I can execute some other commands from Az module after the login. They could be different each time, but still the ISE is hanging after ~3 min. By hang I mean you get 'select' cursor on whole window of ISE, you can switch to it with Alt+Tab, you cannot click on button, move the window, select anything on it. I tested how long the ISE could be hung - after ~5 hours it still was in the same state. I don't understand the part related to "-UseDeviceCode" - what should I execute? 'Connect-AzAccount' has only '-UseDeviceAuthentication' switch.
@evgeniylu Please do try with the -UseDeviceAuthentication, and let us know if you are still seeing this issue. Please also note that we now recommend using Visual Studio Code (with the PowerShell extension) rather than ISE for scripting.
After more than 10 min check, ISE still available. Thanks for help
Seeing same behavior with ISE and connection to Azure Internal subscription - switching to VSCode.
I'm on a locked-down device and can't access the URL provided by -UseDeviceAuthentication, and can repro this hang every time I use Connect-AzAccount.
Sadly VSCode doesn't work (unrelated problem, PowerShell extension for VSCode, language server fails to start.
Description
After Connect-AzAccount through ~3 minutes I get powershell ISE window hang. I have to kill the process to continue to use it. In ProcessExplorer I see near 25+ lines that powershell_ise.exe hold dll in Az.Account folder.
Script/Steps for Reproduction
Wait ~3 minutes
Module Version
Environment Data
Debug Output