Think about the keys to your office.
Not the front door. All of them. The ones cut for the cleaners in 2014, the contractor who did the refit, the temp who covered reception for a summer, the master key somebody made “just for the move” and never handed back. Nobody keeps a register. Nobody needs to, because in practice nobody walks round the building at night trying every key in every door.
Now imagine you hire an assistant who does exactly that, and never tires of it. Give them your key and a question, and they’ll try every door your key opens, read everything inside, and come back with a neat summary in seconds.
That’s Microsoft 365 Copilot. And this week Microsoft made it better at finding things, while the controls on what it finds are still in preview.
What Microsoft actually says
Microsoft is admirably clear about how Copilot decides what you can see. In its own words, Copilot “only surfaces organizational data to which individual users have at least view permissions”. Then the very next sentence: “It’s important that you’re using the permission models available in Microsoft 365 services, such as SharePoint, to help ensure the right users or groups have the right access to the right content.”
It’s the second sentence that matters. Copilot doesn’t decide who should see what. Your permissions do. Copilot just stops pretending nobody will look.
This is the bit that gets lost in sales conversations. “Permission-aware” sounds like a safety feature, but all it promises is that Copilot won’t go anywhere your people couldn’t already go. Which is fine, if you know where that is.
Most organisations don’t. Until now it hardly mattered, because finding anything in SharePoint took effort. Copilot makes anything SharePoint already lets people open much easier to discover.
Ignite: better at finding, controls still to come
Microsoft Ignite opened on 17 November, and the announcements made Copilot and agents much better at finding things. New retrieval that helps agents “find relevant, permission-aware information” is generally available now, along with SharePoint as an indexed knowledge source for agents built in Foundry, and the runtime for apps people build just by describing them to Copilot. Every file Copilot creates for you “inherits Microsoft 365 permissions, sensitivity labels, and compliance controls from the start” - your permissions again.
And the control that would catch the worst of it? Purview’s new grounding protection, which will “block Copilot from referencing files with sensitive information even when those files are not labeled”, is in preview. Office Watch counted the whole conference: 215 separate features, of which 76 are generally available, and “most agent governance in Entra, Intune, Purview and Agent 365 is in preview”. Their advice was “Believe Copilot when you see it.” I’d add: believe your permissions when you’ve seen them.
See the problem? The tools that read your data are ready today; the tools that stop them reading the wrong data come later. Until then, what Copilot finds is whatever your tenant allows right now.
How permissions rot
Let’s suppose, just for a moment, a firm of a few hundred people.
In 2019 they moved their file shares into SharePoint. The migration ran late, the help desk was drowning in “I can’t find my folder” tickets, so somebody gave “Everyone except external users” read access to the HR and finance sites, just until things settled down. Things settled down. The access stayed.
Six years later a new joiner asks Copilot, “What do people at my grade get paid here?” Copilot, being helpful, finds the partners’ remuneration spreadsheet, a disciplinary file with a colleague’s name on it, and the papers for a deal that was never intended to leave the deal team. It summarises all three, with citations.
Nothing was hacked and no rule was broken. Every one of those files was permission-aware. The new joiner had access from the day they started; they just didn’t know where to look, and now they don’t need to.
It doesn’t take a dramatic mistake. Permissions rot quietly, one sensible shortcut at a time:
- Big groups like “Everyone except external users”, which means every member of staff, present and future. Microsoft’s own guidance flags it, alongside “People in your organization” links, as a higher risk of oversharing.
- Every “share with people in my organisation” link someone made to save time, still there long after the reason has gone.
- Sites whose owners left years ago, which nobody reviews because nobody owns them.
- Permissions broken one folder at a time, so a site looks locked down from the top and leaks halfway down.
- People who change jobs and keep access to everything they had before.
None of these shows up when you look at one site. SharePoint shows you permissions a site at a time, which is a bit like checking your locks by standing in each doorway in turn. What you need is the view across the whole building, and almost nobody has it.
The view across the building
That’s the view we built the JFDI Copilot Readiness Assessment Tool to give you.
You run it against your own tenant, on your own machine; no tenant assessment data comes to us. Give it a SharePoint permissions export and it works out a Copilot Rollout Risk Score, out of 100, for how exposed you are to oversharing, with the findings behind it. It also checks everything else Copilot depends on, across Microsoft 365, Entra, Defender, Purview, Power Platform and Copilot Studio.
Microsoft’s own free readiness check is worth running too. It runs 182 licence and feature checks and gives you a list of recommendations. Ours starts from the same tenant data and adds 43 cross-domain assessments. You get a scorecard, a phased plan to fix what it finds with an owner for every finding, and reports you can take to the board. Run it again a few months later and it tells you what’s been fixed and what’s crept back.
You can download it free today and see what it makes of your Entra ID. The full assessment, including the SharePoint risk score, is a per-tenant licence, or a subscription through Microsoft Marketplace on your existing Microsoft agreement. And if you’d rather we did it, we’ll run the assessment for you and do the fixing too.
What to do before you switch it on
Even Microsoft’s own deployment blueprint puts “remediate oversharing” first, before guardrails and regulation. Here’s the order I’d do it in.
- Find out who can see what, across the tenant, not site by site. Start with the big groups, the organisation-wide links and the sites nobody owns. Until you’ve seen this, every other decision is a guess.
- Protect the obvious first: HR, finance, board papers, client matters, deal rooms. You know where the sensitive material lives; check those sites before anything else.
- Use the stopgap, and know it’s a stopgap. Restricted Content Discovery hides chosen sites from Copilot and organisation-wide search without changing who can open them. Microsoft calls it “a temporary governance control”, and on big sites it can take over a week to take effect. It buys time, but it doesn’t fix anything.
- Fix the permissions properly. Remove the big groups, kill the stale links, give every site an owner who’ll answer for it.
- Check again. Permissions rot back, so measure before and after, then again in three months.
And don’t wait for the preview features. They’ll be useful when they arrive, but “Microsoft will probably fix it in a future release” isn’t a risk assessment you can take to the board.
Copilot is genuinely useful. I’d rather people used it than not. But it’s the first thing in most organisations that will actually try every door, and it does it on behalf of whoever asks. Don’t hand it the keys until you know which doors they open.
Do you know which doors Copilot’s keys open?
The Copilot Readiness Assessment Tool runs on your own machine against your own tenant, scores your oversharing risk out of 100, and gives you a phased plan to fix it before Copilot finds it.

