Before you switch on Copilot: the permissions problem it inherits
· 5 min read · Gary Johnston
- Microsoft 365
- AI security
- Data governance
Copilot creates no new access. It makes the access people already have usable, and years of oversharing become one question away. Readiness means containing the worst of it, not cleaning the whole tenant first.
The usual story goes like this. Someone is given a Microsoft 365 Copilot licence budget and a rollout date. Somewhere in the planning, a security or data protection lead asks what Copilot will be able to see. The honest answer is “everything each user can already see”, and the room goes quiet, because nobody knows what that is.
Copilot doesn’t create new access. Microsoft is explicit that it retrieves content through Microsoft Graph and respects existing permissions, sharing settings and policies. That is accurate, and it is also the problem. Copilot makes the access people already have usable.
Obscurity was doing more work than anyone realised
In most tenants, a large amount of content is technically reachable by far more people than should reach it, and in practice nobody finds it. Finding a document used to take three things: knowing it existed, knowing roughly where it lived, and searching for the right words. Obscurity quietly did the job permissions were meant to do.
A natural-language assistant removes all three. Nobody has to go looking for the restructuring plan. Someone asks what is happening with their team, and the answer is assembled from whatever they can open. The usual sources are unremarkable:
- A team site shared years ago with Everyone except external users, because it was quicker than working out who needed it.
- “People in your organisation” links created to send one board pack to one person, which work for anyone who has the link.
- Broken permission inheritance: one folder in an otherwise locked-down site that someone opened up for a project that ended in 2021.
- Large Teams, where a channel with several hundred members once hosted a conversation that was only ever meant for five.
None of this is a Copilot defect, and none of it is new. Copilot just makes it matter.
Don’t make “clean the tenant” the gate
The instinctive response is to make a full permissions clean-up a precondition of rollout. It sounds responsible, and it never finishes. A tenant with a decade of sites cannot be re-permissioned before a rollout date, and a programme that tries ends in one of two ways. Either the rollout slips indefinitely, or it goes ahead anyway with the clean-up quietly abandoned.
A better gate is narrower and can actually be passed: the content where sensitivity and broad access overlap is contained. That is a list you can build, work through and evidence, and it has a date you can hold.
A sequence that finishes
- Measure before you argue. SharePoint’s data access governance reports show permission states across sites and OneDrive, which sites use “Everyone except external users”, and where sharing links are created most. Start with the facts about your own tenant, not the vendor’s readiness checklist.
- Triage on the overlap. Broad access alone isn’t the problem. A widely shared canteen menu is fine. Sensitive content alone isn’t either, if the right twelve people can see it. The risk is where both meet: HR, deals, legal, board material, client data. In most organisations that is dozens of sites, not thousands.
- Contain those sites now, and fix them properly later. Restricted Content Discovery takes a site out of Copilot and organisation-wide search without touching its permissions. Restricted Access Control limits a site to a named group, whatever links and permissions say. Be clear which one you have used: content discovery restriction is a containment measure, and anyone who already has the link still gets in.
- Fix the defaults so the problem stops growing. Make the default sharing link “specific people” rather than the whole organisation, put an expiry on links, and require every site to have an owner. Otherwise the clean-up is permanent.
- Use the labels you already have. If sensitivity labels are already applied, a Purview DLP policy on the Microsoft 365 Copilot location can stop labelled content being used in responses. Don’t start a labelling programme as a precondition of rollout. That is the “clean the tenant” gate in another form.
- Pilot with people who will tell you. Pick a pilot group that spans departments, and give them one simple route to report “Copilot showed me something I shouldn’t have seen”. Treat each report as a permissions incident on the underlying content. The fix is to the content, not to Copilot.
After switch-on
The work doesn’t end at rollout. Rerun the oversharing reports monthly and watch the trend, not the absolute number. Make sure Copilot interactions are captured in your audit logging before you need them, not after an incident. Review the contained-site list quarterly: every site on it is either fixed and released, or deliberately kept out of Copilot with an owner’s name against the decision.
What to say in the steering meeting
For the person holding the deadline: the rollout isn’t blocked on a perfect tenant. It is gated on a short, named list of high-risk sites being contained, a small pilot group, and a route for surprises to be reported. That is a position a security team can sign off, and a plan a delivery team can hit.
It also leaves you somewhere better than before you started. The oversharing was already there. Copilot made it impossible to ignore.
Written by Gary Johnston, Principal Security Architect at Cairn Cyber Advisory Ltd. CISSP, CCSP. Nothing here describes any client's environment.
More insights
Your model provider is an ICT third party. Most registers don't say so.
An LLM behind a business process is an ICT third-party dependency under DORA and the UK outsourcing rules. It usually arrives without a procurement event, so it is usually missing from the register, the contract review and the incident process.
ISO 42001 readiness without building a second bureaucracy
ISO/IEC 42001 asks for a management system for AI. With ISO 27001 in place most of the structure exists already; readiness is about the parts that are new.