Microsoft Windows Autopatch Available

Microsoft Windows Autopatch Available, supplier reports on their website. About licenses, Windows Autopatch requires that Windows 10/11 Enterprise E3 (or later) be assigned to users. Additionally, Azure Active Directory Premium and Microsoft Intune are required.

In terms of connectivity, all Windows Autopatch devices require that they connect to multiple Microsoft service endpoints from the corporate network.

Azure Active Directory Azure Active Directory must either be the source of authority for all user accounts, or user accounts must be synchronized from on-premises Active Directory using the latest supported version of Azure Active Directory Connect to enable joining the hybrid Azure Active Directory.

In terms of management, Windows Autopatch devices must be managed by Microsoft Intune. Intune must be set up as Mobile Device Management (MDM) permission or Shared Management must be enabled and enabled on the target devices

Workloads for Windows Update, Device Configuration, and Office Click-to-Run applications must be set to Pilot Intune or Intune at a minimum.

Other device management requirements include:

Devices must be owned by the company. Windows Bring Your Own Devices (BYOD) is blocked during device registration requirements checks.

Devices must be managed by Intune or Configuration Manager Co-manager. Only devices managed by Configuration Manager are not supported.

Devices must have been connected to Microsoft Intune within the past 28 days. Otherwise, devices will not be registered in Autopatch.

Devices must be connected to the Internet.

Devices must have a serial number, model, and manufacturer. Device emulators that you don’t build do not pass the requirements for the associated Intune or Clout scan.