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
Customer environment:
Both users and devices are located in Azure China while the application registration is created in the Public Cloud. Azure China users are invited to the same tenant as the application registration in the public cloud via CCB2B. Devices are HAADJ in Azure China.
Symptom:
while we are getting a 0-creds experience with CCB2B (Just selecting the accounts in picker windows). When user is trying to sign in to the application developed by the above-mentioned sample codes in the HAADJ device, each time the authentication window will pop up twice, which is quite not user-friendly
Expected behavior:
We're expecting/want a silent SSO experience like you're receiving in non-CCB2B scenarios.
Proposed solution
No response
Alternatives
No response
The text was updated successfully, but these errors were encountered:
MSAL client type
Managed identity
Problem statement
We use the sample code in document to develop their app:
Using MSAL.NET with Web Account Manager (WAM) - Microsoft Authentication Library for .NET | Microsoft Learn
Customer environment:
Both users and devices are located in Azure China while the application registration is created in the Public Cloud. Azure China users are invited to the same tenant as the application registration in the public cloud via CCB2B. Devices are HAADJ in Azure China.
Symptom:
while we are getting a 0-creds experience with CCB2B (Just selecting the accounts in picker windows). When user is trying to sign in to the application developed by the above-mentioned sample codes in the HAADJ device, each time the authentication window will pop up twice, which is quite not user-friendly
Expected behavior:
We're expecting/want a silent SSO experience like you're receiving in non-CCB2B scenarios.
Proposed solution
No response
Alternatives
No response
The text was updated successfully, but these errors were encountered: