SSO and Profiles broken after recent update
After a recent Update I can't login to our intranet sites anymore! When I first used Chromium Edge I setup a profile with my Microsoft account, to sync all settings. I used Single Sign on with my Domain user to sign in to our intranet sites. This worked until some days ago, when I suddenly couldn't login to our intranet sites anymore! At the same time a new profile appeared, with my domain account. - But this profile cannot be synced! - When I use this domain profile, I can login to our intranet sites. But of course, all my browser settings are gone, if I do so. When I use "Guest" profile, instead of single sign on, I get asked for my username and password to sign in. But with my Microsoft Account profile, I don't get asked for credentials, but instead the sign on (I assume, the browser tries to login with my Microsoft account instead) is rejected. This is a big issue, until now I was able to use my Microsoft Account for syncing and at the same time my Active Directory Domain Account for SSO in the intranet. The new Update broke this. Has anyone else similar problems or maybe a viable solution? PS: I tried using a guest account to login, then added my Microsoft account to Login, so my guest account got updated. The save credentials (i entered manually) are still there, but as soon as my account is connected with Microsoft Account, the saved credentials are not used anymore, instead the sign in is immediately rejected. Sincerely Martin
Microsoft Edge Dev - Azure Active Directory Seamless Single Sign-On
Microsoft Edge Dev build Version 76.0.182.6. We have implemented Azure Active Directory Seamless Single Sign-on (https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sso) and confirmed that it works both in Google Chrome (build 75.0.3770.90) and Internet Explorer v11 on Windows 10 v1903 build 18362.175. On Chrome and IE when accessing an Office 365 URL, after entering the username a redirect occurs that shows that the account is trying to sign-in without the need for the password to be entered before being prompted to confirm sign-in using MFA. On Microsoft Edge Dev this does not occur and the normal login procedure is followed of username => password => MFA. Is there a setting in the browser that needs to be enabled in the current build for the SSO to work or will it be a feature added to a later build? Thanks.