Purview & DLP
Does historically overshared SharePoint still ground Copilot?
Yes, if a licensed user can already open them. Copilot does not create a new SharePoint permission. It summarises existing ACLs — including Everyone, Anyone links and “except external users”. Sensitivity labels and Purview DLP only stop that if they are applied and if Microsoft 365 Copilot is a location in the policy.
Reviewed by Datalegale · last source check 24 August 2026Score before any emailNot legal advice
What to do next
Run sharing reports before the licence wave. A label taxonomy that is not applied is not a control. DLP that omits Copilot as a location will not see the chat.
Questionnaire and contact
This is a self-assessment, not a certificate and not legal advice. Work through the questionnaire at /assessments/oversharing-purview/start. You see a result before any email. If your organisation needs consultation, implementation or development of Microsoft 365 Copilot controls in an EU tenant — or you simply have a question — write to hello@datalegale.com.
Copilot does not bypass permissions. It accelerates them.
The Copilot oversharing problem is not a new ACL. It is retrieval. A licensed user asks a question. Copilot grounds on anything that user can already open. Files shared with Everyone in 2019, Anyone links that were never expired, and broad Microsoft 365 groups become answers in a chat. People did not go looking for the personnel folder. Copilot did, because the identity could already open it.
That is why a clean EU Data Boundary configuration does not save you. You can keep every token in Europe and still disclose a customer contract in a Teams chat. Extra-EU processing and oversharing are different harms. Mixing them in one “Copilot risk” score hides the one you can actually fix this quarter: sharing hygiene.
Sensitivity labels only work where they are applied
A published Microsoft Purview label taxonomy is not a control. Coverage is. Labels that never reach HR, legal and finance libraries will not stop Copilot summarising those libraries. Downstream controls — encryption, Restricted Content Discovery, DLP — inherit the same gap. An 8% labelled corpus with a perfect information-protection policy is a policy, not a barrier.
Restricted Content Discovery is the holding control while you remediate: Copilot can be stopped from using labelled content as grounding even when the user could open the file. Use it as a bridge, not as a substitute for fixing shares.
DLP must list Microsoft 365 Copilot as a location
Labels classify. DLP enforces. Existing Exchange and SharePoint DLP policies that never list Microsoft 365 Copilot as a location will not inspect Copilot chat. The model will return the same sensitive content the email policy would have blocked on the way out. Adding Copilot as a location is a configuration change, not a new product purchase — and it is the change most tenants skip because “we already have DLP”.
Encrypted or otherwise technically blocked content is the other half. If Copilot can decrypt or retrieve what DLP thinks is sealed, the DLP story in the DPIA is wrong. Test with a distinctive labelled file, a pilot user, and a prompt that should fail. Put the test date in the governance file.
Order of controls before a licence wave
Assess sharing (SharePoint sharing reports, Everyone / Anyone, guest links). Apply labels to personal and confidential content that Copilot must not casually retrieve. Use Restricted Content Discovery while you remediate. Extend DLP to Copilot. Then expand licences. Reverse that order and every historical link becomes a faster interface.
7 questions · ~4 min. Score and first risks before any email
Does not score Flex Routing or DPIA paperwork.
Read first
- Do SharePoint labels stop Copilot seeing a file?
Labels are a primary control that can limit what Copilot can access or return. A taxonomy that is not applied is not a control.
- Do your DLP policies include Copilot?
Standard DLP is not automatically sufficient. Policies should explicitly include Microsoft 365 Copilot as a location where the platform supports it.
FAQ
Does historically overshared SharePoint still ground Copilot?
Yes — if a licensed user can already open those files. Copilot follows existing ACLs. Labels and DLP only constrain it where they are applied and where Copilot is a DLP location.
Is this a Microsoft Graph oversharing scan?
No. It is a control-readiness questionnaire. You still need SharePoint sharing reports or a Purview assessment in the tenant.
Do sensitivity labels stop Copilot?
Only where they are applied and where downstream controls (DLP, Restricted Content Discovery, encryption) are configured. A published taxonomy with 8% coverage will not save a rollout.
Why is DLP a separate question from labels?
Labels classify. DLP enforces. Policies that never list Microsoft 365 Copilot as a location will not see Copilot chat as a channel.
Can Datalegale help after the score?
Yes. The questionnaire is a self-check. For consultation, implementation, development, or questions about Copilot in your tenant, write to hello@datalegale.com.
Other assessments — not the same questionnaire
- Safe Copilot Rollout: Identity Before Broad Access
Copilot uses the signed-in user’s permissions. Standing admin roles, missing Conditional Access MFA, and guest access widen what a prompt can retrieve. Guests matter even without Copilot licences: they often still sit on the ACLs licensed users retrieve. Unbounded licence assignment copies every other gap to more people. A safe Copilot rollout in the EU is still a bounded pilot — not an E5 checkbox.
- Microsoft 365 Copilot Readiness Assessment (EU)
It can be, but not by turning the product on. Microsoft 365 Copilot GDPR compliance in 2026 depends on EU Data Boundary settings, Flex Routing, oversharing in SharePoint and OneDrive, identity, DLP, and a DPIA you actually hold. A tenant in Europe is not the same as Copilot staying in Europe. Use this pack when the board wants one score. Use the topic assessments for Flex Routing, EUDB, Foundry and DPIA detail.
- Is Microsoft’s Copilot DPIA Template Enough?
Microsoft’s “Build your own” Microsoft 365 Copilot DPIA is a starting file, not the record. Article 35 still needs tenant facts the template cannot know: the Flex Routing value and whether extra-EU inferencing is a transfer, whether historically overshared SharePoint still grounds Copilot, whether DLP lists Microsoft 365 Copilot as a location, web grounding, Anthropic models, commercial vs consumer licensing, and a named owner. A score is not that file.