Microsoft 365 | Windows Policy | Copilot | IT Administration | Endpoint Management
Microsoft has introduced a new admin policy — RemoveMicrosoftCopilotApp — that gives IT administrators a controlled, non-disruptive way to uninstall the standalone Microsoft Copilot app from Windows devices across their organisation. Available as of the April 2026 Windows security update, this policy is a welcome addition for admins managing environments where Microsoft 365 Copilot is already deployed and a duplicate Copilot app creates user confusion.
What Problem Does This Solve?
Organisations licensed for Microsoft 365 Copilot already have access to Copilot integrated directly into Word, Excel, Teams, SharePoint, and the broader Microsoft 365 suite. The standalone Microsoft Copilot app — a separate consumer-facing application that ships with Windows — sits alongside it, creating a fragmented experience where users may be unsure which Copilot to use, or end up using the wrong one for their context.
The RemoveMicrosoftCopilotApp policy lets admins quietly remove the standalone app from qualifying devices, consolidating the experience to a single Copilot entry point per device.
Eligibility Conditions
The policy is intentionally scoped — it only removes the Copilot app from devices and users that meet all three of the following conditions:
- Microsoft 365 Copilot is also installed on the device — the policy won’t remove the standalone app unless the enterprise Copilot is present as a replacement
- Copilot was not installed by the user — user-initiated installs are excluded, respecting individual choice
- Copilot has not been launched in the last 28 days — active users of the standalone app are not affected
If any one of these conditions is not met, the policy has no effect on that device. This makes it safe to deploy broadly without worrying about disrupting users who actively rely on the app.
Note: Even on affected devices, users retain the option to reinstall the Microsoft Copilot app manually after removal. This is a cleanup policy, not a hard block.
Availability and Requirements
| Detail | Info |
|---|---|
| Policy name | RemoveMicrosoftCopilotApp |
| Policy type | Policy CSP and Group Policy |
| Available as of | April 14, 2026 |
| Minimum Windows update required | April 2026 Windows security update (KB5083769) |
| OS builds covered | 26200.8246 and 26100.8246 |
Devices must be running at least the April 2026 Windows security update for the policy to be available. Attempting to apply it on older builds will have no effect.
How to Configure the Policy
Option A: Policy CSP (Intune / MDM)
For organisations managing devices via Microsoft Intune or another MDM solution, the policy is available under the WindowsAI Policy CSP:
- CSP path:
./Device/Vendor/MSFT/Policy/Config/WindowsAI/RemoveMicrosoftCopilotApp - Value: Set to enabled to trigger removal on qualifying devices
Full configuration details are available in the WindowsAI Policy CSP documentation on Microsoft Learn.
Option B: Group Policy
For on-premises or hybrid environments managed via Group Policy:
- Ensure devices have received the April 2026 Windows security update (KB5083769)
- Open the Group Policy Management Console
- Navigate to the relevant GPO for your device scope
- Locate the
RemoveMicrosoftCopilotApppolicy setting under the Windows AI policy node - Set the policy to Enabled and apply
What Action Do You Need to Take?
If your organisation is happy with the default experience — users choosing whether to use the standalone Copilot app — no action is required. The policy does nothing unless explicitly configured.
If you want to streamline the Copilot experience for users who have Microsoft 365 Copilot licensed, configure the policy as described above. It will silently remove the standalone app from qualifying devices without disrupting active users or requiring device restarts.
Admin Considerations
- This is not a block — users can reinstall the standalone Copilot app after removal. If you need to prevent reinstallation, you’ll need a separate app restriction policy via Intune or AppLocker.
- Scope your deployment carefully — audit which devices actually meet all three eligibility conditions before broad rollout. Intune device filters or Entra ID groups scoped to M365 Copilot-licensed users are a clean way to target this.
- Test on a pilot group first — even non-disruptive policies can surface unexpected edge cases in mixed-device environments. Validate on a representative sample before organisation-wide deployment.
- Monitor for the 28-day window — a user who hasn’t launched the standalone Copilot app in 28 days qualifies for removal today, but may have been an active user before that window. Communicate the change through your standard IT comms channels before deploying.
Further Reading
- WindowsAI Policy CSP — RemoveMicrosoftCopilotApp
- KB5083769 — April 14, 2026 Windows security update
- Microsoft Message Center: MC1289507
