The enhancements to Windows Autopatch continue! Check out the latest additions, which include a comprehensive new guide to deploying the service. We cover scenarios like migrating from Configuration Manager or Windows Update for Business and, by popular demand, best practices for Autopatch groups. Dive right into it at aka.ms/AutopatchGuide or read on for a recap of all the recent Windows Autopatch additions based on the feedback we've received from you, our customers!
- Enhanced quality update pause controls for groups
- Self-serve device deregistration (and re-enrollment)
- Registry conflict detection
- New videos explaining the benefits of Windows Autopatch
Introducing the Windows Autopatch deployment guide
We have heard your requests loud and clear. You want a single technical resource to explain the how and why of deploying Windows Autopatch. That's why our learning and engineering teams have collaborated to create a brand new Windows Autopatch deployment guide.
Highlights include:
- Step-by-step information to help you prepare for Windows Autopatch
- Group creation strategy
- Business case and stakeholder communications
- Migration from Configuration Manager or Windows Update for Business
Bookmark the full guide and share your suggestions for improvements using the Feedback option.
More control when pausing updates
Need to pause a quality update? No problem! In Windows Autopatch, you can now:
- Initiate a pause, or resume updates, for multiple or individual Autopatch groups
- Initiate a pause, or resume updates, at the ring level
- See a list of affected deployment rings before you confirm a pause
- Resume an update paused by the Windows Autopatch service
For all the details on the new pause capabilities, see Pause and resume a release.
Easily remove a device from Windows Autopatch management
For those that would like to stop managing a specific device within the Windows Autopatch service, we've now provided self-serve options to do so.
- In the Registered tab of the Windows Autopatch Devices blade, locate the Device actions drop-down menu, and select Exclude device.
Screenshot of device actions in the Devices blade of the Windows Autopatch interface.
Note: Excluding a device will not remove it from the Azure AD group used for registration, but rather will move the device to the Not registered tab in the Devices blade.
- You can also now re-enroll a device that has been excluded or removed from Windows Autopatch management without opening a service request. Simply locate the Not registered tab in the Devices blade and check the box next to the desired device.
Screenshot of the Not registered tab in the Devices blade of the Windows Autopatch interface.
- Select Restore excluded device from the Device actions menu, and the device will be re-registered to the service.
Screenshot of the Restore excluded device action for Not registered devices in the Windows Autopatch interface.
For complete documentation on this new capability, see Exclude a device.
Conflict detection during device registration
When you add new devices to Windows Autopatch, a readiness check takes place. This readiness check now includes a search for registry settings that could prevent devices from receiving Windows updates or working correctly with the Autopatch service. When registry conflicts are detected, devices (and available suggestions for remediation) will be listed in the Not ready tab of the Windows Autopatch Devices blade.
New videos highlight the benefits of Windows Autopatch
Deciding whether to invest in or adopt new technology inevitably involves multiple stakeholders and decision makers, each with differing objectives. To help you make a case in your organization for the adoption of Autopatch, we've created a series of new videos. They are designed to be short, sweet, and directed at the needs of decision makers and IT pros:
- For decision makers: Improve security and productivity with Windows Autopatch
- For the security-minded: Improve cyber hygiene with Windows Autopatch
- For the IT pro: Unlock your productivity with Windows Autopatch
- Thinking about Windows 365 Cloud PCs? The benefits of Windows Autopatch and Windows 365 together
- For IT pros and decision makers: Windows Autopatch - we're patch experts
Make Windows Autopatch work for you
Service improvements and new features are often inspired by your comments and requests. To add your voice to the discussion, visit the Windows Autopatch Tech Community.
Stay informed. For the latest updates on new releases, tools, and resources, stay tuned to this blog and follow us @MSWindowsITPro and @MSIntune on Twitter/X.