How to Turn Off Copilot

A practical walkthrough of every switch you need to hit, plus the data paths that survive after you flip them.

Key Takeaways

• There is no single master switch. Copilot is embedded across the Windows taskbar, Edge, Notepad, File Explorer, and every Microsoft 365 app, each with its own toggle. Knowing how to turn off Copilot means hitting all of them.
• Turning off the visible UI does not turn off the data flow. In our testing, Outlook's Copilot add-in continued background telemetry and data routing after we dismissed it. Cookie imports from Edge persisted after we disabled the taskbar icon.
• A buried, default-on "Memory" setting lets Copilot pull data from Bing, MSN, Edge, and other Microsoft products you've used. Most guides never mention it.
• Microsoft added a new Group Policy in the April 2026 Windows 11 update specifically because Copilot kept returning after removal, including on fresh installs.
• The agentic shift (Copilot Actions) means "off" now involves more than UI toggles: you need to check filesystem permissions granted to agent accounts that persist even when the feature is visually disabled.

Why Is There No Single "Off" Switch for Copilot?

Because Copilot is not one feature. It is a layer spread across a dozen Microsoft surfaces, each with its own launch path and its own data pipeline. The taskbar icon, the Win+C shortcut, the hardware Copilot key, Start menu search, Edge sidebar, app-specific ribbon buttons in Word and Excel, the Outlook add-in, Notepad, File Explorer: these are all separate integration points. Disabling one does not touch the others.

Microsoft's own Q&A forums confirm there is no permanent, universal fix. Their rollout process can silently re-enable settings you thought you'd locked down. This is not a conspiracy theory; it is the documented behavior of a platform that treats AI integration as a rolling deployment.

We run a product (Selina) that also calls frontier model providers via API for inference. We understand the engineering reasons why a tightly integrated assistant touches many subsystems. But understanding the reason does not make the user's job easier. So here is every toggle, policy, and registry key we found during our own testing, laid out in the order that actually matters.

How Do You Remove Copilot from the Windows 11 Taskbar and Sidebar?

Right-click the taskbar, select "Taskbar settings," and toggle off Copilot. This removes the icon and the sidebar launch point. It does not uninstall anything.

For a harder removal, open Settings, navigate to Apps, find "Microsoft Copilot," and uninstall. On builds prior to the April 2026 update, this sometimes failed silently or reversed after a cumulative update. The April 2026 update introduced a dedicated Group Policy called "Remove Microsoft Copilot app" specifically to address the fact that Copilot kept reinstalling itself. That Microsoft had to ship a new policy for this tells you everything about how reliable the previous removal methods were.

To apply the Group Policy: open gpedit.msc, navigate to Computer Configuration > Administrative Templates > Windows Components > Microsoft Copilot, and enable "Remove Microsoft Copilot app." For Windows Home editions that lack gpedit, you can set the equivalent registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Copilot
DWORD: RemoveCopilotApp = 1

A thorough 2026 guide from Windows Forum walks through additional removal methods, including PowerShell uninstall commands via winget uninstall "Microsoft Copilot". We ran all three approaches (Settings uninstall, Group Policy, winget) on clean Windows 11 builds. The Group Policy was the only one that survived two consecutive cumulative updates without Copilot reappearing.

What About the Keyboard Shortcut and Hardware Key?

Win+C still triggers Copilot even after you remove the taskbar icon, unless you also apply the Group Policy or registry key above. If your device has a dedicated Copilot hardware key, you can remap it via Settings > Personalization > Text input > Customize Copilot key. Microsoft added this remapping option after complaints, but it defaults back after feature updates on some OEM devices. Check it after every major update.

How Do You Disable Copilot Inside Microsoft 365 Apps?

This is where the gap between "off in the UI" and "off in practice" gets wide.

Microsoft's official support page tells you to go to File > Options > Copilot and uncheck the relevant boxes, or to remove the Copilot button from the ribbon via "Customize Ribbon." Both of these hide the visible interface. Neither stops Copilot from being reachable through the right-click context menu, and some users report it resurfacing in the ribbon after app updates.

The activity history behavior is also inconsistent by design. In some apps (and on some devices), Copilot starts with a blank slate each time you reopen the app. In Word, Excel, and PowerPoint on Windows and web, activity history remains visible across sessions. There is no universal setting that governs this. You have to check each app individually.

The Outlook Problem

Outlook deserves its own section because it is the worst case we found.

In Outlook for Microsoft 365, Copilot runs as a separate add-in process with its own enable/disable flag. Clicking the "X" to dismiss the Copilot panel does not disable the add-in. It does not stop telemetry. It does not stop data routing to AI endpoints. It closes a panel.

To actually disable the add-in: go to File > Manage Add-ins (or Home > Get Add-ins > My Add-ins), find the Copilot add-in, and disable it. In our testing, we confirmed with Process Monitor that the add-in process was no longer loading after this step. But the add-in re-enabled itself after a policy push in a managed (enterprise) environment, so if your organization controls your Office deployment, this may not stick.

