A cybersecurity analyst monitors an AI-driven device protection dashboard in a modern server operations center.
At Ignite 2026, Microsoft's Intune team gave endpoint administrators a long list of changes. The Intune blog post, "What's new in Microsoft Intune at Ignite," covers controls for AI agents, a remediation agent for vulnerabilities, Windows Server enrollment, faster app inventory, CIS benchmark auditing, AI-assisted investigations and a clearer Autopilot setup screen. Very little of it is generally available. Most items are in public preview, private preview, limited public preview or a Windows Server Insider preview. For admins, those labels matter as much as the features.

Below is what was announced, what Microsoft's documentation adds, and what to check before you turn anything on.

A cybersecurity analyst monitors an AI-driven device protection dashboard in a modern server operations center. The big picture: Intune as the control layer for AI​

The Intune post describes AI agents as a new kind of insider threat that IT has to discover, limit and govern. The same idea appears in Microsoft's wider Ignite material. The Ignite 2026 Book of News says new agent governance and security capabilities across Agent 365, Microsoft Entra, Intune, Defender and Purview give organizations greater visibility and control over agents, their identities, tools, access and data.

Redmondmag reported that Microsoft's security news at the show focused on helping IT teams keep up with increasingly automated cyberattacks while managing the growing number of AI agents inside their organizations.

The question for most organizations is no longer whether staff will run local AI agents on managed PCs. They already are. The question is whether IT will know about it.

Governing AI agents: compliance, app protection and containers​

Blocking unsanctioned agents​

Microsoft describes a three-step path:

  • Discovery. Agent 365 combines detection from Defender, Entra and Intune to find agents running in the organization, including ones IT hasn't approved.
  • Compliance. A new Intune software compliance policy, in public preview, marks Windows devices running specified unsanctioned agents as noncompliant. A screenshot in Microsoft's post shows restricted apps being identified by MSI product codes.
  • Access control. Conditional Access blocks noncompliant devices from corporate resources. Users are then guided to remove the unwanted agent so the device can become compliant again.

The Book of News describes the same flow: IT will be able to discover which agents are running on managed devices with Microsoft Agent 365, mark devices with unapproved agents as noncompliant with Intune policies and block those devices from company data with Microsoft Entra.

This is an access-control mechanism, not a removal tool. Microsoft doesn't say the compliance policy uninstalls anything. It cuts off access until the user fixes the device.

There is also a practical limit. Because targeting is by MSI product code, agents installed another way, such as MSIX packages, per-user installers or portable executables, may not fit this model. Microsoft's post doesn't say how those cases are handled. Test with the agents your users actually run before you rely on the policy.

If you need product codes, Microsoft's app inventory documentation (covered below) says the "Platform-specific app ID" property is the MSI product code for Win32 apps. Device-level app inventory is a reasonable place to look them up.

App protection for approved AI apps​

Microsoft says Microsoft Copilot, GitHub Copilot, Anthropic Claude and OpenAI ChatGPT have integrated the Intune SDK. That means organizations can apply Intune app protection policies to these apps, the same mobile application management (MAM) controls already used for work data in other apps.

The announcement doesn't list supported platforms, app versions or licensing requirements. Check those per app before you write a policy that assumes coverage.

Microsoft Execution Containers (MXC)​

For supported agents, Intune is rolling out policies for Microsoft Execution Containers (MXC). These let admins set limits on what an agent running in a container can do with files and the network. Microsoft's Windows security blog explains the background: Announced last month, Microsoft Execution Containers provide governed boundaries for agent execution, helping organizations contain agent activity and maintain control over access to resources and tools. The Book of News says that for approved agents, Intune policies will define boundaries on what they can access and do with Microsoft Execution Containers.

Microsoft says it is still expanding coverage and enforcement, so not every agent or scenario is covered yet. Microsoft's MXC policy guidance on Microsoft Learn adds some useful cautions:

  • Start with deny-by-default and grant only the paths and network access the workload needs.
  • IP/CIDR and port rules don't identify a protocol or hostname. Allowing TCP 443 doesn't prove the traffic is HTTPS or that it reaches only one service.
  • Enforcement depends on the backend and host. Microsoft warns that a policy parsing successfully or a container launching is not proof that every restriction is in effect.
  • Run negative tests, such as trying to read secrets or write outside the allowed output folder, before you trust a policy.

These come from MXC developer documentation, not from the Intune announcement. They still apply to anyone writing container rules in Intune.

Section summary: Agent governance in Intune now has three layers: discovery through Agent 365, compliance enforcement through Conditional Access, and containment through MXC. All three are early, and the compliance path depends on MSI product codes.

Reducing exposure: remediation agent and Windows Server​

Vulnerability Remediation Agent​

The Intune Vulnerability Remediation Agent is in limited public preview as part of Microsoft Perception's "green team" agents. It combines Defender vulnerability data with Intune device and app context to build and run remediation playbooks, including automated app and OS patching on Intune-managed devices. You can reach it from Perception's "Reduce Risk Exposure" playbook or run it directly from the Intune admin center.

Microsoft is presenting this as automation with an admin in charge. The Book of News says that when a permanent fix is ready, the agent can coordinate patching through Microsoft Intune, with IT maintaining control of deployment.

