Microsoft Purview for Copilot is a set of Microsoft Purview data security and compliance controls that govern what Microsoft 365 Copilot can find, process, and return to your users, and that record what people ask it. In practice, Purview finds overshared content, labels and encrypts sensitive files, blocks Copilot from processing them, and audits every prompt and response.
Executive Summary
- Microsoft 365 Copilot only returns content a user already has permission to open, so oversharing in SharePoint and OneDrive becomes oversharing in Copilot answers.
- Purview Data Security Posture Management (DSPM) and SharePoint Advanced Management show you where that oversharing is before you widen your rollout.
- Sensitivity labels and Purview Data Loss Prevention (DLP) for the Microsoft 365 Copilot location keep labeled files, emails, and sensitive prompts out of Copilot’s processing.
- Several controls depend on your license. Blocking Copilot from labeled files with DLP requires an E5-level plan, while DLP for prompts is available to all Copilot and Copilot Chat users.
Why Copilot Oversharing Starts in SharePoint Permissions
Microsoft 365 Copilot oversharing starts with permissions that were already too broad. Microsoft states that “Copilot can only summarize or reference content that the user is authorized to access.” Copilot does not create new access. It makes existing access fast and easy to search.
A salary spreadsheet in a site shared with “Everyone except external users” was low risk when someone had to know it existed. Once a user can ask Copilot about compensation in plain language, it is one prompt away.
In the Microsoft 365 tenants we assess, we often find the same pattern: sites created years ago with broad membership, “Anyone” and company-wide sharing links that never expire, and libraries with no clear owner. Those settings rarely caused incidents while users had to know where to look. Copilot searches across all of them on every prompt. Our post on why your data structure matters more than the AI model covers how that debt builds up.
Why This Matters to You
You are accountable for data that Copilot can now surface in seconds. A single overshared HR, legal, or finance library can expose regulated data to every licensed user, and the audit trail will show that Copilot retrieved it under a valid permission. Nothing was breached, but sensitive data still reached people who should not have seen it.
Purview also gives you evidence for compliance reviews. Copilot prompts and responses are captured in the unified audit log, retention policies can keep or delete them, and eDiscovery can search them. If legal or an auditor asks what Copilot showed a user last quarter, you can answer.
Licensing also shapes your plan. Many Purview controls for Copilot are already in your Microsoft 365 plan, and knowing which ones you own keeps you from buying add-ons too early. Our Microsoft Copilot licensing webinar walks through those trade-offs.
How Sensitivity Labels Control What Copilot Can Use
Microsoft Purview sensitivity labels control Copilot through encryption and usage rights. When a label applies encryption, a user must have both the EXTRACT and VIEW usage rights for Copilot to return that content. If a user can open a file but lacks EXTRACT, Copilot will not use it in a response, according to Microsoft’s Copilot data protection architecture.
Labels also carry forward. When Copilot creates new content from labeled sources, the highest-priority sensitivity label is inherited where supported, and Copilot Chat can display the label of returned data.
There are practical limits to plan for:
- Turn on labels for SharePoint and OneDrive. Microsoft notes that when sensitivity labels are not enabled for these services, the encrypted files Copilot can access are limited to data in use from Office apps on Windows. Microsoft’s guide to enabling sensitivity labels for Office files in SharePoint and OneDrive covers the setting, which takes about 15 minutes to apply.
- Unlabeled content has no protection to inherit. Without a label, new items Copilot helps create get no automatic protection.
- Copilot agents cannot read files that use user-defined label permissions.
- S/MIME-protected email is not returned by Copilot, according to Microsoft’s overview of Purview protections for generative AI apps.
Can Purview DLP Stop Copilot From Using Sensitive Files and Prompts?
Yes. Microsoft Purview Data Loss Prevention for the Microsoft 365 Copilot location can stop Copilot, Copilot Chat, and Cowork from processing files and emails that carry selected sensitivity labels, and from processing prompts that contain sensitive information types such as credit card or passport numbers. Blocked items can still appear in citations, but their content is not used in the response.
Details from Microsoft’s DLP for Microsoft 365 Copilot documentation, updated November 10, 2026:
- Location: Microsoft 365 Copilot and Copilot Chat is available only in the Custom policy template, and other locations are disabled when you select it.
- Rule design: you cannot combine “content contains sensitive info types” and “content contains sensitivity labels” conditions in the same rule, so build separate rules.
- Prompt blocking: blocking sensitive information types in prompts is in preview and rolling out. When it triggers, the prompt text is not used for internal or web search.
- Email coverage: label-based blocking applies to emails sent on or after January 1, 2025. Calendar invites are not supported.
- Uploaded files: DLP cannot scan files a user uploads directly into a prompt.
- Timing: policy changes can take up to four hours to take effect, and Office apps evaluate the policy when a file is opened.
- Testing: simulation mode is available for Microsoft 365 Copilot and Cowork.
How Purview DSPM Finds Copilot Oversharing
Microsoft Purview Data Security Posture Management (DSPM) finds Copilot oversharing by running data risk assessments that show which SharePoint sites hold sensitive data and how broadly they are shared. The current version of DSPM, found under Solutions in the Purview portal, includes an objective named “Prevent data exposure in Microsoft 365 Copilot and Microsoft Copilot interactions.”
According to Microsoft’s DSPM overview, the current experience brings posture, objectives, AI observability, data risk assessments, and remediation actions into one place. The earlier tools are now labeled DSPM for AI (classic) and DSPM (classic).
Microsoft’s DSPM for AI (classic) documentation describes a default weekly data risk assessment of the top 100 SharePoint sites by usage, with a four-day delay before the first results appear. Its one-click policies include a DLP policy that blocks Copilot from processing items with selected labels. Microsoft 365 roadmap item 571157 adds a Copilot readiness view and a data explorer to DSPM, with preview listed for January 2027 and general availability for March 2027.
Pair DSPM with SharePoint Advanced Management. Its data access governance reports, site access reviews, and Restricted Content Discovery give site owners and admins the tools to fix what DSPM finds.
What Licenses Do You Need for Purview Copilot Protections?
Microsoft Purview protections for Copilot depend on your Microsoft 365 plan. Microsoft 365 E3 covers manual sensitivity labels, standard audit, DLP for prompts, and basic eDiscovery for Copilot interactions. Microsoft 365 E5 or a Purview add-on is needed for DLP that blocks labeled files, auto-labeling, and premium audit and eDiscovery.
From the Microsoft Purview service description, updated November 9, 2026:
- DLP to restrict Copilot from processing files and emails: included in Microsoft 365 E5/A5, Microsoft Purview Suite, Microsoft 365 E5 Information Protection and Governance, and Office 365 E5/A5. Not included in Microsoft 365 E3 or Business plans.
- DLP to safeguard prompts: available to all users of Microsoft Copilot and Copilot Chat.
- Manual sensitivity labeling: included in Microsoft 365 E3 and E5, Business Premium, and Office 365 E3 and E5.
- Automatic sensitivity labeling: requires Microsoft 365 E5 or Microsoft 365 Information Protection and Governance.
- Audit (Standard) for Copilot interactions: included in Microsoft 365 E3. Copilot audit logs are generated only when Copilot is licensed and in use.
- Audit (Premium): included in Microsoft 365 E5, with up to one year of audit log retention.
- Premium eDiscovery search for Copilot interactions: included with Microsoft 365 E5 plus Copilot. Content search, legal hold, and export for Copilot interactions are included with E3 plus Copilot.
- Communication Compliance analysis of Copilot prompts and responses: included with Microsoft 365 E5 plus Copilot.
SharePoint Advanced Management is a separate case. If at least one user has a Microsoft 365 Copilot license, SharePoint admins get the SharePoint Advanced Management features that support Copilot, including Restricted Content Discovery, restricted access control, and site access reviews. Restricted site creation by apps still requires the SharePoint Advanced Management Plan 1 add-on.
The IncWorx Copilot Data Guardrails Model
The IncWorx Copilot Data Guardrails Model is a five-stage approach for preparing Microsoft 365 data for Copilot: Assess, Remediate, Label, Restrict, and Monitor. Each stage produces an output the next stage needs, so we run them in order. It follows Microsoft’s foundational deployment guidance for securing Copilot and adds the sequencing we use with clients.
Stage 1: Assess
Run DSPM data risk assessments and SharePoint Advanced Management reports to find sites with sensitive data and broad access. The output is a ranked list of high-risk sites with named owners.
Stage 2: Remediate
Fix permissions on the highest-risk sites first: remove “Everyone except external users,” expire old sharing links, and assign owners. Use Restricted Content Discovery to hide sites from Copilot while the cleanup is underway.
Stage 3: Label
Publish a short sensitivity label taxonomy that users can understand, enable labels for SharePoint and OneDrive, and set default labels for sensitive libraries. Add auto-labeling where your license supports it.
Stage 4: Restrict
Create DLP policies for the Microsoft 365 Copilot location, one for labeled files and emails and one for sensitive prompts. Run them in simulation, review the matches, then turn them on.
Stage 5: Monitor
Watch Copilot activity in DSPM activity explorer and the audit log, set retention for Copilot interactions, and use the Insider Risk Management “Risky AI usage” policy template where licensed. Feed what you learn back into Stage 1.
At a Glance
- Assess: data risk assessments and access reports produce a ranked list of overshared, sensitive sites.
- Remediate: permission fixes and Restricted Content Discovery produce a smaller, cleaner set of content Copilot can reach.
- Label: a label taxonomy and default labels produce classified content that Copilot and DLP can act on.
- Restrict: DLP for the Copilot location produces enforced rules for labeled items and sensitive prompts.
- Monitor: audit, activity explorer, and retention produce evidence and the input for the next review cycle.
What to Configure in Purview Before Rolling Out Copilot
Before rolling out Microsoft 365 Copilot widely, configure Purview in this order: confirm auditing, assess oversharing, fix the riskiest sites, enable and publish sensitivity labels, add DLP for the Copilot location, and set retention. The steps below follow that order.
- Confirm auditing is on. Auditing is on by default, but verify it in the Purview portal, because Copilot audit records are the evidence every later step relies on.
- Run a data risk assessment in DSPM. Start with the default assessment, add custom assessments for known sensitive sites, and assign each high-risk site to a business owner.
- Hide high-risk sites with Restricted Content Discovery. Restricted Content Discovery keeps those sites out of Copilot results without changing permissions, so treat it as temporary and set a removal date.
- Clean up permissions and sharing links. Use data access governance reports and site access reviews so site owners confirm who should have access. Disable or restrict “Anyone” and company-wide links at the tenant level if your business allows it.
- Turn on sensitivity labels for SharePoint and OneDrive. Run
Set-SPOTenant -EnableAIPIntegration $trueor use the Purview portal, then publish your labels. Existing encrypted files need to be re-uploaded or edited before SharePoint can process them. - Build DLP policies for the Microsoft 365 Copilot location. Create one rule for labeled files and emails and a separate rule for sensitive information types in prompts. Run both in simulation for at least a week and review the matches with the data owners.
- Set retention for Copilot interactions. In your retention policy, select the “Microsoft Copilot Experiences” location and match the period to your records schedule. Confirm with legal before you choose to delete prompts and responses.
- Review monthly. Check DSPM, the audit log, and DLP matches, and rerun your data risk assessment after each wave of new Copilot users.
Best Practices for Purview and Copilot
- Start with the sites that hold the most sensitive data, then expand.
- Keep your label taxonomy to five or six labels so users apply them correctly.
- Name an owner for every site that Copilot users can reach.
- Include Copilot Cowork in scope, since it runs long, multi-step tasks across apps.
- Document every exception so auditors can follow your decisions.
Real-World Example: Cleaning Up SharePoint Permissions Before AI
A clinical-stage biotech came to IncWorx with SharePoint sprawl across 14 sites, no consistent structure, and permissions for internal staff, external partners, and contractors that had never been audited. Four collaboration portals were shared with contract research organizations and needed their own governance review.
IncWorx inventoried every site, analyzed permissions, completed a Microsoft 365 security audit measured against CIS benchmarks, and delivered a security matrix for internal and external access. Five departments moved onto a new intranet hub, four kept standalone sites with documented decisions, and the client signed off on the final deliverables in October 2026. Copilot relies on that same groundwork, since it can only return content users already have access to. Read the full SharePoint intranet governance case study for a clinical-stage biotech.
Common Mistakes When Securing Copilot With Purview
A costly mistake is turning on Purview controls after Copilot is already in users’ hands. At that point, every permission fix or new DLP rule removes access people have started to rely on, and each change needs an explanation.
- Licensing Copilot broadly before running a data risk assessment.
- Assuming Microsoft 365 E3 includes DLP that blocks labeled files. E3 covers DLP for prompts only.
- Leaving Restricted Content Discovery on permanently, which hides good content and weakens Copilot answers.
- Creating labels with encryption that removes EXTRACT rights for people who need Copilot to work with the content.
Frequently Asked Questions
Do you need Microsoft 365 E5 to protect Copilot with Purview?
No. Microsoft 365 E3 includes manual sensitivity labels, standard audit for Copilot interactions, and DLP for sensitive prompts. Using DLP to block Copilot from processing labeled files and emails requires Microsoft 365 E5, Microsoft Purview Suite, Microsoft 365 E5 Information Protection and Governance, or Office 365 E5. Auto-labeling also requires E5 or Information Protection and Governance.
Can Purview audit Copilot prompts and responses?
Yes. Microsoft Purview captures Microsoft 365 Copilot prompts and responses in the unified audit log, including the sensitivity labels of files Copilot referenced. Audit (Standard) is included in Microsoft 365 E3, and Audit (Premium) in E5 adds up to one year of audit log retention.
Can eDiscovery search Copilot conversations?
Yes. Microsoft 365 Copilot interaction data is stored in the user’s mailbox, and Microsoft Purview eDiscovery can find it using the “Copilot activity” condition. Content search, legal hold, and export for Copilot interactions are included with E3 plus Copilot, while premium search for Copilot interactions requires E5 plus Copilot.
Does DLP for Copilot scan files uploaded directly into a prompt?
No. Microsoft states that Purview DLP for the Microsoft 365 Copilot location cannot scan the contents of files that a user uploads directly into a prompt. DLP can block prompts that contain sensitive information types and can block Copilot from processing labeled files stored in Microsoft 365.
Is SharePoint Advanced Management included with Copilot?
Yes, for the features that support Copilot. When at least one user in your organization has a Microsoft 365 Copilot license, SharePoint admins get SharePoint Advanced Management features such as Restricted Content Discovery, restricted access control, data access governance reports, and site access reviews. Restricted site creation by apps still requires the SharePoint Advanced Management Plan 1 add-on.
Does Purview protect Microsoft 365 Copilot Cowork?
Yes, for most controls. According to Microsoft’s Purview guidance for Copilot Cowork, Cowork supports DSPM, auditing, sensitivity labels, DLP, Insider Risk Management, Communication Compliance, eDiscovery, and Data Lifecycle Management. Data classification and Compliance Manager are not supported, and DLP blocking of external email is not yet supported for Cowork.
What to do next
If Copilot is already licensed in your tenant, start with visibility. You cannot prioritize permission fixes or DLP rules until you know where sensitive data and broad access overlap. Our post on Copilot Cowork cost and governance risks covers the agent side of the same problem.
- Open DSPM in the Purview portal this week and review your data risk assessment results.
- List the ten sites with the most sensitive content and confirm an owner for each.
- Check which Microsoft 365 plan your Copilot users hold, so you know whether DLP can block labeled files.
- Draft a five- or six-label taxonomy with your legal and records teams.
- Build one DLP policy for the Microsoft 365 Copilot location and run it in simulation.
Get Your Data Ready for Copilot
IncWorx can run the oversharing assessment, permissions cleanup, and Purview configuration with your team so Copilot works from the right content. Start with an AI readiness assessment before you scale, or explore our Microsoft Copilot consulting services. When you are ready, contact the IncWorx team.