Microsoft Edge 94 is now available in the stable channel. This version marks the transition from a 6-week to a 4-week release cycle. Microsoft explained in March that this faster release cycle will bring more intensive new features to Edge users, but the company also provides enterprise users with a new 8-week “extended stable” release cycle option, every two Perform security updates once a week.
To select the 8-week extended stable release cycle option, IT administrators will need to use Group Policy or select new channel options through Intune in Microsoft Endpoint Manager. The company explained that the 8-week extended stable release cycle option for the Microsoft Edge stable version will provide cumulative feature updates consistent with the even-numbered version from Microsoft Edge 94; any feature updates in the odd-numbered version will be packaged and used as subsequent even-numbered versions. Part of it is provided.
Microsoft Edge 94 is a fairly small version with security improvements and a new accessibility settings page. You can find a list of improvements below:
- Improvements to the default behavior of opening MHTML files. If IE mode is enabled, the MHTML file will continue to open in IE mode unless the MHTML file was saved from Microsoft Edge (using the Save As or Save Page As option in Microsoft Edge). If the file was saved from Microsoft Edge, it will now open in Microsoft Edge. This change will fix the rendering issues that occur when MHTML files saved from Microsoft Edge are opened in IE mode.
- Limit private network requests to a safe range. To access resources on the local (intranet) network from pages on the Internet, these pages need to be delivered via HTTPS. This change occurred in the Chromium project, and Microsoft Edge is based on this project. For more information, please visit the Chrome platform status entry. Two compatibility strategies are available to support situations where compatibility with non-secure pages needs to be preserved. InsecurePrivateNetworkRequestAllowed and InsecurePrivateNetworkRequestAllowedForUrls.
- Block the download of mixed content. The secure page will only download files hosted on other secure pages. If you start from the secure page, downloads hosted on non-secure (non-HTTPS) pages will be blocked. This change occurred in the Chromium project, which Microsoft Edge is based on. For more information, please visit the Google Security Blog entry.
- Enable implicit login for internal corporate accounts. By enabling the OnlyOnPremisesImplicitSigninEnabled policy, only internal corporate accounts will be enabled for implicit login. Microsoft Edge will not try to implicitly log in to MSA or AAD accounts. The upgrade from an internal company account to an AAD account will also be stopped.
- New accessibility settings page. Edge now centralizes accessibility-related settings on one page. You can find the new edge://settings/accessibility page under the main settings list. Here, you can find settings to make web pages larger, to display high-visibility outlines around the focus area, and other settings that can help improve your web browsing experience. Future versions of Microsoft Edge will continue to add new settings here.
- Since the Microsoft Edge update now follows the Chromium update, the Google Chrome browser has also switched to a four-week release cycle from Chrome 94, which was released earlier this week. Just like Microsoft, Google has also begun to provide new extension channel options for its Chrome browser on Windows and macOS.
