Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
With the Microsoft Edge 83 release, gradual rollouts of major updates to Microsoft Edge Stable channel are done over the span of a few days. This progressive rollout allows us to monitor upgrades and safely update the browser across the organization.
Note
This applies to Microsoft Edge Stable channel version 83 or later.
Why do we need progressive rollout?
By monitoring the health of our updates closely and rolling out the updates over the course of several days, we can limit the effect of issues that might occur with the new update. With Microsoft Edge release 83, Progressive Rollouts are enabled for all Windows 7, Windows 8 & 8.1, and Windows 10/11 versions of Microsoft Edge. Starting with the January 17 release (version 132.0.2957.115), the Stable channel of Microsoft Edge on macOS also follows the progressive rollout process, aligning with the Windows release strategy.
How will the updates work?
Each installation of Microsoft Edge is assigned as an upgrade value. When we start rolling out incrementally, the update is done when the value on your device falls within the upgrade value range. As the rollout progresses (within a few days), all users the update. Browser updates with critical security fixes have a faster rollout cadence than updates that don't have critical security fixes. Update is done to ensure quick protection from vulnerabilities.
How does this affect enterprises?
Microsoft Edge artifacts are distributed to enterprises using multiple mechanisms such as Microsoft Intune, Windows Server Update Service (WSUS), and Configuration Manager. These deployment tools behave differently with respect to Progressive Rollout:
- Enterprises that manage distribution via Microsoft Intune are registered for automatic updates. Progressive Rollout is used, and all the users see an update in a few days.
- Enterprises that manage distribution through WSUS (Windows Server Update Services) or Configuration Manager aren't registered for autoupdates. Administrators manage and apply the updates that will be available from the start. Progressive Rollout doesn't affect this process.
Share your valuable feedback through user voice, the in-application feedback button, or below in the comments if you have any concerns or questions.