Get current and stay current with Windows Autopatch

nlmitchell - thank you for the comment:

As an organisation we moved away from a ringed testing approach for patching when we transitioned the 'patching workload' from MECM (very manual and time consuming) to Intune\WUfB (very automated). Something which proved a big change in the way that we worked and took a lot of persuading at many levels 🙂 Windows Autopatch would seem a step back for us personally, but I can certainly see use cases for it in certain scenarios.

We will continue to patch using WUfB driven by Intune Policies as this is a real hands off approach and also enables us to effectively manage devices on multiple channels, i.e. Insider, Retail, DEV, Beta

Autopatch uses WUfB to update devices. We build out the rings and maintain them. A customer does not have to do anything with ring setup, thus the deployment of updates within a customer environment is automatic. Autopatch has a team of "IT admins" that help when/if there is a problem related to an update.