This is a vendor roadmap post, so most of the reporting work here is sorting it out. Some features are generally available today. Others are in private preview or due next spring, and a few are simply direction. The table below separates them, and the sections after it add the requirements and caveats from Microsoft's own documentation.
The status board
| Capability | Status per Microsoft |
|---|---|
| Hotpatch updates in Windows Autopatch | Generally available |
| Approval by update type (automatic or manual) for quality updates | Generally available |
| Device risk exposure reporting (Current / Exposed / Critical) | Generally available |
| Driver update reporting in Intune and Microsoft Graph | Generally available |
| Quick machine recovery management with Autopatch | Generally available |
| Cloud rebuild | Generally available |
| Automatic Windows app updates via Intune Enterprise App Management | Private preview from November 23 |
| Maintenance windows for update actions | Microsoft says availability details will come later this month |
| OS reliability report in Intune | Private preview |
| New Windows experience controls policy type | Private preview |
| Copilot-assisted user troubleshooting | Windows Insider Program and Microsoft Frontier Program |
| Intune management for Windows Server | Preview, arriving with Windows Server 2028 |
| Autopatch for Windows Server updates | Public preview planned for next spring |
| Windows declarative management | Stated direction, not a shipped product |
Section summary: Four Autopatch items, quick machine recovery management, and cloud rebuild are GA now. Nearly everything else is in preview or still on the roadmap.
Autopatch: shorter exposure windows, more approval control
The three-day target
Microsoft's case starts with security. Its post argues that AI is speeding up vulnerability discovery for defenders and attackers alike, so the time between a patch's release and its installation matters more. Under Microsoft's updated recommendations, a device should have the latest security update within three days of release to count as "Current." To support that, the default quality-update deadline in Windows Update client policy and in Intune Windows update rings is now one day. Admins can also set separate grace periods for quality and feature updates.
Microsoft Learn's Autopatch group policy documentation defines the terms Autopatch reports use:
- Current: the quality update rollout is within three days of the update becoming available.
- Exposed: the release is between three and seven days old.
- Critical: the release is more than seven days old.
The same documentation recommends a quality-update deferral of less than three days, a deadline of 0 or 1 day, and a grace period of 1 or 2 days. Its sample ring layout goes from a Test ring with no deferral, deadline, or grace period to a Last ring with a two-day deferral, one-day deadline, and two-day grace period. The blog says Autopatch will flag settings likely to leave devices Exposed or Critical, show how many devices are affected and what to change, and warn admins when they create or edit update rings.
What the timeline looks like on a device: Microsoft's quality update end-user experience documentation walks through one case. With a two-day deferral, a one-day deadline, and a two-day grace period:
- Day 0: the update is published.
- Day 2: the deferral ends, and the device tries to download and install it.
- Day 3: the deadline arrives, installation is required, and the pending-restart period begins.
- Day 5: the grace period ends, and the device is forced to restart if it hasn't already.
So a policy can enforce installation by the deadline and still leave a restart pending until the grace period ends. Admins checking whether rings will actually produce "Current" devices need to read the dashboard with that in mind.
Hotpatch is GA, but not every device qualifies
Microsoft lists hotpatch as generally available in Autopatch and pitches it as a way to apply eligible security updates without a restart. The restart-free part depends on eligibility, which Microsoft's Autopatch FAQ spells out:
- Licensing: Windows 11 Enterprise E3, E5 or F3; Windows 11 Education A3 or A5; Microsoft 365 Business Premium; or Windows 365 Enterprise.
- OS: Windows 11, version 24H2 (build 26100.2033 or later), on the current baseline.
- CPU: x64 Intel or AMD. The FAQ also covers Arm64 support, with a CHPE-related prerequisite.
- Management: Intune with a hotpatch-enabled Windows quality update policy.
- Security: Virtualization-based Security enabled.
The FAQ plans hotpatch releases eight times a year. January, April, July and October are baseline months, and baseline updates still need a restart. Devices that don't qualify keep getting the standard monthly security updates.
The GA label is less of a change than it sounds, because hotpatch was already on by default for many tenants. Microsoft said it would turn on hotpatch security updates by default for all eligible Windows devices managed through Microsoft Intune and the Microsoft Graph API, beginning with the May 2026 Windows security update. Admins who want to opt out can use the tenant-level control BleepingComputer documented: navigate to Tenant administration > Windows Autopatch > Tenant management. Devices without VBS running are flagged as well. 4sysops reported that devices with VBS disabled will show the alert "Hotpatch – VBS not running" in Autopatch alerts.
Approvals and driver visibility
Quality update policies now let admins choose automatic or manual approval for each update type, covering monthly security, preview and out-of-band releases. Admins can also control when automatically approved updates are offered, and defer or pause at any time. Supported .NET Framework updates and quick machine recovery fixes are handled in the same policy.
Driver update reporting shows each device's status (offered, installed, failed, or on hold) along with its policy and ring, in Intune and through Microsoft Graph. One caveat comes from Microsoft's Graph documentation: once a device is enrolled in driver management, Autopatch becomes the authority for driver updates from Windows Update. That device then gets no Windows Update drivers until a deployment is created or the device is added to a driver policy with approvals. Admins who enroll devices and then forget to approve anything should expect complaints about the new docks.
Section summary: The Autopatch features are real and GA, but how much they help depends on eligibility, VBS, licensing, and ring math. Before trusting the reports, run your own deferral, deadline and grace-period numbers.
Apps, maintenance windows and servers
Automatic app updates (private preview, November 23)
Intune Enterprise App Management is gaining automatic updates for supported Windows apps, using the approval and timing controls Autopatch already has. The private preview opens November 23. Microsoft hasn't said which apps count as "supported," so this won't replace your packaging work for line-of-business software just yet.
Maintenance windows
The blog's examples are kiosks, medical devices and manufacturing systems. Admins can choose which update actions are limited to a window and set one-time or recurring windows, and Microsoft says it will share availability details later in November.
Microsoft Learn already has an Intune page describing how the feature behaves, and it answers most of the practical questions:
- Requirements: Windows 11, version 24H2 with KB5077181, build 26100.7840, or later. Devices must be enrolled in Intune, and admins need permissions to create and assign device configuration policies.
- Location in the console: Devices > Manage devices > Maintenance windows > Create policy. Under Maintenance Windows, set Workload type to Updates, turn Enable Maintenance windows On, and pick an update action.
- Update actions: "Download, install and restart," "Install and restart," or "Restart only."
- Schedules: None (one-time), Daily, Weekly, or Monthly. Monthly can be day-based (days 1–28) or week-based, for example the second Tuesday. Duration must be between 2 and 24 hours.
- Time zone: windows run on the device's local time.
The documentation also lists the limits:
- Work that starts inside the window can keep running after it closes.
- Users can still start update actions themselves.
- Expedited quality updates, expired deadlines and grace periods, device provisioning, education cart servicing, and minor-impact updates can all act outside the window.
- Deferrals still decide when an update is offered. A device with a seven-day deferral may miss the first Saturday window after a Tuesday release.
- Maintenance windows don't decide which updates are approved or offered.
- Intune's policy status confirms the policy reached the device, not that an install or restart happened inside the window.
What success looks like: In the documentation's example, an "Install and restart" weekly window starts Sundays at 23:00 for four hours. Downloads can still happen during business hours, while installation and restart work starts between 11:00 PM Sunday and 3:00 AM Monday in each device's local time. To check it, compare install and restart timestamps in Windows Update or Autopatch reporting against the schedule, adjusted for local time.
Common failure points the documentation calls out:
- A weekly schedule with no day selected.
- A one-time window whose date has already passed.
- A window too short for the selected actions.
- An update that is still deferred when the window opens.
Windows Server joins the Intune console
Microsoft says Windows Server management is coming to Intune with Windows Server 2028. Servers will be able to join Microsoft Entra, get Conditional Access and the MDM stack, and use Autopatch patching and reporting in the same console as clients. A public preview of Autopatch for Windows Server updates is planned for "later next spring."
Microsoft's separate Windows Server 2028 announcement, also published November 17, says Server 2028 is in public preview and Intune management for Windows Servers is in preview. It covers configuration, compliance, applications and updates for eligible, persistent servers. That post also says Azure and Azure Arc remain the cloud-native options for production and business-critical servers, so this isn't a single replacement console for every server yet.
Section summary: App auto-updates and server Autopatch are previews. Maintenance windows are documented but have real exceptions, so treat them as a scheduling control rather than a guarantee.
AI agents, device health and recovery
AI agent containment: Microsoft says Intune offers policy-based controls for agents running in Microsoft Execution Containers (MXC), including which files and networks they can reach. Microsoft Learn describes MXC as an open-source, policy-driven execution technology in which a host app defines the resources a workload may use. Depending on the backend, that can be a process sandbox, a separate session, or a virtualized environment, and the available restrictions vary by MXC release, backend and host. Admins shouldn't assume that "container" means VM-level isolation. Microsoft's advice to set those boundaries before agents spread is sensible, if not new.
Device health (all preview):
- OS reliability report: stop-error trends, recurring failure patterns and affected devices in Intune, alongside quality update history. Private preview.
- Windows experience controls: a new policy type whose template grows as Microsoft adds controls for user-facing Windows features. New controls arrive as "Not configured," so Windows defaults apply until an admin sets a value. Private preview. If your organization cares how Windows looks and behaves for users, schedule regular reviews, because defaults will keep applying until you act.
- Copilot user troubleshooting: available through the Windows Insider Program and Microsoft Frontier Program, not GA.
Recovery: Quick machine recovery management with Autopatch and cloud rebuild are now GA. They join point-in-time restore and existing tools such as crash recovery and rollback, cloud-initiated driver recovery, and device wipe. Microsoft's post doesn't give the licensing or prerequisites for each option, so check them per tool before you need one in an emergency.
Declarative management: the long game
The forward-looking part of the post is Windows declarative management. IT defines the desired state for supported settings, and Windows applies and maintains it whether the device is online or offline. Microsoft's stated goals:
- Fixing configuration drift locally.
- Clear visibility into intended versus actual state.
- Predictable rules for resolving conflicts.
- Less manual policy repair.
There is precedent. Microsoft Learn documents the existing Windows declared configuration protocol, which uses a desired-state model with a default refresh task every four hours that compares the device against server intent and reapplies on drift. The Ignite vision is broader than that protocol, and Microsoft says it is "building toward" it. Expect "supported settings" to be a limited list for a while.
The skeptic's corner
Not everyone is happy with faster patching. A reader comment under Microsoft's post argued that admins would install on day one if quality updates were reliable. The commenter pointed to January and March 2026 updates as painful examples and said that changing defaults doesn't fix quality. That's one person's view, but it captures the real trade-off. A one-day deadline helps when the patch is good and hurts across the fleet when it isn't.
Microsoft's answer, in effect, is the combination of approval controls, rings, pause, hotpatch, and stronger recovery tools. Independent commentary is more cautious. Tanium noted that Autopatch reporting dashboards have reported accuracy limitations: devices can show as non-compliant even when updates are installing correctly, which matters if a "Critical" label is going to drive your escalations.
What to do this week
- Audit ring math. Add up deferral, deadline and grace period for each ring and compare the total with Microsoft's three-day "Current" target.
- Check hotpatch eligibility. Confirm licensing, 24H2 builds, and VBS status, and look for "VBS not running" alerts.
- Choose approval modes by update type, especially for preview and out-of-band releases.
- Approve drivers for devices enrolled in Autopatch driver management, or they won't get Windows Update drivers.
- Test maintenance windows on a small group once your devices meet the 24H2 build requirement, and plan around the documented exceptions.
- Inventory server workloads that could move to Intune, and leave production and business-critical servers where they are for now.
- Write down agent boundaries before AI agents are deployed widely.
Microsoft's stated aim is that the effort to manage Windows shouldn't grow as fast as the estate does. For now, a fair amount of that is still in preview or roadmap form, and admins should judge the GA pieces on their own merits.
References
- Rethinking Windows management for modern IT Windows IT Pro Blog · Tue, 17 Nov 2026 18:43:35 GMT
- Windows Autopatch enables hotpatch updates by default in May 2026 4sysops.com
- Is Windows Autopatch ready for enterprise use, or does it trade too much control for convenience? tanium.com