Remove the Consumer Microsoft Copilot App with the New RemoveMicrosoftCopilotApp Group Policy (Windows 11)

Microsoft has introduced a new Group Policy setting named Remove Microsoft Copilot App (policy name: RemoveMicrosoftCopilotApp) that enables IT administrators to uninstall the consumer Microsoft Copilot app from managed Windows 11 Pro, Enterprise, and Education devices.

This is not a “disable Copilot everywhere” policy. It targets only the consumer Copilot app and is designed to leave Microsoft 365 Copilot intact.

At the time of writing, this capability is available in Windows 11 Insider Preview Build 26220.7535 (KB5072046) in the Dev and Beta channels.

---

What the policy does

When enabled, the policy:

• Uninstalls the preinstalled consumer Microsoft Copilot app for the user.
• Runs as a one-time uninstall action.
• Does not prevent a user from reinstalling the app later from the Microsoft Store (unless you add separate controls).

---

The strict conditions (why this often “does nothing”)

The uninstall triggers only if all conditions are true:

1. Both are installed on the device:
   • Microsoft 365 Copilot (work/paid), and
   • Microsoft Copilot app (consumer/free)
2. The consumer Copilot app is system-provisioned (installed by Windows/OEM/managed provisioning), not installed or reinstalled by the user from the Microsoft Store.
3. The consumer Copilot app has not been launched in the last 28 days.

Practical impact

That 28-day condition is the biggest blocker in real environments. Copilot can be launched unintentionally through:

• taskbar shortcuts,
• keyboard shortcuts,
• dedicated Copilot keys (on some keyboards),
• shell integrations depending on configuration.

If it is launched even once, you effectively restart the 28-day clock.

---

Where the policy lives (Local Group Policy path)

This is a User Configuration policy:

User Configuration
Administrative Templates
Windows AI
Remove Microsoft Copilot App

Set it to Enabled to trigger the one-time uninstall (when conditions are satisfied).

---

How to configure it (Local GPO test)

Use this for validation on a test device first.

Step-by-step

1. Run gpedit.msc
2. Navigate to:
   User Configuration > Administrative Templates > Windows AI > Remove Microsoft Copilot App
3. Set the policy to Enabled
4. Run:gpupdate /force Then sign out and sign in, or reboot (depending on your testing workflow).

Verify removal

• Settings > Apps > Installed apps: confirm Copilot is gone
• PowerShell (current user):Get-AppxPackage | Where-Object { $_.Name -like "*Copilot*" }

---

Deploy at scale with Active Directory Group Policy (Domain GPO)

Recommended approach

• Create a pilot GPO and apply it to a test OU or pilot users first.
• Configure the same policy path under User Configuration.
• Use security filtering for pilot groups.
• Expand in rings after you confirm behavior.

Key gotcha

Because this is a User Configuration policy, it is best targeted at user OUs/groups or a setup where you have predictable user-to-device mapping.

---

Deploy with Microsoft Intune (MDM-managed endpoints)

Because this is an Administrative Template-style setting, your deployment options typically fall into these categories:

Option 1: Settings Catalog (preferred, when available in your tenant)

1. Devices > Configuration > Create > New policy
2. Platform: Windows 10 and later
3. Profile type: Settings catalog
4. Search for: Windows AI or Remove Microsoft Copilot App
5. Set the setting to Enabled
6. Assign to a pilot user group first

Option 2: Templates > Administrative Templates (if exposed)

If the setting appears in the Administrative Templates UI:

• Configure it there, assign, and monitor per-user results.

Option 3: Custom policy (fallback)

Use only if the setting is not surfaced yet in your tenant UI. In practice, most admins will wait until the setting is directly supported in catalog/templates to reduce fragility.

Assignment guidance (important)

Because it is a user policy, start with:

• a pilot user group,
• with users who sign into dedicated test devices.

---

Verification and monitoring at scale

Intune

• Profile status: Devices > Configuration profiles > [profile]
• Review User status and Device status (expect user-centric reporting to be the more meaningful signal)

Client-side (MDM processing)

On a target device, validate MDM policy processing events:

• Event Viewer:
  Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin

App presence check (scriptable)

Use this to confirm the package is still present for the user:

Get-AppxPackage | Where-Object { $_.Name -like "*Copilot*" } |
Select-Object Name, Version, PackageFullName

---

Alternatives: remove vs hide vs block (pick the right control)

1) Hide Copilot (lowest friction)

If you just want it out of the way without enforcing removal:

• Turn off the Copilot toggle in taskbar settings via policy (user experience control).

Best for: environments that are not ready for app-control enforcement.

2) Uninstall Copilot (operationally simple, not durable)

• Use RemoveMicrosoftCopilotApp where it works.
• Use Settings “Uninstall” where available.
• Use PowerShell for direct removal when governance allows.

Best for: reducing noise on managed devices, without strict prevention.

3) Block Copilot (durable enforcement)

If you must prevent reinstallation and execution:

• Use WDAC or AppLocker packaged app rules to block the Copilot package family.
• Consider Microsoft Store controls (depending on your Store management model).

Best for: regulated environments and locked-down enterprise baselines.

---

PowerShell removal (when you need immediate action)

If policy conditions prevent the GPO method from triggering (common), PowerShell may be required for immediate remediation.

Current user uninstall

Get-AppxPackage *Microsoft.Copilot* | Remove-AppxPackage

Inventory across users (discovery)

Get-AppxPackage -AllUsers | Where-Object { $_.Name -like "*Copilot*" } |
Select-Object Name, PackageFullName, InstallLocation

Note: “remove for all users” is not always straightforward for Store apps due to provisioning and per-user installs. Treat this as an operational decision and test carefully in your ring strategy.

---

Troubleshooting checklist (when it does not uninstall)

If the policy is enabled but Copilot remains installed:

• Confirm the device is on a build that supports the policy (Insider Dev/Beta in this case).
• Confirm the policy is applying to the correct user (RSOP/MDM status).
• Confirm the app is system-provisioned, not user-installed/reinstalled.
• Confirm Copilot has not launched in the last 28 days (this is the usual failure point).
• Confirm the device has both consumer Copilot and Microsoft 365 Copilot installed (required condition).

---

Rollback plan

• Set the policy to Not configured (or Disabled) and refresh policy.
• If users are allowed, they can reinstall Copilot from approved channels.
• If you used WDAC/AppLocker to block it, roll back those rules in a controlled change window.

---

Enterprise decision matrix

Goal	Recommended approach	Tradeoffs
Reduce user distraction	Hide taskbar Copilot	App still installed
Remove from managed devices “when possible”	RemoveMicrosoftCopilotApp + reporting	Conditional, one-time, not durable
Prevent any usage/reinstall	WDAC/AppLocker + Store controls	Heavier design/testing, potential support load
Rapid cleanup after deployment	PowerShell remediation	Needs governance, may be re-provisioned later

---