As of October 2026, only one of the four Security Copilot agents Microsoft shipped in the Intune admin center is still available: the Vulnerability Remediation Agent, which is in public preview. The Device Offboarding Agent was removed on June 1, 2026. The Policy Configuration Agent and Change Review Agent were removed on August 31, 2026. If you’re budgeting Security Compute Units (SCUs) for Intune agents, budget for that one agent.
This article covers each agent’s current status, how to set up the Vulnerability Remediation Agent, and how SCU billing works. For what to use in place of each retired agent, see Intune Copilot agents: what replaced the retired ones.
Agent status as of October 2026
| Agent | Status | Source |
|---|---|---|
| Vulnerability Remediation Agent | Public preview | Learn |
| Policy Configuration Agent | Retired August 31, 2026 | Learn |
| Change Review Agent | Retired August 31, 2026 | Learn |
| Device Offboarding Agent | Retired June 1, 2026 (setup blocked from April 30) | Learn |
Microsoft’s agents overview page still lists all four agents, but each retired agent’s own page opens with its retirement notice. Trust the agent pages.
The Change Review Agent evaluated Multi Admin Approval requests for PowerShell scripts, using signals from Defender Vulnerability Management, Entra ID, and Intune. It was still in public preview when it was retired. The Policy Configuration Agent mapped documents and plain-language requirements to settings catalog settings. If you relied on it, Intune Policy Configuration Agent retired: what to use now covers what happens to the policies it created.
The Vulnerability Remediation Agent
The remaining agent uses Microsoft Defender Vulnerability Management data to find CVEs on managed Windows devices. It prioritizes them using factors like CVSS score, exposure, and device count, and gives step-by-step remediation guidance for Intune. It doesn’t change anything on its own. You apply the fix, then mark the suggestion as applied to keep a record.
Licensing beyond Intune Plan 1 and Security Copilot: it needs Defender Vulnerability Management, which comes with Microsoft Defender for Endpoint P2 or Defender Vulnerability Management Standalone. It also needs the Intune and Microsoft Defender plugins. Limits Microsoft documents for the preview:
- Public cloud only.
- CVE counts and exposed devices exclude Windows Server.
- No scope tag support in preview. Admins who can open the Intune admin center may see agent data outside their assigned scope.
- Once started, it can’t be stopped or paused.
Set up the Vulnerability Remediation Agent
From the agent’s Learn page:
- Setup role: Intune Read Only Operator, or a custom role with Security Tasks/read, Mobile apps/read, Device configurations/read, and Organization/read.
- Platforms: Windows, and apps in Intune.
- In the Intune admin center, go to Agents > Vulnerability Remediation Agent. It’s also reachable from Endpoint security, and both paths open the same agent.
- In Overview, select Set up Agent and review the permissions and plugins it lists.
- Select Start agent. Setup creates a Microsoft Entra agentic identity and a matching agentic user in your directory.
- Delegate the required permissions to that agentic user in the Entra and Defender admin centers. The Learn prerequisites list them, including Defender XDR RBAC permissions. Agent runs stay disabled until you do.
- Select Run Readiness Check. When it passes, you can run the agent.
Intune RBAC assignments for the agentic user can take several minutes to apply. If Allow admins without an Intune license is off in your tenant, the agentic user needs a license. If the agent’s identity breaks beyond repair, Microsoft’s fix is to remove the agent and set it up again, which provisions a new identity.
How SCU billing works
Every agent run uses SCUs from your Security Copilot capacity. Per Microsoft’s capacity documentation:
- Provisioned capacity is set up in advance (minimum one SCU) and billed per hour, whether or not you use it.
- Overage capacity is consumed as used and billed on usage. You can set a maximum limit or leave it unlimited, so set a limit if you want a hard stop.
- Microsoft 365 E5 and E7 inclusion gives 400 SCUs per month for every 1,000 paid user licenses, up to 10,000 SCUs per month. It isn’t billed hourly. Microsoft started the rollout on November 18, 2025 and is enabling tenants in phases (inclusion FAQ).
The pool is shared. Intune agents draw from the same Security Copilot capacity as other Security Copilot experiences in that tenant. Watch the usage dashboard in the Security Copilot portal during your first runs.
What the agents are not
- Not autonomous. Microsoft’s Vulnerability Remediation Agent documentation describes suggestions and guidance. Remediation stays with the admin.
- Not the same as Entra, Defender, or Purview agents. Those products have their own Security Copilot agents, which Microsoft lists separately.
- Not a reason to skip Intune expertise. Someone still has to judge whether a suggested remediation is safe for your devices.
Where this fits: Agent 365 and shadow AI
The Intune agents are only one part of Microsoft’s agent tooling. Microsoft Agent 365 went generally available for the Commercial segment on May 1, 2026, licensed per user. It covers observing, governing, and securing agents through a central registry in the Microsoft 365 admin center, along with Microsoft Entra and Microsoft Purview. For the governance side, see Microsoft Agent 365 GA: AI agent governance.
For agents running on endpoints, three pieces are documented today:
- Shadow AI page (public preview, Frontier program): the page is in the Microsoft 365 admin center, not the Intune admin center. It finds and governs unmanaged AI agents. Learn lists these prerequisites: Defender for Endpoint on devices, Microsoft 365 E5, and Intune enrollment for managed Windows devices (Learn).
- Defender for Endpoint AI agent runtime protection (preview): detects malicious prompts and harmful agent actions on local AI agents, and can block them before they run (Learn).
- Intune device query: multi-device query includes a Local AI Agent entity for inventory. See Copilot device query in Intune.
FAQ
Which Security Copilot agents are still in Intune?
Only the Vulnerability Remediation Agent, in public preview. The Policy Configuration, Change Review, and Device Offboarding agents are retired.
When were the Policy Configuration and Change Review agents retired?
August 31, 2026. Microsoft removed both from the Intune admin center on that date.
Do Intune agents cost extra?
They use Security Copilot SCUs. Microsoft 365 E5 and E7 tenants get an included monthly allocation. Other tenants pay for provisioned or overage capacity.
Can I cap overage SCU spend?
Yes. Microsoft documents that overage capacity can be configured with a maximum limit.
Do I need to contact Microsoft to get the Vulnerability Remediation Agent?
Microsoft Learn documents it as public preview with self-service setup from Agents in the Intune admin center. It doesn’t mention an access request.
Why won’t the Vulnerability Remediation Agent run after setup?
Usually the agentic user doesn’t have its delegated Entra and Defender permissions yet. Assign them, then run Run Readiness Check.
Sources
- Security Copilot agents in Intune overview, Microsoft Learn
- Vulnerability Remediation Agent, Microsoft Learn (updated August 25, 2026)
- Change Review Agent, Microsoft Learn (retirement notice)
- Policy Configuration Agent, Microsoft Learn (retirement notice)
- Device Offboarding Agent, Microsoft Learn (retirement notice)
- Security Copilot compute units and capacity, Microsoft Learn
- Security Copilot for Microsoft 365 E5 and E7 customers, Microsoft Learn
- Microsoft Agent 365 overview, Microsoft Learn (updated August 20, 2026)
- Understand Shadow AI in Microsoft 365 admin center, Microsoft Learn
- AI agent runtime protection with Defender for Endpoint (Preview), Microsoft Learn