The RemoveMicrosoftCopilotApp setting became broadly available with the April 2026 Windows security update, including KB5083769 for Windows 11 version 25H2. It is available through both Policy CSP and Group Policy, allowing administrators to apply it through device-management systems used in corporate, education and public-sector environments.
The change is narrowly designed. It applies only when Microsoft 365 Copilot and Microsoft Copilot are both installed on the same device, when the Microsoft Copilot app was not installed manually by the user, and when the app has not been launched in the previous 28 days. When those conditions are met and the policy is enabled, Windows silently uninstalls the consumer Copilot app. Users may still reinstall it later if they choose.
That limitation makes the policy more of a fleet-cleanup mechanism than a hard ban on Copilot. It does not remove Microsoft 365 Copilot, the paid workplace assistant connected to Microsoft Graph and enterprise data controls. It targets the consumer-facing Copilot app, which does not support Microsoft Entra authentication and redirects users signing in with organisational accounts towards the Microsoft 365 Copilot web experience.
For IT departments, the distinction matters. Large organisations have been pressing software vendors for clearer controls over AI features that appear through operating system updates, productivity suites and app-store components. Copilot’s expanding presence across Windows, Microsoft 365, Edge, Teams and Outlook has raised questions about data governance, user consent, support burdens and software standardisation.
Microsoft’s latest setting gives administrators a formal route to reduce duplication where both Copilot experiences appear on a device. It also reflects a wider adjustment in the company’s Windows AI strategy, after earlier efforts to embed Copilot more deeply into the operating system drew scrutiny from enterprise customers and privacy specialists.
Windows 11 has already moved through several Copilot phases. Microsoft first promoted Copilot as a prominent operating-system assistant, including taskbar and keyboard entry points. The experience later shifted towards a standalone app and Microsoft 365 Copilot Chat, while the legacy Windows Copilot policy began moving towards deprecation. The company now advises administrators to use tools such as AppLocker and WindowsAI policies rather than relying on older controls built for the first Windows Copilot implementation.
The policy is available for Windows 11 Pro, Enterprise and Education client editions running version 25H2 with the April 2026 security update or later. Administrators can configure it through the WindowsAI policy path in mobile device management, with integer values used to disable or enable removal. A value of 1 enables removal, while 0 leaves the app in place.
For managed organisations, the practical impact will depend on deployment habits. Devices where users have opened Copilot within the previous 28 days will not qualify. Machines where the user installed Copilot manually are also excluded. That means administrators seeking full removal across an estate may still need additional controls, including app-blocking rules, software inventory checks and user-communication plans.
The move comes as AI governance becomes a growing part of endpoint management. Companies adopting Microsoft 365 Copilot are often trying to separate approved workplace AI from consumer AI assistants that may not fit internal data policies. Regulated sectors such as banking, healthcare, insurance and government contracting are particularly sensitive to where prompts, files, identities and transcripts are processed.
Microsoft has continued to present Copilot as central to its productivity strategy, but it has also had to reassure enterprise customers that adoption can be controlled. The new removal policy supports that effort by allowing organisations to simplify the user experience to one approved Copilot route, rather than leaving multiple versions on the same device.
Topics
Technology