Wednesday, 11 March 2026

Windows Autopatch will default hotpatching for eligible Intune devices in May

The period’s significant change is a Message Center plan to make Windows Autopatch hotpatch security updates the default for eligible Intune devices starting in May 2026. The remaining updates clarify existing Intune compliance-policy behavior and Configuration Manager LTSB database-support wording.

• Intune · Device enrollment

  Hotpatch updates will become the Windows Autopatch default

  Microsoft plans to enable hotpatch security updates by default from May 2026 for eligible Intune devices. Hotpatching is intended to accelerate security updates without restarts, and an opt-out setting will be available from April 2026. Devices must meet prerequisites such as enabling Virtualization-based Security.

• Intune · Troubleshooting

  Compliance-policy unassignment guidance now documents enforcement until sync

  The Intune troubleshooting page clarifies that a compliance policy unassigned from a device with an associated user remains assigned and enforced until the device syncs with the Intune service. It also points administrators to manual device sync and policy refresh guidance. This is a documentation clarification of existing behavior, not a newly announced policy change.

• Configuration Manager · General

  LTSB support wording now specifies SQL Server 2016 ESU-licensed hosting

  Configuration Manager guidance now states that Configuration Manager LTSB continues to be supported when the site database is hosted on SQL Server 2016 ESU-licensed servers, replacing the broader note that SQL Server 2016 ESU licenses would continue to be supported for Configuration Manager LTSB. The evidence indicates a documentation clarification rather than a separate support announcement.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.