Site icon

What’s new in Windows Autopatch: August 2023

This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .

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 or read on for a recap of all the recent Windows Autopatch additions based on the feedback we've received from you, our customers!

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:

Bookmark the full guide and share your suggestions for improvements using the Feedback option.

Screenshot of the Feedback link on the Windows Autopatch deployment guide web page.

More control when pausing updates

Need to pause a quality update? No problem! In Windows Autopatch, you can now:

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.

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.

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.

Screenshot of a readiness report for devices 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:

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.

Exit mobile version