Data security & Purview
Copilot, safe with your data
Yes, Microsoft 365 Copilot is safe with your data — provided your data protection is in order. Every prompt runs in your security context, so Copilot only cites what you may already access.
The starting point
Copilot inherits your rights
Copilot adds no access layer of its own. Every prompt runs in the security context of the requesting user — Copilot only sees what that person may already see and leans entirely on existing SharePoint, OneDrive and Exchange permissions. If you want to know how Microsoft Copilot works, then data security does not start with Copilot, but with who may access what.
The protection model
Four layers between question and answer
On top of your existing rights, four Microsoft Purview mechanisms go to work. Together they form a gate that every question passes before an answer arrives.
Question
Your prompt
You ask a question inside your own security context.
Layer 1
Sensitivity label
Classifies and encrypts content; helps decide whether Copilot may use it.
Layer 2
DLP for Copilot
Keeps labelled files and sensitive information out of the grounding.
Layer 3
Rights & grounding gate
Checks EXTRACT/VIEW usage rights and SharePoint permissions before retrieval.
Layer 4
Copilot response
Inherits the highest label from the sources — protection travels with it.
The mechanisms
Four protection layers
Each layer does one thing well. Together they keep sensitive data out of the wrong answers.
Sensitivity labels
Classify and encrypt. EXTRACT and VIEW rights decide whether Copilot may read.
DLP for Copilot
Keeps labelled files out of the summary. Citation stays visible, content does not.
Rights inheritance
Copilot runs in your security context — never broader than your own rights.
Oversharing remediation
Restricted Content Discovery takes overshared sites out of Copilot and search results while you clean up permissions.
Our conviction
Copilot does not leak — oversharing does.
The real risk
Oversharing, not Copilot
Permissions set too broadly suddenly become easy for Copilot to find. So the real work sits in cleaning up permissions — before and during the rollout. We start with a readiness scan and anchor the whole thing in your governance. What the Dutch DPA and the AI Act ask of you is covered in Copilot and the EU AI Act.
-
Restricted SharePoint Search (retiring)
Since 31 July 2026 it can no longer be newly switched on; on 31 January 2027 it stops. Settings do not carry over automatically — move to Restricted Content Discovery in good time.
-
Restricted Content Discovery
Take specific overshared sites out of Copilot and search results — including recently opened files and the Copilot buttons on those sites.
-
SharePoint Advanced Management
Data access governance and oversharing reports down to file level, plus the SharePoint Admin Agent for access reviews.
-
Lifecycle & sharing policies
Reduce oversharing over the long term; site owners help watch over it, delegated.
-
Authoritative sites
Designate official SharePoint sites, so Copilot gives trusted sources priority over old copies.
31 Jan 2027
The date Restricted SharePoint Search stops for good; Restricted Content Discovery takes over.
Our approach
From risk to protection
Consultancy, advice and development — we map the gaps and set up the protection layers.
- 1
Scan
We map oversharing and permission risks with a readiness scan.
- 2
Advice & design
We design label taxonomy, DLP rules and SharePoint controls around your risk profile.
- 3
Implementation
We set up the protection layers step by step — rollout continues during cleanup.
- 4
Monitoring
We keep labels, DLP and permissions healthy with ongoing monitoring and tuning.
FAQ
Frequently asked questions
On data security, Purview and oversharing.
Is Microsoft Copilot safe with our company data?
Yes, provided your data protection is sound. Copilot works within the Microsoft 365 service boundary and adds no access layer. Every prompt runs in your security context: Copilot only sees what you may already see.
Can Copilot show files I have no access to?
No. Copilot inherits your existing rights and can only summarise or cite content you are authorised for. The real risk is existing oversharing: permissions set too broadly suddenly become easy to find.
What exactly do sensitivity labels do with Copilot?
Labels classify and encrypt content. With encryption, the user needs EXTRACT and VIEW usage rights before Copilot processes the content. Generated output automatically inherits the highest label from the sources.
How does DLP keep sensitive data out of Copilot responses?
A DLP policy on the Copilot location keeps labelled files out of the summary. The item stays visible in the citations, but the content is not processed. With Purview network DLP you also keep sensitive data away from unapproved AI services.
How do you tackle oversharing before the Copilot rollout?
Restricted Content Discovery takes overshared sites out of Copilot and search results; SharePoint Advanced Management finds them. Still using Restricted SharePoint Search? It stops on 31 January 2027, with no automatic migration. So the rollout continues while you clean up permissions.
Which Microsoft licence do I need for these controls?
SharePoint Advanced Management is included with Microsoft 365 Copilot. For advanced Purview features, such as DSPM (Data Security Posture Management) with AI observability and Insider Risk Management, you typically need E5-level licensing or a Purview suite. In an advisory call we determine which combination fits your situation.
What is DSPM and what changes for DSPM for AI?
Data Security Posture Management (DSPM) in Purview gives you a single view of your data risks, including around Copilot, Copilot Studio agents and Foundry agents. The new, unified DSPM has been generally available since summer 2026, with AI observability and a posture agent. The classic DSPM for AI will be gone by 31 December 2026 at the latest — plan the move now.
What does the Dutch Data Protection Authority ask of Copilot users?
In July 2026, the Dutch Data Protection Authority (AP) advised the municipality of Haarlemmermeer not to deploy Copilot as described. The AP asks for concrete use cases, Copilot working only with classified and labelled data, meaningful human oversight and clarity from Microsoft about which data is processed. The first three you handle yourself with labels, DLP and a readiness scan; Microsoft’s clarification you track through the SLM Rijk and SURF DPIA frameworks.
Want to know where your data gaps are?
Our readiness scan maps oversharing and permission risks — with a concrete advisory report for your protection layers.