Copilot’s whole value is that it reads across Microsoft 365 — Teams chats, SharePoint documents, OneDrive files — and answers in context. The catch is that it does not, on its own, know which of that content is current and which is junk. If Teams is full of abandoned channels and SharePoint is carrying sites no one has opened in a year, Copilot pulls from all of it. If sensitive documents are not labeled, they can surface in answers they should never appear in.
We have watched this play out. A Copilot pilot returns a three-year-old draft as if it were the live version, a few people notice, and trust evaporates faster than it was built. The fix is not a better prompt. It is a cleaner environment underneath. That work falls to IT, and it is worth doing before the rollout, not after the complaints.
Three places the clutter hides
Almost all of it lives in three systems, each needing a different kind of attention.
Teams accumulates channels faster than anyone retires them. Channels idle for months still carry old project chatter that muddies Copilot’s sense of what is current.
SharePoint is where dormant sites pile up quietly. Every stale site is more noise in the pool Copilot scans.
OneDrive is less about clutter than exposure. The risk is an unlabeled sensitive file — an HR document shared more widely than intended — turning up in a summary because nothing told Copilot to leave it alone.
How the cleanup gets done
The work is methodical, and most of it happens in admin tools you already have.
For Teams, review active channels in the Teams admin center and sort by last activity. Anything idle for 90 days or more is a candidate to remove; deletions sit in a recycle bin for 30 days, so there is room to be wrong. For larger sweeps, PowerShell handles batches. The one rule: tell channel owners before you delete, so cleanup does not feel like loss.
For SharePoint, sort active sites by last activity in the admin center. Dormant sites can be archived rather than deleted, which preserves them without leaving them in Copilot’s scope. Truly obsolete sites can go entirely. Shrinking the pool of content Copilot reads is one of the most direct ways to improve what it returns.
For OneDrive, the work is labeling. In Microsoft Purview, set up a simple scheme — Public, Internal, Confidential — and get people applying Confidential to HR and financial material, which Copilot will then respect based on permissions. Turn on auto-labeling for obvious PII like SSNs and card numbers so the most sensitive data is covered without relying on anyone to remember.
Then test before you trust it. Run a small pilot — a handful of users querying something like “recent project updates” — and confirm only current, secured content comes back. That is also when you tune retention (we usually land around 90 days for Teams chat) and tidy metadata.
The obstacles are predictable
A few things reliably come up. Teams users resist deletions because they fear losing history — export the chat logs first via the Compliance Center and the objection mostly disappears. In SharePoint, the hard part is telling a disposable dormant site from a critical one that simply sits quiet; check with team leads before archiving rather than guessing. In OneDrive, manual labeling always lags, so audit weekly in Purview’s Activity Explorer to catch what slipped through. And when the volume is too large to work by hand, PowerShell will list and prune far faster than clicking through.
Why it is worth the effort
A clean environment is the difference between Copilot that earns its seat and Copilot that gets quietly abandoned. When the content it reads is current and secured, the answers are accurate, IT stops fielding “why did it say that” tickets, and the people you are trying to win over actually keep using it. The cleanup is unglamorous, but it is the foundation everything else stands on.
Keep it from sliding back by pulling the Teams and SharePoint usage reports monthly, setting Purview alerts for untagged files, and testing a Copilot query now and then to confirm the cleanup is holding.