-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Known Issues of Az.Accounts 3.0.0 and Their Workarounds #25005
Comments
What about #25003? |
In ISE, on Windows 11 mine says the following, does this correlate? # 12.0.0 Az
# 3.0.0 Az.Accounts
# 6.0.0 Az.KeyVault
Connect-AzAccount -Tenantid [TenantID] -Subscription [Subscription]
# > Connect-AzAccount : InteractiveBrowserCredential authentication failed: A window handle must be configured. See https://aka.ms/msal-net-wam#parent-window-handles
# > Could not find tenant id for provided tenant domain '[TenantID]'. Please ensure that the provided user is found in the provided tenant domain. |
Thanks for reporting the issue. I reply in it. |
@weyCC81 Thanks for reporting the issue. I shall say yes Please disable WAM to workaround it firstly
|
@weyCC81 Yes, we have reported your issue to MSAL AzureAD/microsoft-authentication-library-for-dotnet#4796 |
I get the same issue whenever I run from an elevated console window. Running the:
...command fixes it. |
We have solved the below issue in the latest version: Az.Accounts 3.0.1
|
1. The interactive login method cannot popup window for WAM (Fixed)
Report an error "User canceled authentication" Refer to AzureAD/microsoft-authentication-library-for-python#707
Note
Fixed in Az.Accounts 3.0.1
2. Azure PowerShell cmdlets are unable to run after login with DeviceCode and DeviceCode login methods will fail without
-Tenant
parameter (Mitigated)Note
Mitigated in Az.Accounts 3.0.1
Root cause
The root cause was found to be an issue with the cache of MSAL. See AzureAD/microsoft-authentication-library-for-dotnet#4786. We are going to integrate the fix into Az.Accounts soon #25618
3. Azure PowerShell cmdlets are unable to run after login with UserName+Password and UserName+Password login methods will fail without
-Tenant
parameter (Mitigated)Note
Mitigated in Az.Accounts 3.0.1
Root cause
UserName+Password cannot support WAM yet and we are requesting Azure.Identity to add the related interface Azure/azure-sdk-for-net#45439
4. WAM pop-up window to select an account is not easy to find
Root case
Fail to get the right console handle. See AzureAD/microsoft-authentication-library-for-dotnet#4887
5 WAM pop-up window doesn't display "Work and school account" option
Note
MSAL team is working on the issue see AzureAD/microsoft-authentication-library-for-dotnet#4797
6. The interactive login method cannot popup window for WAM in Window PowerShell ISE Console
Note
Reported to MSAL team, see AzureAD/microsoft-authentication-library-for-dotnet#4796
The text was updated successfully, but these errors were encountered: