Forum Discussion
Dev channel update to 92.0.884.2 is live
rshupak oh and also, for the SSO issue, can you try clearing your cookies and seeing if that helps? If you're signed into Edge with your MSA, you're right that it's what should be used for SSO instead of your AAD account, which makes me think that maybe your AAD credentials are just saved and being used, and so getting rid of them may help.
When AAD SSO is disabled, Edge sends the following, which I elided, on the first request to https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=09213cdc-9f30-4e82-aa6f-9b6...
Cookie: ESTSAUTHLIGHT=+00000000-0000-0000-0000-000000000000; ESTSSC=00; esctx=...; x-ms-gateway-slice=estsfd; stsservicecookie=estsfd; brcap=0; ESTSAUTHPERSISTENT=...; ESTSAUTH=...; ch=...; buid=...; fpc=...; clrc={...]}
When AAD SSO is enabled, the Cookie header is not sent but the following is
x-ms-RefreshTokenCredential: ey...n0.ey...d4
It seems that with one or the other, there is no way this can work well for sites that support both AAD AND MSA since they are not provided with both credentials in order to present the user with a choice. As implemented right now, I need to change the Edge setting off to allow signing in with the MSA at all since otherwise the AAD account is selected. Some sites, such as this one, don't even allow a choice after signing out. In contrast, Edge will select AAD with no user choice on https://portal.azure.com or https://www.office.com but after being signed in you can sign out and then are presented with a choice immediately (portal.azure.com) or for the next sign in (www.office.com)