Today, Microsoft made Edge version 88.0.705.50 generally available to the Edge stable channel. Consequently, Edge 88 will be rolling out to devices in the next few days.
What’s New in Identity
Edge version 88 provides these new features in terms of identity:
Single Sign-on on Windows 7 and Windows 8.1
When using Microsoft Edge on Windows 10, people enjoy Single Sign On (SSO) access to their Azure Active Directory (Azure AD) accounts and Microsoft Account (MSA). These results in lesser prompts, a more pleasant browsing experience and helps to eliminate prompt-fatigue.
This functionality is now also available on down-level Windows. A person signed in on Microsoft Edge on down-level Microsoft Windows (7, 8.1) will now get automatically signed into websites that are configured to allow single sign on with Work and Microsoft accounts, like bing.com, office.com, msn.com and outlook.com.
You may have to sign out and then sign back in if they'd signed into Microsoft Edge in a version prior to Microsoft Edge 88 to leverage this feature.
Microsoft Edge version 88 introduces a built-in strong password generator that people can use when signing up for a new account or when changing an existing password.
You can now also edit your saved passwords directly in Microsoft Edge Settings. Any time a password has been updated outside of Microsoft Edge, it’s easy to replace the saved older password with the new one by editing the saved entry in Settings.
Alerts are generated if a password is found in an online leak. When any of your passwords saved to the browser matches with those seen in sets of leaked credentials, Microsoft Edge will notify you and prompt you to update your password.
Passwords are checked against a repository of known-breached credentials and sends an alert if a match is found. To ensure security and privacy, passwords are hashed and encrypted when they're checked against the database of leaked credentials.
Password Monitor scans for matches on your behalf and is on by default.
Group Policy settings changes
Microsoft Edge now offers the Allow Basic authentication for HTTP Group Policy setting. If you enable this policy or leave it unset, Basic authentication challenges received over non-secure HTTP will be allowed. If you disable this policy, HTTP requests from the Basic authentication scheme are blocked, and only HTTPS is allowed. This Group Policy setting corresponds to the BasicAuthOverHttpEnabled DWORD Registry setting.
The Enable Proactive Authentication Group Policy setting is being deprecated in version 88. It will be removed in Microsoft Edge version 91. Proactive Authentication is turned on, by default and configures Microsoft Edge to try to seamlessly authenticate to websites and services using the account which is signed-in to the browser. If you disable this policy, Microsoft Edge does not try to authenticate with websites or services using single sign-on (SSO). Authenticated experiences like the Enterprise New Tab Page (NTP) will not work.