How updates are handled in Microsoft Managed Desktop
Microsoft Managed Desktop connects all devices to a modern cloud-based infrastructure.
Keeping Windows, Office, drivers, firmware, and Microsoft Store for Business applications up to date is a balance of speed and stability. We use update groups to ensure operating system updates and policies are rolled out in a safe manner. For more information, see the video Microsoft Managed Desktop Change and Release Process.
Updates released by Microsoft are cumulative and are categorized as quality or feature updates. For more information, see Windows Update for Business: Update types.
Microsoft Managed Desktop uses four Azure AD groups to manage updates:
|Test||Used to validate Microsoft Managed Desktop policy changes, operating system updates, feature updates, and other changes pushed to the Azure AD organization ("tenant"). The Test group is:
|First||Contains early software adopters and devices that could be subject to pre-release updates.
Devices in this group might experience outages if there are scenarios that weren't covered during testing in the test ring.
|Fast||Prioritizes speed over stability. The Fast group is:
|Broad||This group is the last group to have feature and quality updates available.
The Broad group contains most of users in the Azure AD organization, and therefore favors stability over speed in deployment. Testing of apps should be done with this group because the environment is the most stable.
Moving devices between update groups
You might want some devices to receive updates last and others that you want to go first. To move these devices into the appropriate update group, see Assign devices to a deployment group.
For more information on roles and responsibilities within these deployment groups, see Microsoft Managed Desktop Roles and responsibilities
Using Microsoft Managed Desktop update groups
There are parts of the service that you manage, like app deployment, where it might be necessary to target all managed devices.
Below describes how update deployment works.
|Step 1||Microsoft Managed Desktop deploys a new feature or quality update according to the schedule specified in the following table.|
|Step 2||During deployment, Microsoft Managed Desktop monitors for signs of failure, or disruption based on diagnostic data and the user support system. If any are detected, we immediately pause the deployment to all current and future groups.
For example, if an issue is discovered while deploying a quality update to the First group, then update deployments to First, Fast, and Broad groups will be paused until the issue is mitigated.
You can report compatibility issues by filing a ticket in the Microsoft Managed Desktop Admin portal.
Feature and quality updates are paused independently. The pause is in effect for 35 days by default. However, it can be reduced or extended depending on whether the issue is mitigated.
|Step 3||Once the groups are unpaused, deployment resumes according to the schedule in the table.|
|Step 4||Users are empowered to respond to restart notifications for a set period. This period is known as the deadline, and it's measured from the time the update is offered to the device.
During this time, the device will only automatically restart outside active hours. After this period expires, the deadline has been reached and the device will restart at the next available opportunity, regardless of active hours.
The deadline for quality updates is three days; for feature updates it's five days.
This deployment process applies to both feature and quality updates, though the timeline varies for each.
Update deployment settings listed below:
|Quality updates for operating system||Zero days||One day||Six days||Nine days|
|Feature updates for operating system||Zero days||30 days||60 days||90 days|
|Drivers/firmware||Follows the schedule for quality updates.||Follows the schedule for quality updates.||Follows the schedule for quality updates.||Follows the schedule for quality updates.|
|Anti-virus definition||Updated with each scan.||Updated with each scan.||Updated with each scan.||Updated with each scan.|
|Microsoft 365 Apps for Enterprise||Learn more||Learn more||Learn more||Learn more|
|Microsoft Edge||Learn more||Learn more||Learn more||Learn more|
|Microsoft Teams||Learn more||Learn more||Learn more||Learn more|
These deferral periods are intentionally designed to ensure high security and performance standards for all users.
Based on data gathered across all Microsoft Managed Desktop devices and the varying scope and impact of updates, Microsoft Managed Desktop reserves flexibility to modify the length of the above deferral periods for any and all deployment groups on an ad hoc basis.
Microsoft Managed Desktop conducts an independent assessment of each Windows feature release to evaluate its necessity and usefulness to its managed tenants. Consequently, Microsoft Managed Desktop might or might not deploy all Windows feature updates.
Windows Insider Program
Microsoft Managed Desktop doesn't support devices that are part of the Windows Insider program.
The Windows Insider program is used to validate pre-release Windows software. It's intended for devices that aren't mission critical. While it's an important Microsoft initiative, it's not intended for broad deployment in production environments.
Any devices found with Windows Insider builds might be put into the Test group. These devices will be exempt from update service level agreements and user support from Microsoft Managed Desktop.
We use Delivery Optimization for all operating system and driver updates. Delivery Optimization minimizes the download size from the Windows Update service by seeking updates from peers within the corporate network.