Almost every Copilot pilot we have paused was paused for the same reason, and it was never the model. It was a clinician typing a reasonable question and receiving a document they were technically permitted to open and had no business reading.
The permission debt was always there. What changed is that finding it used to require knowing the file existed.
Why healthcare estates overshare more than most
Clinical work is collaborative and urgent, and SharePoint's sharing model rewards speed. A consultant needs a protocol document at eleven at night, so somebody shares it with everyone in the organization because that link works immediately and a permissions request does not.
Repeat that for ten years across a merged estate that has absorbed two acquisitions and a handful of departmental site collections nobody has audited, and you have a document library where the effective permissions bear no relationship to anyone's intent.
Microsoft's own tooling now reflects how common this is. SharePoint Advanced Management has grown into a content governance suite with reporting for files shared with Everyone Except External Users — the specific pattern that causes most of this — because enough organizations needed it.
What a readiness assessment actually looks for
Not a list of sites. A list of content that is reachable by more people than the owner believes, weighted by how sensitive it is.
- Sites where broad-access sharing links have been used on libraries containing patient-identifiable material
- Permission inheritance that was broken years ago and never reviewed
- Sites with no active owner, where nobody can approve a change
- Content with no sensitivity label, in libraries where labelling was assumed to be automatic
- Guest and external access that outlived the project that justified it
The sequence that works
Discovery first, remediation second, deployment third. Organizations that reverse the first two spend the pilot period arguing about individual documents instead of learning whether Copilot helps.
In practice, remediation is less painful than leadership expects. Most oversharing concentrates in a small number of sites, and fixing those covers the majority of the exposure. The work that takes time is the governance decision underneath — who is allowed to share broadly, and what happens when they leave.
Where this is heading
Microsoft is positioning SharePoint as the trusted content backbone for Copilot, with agents that clean up metadata, flag stale content and make libraries answerable. That direction only helps organizations whose permission model is already sound.
If your AI roadmap is ahead of your data governance, the two meet here. It is cheaper to find that out during an assessment than during a pilot.
What to take away
- Run a permission and oversharing assessment before assigning a single Copilot licence
- Expect the exposure to concentrate in a small number of sites — remediate those first
- Treat sensitivity labelling as a prerequisite, not a follow-up project
- Give every site an accountable owner before you give it an agent
- Budget for a delay: six weeks of remediation is normal and far cheaper than an incident
Where to go from here
If Copilot is on your roadmap for this financial year, the readiness assessment belongs in this quarter's plan rather than next. We run these as a scoped, fixed-price piece of work and the output is yours whether or not you go further with us.