Blog
Windows Autopatch: how it works and where additional management fits
Learn what Windows Autopatch covers, where Azure Virtual Desktop differs, and how management supports apps, scheduling, and audit reporting.
Nerdio is Microsoft’s 2026 Americas ISV Partner of the Year Get the story
Blog
Learn what Windows Autopatch covers, where Azure Virtual Desktop differs, and how management supports apps, scheduling, and audit reporting.
Table of Contents
On the second Tuesday of each month, Microsoft releases its scheduled security and quality updates for Windows. Within days, Autopatch rings have moved thousands of laptops and Cloud PCs to the new build, while pooled multi-session Azure Virtual Desktop hosts still show Not ready.
Microsoft's automated patching service delivers Windows and Microsoft 365 Apps updates to Microsoft Intune-managed devices across Windows Cloud (the umbrella term for Windows 365 and Azure Virtual Desktop). Coverage stops at pooled multi-session hosts and third-party applications, and reporting stops at device state when auditors want patch history and third-party status.
This guide is for platform owners and IT operations leads deciding what to hand to Autopatch and what needs management above Intune.
Many enterprises use Windows 365 and Azure Virtual Desktop together for different workload requirements. Autopatch runs from the Intune admin center and covers a defined set of Microsoft products, leaves specific systems out, and hands third-party applications to a separate workflow.
Windows Autopatch automates updates across the following Microsoft products:
In September 2024 Microsoft folded the Windows Update for Business deployment service into Autopatch. Microsoft's stated targets are to keep at least 95% of Up to Date devices on the latest quality update and at least 90% of eligible devices on a supported Monthly Enterprise Channel build of Microsoft 365 Apps.
Feature activation ended in April 2025, which opened Autopatch to Microsoft 365 Business Premium and Education A3 or A5.
Autopatch does not cover the following systems and applications:
Each of these gaps points to a workflow that has to sit alongside Autopatch, and the largest of those gaps is third-party application patching.
Intune has no universal policy for updating non-Microsoft apps, which makes Windows patch management a two-track job for many estates. Enterprise App Management (EAM) auto-update, generally available in July 2026, extends coverage to catalog apps with a required assignment.
EAM auto-update supports no custom installation scripts or detection rules and requires the Intune Suite or Microsoft 365 E5. Nerdio Manager for Enterprise deploys applications outside that catalog through Unified Application Management.
Coverage is the first boundary you hit. The second is how much say you get over when the covered updates land.
Admins control ring design and licensing prerequisites. Autopatch controls sequencing through rings and restart cadence through hotpatch, and the sections below cover how each works and where the trade-offs land.
Autopatch's ring model automates sequencing and takes the calendar out of your hands. An Autopatch group bundles Entra ID groups with the Windows, driver, and Microsoft 365 Apps update policies. That setup standardizes policy and device placement before rollout begins. The default structure progresses from Test through First and Fast to Broad, and Microsoft does not let administrators remove the Test and Last rings. When you add a device, Autopatch runs readiness checks and then places it in a single ring.
Operationally, that makes ring design the main change-control decision, and device placement needs to be set correctly before the rollout starts.
With Windows Server Update Services deprecated in September 2024, Microsoft's stated path is Autopatch for clients and Azure Update Manager for servers.
A Microsoft Q&A answer says administrators cannot control when Microsoft pushes updates to devices or moves them from one ring to another. Autopatch also shifts Sunday deadlines to Monday. Switching a device to ScheduledInstall removes the restart deadline, and such devices no longer count toward the service level objective.
You gain flexibility on restart timing, and the device drops out of the metric Autopatch uses to measure update performance.
Two changes soften the trade. Maintenance windows, which Microsoft announced for Q1 2026, let you set restart windows down to the hour. Microsoft's Intune in-development notes say admins will be able to approve, auto-approve, reject, and schedule quality updates by update type. The capability will roll out from September through October 2026.
Restart timing is the other half of the scheduling problem, and hotpatch takes it off the table for eight months of the year.
Hotpatch installs monthly security updates without a restart, and Autopatch turned it on by default with the May 2026 Windows security update. Microsoft's Tech Community post states that applying fixes without waiting for a restart "can get organizations to 90% compliance in half the time."
Hotpatch eligibility requires all of the following:
If any one of these is missing, the device falls back to restart-required updates. Four baseline months a year also still require a restart, so the change calendar needs to account for those quarters even on eligible devices.
Hotpatch and rings both rely on in-place updates to persistent devices. That model fits laptops and Cloud PCs, and Microsoft's support guidance routes pooled multi-session hosts to a different track entirely.
Autopatch support splits by workload. Microsoft's own update management methodologies guidance draws the line at pooled multi-session hosts, which it steers toward image-based updates instead.
The table below shows where each Windows Cloud workload lands, whether Autopatch supports it, and the update path Microsoft recommends.
| Workload | Autopatch support | Path Microsoft recommends |
| Windows 365 Enterprise Cloud PCs | Full feature set. Microsoft's FAQ states that its features do not differ from those on a physical device | Autopatch groups and rings |
| Windows 365 Flex (Shared mode) | No Autopatch option in the provisioning policy UI, though Microsoft says devices can still enroll and receive update policies | Intune update policies, assigned directly |
| Azure Virtual Desktop personal single-session hosts | Register like physical devices. Azure Virtual Desktop-specific issues go to Azure support | Autopatch groups and rings |
| Azure Virtual Desktop pooled multi-session hosts | "Not recommended" in Microsoft's update management methodologies table (previously cited). The registration documentation says to exclude them | Session Host Update or Azure Compute Gallery |
Two constraints push pooled multi-session hosts to a different track. Intune's documentation for Azure Virtual Desktop multi-session states that "Windows update rings policies aren't currently supported," and those rings underpin Autopatch. Multi-session host pools also do not support in-place upgrades between Windows versions.
Microsoft's recommended path for pooled multi-session hosts is the image lifecycle. The session host update documentation describes managing updates "within the core source image, rather than distributing and installing updates to each session host individually." Session Host Update, generally available July 9, 2026, rolls configuration changes to existing hosts in batches. It "deallocates or deletes the existing virtual machines and creates new ones."
Native tooling gives you the reimage mechanism, and scheduling and standardizing that monthly cycle across multi-session host pools is still yours to orchestrate.
Nerdio Manager turns it into a scheduled workflow. Rings handle persistent devices, the image cycle handles pooled multi-session hosts, and both tracks require evidence that the patch landed, which creates additional reporting requirements.
Autopatch reporting covers device state. Audit evidence that combines patch history and third-party patch status requires separate reporting work, and tenant scope adds another layer on top of that for teams managing more than one customer.
The reports live in the Intune admin center, and the quality update status report refreshes every four hours. It gives you per-device state (Up to date, In progress, Not up to date), target and installed release, Autopatch group, and hotpatch status, with CSV export.
The management status report singles out devices in no cloud policy at all, the group that Microsoft says "may have fallen through the cracks." Update Readiness, generally available per Microsoft's March 2026 post, flags devices as At Risk ahead of deployment failures.
The gap becomes clear when a governance, risk, and compliance (GRC) lead asks for evidence rather than status. The 95% target is a stated aim, and it is not described as a contractual SLA or remediation commitment if it is missed.
Intune reporting has its own quirk here. The Security Update Status Dashboard reflects each device's update currency, and rollout rings and staged deployment strategies aren't modeled directly in the dashboard state, so devices in a healthy phased rollout can display as Exposed.
Beyond how the reports display data, Autopatch itself constrains where that data can be pulled from and how far it reaches across tenants. Three limits show up in audit and multi-tenant scenarios:
A management layer above Intune can cover the remaining reporting and tenant-by-tenant verification work.
Nerdio Manager adds scheduled image and application workflows to Intune from within your Microsoft tenant. Reporting workflows are also included. Autopatch remains the update engine for managed laptops and Cloud PCs, which keep their rings.
For Windows 365 Cloud PCs, Nerdio Manager extends Intune management with application workflows and reporting. It also adds policy backup and restore.
Desktop orchestration in Nerdio Manager schedules the image lifecycle Microsoft recommends for multi-session hosts. It patches the golden image and seals it with an automated Sysprep. Desktop orchestration supports custom images and Azure Compute Gallery images. It also supports Microsoft Marketplace images. Scripted Actions supply the automation steps inside those image and host workflows, including built-in scripts for automated Windows patching tied to "Patch Tuesday."
Teams can manage Azure Virtual Desktop through the Azure Portal, PowerShell, and Microsoft Intune. Independent testing by Dr. Benny Tritsch measured updating a custom image at 146 clicks and 5 minutes 9 seconds in native Azure Virtual Desktop tooling versus 13 clicks and 37 seconds in Nerdio Manager. Fewer manual steps mean fewer places to mistype a version or skip a host.
Howell Technology reported monthly security patching dropping from 8 hours to 2 hours per customer after moving patching and image management into Nerdio Manager.
Unified Application Management pulls WinGet (public and private repositories) and Intune app repositories into one catalog. It then deploys by policy across Windows 365 Cloud PCs and Intune-managed endpoints, as well as Azure Virtual Desktop hosts.
Nerdio measures delivery to a Windows 365 endpoint at about 30 seconds, versus native Intune delivery that can take up to 3 hours because Intune does not poll continuously. Unified Application Management reaches app types outside the Enterprise App Management catalog's auto-update path.
Intune Insights delivers scheduled, customizable reports covering compliance and configuration. The reports also cover application and patch status. Nerdio pulls Intune data into a unified console with reporting on application and patch status. Nerdio Manager also backs up and restores Intune policies, so a deleted policy becomes a restore instead of a rebuild.
The same console manages these image lifecycle and reporting workflows alongside the rest of your Windows Cloud estate.
The practical split follows Microsoft's own support matrix: laptops, Windows 365 Cloud PCs, and personal Azure Virtual Desktop hosts go into Autopatch groups. Where teams meet the 24H2 and license prerequisites, they can turn hotpatch on and put the four baseline restart months in the change calendar.
Handing the covered workloads to Autopatch takes the monthly Patch Tuesday cycle off your team's plate for those devices. Pooled multi-session hosts and third-party applications still require complementary workflows.
If multi-session hosts remain "Not ready" or third-party app tracking and last quarter's patch evidence still sit outside Autopatch, Nerdio Manager adds the complementary workflows above Intune.
Get a demo to see how Nerdio Manager works across your Windows 365, Intune, and Azure Virtual Desktop environment, or try it free in your Azure tenant.
Autopatch is built on Windows Update for Business rings, and Microsoft's guidance is that you typically should not assign custom update rings to Autopatch-managed devices, since conflicting policies are a documented source of failures. Update ring policies remain the right tool for the devices Autopatch will not take, Windows LTSC among them.
Windows Autopatch requires Microsoft 365 Business Premium, Windows 10/11 Education A3 or A5, or Windows 10/11 Enterprise E3 or E5 (including via Microsoft 365 F3, E3, or E5) or E3/E5 VDA, plus Intune Plan 1 and Entra ID P1 or P2. Business Premium and A3+ customers gained access in April 2025, when Microsoft removed feature activation. Hotpatch adds its own list, which includes Windows 365 Enterprise.
Yes. Configuration Manager must assign both the Windows Update policies workload and the Device configuration workload to Intune or Pilot Intune in co-management. When administrators never shifted the Windows Update workload, devices show up as "Prerequisites failed," and Windows Server Update Services (WSUS) can disrupt Autopatch release schedules when it still routes updates.
Microsoft does not recommend Windows Autopatch for pooled Azure Virtual Desktop multi-session hosts. GCC High and DoD tenants are not supported yet, and scheduling control is limited.
Learn more about Nerdio Manager