Microsoft is giving IT administrators a long-requested lever: the ability to permanently strip the Copilot app from managed Windows 11 machines. A new Group Policy and MDM setting, documented under Windows Components, will roll out after the April 2026 update, targeting Windows 11 version 24H2 and later.

For enterprises that have wrestled with AI assistant bloatware creeping onto corporate desktops, this policy closes a gap that third-party tools and registry hacks only partially addressed. Until now, Copilot arrived pinned to the taskbar by default on Windows 11, and although users could unpin it, the integrated Copilot in Windows (the side panel) was baked into the OS, and the standalone Microsoft Copilot app could reinstall itself after cumulative updates or feature packs. The new policy, officially titled Turn off Microsoft Copilot, eliminates the app entirely from user devices.

The New Policy Explained

The policy appears under Computer Configuration > Administrative Templates > Windows Components > Microsoft Copilot in Group Policy Editor. When enabled, it removes the Microsoft Copilot app from the system and prevents the operating system from silently reinstalling it during future updates. The policy does not disable the browser-based Copilot experience (copilot.microsoft.com) nor does it affect the Copilot key on new keyboards—those shortcuts will simply stop functioning if the app is absent. However, the web-based Copilot and Copilot in Edge remain accessible unless separately blocked via browser policies.

For Microsoft 365 commercial customers, this is a direct response to feedback that AI tools should be opt-in for regulated industries, educational institutions, and any organization where data governance requirements clash with consumer-grade AI defaults. The policy applies to Windows 11 Pro, Enterprise, and Education editions, as well as Windows Server 2025 when the Desktop Experience is installed.

Microsoft has published the ADMX template files with the associated registry path: HKLM\Software\Policies\Microsoft\Windows\WindowsCopilot. A DWORD value named TurnOffCopilot set to 1 triggers the removal. The Group Policy setting also surfaces in Microsoft Intune through the Administrative Templates profile, meaning organizations can deploy the restriction at scale without touching each endpoint.

How to Configure via Group Policy

For on-premises Active Directory environments, the steps are straightforward once the April 2026 security update or feature pack has been applied to domain controllers and clients:

  1. Open Group Policy Management Console (gpmc.msc).
  2. Create or edit a GPO linked to the organizational unit containing Windows 11 24H2 devices.
  3. Navigate to Computer Configuration > Policies > Administrative Templates > Windows Components > Microsoft Copilot.
  4. Double-click Turn off Microsoft Copilot.
  5. Set the policy to Enabled, then click OK.
  6. Run gpupdate /force on target machines, then restart.

After the policy applies, the Copilot icon disappears from the taskbar, the app entry is removed from the Start menu, and any attempt to invoke it via keyboard shortcut fails silently. The application binaries may remain in the system image but will be inaccessible. This approach prevents users from re-pinning Copilot and stops Windows Update from restoring it.

Administrators should note that the policy only affects the standalone Microsoft Copilot app (the consumer-focused chat client), not the legacy Copilot in Windows sidebar that was deprecated in favor of the app experience. If devices are running an older build where Copilot appears as a side panel, a separate policy—Turn off Copilot in Windows—may be necessary until those systems are upgraded.

How to Configure via MDM/Intune

Cloud-native organizations can push the same restriction through Microsoft Intune or any MDM provider that supports CSP (Configuration Service Provider) policies:

  1. Sign in to the Microsoft Intune admin center.
  2. Go to Devices > Configuration and create a new Settings catalog profile.
  3. Add the setting Turn off Microsoft Copilot from the Windows node. The OMA-URI path is ./Device/Vendor/MSFT/Policy/Config/WindowsCopilot/TurnOffCopilot.
  4. Set the integer value to 1.
  5. Assign the profile to the desired device or user groups.

Alternatively, organizations can deploy the policy via Administrative Templates in Intune, which mirrors the Group Policy user interface. That method requires no custom OMA-URI entry and is available after synchronizing the latest ADMX templates (included in the Windows 11 24H2 April 2026 update).

For co-managed environments, the policy will respect any conflict resolution rules already in place. If both Group Policy and Intune attempt to set the value, the more restrictive setting usually wins, but administrators should test to avoid unexpected behavior.

Implications for Enterprise Management

The ability to remove Copilot at the device level is more than a cosmetic tweak. It addresses several persistent pain points:

  • Compliance with data protection regulations: Many industries, including healthcare and finance, must verify that no unsanctioned AI tools are processing sensitive data. By removing the app outright, organizations reduce the surface area for accidental data leaks.
  • User productivity and focus: Copilot’s presence on the taskbar can be a distraction, especially when it prods users to interact with features that they are not trained to use or that their workflows don’t require.
  • Software asset management: In some licensing scenarios, Copilot’s entitlement is tied to specific Microsoft 365 plans. Removing the app helps prevent unlicensed usage and simplifies compliance reporting.
  • Update and restart predictability: A common complaint was that Copilot would reappear after cumulative updates, forcing IT to re-customize the Start layout. The policy ensures persistent removal without scripting.

From a support perspective, the policy reduces help-desk tickets. Previously, users who did not want Copilot had to manually unpin it, and those who later changed their minds found the app vanished from the Microsoft Store. The new setting provides a single point of control.

What This Means for the Future of Copilot

Microsoft’s decision to ship a removal policy suggests the company is acknowledging that not every organization wants AI integrated into the operating system layer. It mirrors past moves: the ability to hide OneDrive notifications, block Cortana, or disable Windows tips through Group Policy. As Copilot evolves into a subscription-based productivity suite (Microsoft 365 Copilot) alongside the free consumer version, granular management becomes essential for enterprise adoption.

Looking ahead, Microsoft is expected to deepen Copilot’s integration with Windows 11, including Copilot+ for specialized AI hardware and deeper hooks into File Explorer, Settings, and security tools. The admin policy documented for April 2026 may be the first in a series of controls that let IT departments decide exactly which AI features reach their endpoints. Expect companion policies for Copilot in Edge, Microsoft 365 apps, and even the Copilot key itself.

For now, the Turn off Microsoft Copilot policy gives administrators a binary choice: on or off. But given the pace of AI updates, future iterations might offer more nuanced options—for instance, restricting Copilot to specific user groups, disabling only certain chat modes, or blocking connectivity to external services while allowing local AI processing.

Conclusion

The wait until April 2026 may feel long for organizations struggling with AI governance today. In the interim, admins can use existing controls: unpinning Copilot from the taskbar via a customized Start layout XML, blocking the app with AppLocker or Windows Defender Application Control, or redirecting the Copilot website via DNS filtering. None of these are as clean as the built-in policy, but they can serve as stopgaps until the update lands.

For Windows 11 24H2 and later, this policy represents a maturing of Microsoft’s enterprise AI strategy—one that prioritizes admin choice alongside innovation. When the setting arrives, it will be a welcome addition to the Group Policy catalog and a signal that user agency over AI features is here to stay.