How Do You Disable Copilot in Excel Specifically?

Microsoft's own answer thread for Excel points to the same File > Options > Copilot path. The toggle there controls whether the Copilot button appears, not whether Excel sends usage data to Microsoft's AI services. If you have a Microsoft 365 subscription with Copilot entitlements, the underlying service connection exists regardless of the button's visibility. For enterprise admins, the only reliable approach is to remove the Copilot license assignment from the user account entirely.

How Do You Stop Copilot in Microsoft Edge?

Edge has its own Copilot sidebar, and it has a data-sharing behavior that most guides skip entirely.

To remove the sidebar: open Edge, go to Settings > Sidebar, and toggle off Copilot. You can also disable it via the edge://flags page by searching for "Copilot" and setting relevant flags to Disabled.

The less obvious issue: Copilot for Windows can import browsing cookies and site data from Edge every time it launches. This is controlled via a separate toggle in the Copilot app's Profile > Settings > Browsing settings > Sync and import > "Bring over your site data from Microsoft Edge." This setting is independent of whether you've disabled Copilot in Edge itself. You can have Copilot removed from Edge's sidebar while the Windows Copilot app still pulls your Edge cookies on every launch.

We tested this by disabling Copilot in Edge, then launching the standalone Copilot app and checking whether it had access to logged-in session context from Edge. It did, until we found and disabled the cookie-import toggle. This is the kind of thing that makes "how to turn off Copilot" a more involved question than it appears.

What Is the "Memory" Setting and Why Is It On by Default?

This is the setting most people miss.

Microsoft added a "Memory" or personalization setting that permits Copilot to pull in data from Bing, MSN, Edge, and other Microsoft products you've used. It was turned on by default for many users. There is a secondary control labeled "Microsoft usage data" that is also on by default.

To find these: open the Copilot app or copilot.microsoft.com, go to Settings > Personalization (the exact path varies by build), and look for "Memory" and "Microsoft usage data." Turn both off.

What this means in practice: if you disabled the Copilot taskbar icon, removed it from Edge, toggled it off in Word, and felt satisfied, Copilot's personalization engine was still aggregating your activity across Microsoft's entire product surface. The "off" you achieved was cosmetic. The data pipeline was intact.

Does Disabling the UI Actually Stop Data Collection?

No, or at least not completely, based on what we observed.

We ran a series of tests across three clean Windows 11 machines (24H2 and the April 2026 build) with varying levels of Copilot disablement. Here is what we found still active after each level:

Level 1: Taskbar icon removed, Copilot dismissed in Office apps. Edge background processes still running with Copilot-related service connections. Outlook add-in still loaded. Memory/personalization settings still on. Cookie import from Edge still active.

Level 2: Level 1 plus Outlook add-in disabled, Edge Copilot sidebar off, Memory and usage data toggles off. The standalone Copilot app process still appeared in Task Manager after boot. Other users have reported the same: background text analytics and analysis processes running even after the user-facing feature is disabled.

Level 3: Level 2 plus Group Policy removal, winget uninstall, registry key set. This was the first configuration where we saw no Copilot-related processes in Task Manager and no unexpected outbound connections in our network monitor. But it did not survive the next cumulative update on one of the three machines (the one running the older 24H2 build without the April 2026 Group Policy).

The takeaway is blunt: the visible UI and the data machinery are separate systems. Microsoft's own documentation does not clearly state which backend processes stop when which frontend toggles are flipped. You have to verify empirically.

What About GitHub Copilot and Code Telemetry?

If you use GitHub Copilot for code completion, the privacy model is different from Windows Copilot but has its own wrinkle.

You can opt out of having your code used for AI model training via GitHub's settings (Settings > Copilot > "Allow GitHub to use my code snippets for product improvements"). Opting out stops future data collection and does not reduce Copilot's functionality. However, GitHub cannot guarantee the removal of data already used in prior training runs. If your code was collected before you opted out, it may remain in existing training sets. DataCamp's analysis covers the telemetry pipeline in more detail.

For the IDE extensions, some users have found that disabling the Copilot extension does not fully stop telemetry pings from the language server process. Uninstalling the extension entirely is the cleaner path.

Why Does the Agentic Shift Make This Harder?

Because "off" used to mean "the assistant isn't responding to my prompts." Now it also needs to mean "the assistant's agent accounts don't have standing filesystem access."

Microsoft's Copilot Actions feature lets AI agents perform real tasks: organizing files, scheduling meetings, sending emails. Each agent runs under its own standard Windows account with default access to Documents, Downloads, Desktop, and Pictures. The feature is labeled experimental and is off by default (Settings > System > AI components > Agent tools > Experimental agentic features).

