Someone asked Copilot a simple question
A team leader asks Copilot to summarise recent documents about pay reviews, expecting their own team's notes. Copilot helpfully produces a summary that includes the company-wide salary spreadsheet from the finance site. Or a new starter asks about restructuring and gets extracts from a board paper. Nobody hacked anything. The files were reachable all along.
You now have a rollout that some staff love and a nervous HR and finance team asking for it to be switched off. The real question is how much else is exposed that nobody has asked about yet.
Why Copilot exposes it
Microsoft 365 Copilot works within each user's existing permissions. The trouble is that those permissions have drifted for years. A folder was shared with "everyone except external users" to fix an access problem quickly. A sharing link set to "anyone in the organisation" was sent round once and never removed. A Teams channel was made public. A departing manager's OneDrive was left open.
Before Copilot, this oversharing was mostly harmless in practice, because finding a file required knowing it existed and where it was. Copilot removes that obscurity. It searches everything a user can open and brings the relevant parts to the surface. Access that was always technically there is now actually used.
What the exposure risks
| Overshared content | Consequence if surfaced |
|---|---|
| Salary and bonus data | Staff relations problems and grievances |
| HR cases and absence notes | Personal data exposure and data protection issues |
| Board and restructuring papers | Rumours and loss of confidence before decisions are made |
| Client contracts and pricing | Breaches of confidentiality terms |
| Passwords in documents | Security risk well beyond AI |
Switching Copilot off hides the symptom but leaves the files exactly as exposed as before, to anyone who searches or browses.
How we fix the permissions underneath
- We run a permissions audit across SharePoint, OneDrive and Teams using the Microsoft Graph API and Microsoft 365 admin reporting, listing sites, libraries and files shared with large groups, the whole organisation or anonymous links.
- We identify the sensitive content in that list, looking for material such as payroll, HR, legal, board and client-confidential documents, using both content matching and a review with the owners of each area.
- We tighten access: removing organisation-wide and anonymous links, replacing broad groups with the right ones, restoring broken permission inheritance, and making private the Teams channels that should be private.
- We apply sensitivity labels to confidential content with Microsoft Purview where your licences include it, so protection travels with the file and Copilot handling respects it.
- We set sensible defaults for new sharing, such as specific people rather than the whole organisation, so the problem does not rebuild.
- We set up a regular report of new oversharing on sensitive sites, sent to the people who own them.
We work in order of sensitivity, fixing the highest-risk areas first so Copilot can stay on for the rest of the business while the cleanup continues.
What changes afterwards
Copilot keeps doing what people found useful, summarising their own team's work and finding documents they need, without pulling in the finance or HR material they should never have been able to open. HR and finance can see who has access to what, and get told when that changes.
The same fix protects you from ordinary search, a curious browse, or an attacker using a compromised account. Copilot just made the problem visible.
Owners of each area also get something they rarely had before: a plain list of who can open their content. Most are surprised by it the first time. After that, the regular report keeps it in front of them, and sharing decisions become deliberate rather than the quickest way to fix an access request.
Is this your situation?
- Copilot has surfaced confidential content to people who should not see it.
- Your Microsoft 365 tenant has grown for years without a permissions review.
- Files are regularly shared with "everyone" or by organisation-wide link.
- HR or finance have asked for Copilot to be turned off.
- You are planning a wider Copilot rollout and want to avoid this first.