You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To Reproduce
Steps to reproduce the behavior:
Attempt to connect to OSD Cloud Azure it will fail after authenticating with the above error
Expected behavior
AZ connect should connect after Authenticating Azure PowerShell
Desktop (please complete the following information):
Windows WinPE
Additional context
Add any other context about the problem here.
we need to add in the workaround mentioned in the article for azure powershell Update-AzConfig -EnableLoginByWam $false
of force the process to use an older module instead of installing the latest module until the bug gets corrected.
The text was updated successfully, but these errors were encountered:
That works for the standalone ISO but causes the no prompt one to be broken I was able to tweak the module connect-osdcloduazure.ps1 to include
Update-AzConfig -EnableLoginByWam $false -LoginExperienceV2 Off -ErrorAction SilentlyContinue
right after the import az account module and tweaked the edit-OSDClodudwinPE command to not install a fresh copy of the module but to copy the edited one this works until a new version comes out since booting into the iso causes the module to update undoing my changes
can this fix be implemented until Microsoft puts out a fix for the AZ module?
Describe the bug
We seem to be affect by this bug:
Azure/azure-powershell#24967
To Reproduce
Steps to reproduce the behavior:
Attempt to connect to OSD Cloud Azure it will fail after authenticating with the above error
Expected behavior
AZ connect should connect after Authenticating Azure PowerShell
Desktop (please complete the following information):
Windows WinPE
Additional context
Add any other context about the problem here.
we need to add in the workaround mentioned in the article for azure powershell Update-AzConfig -EnableLoginByWam $false
of force the process to use an older module instead of installing the latest module until the bug gets corrected.
The text was updated successfully, but these errors were encountered: