Windows management has always had a straightforward goal: keep people productive while keeping devices secure, current, and resilient. But the environment has changed. IT teams are managing more apps, more types of devices and workloads, and now AI agents. Adding another tool or process doesn't solve that challenge. It just gives IT one more thing to manage.
Security updates add urgency to the equation. AI is changing the pace of vulnerability discovery for defenders and attackers alike. As that pace increases, reducing the time it takes to get available security updates onto devices becomes even more important. But moving faster can't mean giving up the testing, visibility, and control IT needs to manage change across the environment. The challenge is, therefore, building an approach that can reduce that exposure window while managing change responsibly.
That's the direction we're taking with Windows management. At Microsoft Ignite, we're sharing new capabilities that automate more routine work, give IT clearer control where decisions matter, and bring more of the environment into a consistent management approach.
More control and visibility with Windows Autopatch
Keeping devices current is one of the most important things IT can do to reduce risk. But moving faster only works when IT has the visibility and control to understand what's being deployed and how it's progressing. We're continuing to build Windows Autopatch around both needs: helping organizations reduce the time it takes to get updates onto devices while keeping IT in control of the decisions that matter.
Want to use the latest capabilities to refine your approval approach, help reduce exposure windows, and bring driver status into your update decisions? Start here:
-
Use hotpatch updates to apply eligible security updates without requiring a restart.
-
Review your update approvals. Decide which updates can be deployed automatically, and which need explicit team approval. Quality update policies let you set approval method (automatic or manual) by update type, including monthly security, preview, and out-of-band updates. You can control when automatically approved updates are offered to devices. You can defer updates or pause at any time. The same policy experience covers supported .NET Framework and quick machine recovery fixes, helping you manage approvals and rollout timing in one place.
-
Reassess your exposure window. Deferral, deadline, and grace period settings add up to determine how quickly Windows quality (security) updates reach your devices. Under our updated recommendations, devices should be on the latest security update within three days of release to be considered Current. To help you get there, the default quality update deadline in Windows Update client policy and in Windows update rings within Microsoft Intune is now one day. You can also set separate grace periods for quality and feature updates. Curious which settings could leave devices Exposed or Critical? Windows Autopatch flags them in its reports, showing how many devices are affected, and what to change. It will also provide warnings when you create or edit update rings.
-
See where drivers might need attention. Driver update reporting shows each device's status, offered, installed, failed, or on hold, with policy and ring context, in Intune and through Microsoft Graph. Use this visibility to quickly identify where deployment needs attention rather than treating driver updates as a separate troubleshooting exercise.
Hotpatch updates, granular control approval for quality updates, device risk exposure, and driver update reporting are generally available in Windows Autopatch today.
A consistent approach to updating your whole estate
Update management becomes harder when every part of the environment requires a different process. We're working to simplify Windows management and reduce IT overhead through a consistent approach across more of the Windows estate, while retaining the controls each workload needs. That includes the operating system, apps, and, increasingly, Windows Server, all with a common approach used in Windows Autopatch.
Automatic updates for Windows apps
Keeping apps current can mean finding the latest version, packaging it, deploying it, and doing it all again with the next release. Microsoft Intune Enterprise App Management is expanding automatic updates for supported Windows apps with simplicity and controls already available via Windows Autopatch, helping IT reduce manual update work while maintaining control over deployment.
Think about the apps your team still maintains manually today. Where could automatic updates give that time back? Available for private preview on November 23.
Plan update activity around critical devices
For some devices, when an update happens matters just as much as staying current. Think about a kiosk, medical device, or manufacturing system that needs to be available during specific operating hours. Maintenance windows let you designate when selected update actions can take place, helping those devices stay current while remaining available when they're needed.
You can choose which update actions are limited to that window and configure one-time or recurring windows based on how the device is use. Follow the Windows IT Pro Blog for more details later this month on availability.
Bring Windows Server into your Windows Autopatch workflow
Servers have different update requirements, but that doesn't mean you should need a separate tool to keep them up to date. Windows Server management is coming to Intune with Windows Server 2028, bringing the ability to Microsoft Entra-join your servers to get Conditional Access, the Mobile Device Management (MDM) stack, Windows Autopatch patching and reporting into Microsoft Intune, the same console you use for clients today. As you explore the public preview of Windows Autopatch for Windows Server updates later next spring, look at which server workloads could benefit from that more consistent approach and which requirements you need to preserve.
Contain and manage AI agents running on your Windows devices
AI agents are introducing a new kind of workload to the Windows environment, but the management question is a familiar one: what should be allowed to run, what should it be able to access, and how does IT maintain control? We believe those boundaries should be part of the platform and management model from the start, not something organizations have to address agent by agent after deployment.
Windows and Intune provide control over agents running on managed Windows devices. Intune Windows provides policy-based controls that can help you manage agents running in Microsoft Execution Containers (MXC) including the files and networks they have access to. Think about boundaries as part of your management strategy from the start, rather than after agents are already in use.
Device health: See more, react faster, avoid issues altogether
Good management isn't measured only by whether a policy applied or an update installed. Ultimately, the device has to work well for the person using it. That means giving IT a clearer view of reliability and the user experience alongside configuration and update status.
Here are three capabilities you can bring into your device health and support strategy:
-
Leverage the OS reliability report. Understand Windows stop error trends, identify recurring failure patterns, and see which devices are affected—all within Microsoft Intune. Explore error details alongside Windows quality update history to help focus your troubleshooting. Available now in private preview.
-
Review new Windows experience controls deliberately as they arrive. New Windows experience controls give you a curated view of newly available controls for user-facing Windows experiences, so you can quickly see what's changing and where users will notice it. To manage them, we're introducing a new policy type with a template that grows as new controls are added. Your decisions stay in place, and new controls arrive as "Not configured," so the default behavior applies until you set a value. Use this as an opportunity to review and make each choice explicit. Available now in private preview.
-
Include user troubleshooting in your support approach. Copilot helps users troubleshoot Windows device issues, potentially reducing the need for IT assistance. Available now via the Windows Insider Program and the Microsoft Frontier Program.
Recover faster when something goes wrong
Even with strong management and faster patching, issues will happen. Resilience means planning for recovery before you need it. The question for IT isn't whether you have a recovery tool, but whether you have the right recovery option for the scope and severity of the problem.
Quick machine recovery management with Windows Autopatch, and cloud rebuild are now generally available, joining point-in-time restore in our suite of modern recovery tools. They are backed by existing tools like built-in crash recovery and rollback, cloud-initiated driver recovery, and traditional device wipe capabilities. For guidance on which tool to use when, read Windows device recovery in 2026: a guide for IT pros.
Where Windows management is headed
The way organizations manage devices needs to evolve. Devices work across locations and networks with varying connectivity, while IT still needs to maintain consistent configuration, security, and compliance without adding operational complexity.
Today, device management largely relies on services pushing configurations, checking whether they apply, detecting changes, and correcting devices that drift from their intended state. Windows declarative management shifts more of that work to Windows itself. IT defines the desired state for supported settings, and Windows works to apply and maintain it, whether the device is online or offline. The goal is to move from managing individual actions toward managing outcomes, specifically regarding capabilities that support:
-
Configuration drift protection. Detect when supported settings move from their intended state and take corrective action locally, even when the device isn't connected to the management service.
-
Configuration clarity. IT can see the intended configuration, the device's current state, and whether settings were successfully applied.
-
Predictable conflict handling. Defined rules determine which configuration takes precedence when settings compete.
-
Less manual intervention. By maintaining supported configurations locally, Windows can reduce the need to monitor individual policy actions and manually correct configuration issues.
This is the direction we are building toward. IT remains in control of the configurations it sets, while Windows takes on more of the work of maintaining them. As the environment IT manages continues to grow, the effort required to manage it shouldn't have to grow at the same rate.
Get started
The path forward will look different for every organization. Wherever you are in that journey, there are a few ways to stay connected and prepare for what's next:
-
Learn why timely updates matter. Read A new standard for vulnerability management in the AI era to learn why deploying updates promptly is more important than ever.
-
Get involved early. Join the Microsoft Management Advisors Program for early access to private previews and to work directly with the engineering teams building the next set of capabilities.
-
Keep up with what's changing. Catch up on all the Windows Security news from Microsoft Ignite 2026 then tune in to Ctrl+Manage, our monthly podcast on Windows management. Save the date for the next episode, November 30.
-
Plan your path to cloud management. Review where you are today and the next steps for moving more of your Windows management to the cloud.