Microsoft now gives IT admins a policy to remove Copilot from Windows 11 enterprise PCs

Microsoft has added an official Windows policy that lets IT administrators uninstall the Microsoft Copilot app from managed Windows 11 devices. The policy is called RemoveMicrosoftCopilotApp, and it works through both Policy CSP and Group Policy.

The setting is not meant to remove every Copilot experience from Windows. It targets the Microsoft Copilot app in specific enterprise scenarios, especially when Microsoft 365 Copilot is already installed on the same device. Microsoft describes it as a non-disruptive way to remove Copilot from organizational devices.

The policy is available on Windows 11 version 25H2 with KB5083769 and later. Microsoft lists support for Pro, Enterprise, Education, and IoT Enterprise editions, which covers most managed business and school environments.

What the new Copilot removal policy does

The RemoveMicrosoftCopilotApp policy gives admins a cleaner way to uninstall the Microsoft Copilot app without manually touching each device. It can run at the user level or device level, depending on how the organization manages Windows endpoints.

Admins can configure it through the Windows AI policy area. The Policy CSP paths are ./User/Vendor/MSFT/Policy/Config/WindowsAI/RemoveMicrosoftCopilotApp and ./Device/Vendor/MSFT/Policy/Config/WindowsAI/RemoveMicrosoftCopilotApp.

The setting uses an integer value. Setting it to 1 enables the uninstall behavior, while 0 disables it. That makes it simple to deploy through MDM tools, Intune, or traditional policy workflows.

It only removes Copilot in certain cases

Microsoft has placed clear limits on when this policy works. It applies only when Microsoft 365 Copilot and Microsoft Copilot are both installed on the device.

The Microsoft Copilot app also must not have been installed by the user. On top of that, the app must not have been launched in the last 28 days. These limits help prevent the policy from removing Copilot for users who actively chose or recently used the app.

This makes the policy more of a cleanup tool than a full Copilot ban. It helps organizations remove an unused consumer-facing Copilot app while keeping Microsoft 365 Copilot as the main workplace AI experience.

At a glance

Item	What Microsoft lists
Policy name	RemoveMicrosoftCopilotApp
Main use	Uninstall the Microsoft Copilot app from eligible managed devices
Management options	Policy CSP and Group Policy
Supported Windows version	Windows 11 version 25H2 with KB5083769 and later
Supported editions	Pro, Enterprise, Education, IoT Enterprise, IoT Enterprise LTSC
User-level path	./User/Vendor/MSFT/Policy/Config/WindowsAI/RemoveMicrosoftCopilotApp
Device-level path	./Device/Vendor/MSFT/Policy/Config/WindowsAI/RemoveMicrosoftCopilotApp
Required value	1 to enable removal
Key limitation	Users can reinstall Copilot unless admins block it separately

Why Microsoft added this option

The new policy fits Microsoft’s broader effort to separate consumer Copilot and commercial Copilot experiences. Microsoft’s admin guidance explains that work and school users can use Microsoft 365 Copilot Chat, while IT teams can manage Copilot access and entry points in Windows.

For enterprise admins, that distinction matters. A company may want employees to use Microsoft 365 Copilot because it connects to work accounts, enterprise controls, and approved data boundaries. The separate Microsoft Copilot app may create confusion in managed environments.

This policy gives IT teams a practical way to reduce that overlap. It does not remove all AI from Windows, but it gives admins more control over which Copilot app remains on corporate PCs.

This does not permanently block Copilot

The most important catch is that the policy performs removal, not permanent prevention. Microsoft’s own Windows message center says the policy allows admins to uninstall Copilot in a non-disruptive way, but it does not describe it as a full block.

If an organization wants to stop users from installing or launching the app again, it needs an additional control. Microsoft’s Copilot management guidance points admins toward tools such as AppLocker for blocking the consumer Microsoft Copilot app.

That means admins should treat RemoveMicrosoftCopilotApp as one part of a larger policy plan. It handles cleanup. App control handles enforcement.

What enterprise admins can do now

• Check whether managed devices run Windows 11 version 25H2 with KB5083769 or later.
• Confirm whether both Microsoft 365 Copilot and Microsoft Copilot exist on affected devices.
• Use the Windows AI policy path to configure RemoveMicrosoftCopilotApp.
• Set the policy value to 1 when removal should run.
• Use Intune, Policy CSP, or Group Policy depending on the existing management setup.
• Add AppLocker or another app-control policy if the organization wants to prevent reinstalling Copilot.
• Communicate the change to users so they understand which Copilot experience remains available.

Why security and IT teams may care

This update matters because many companies want tighter control over AI tools on employee devices. Even when an app comes from Microsoft, IT teams still need clear policies for availability, identity, data access, and user experience.

The new policy helps companies standardize around a single Copilot option for work. That can reduce confusion for users who see both Microsoft Copilot and Microsoft 365 Copilot on the same device.

It also gives admins a supported path instead of relying on scripts or manual cleanup. For large organizations, that difference matters because supported policies are easier to audit, document, and deploy consistently.

FAQ