The release status needs one clarification. Industry coverage reports that Microsoft Perception, the agent platform, is generally available. The Intune post, however, labels both the Vulnerability Remediation Agent and the Intune Perception experience as limited public preview. The platform being GA doesn't make every Intune feature on top of it GA.

The existing Microsoft Learn page for the agent gives the most concrete operational detail. It describes the earlier public-preview version, so the Ignite release may differ:

Requirement or behaviorMicrosoft Learn says
CloudPublic cloud only; government clouds aren't supported
LicensingIntune Plan 1, Security Copilot with enough SCUs, and Defender Vulnerability Management (via Defender for Endpoint P2 or the standalone product)
PlatformsWindows
IdentityRuns under a Microsoft Entra agentic identity; runs stay disabled until permissions are delegated and the Run Readiness Check passes
Server coverageCVE counts and exposed-device lists exclude Windows Server editions
Scope tagsNot supported in public preview
Visibility caveatAdmins may see agent findings outside their assigned Intune scope

The scope-tag gap is the item to watch. In a delegated-admin setup, a regional admin could see vulnerability findings for devices they don't manage. Note also that the agent currently excludes Windows Server CVEs, which matters given the next announcement.

Windows Server management in Intune (Insider preview)​

This could be the most significant change for many organizations. Intune is extending its endpoint workflows to eligible Windows Servers, including edge and branch servers and persistent virtual desktop sessions. It covers configuration, app deployment, compliance and Windows Autopatch update management. Microsoft's Windows security blog says the company is extending Intune and Windows Autopatch to eligible Windows Server scenarios, in preview, helping endpoint teams manage configuration, compliance, applications, updates, and security across Windows clients and supported servers. Redmondmag adds that this is tied to Windows Server vNext, Microsoft plans to bring server management into Intune, including Autopatch integration and Microsoft Entra-based management.

A separate Microsoft post on managing Windows Servers alongside PCs gives the rollout details:

  • Off by default. Device platform restrictions include a Windows Server setting set to Block. You must change it to Allow, and existing custom Windows restrictions keep blocking servers until you edit them.
  • Eligible scenarios. Active Directory???joined servers in environments using Microsoft Entra Connect, and servers joined to Microsoft Entra ID. Typical cases are jump boxes, privileged access workstations, RDS session hosts, branch servers and Azure Virtual Desktop Hybrid sessions. Multiple concurrent sessions are out of scope for this preview.
  • Not included. Windows Autopilot doesn't apply to servers. MDM-only enrollment, bulk enrollment and automatic enrollment for co-managed devices aren't available yet.
  • Azure Arc still applies. Microsoft still recommends Azure Arc as the management plane for on-premises and hybrid servers owned by infrastructure teams. Intune and Arc can each manage different areas of the same server, but they shouldn't enforce competing policies on the same settings.

The biggest risk is "All devices." Enrolled servers appear there alongside PCs. Commenters on Microsoft's server post objected that excluding servers means editing assignment filters across many existing deployments, since Intune doesn't allow multiple filters on one assignment.

Microsoft's suggested pre-enrollment checklist:

  • Review every assignment that targets All devices.
  • Create assignment filters using the operatingSystemSKU property to include or exclude server SKUs.
  • Audit roles and scope tags, since admins who manage PCs may otherwise be able to act on servers, including jump boxes that give access to production.
  • Pilot with non-production servers on a supported Windows Server Insider build, preferably in a test tenant.
  • If Configuration Manager, Group Policy or Arc already manages a server, decide which tool owns each workload.

Section summary: Remediation is becoming more automated and servers are coming into Intune, but both require planning: licensing and scope-tag gaps for the agent, and assignment cleanup for servers.

App visibility and configuration auditing​

Device-level app inventory (public preview)​

Microsoft's Learn documentation says the new app inventory collects more detail than Discovered apps, including install paths, uninstall commands, app sizes and MSI product codes. It runs several times a day on active devices. Discovered apps refreshes every seven days, or every 24 hours for Win32 apps via the Intune Management Extension. Microsoft describes app inventory as the long-term replacement for Discovered apps, and both currently run side by side.

To turn it on:

  • In the Intune admin center, go to Devices > Manage devices > Configuration > Create > New policy.
  • Choose Windows 10 and later and the Properties catalog profile type.
  • Add ApplicationProperties and select the properties to collect. Name, version, publisher, architecture and install-scope fields are required.
  • Assign the policy to device or user groups.
  • View the results under Devices > All devices > [device] > All Apps > App Inventory.

Prerequisites and limits: Devices must be enrolled in Intune and Microsoft Entra joined, running Windows 10 or 11. Nothing is collected until a policy is assigned. If no data appears, check those two things first. Microsoft also says that if the policy is removed, collection continues for about three days before stopping.

EAM automatic updates and in-use detection (private preview)​

Enterprise Application Management is extending automatic updates to more verified Windows apps, including apps IT didn't deploy. New update policies are meant to remove the need for manual repackaging or a separate policy per app. The Windows Mode summary of the keynote describes it as Intune automatically updating apps people installed themselves, not just the ones IT deployed. Microsoft hasn't published the list of eligible apps, so don't assume your whole catalog is covered.

