Achieving update harmony through unified update management

Windows Autopatch requires an E3+ or F3 license. To stay up to date with the latest requirements, see https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites?tabs=windows-enterprise-e3-f3-entitlements%2Cbusiness-premium-a3-intune-permissions#licenses-and-entitlements.

This is a scenario we're investigating. If you're interested in shaping the future of Autopatch, consider joining the https://aka.ms/JoinCCP for early preview opportunities.

Here are two resources that may help identify what’s preventing those remaining devices from upgrading:

1. Check if anything is blocking Windows Update from offering the update: This guide can help you determine if there are policies, settings, or other factors preventing Windows Update from offering the update to your devices. See: https://learn.microsoft.com/en-us/troubleshoot/windows-client/installing-updates-features-roles/troubleshoot-windows-update-issues#the-device-isnt-receiving-an-update-that-you-deployed
2. Review compatibility reports: These reports can help identify any hardware or compatibility issues preventing the update. See: https://learn.microsoft.com/en-us/mem/intune/protect/windows-update-compatibility-reports

If neither of these resources resolve the issue, I recommend opening a support request so we can take a closer look.

1. Windows Autopatch is a cloud-based solution that requires Internet connectivity. Can you help us better understand your specific requirements and where Delivery Optimization (see below) might not meet your needs?
2. Our solution for this is Delivery Optimization, which allows devices to share Windows Update content with peers on the same local network. This reduces the need to download updates individually from Microsoft, helping to conserve bandwidth and improve update efficiency.  To learn more, see https://learn.microsoft.com/en-us/windows/deployment/do/waas-delivery-optimization

Thanks M_Bolton, we're looking at this scenario. If you want to join us on the journey, join the Microsoft Management Customer Connection Program for early preview opportunities.

There are subtle differences between Active Hours and Maintenance Windows. You can learn more about Active Hours here: https://learn.microsoft.com/en-us/windows/deployment/update/waas-restart.

We're currently investigating how Maintenance Windows could be implemented in Autopatch.

Could you please help explain the scenario a bit more, are you looking for scheduling automatic deployments on device groups and not leverage the deferral days configuration?

Thank you for your feedback and interest in the features, we are currently investigating the request. 

https://intune.microsoft.com 

Under Devices>Windows Updates

ucbryanweaver  -- Try

https://intune.microsoft.com (with the correct licenses and subscriptions). It should be enabled and found in Tenant Administration