But here is what we wanted to verify: when you toggle the feature off, does the agent account lose its filesystem permissions? In our testing on a Windows 11 Insider build, disabling the toggle stopped the agent from initiating new actions. The agent's user account, however, still existed on the machine with its folder-level access intact. The account was not deleted or demoted. Someone (or something) with access to that account could still read your Documents folder.

Microsoft itself flagged the security risk, warning that the experimental AI agent could potentially infect devices and access sensitive user data. Signal Foundation president Meredith Whittaker went further, arguing that AI assistants and agents with deep system access should never be treated as trusted confidants, particularly without end-to-end encryption.

This matters for the "how to turn off Copilot" question because the traditional advice (toggle, uninstall, set a registry key) does not address standing permissions granted to agent accounts. The attack surface has expanded beyond UI toggles into identity and access management.

What About Enterprise Environments?

If your organization runs Microsoft 365 with Copilot licenses, the individual toggles described above may be overridden by organizational policy. Admins can disable Copilot at the tenant level, but a recent analysis argues the real enterprise risk is not Copilot gaining new access but Copilot exposing pre-existing oversharing. A broadly shared SharePoint library, an old mailbox delegation, a Teams site with lax permissions: these become useful context for the assistant even though no new permission was granted. Copilot does not create the oversharing problem. It makes it trivially discoverable.

Microsoft's response to the OWASP Top 10 for Agentic AI describes their mitigation approach, but the practical takeaway for admins is: audit your permissions before enabling Copilot, not after. Turning Copilot off after it has already indexed broadly shared content does not un-index it.

Policy names and CSPs have shifted across Windows 11 releases, with some legacy policy mappings deprecated. If you are managing a fleet, verify your policies against the current build's ADMX templates. Do not assume a policy that worked on 23H2 still applies on the April 2026 build.

The Full Checklist

Here is every step, in order, that resulted in no detectable Copilot activity in our testing:

1. Open Settings > Apps, find "Microsoft Copilot," uninstall.
2. Apply Group Policy: Computer Configuration > Administrative Templates > Windows Components > Microsoft Copilot > "Remove Microsoft Copilot app" = Enabled. Or set the equivalent registry key.
3. Open Edge > Settings > Sidebar, disable Copilot.
4. In Edge, go to edge://settings/profiles and disable any Copilot-related sync options.
5. Open each Microsoft 365 app (Word, Excel, PowerPoint, Outlook). In each: File > Options > Copilot, uncheck all boxes.
6. In Outlook specifically: File > Manage Add-ins, find the Copilot add-in, disable it.
7. Open copilot.microsoft.com or the Copilot app settings. Turn off "Memory" and "Microsoft usage data."
8. In the Copilot app (if it still exists): Profile > Settings > Browsing settings > disable "Bring over your site data from Microsoft Edge."
9. Settings > System > AI components > Agent tools > disable "Experimental agentic features."
10. Check Computer Management > Local Users and Groups for any agent-created accounts. Remove if present and not needed.
11. Run winget uninstall "Microsoft Copilot" from an elevated terminal for good measure.
12. After the next Windows cumulative update, verify steps 1, 2, 5, 6, and 7 again.

Step 12 is not optional. We watched Copilot return on one of our test machines after a cumulative update applied to the older build. The April 2026 Group Policy held on the other two.

What We Learned Building a Different Kind of Assistant

We build Selina, a privacy-focused AI assistant that remembers you across conversations. It runs on a stack of frontier models, routed per task, accessed via API. We are not running inference locally on your device. A slice of each request reaches a frontier provider at inference time. Memory is encrypted at rest, but it is not end-to-end encrypted. We say this plainly because the alternative is to pretend the constraint does not exist.

Building a product like this gives you a very specific lens on the Copilot situation. When we see the gap between "UI off" and "data pipeline off," we recognize it because we have spent years thinking about what "off" should actually mean in a system that depends on external model providers. The honest engineering answer is that any assistant calling a frontier API has a trust boundary at the provider. The question is whether the product's architecture minimizes what crosses that boundary, and whether "delete" means the data is actually gone.

In Selina, delete means gone. Actually gone. Files and transfers via SelinaSend are zero-knowledge encrypted. Non-content operational metadata is kept for a short retention window, not indefinitely. We designed it this way because we wanted "off" to be a data state, not just a UI state.

None of this makes Copilot a bad product for everyone. It makes it a product where "turning it off" requires more diligence than most users expect, and where the meaning of "off" varies by surface, by app, by build, and by update cycle. If that bothers you, now you have the full checklist. And if you want an assistant where the privacy architecture was the starting constraint rather than a retrofit, start a free 7-day trial, no card required.

Michael C.

Founder & Principal Engineer, Selina Labs

Michael builds Selina, a privacy-first AI that remembers you across conversations. He ships security-sensitive AI in production — real attacks, real fixes, measured in minutes and dollars — and writes about privacy, security, and LLMs from that seat. Top Rated Plus and expert-verified on Upwork.

• www.upwork.com
• x.com
• medium.com
• selinalabs.io