App in-use detection, also in private preview, deals with installs that fail because the target app is running. Admins can report the blocked install or configure Intune to close the blocking process, with or without notifying the user. Silently closing apps can lose unsaved work, so the notification setting needs careful thought.

CIS benchmark auditing (public preview, November)​

Intune Advanced Analytics is adding CIS benchmark auditing alongside its existing DISA STIG auditing. Admins can assess device groups, review results per check and track progress over time. Microsoft's screenshot shows a CIS Windows 11 benchmark. Both auditing tools only report. They don't change device settings, so fixing gaps is still a separate task. Advanced Analytics is required.

Perception in Intune, fresher data and Autopilot​

AI-powered investigations (limited public preview)​

The Microsoft Perception experience in Intune takes plain-language questions and turns them into multi-step investigations. It writes and runs queries, calls APIs and explains each step with citations, and admins can inspect the underlying queries. Results can be refined in conversation, saved as Custom Reports with visualizations, and used to add affected devices or users to groups for normal Intune follow-up. It's available to Intune customers onboarded to Microsoft Perception, not to every tenant.

Being able to see the underlying queries matters more than the conversational interface. AI-generated queries can be wrong, and an investigation you can't check can't be trusted.

Near-real-time data and Remote Help​

Microsoft says platform changes are bringing Windows device data closer to real time. It cites faster app inventory and policy reporting, freshness timestamps, new registry key and file inventory, and richer device details in Remote Help Diagnostic Data Reports. Microsoft didn't publish refresh intervals or a field list for these changes. Registry inventory can expose sensitive configuration data, so check who can read inventory before you broaden collection.

Autopilot device preparation (limited public preview)​

On supported deployments, Company Portal now opens automatically after OOBE and shows compliance and app installation status: what's done, what's pending and when setup is finished. Microsoft calls it a non-blocking experience. It shows progress during setup but doesn't change the deployment's readiness requirements.

The verdict​

This is a substantial set of announcements, and it shows Microsoft positioning Intune as the policy layer for agent governance. The caveats are just as clear:

  • Preview labels vary. Public preview, private preview, limited public preview and Insider preview mean different levels of access. Few of these features can be adopted today without some form of onboarding.
  • Licensing adds up. The remediation agent alone needs Security Copilot capacity and Defender Vulnerability Management. CIS auditing needs Advanced Analytics.
  • Server enrollment needs cleanup first. Review All-devices assignments, filters and scope tags before the first server enrolls.

The sensible order is to start with app inventory (public preview, documented and low-risk), then pilot server enrollment in a test tenant, then test agent compliance policies against the agents your users actually run.


Update: Microsoft reportedly tightens Windows update deadlines and confirms recovery tools are GA (November 18, 2026)​

Windows Report says Microsoft is reducing the default quality-update deadline in Windows Update policies and Intune update rings to one day, while recommending that organizations install security updates within three days of release. The company is also adding maintenance windows for critical devices such as kiosks and medical equipment, alongside more granular quality-update approval controls and improved driver-update reporting.

The report also says Windows Server management through Intune is planned for public preview in spring 2027. That is a more specific timetable than the earlier Insider-preview messaging, so administrators should not treat current server-management capabilities as broadly available until Microsoft publishes the supported-build and enrollment details.

Separately, Windows Report reports that Quick Machine Recovery management and cloud rebuild are now generally available. For endpoint teams, that could provide a more established recovery path for devices affected by failed updates or startup issues, rather than another preview-only workflow.


Update: Microsoft says Execution Containers are now generally available on Windows 11 (November 18, 2026)​

Microsoft’s new Intune guidance says Microsoft Execution Containers (MXC) are now generally available on Windows 11, although Intune’s agent-containment policy remains the administrative control for setting each managed device’s maximum permissions. Initial supported coverage begins with process containers and MXC-enabled agents identified by Defender, including GitHub Copilot CLI and OpenAI Codex CLI.

The guidance also clarifies that Intune software compliance policies can use either an MSI product code for Win32 software or a package full name for Microsoft Store apps. However, the preview cannot select editor extensions, npm packages or standalone executables. Compliance is evaluated against the host application rather than an agent identity, so agents with multiple supported host apps may require multiple restricted-software entries.

Microsoft further says the policy can block access across the whole device even when the agent is inactive. That makes pilot testing especially important: an incorrect match can deny corporate-resource access through Conditional Access until the software is removed and compliance is restored.

For approved CLI agents, Microsoft says Defender’s AI agent runtime protections can audit or block supported prompt-injection attempts and certain high-risk actions. Admins should begin in audit mode and validate detections before enabling blocking.

 

References

  1. Microsoft Announces Major Windows 11 Management Upgrades With Intune and AI - Windows Report Windows Report 2026-11-18T08:53:07+00:00
  2. What’s new in Microsoft Intune at Ignite Microsoft Intune Blog 2026-11-17T18:15:23+00:00
  3. A guide to governing local AI agents with Intune Intune Customer Success 2026-11-17T18:15:31+00:00