Microsoft has officially documented a new policy that arms IT administrators with the ability to completely uninstall the Microsoft Copilot app from managed devices. The policy, called RemoveMicrosoftCopilotApp, appeared in the latest update to the Group Policy administrative templates and Mobile Device Management (MDM) policy catalog for Windows 11 version 24H2. This marks a significant shift from the integrated Copilot experience in earlier builds, reflecting Microsoft's pivot to a standalone app model and giving enterprises granular control over AI productivity tools on company hardware.

What the RemoveMicrosoftCopilotApp Policy Does

The policy, when enabled, removes the Microsoft Copilot app from Windows 11 devices running version 24H2 and prevents users from reinstalling it from the Microsoft Store. This is not simply a toggle to hide the icon or suppress the feature—it is a full uninstallation. The app, which debuted as a dedicated application in the 24H2 update, replaces the previous side-panel integration that many organizations found difficult to disable or remove. Now, administrators can enforce a clean removal across fleets via Group Policy or MDM solutions like Microsoft Intune.

The policy is found under the following paths:

  • Group Policy: Computer Configuration\Administrative Templates\Windows Components\Windows Copilot\Remove Microsoft Copilot app
  • MDM CSP: ./Device/Vendor/MSFT/Policy/Config/Experience/RemoveMicrosoftCopilotApp

It is available only on Windows 11 Enterprise, Education, and other commercial SKUs managed by an organization. Consumer editions (Home, Pro) are not supported, and the policy has no effect on them.

Why This Policy Matters Now

Windows 11 24H2 restructured Copilot into a full-fledged application that can be pinned to the taskbar, resize, and operate more like a traditional office tool. While that improves usability for many, it introduces new challenges for IT departments concerned with data governance, compliance, and license management. The RemoveMicrosoftCopilotApp policy directly addresses these concerns by allowing organizations to opt out of the Copilot app entirely without resorting to complex workarounds like blocking the Microsoft Store app ID or using AppLocker.

The policy’s documentation also clarifies that it only affects the Copilot app as an application. Copilot integrations inside other Microsoft 365 apps—such as Word, Excel, or Teams—are governed by separate admin controls and license entitlements. This decoupling means admins can remove the standalone Copilot consumer experience while still deploying Microsoft 365 Copilot with its enterprise data protections if desired.

How to Configure the Policy

Via Group Policy

  1. Download the latest administrative templates (ADMX/ADML) for Windows 11 24H2 from the Microsoft Download Center and copy them to your central store or local PolicyDefinitions folder.
  2. Open the Group Policy Management Console (GPMC) and navigate to the desired organizational unit.
  3. Go to Computer Configuration > Administrative Templates > Windows Components > Windows Copilot.
  4. Double-click Remove Microsoft Copilot app and set it to Enabled.
  5. Click OK and apply the Group Policy Object (GPO).

After the next Group Policy refresh, the Copilot app will be uninstalled from the target devices. No reboot is typically required, though users may need to log off and back on for the change to take full effect.

Via Microsoft Intune (MDM)

For cloud-managed devices, admins can deploy the setting through the Settings Catalog or a custom OMA-URI profile:

  • Settings Catalog: Search for "Remove Microsoft Copilot app" in the Experience category and set it to Allowed.
  • Custom OMA-URI:
  • OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Experience/RemoveMicrosoftCopilotApp
  • Data type: Integer
  • Value: 1 (enabled)

The policy will sync with Intune and remove the app on next check-in. You can verify successful removal by looking for AppX deployment logs or simply checking the Start menu for the Copilot entry.

Real-World Impact on IT Operations

Early adopters in enterprise environments have reported that the policy works reliably on build 26100 or later. However, a few nuances have surfaced:

  • Pinned taskbar icons: If a user had pinned the Copilot app to the taskbar before removal, the icon may persist as a dead shortcut until manually unpinned or the taskbar layout is refreshed.
  • Store reinstall blocks: Attempting to reinstall the app from the Microsoft Store results in an error message stating the app is blocked by policy, which is the desired behavior.
  • Side effects on Copilot in Edge: This policy does not affect the Copilot icon inside Microsoft Edge or the Edge sidebar. Those are controlled by separate browser policies.

For organizations that had previously used the TurnOffWindowsCopilot policy (now considered legacy), Microsoft recommends switching to the new RemoveMicrosoftCopilotApp policy because the old policy only hides the taskbar button and does not remove the app binaries in 24H2.

Background: The Copilot App Transition

When Windows 11 first launched with Copilot, it was a deeply integrated feature tied to the taskbar and the Edge browser. IT administrators had limited options to disable it, and even then, components remained on the system. The move to a standalone app in 24H2 was partly driven by user feedback requesting a more flexible, resizable interface. But it also conveniently enables simpler enterprise management—a standalone app can be removed with app management tools, whereas a baked-in OS feature cannot.

The RemoveMicrosoftCopilotApp policy is the formalization of that capability. It aligns with Microsoft’s broader strategy of treating Copilot as a platform that can be tailored, rather than a one-size-fits-all feature. Enterprise admins can choose to keep the Copilot app, remove it, or replace it with the Microsoft 365 Copilot experience that respects organizational compliance boundaries.

Looking Ahead: IT Governance in the AI Era

As AI assistants become more embedded in operating systems, the demand for precise administrative controls will only grow. The RemoveMicrosoftCopilotApp policy sets a precedent for how Microsoft might handle future AI-driven features: ship them as separable components with clear on/off switches accessible through standard management tools.

IT decision-makers should evaluate this policy now, even if they plan to deploy Copilot eventually. Having a well-defined removal mechanism ensures that pilot programs can be conducted safely and that any unexpected compliance issues can be resolved by temporarily uninstalling the app while maintaining other Copilot services that pass security reviews.

No official end-of-life has been announced for the older TurnOffWindowsCopilot policy, but its efficacy is diminished on 24H2. Administrators are strongly advised to transition to RemoveMicrosoftCopilotApp to maintain a clean, predictable device configuration. With the right policy in place, the days of scrambling to hide unwanted AI shortcuts on enterprise desktops are numbered.