WAM triggers a server lockup when configured as the default login method on Windows Server 2022 running in core mode (without a GUI) #24787
Labels
Accounts
Issues in Az.Accounts except authentication related
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
Investigate 🔍
Tracking
We will track status and follow internally
WAM
Web Account Manager
Milestone
Description
Setting
Update-AzConfig -EnableLoginByWam $true
and runningConnect-AzAccount
on a fresh installation of Windows Server 2022 in core mode (without a GUI) with Az 11.6.0 causes the console for Windows PowerShell 5.1 and the server to become unresponsive. I can replicate the problem every time, but the server has to be reset because you cannot close the console or usecntl+alt+del
.I would expect
Connect-AzAccount
to detect that a GUI is not present and default to using the-DeviceCode
parameter.Issue script & Debug output
Environment data
Module versions
Error output
The text was updated successfully, but these errors were encountered: