Forum Discussion
Dev channel update to 92.0.884.2 is live
rshupak for the settings page crashing when you search, we've actually made a few fixes this week that should make their way into next week's Dev. A couple of those crashes were only on Mac, and I use Windows machines, so that's likely why I wasn't seeing them.
As for the SSO behavior, I think I may have initially misunderstood what your problem was. The setting to "Allow single sign-on for work or school sites using this profile" actually forces SSO using your AAD account when it's turned on since AAD is the same as a work/school account (and thus MSA equals personal). So, since it sounds like that setting is working as intended, I think the problem is maybe that this website support both kinds of logins, and thus the problem is with the site? If so, that's feedback you should definitely give to the site.
The settings pages were fixed last week. The problem I reported was on Windows not Mac. It depended on your specific cookie settings to fail which I why you did not see it. I didn't see it on PCs which had different settings. The problem settings are obviously ones that do not roam though Edge doesn't identify what does and does not roam so that doesn't help anyone.
In regard to SSO, let me remind you of the text of the setting
Allow single sign-on for work or school sites using this profile
If this setting is on, you’ll be able to access work or school sites on this device using this profile. If this setting is off, you’ll need to switch to your work or school account profile to use single sign-on.
Note that it describes enabling or disabling AAD SSO. It does not make any mention of switching from MSA SSO to AAD only SSO. If the latter is intended, the text should be updated to be accurate which it is not.
I need to find a PC with the old Edge but I am pretty sure that the old Edge supported SSO for MSA and AAD simultaneously. I can't see it worked well on all sites because it likely didn't work on a site like this one which supports both. It appears that the identity team does not provide any mechanism for sites supporting both MSA and AAD to work well but maybe it does and no Microsoft site has implemented this.
It does appear from https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-js-prompt-behavior that clients can force an account selection always while the default is not to prompt when there is only a single AAD account authenticated. There is no mention of MSA on this page though MSAL and the v2.0 endpoint do explicitly note support for MSA elsewhere. Maybe the endpoint itself isn't functional enough to handle this correctly.