Share via


Configure data security for Microsoft 365 Copilot

Applies to: Microsoft 365 Copilot, SharePoint Advanced Management, and Microsoft Purview

Microsoft 365 Copilot responds to user prompts using data that the user already has permission to access. When your organization's data is well governed, current, and appropriately shared, Copilot can deliver accurate, relevant, and secure responses. This article explains how to prepare and secure your data so Copilot can provide high‑quality results while respecting your organization's security and compliance requirements.

This guidance is intended for IT administrators and security administrators who are preparing their organization for Microsoft 365 Copilot or tightening controls after Copilot is enabled.

What this article helps you achieve

By completing the steps in this article, you can:

  • Reduce oversharing and stale content that can negatively affect Copilot responses.
  • Ensure sensitive data is correctly classified and protected.
  • Control how SharePoint and OneDrive content is discovered by Copilot.
  • Monitor changes and Copilot activity to identify and remediate risk.

Before you begin

Microsoft recommends that you also review and follow Microsoft 365 Copilot – best practices with SharePoint, which covers optimizing SharePoint search, reviewing sharing settings, and validating site permissions.

Licensing

The capabilities described in this article require:

Admin roles

You need access to the following admin portals and permissions:

Admin portal Required role
Microsoft 365 admin center Global Administrator or Privileged Role Administrator
SharePoint admin center SharePoint Administrator
Microsoft Purview portal Varies by task. See the following articles:
- Permissions required to create and manage sensitivity labels
- Roles and role groups in Microsoft Defender for Office 365 and Microsoft Purview

Step 1: Reduce oversharing and stale content with SharePoint Advanced Management

SharePoint Advanced Management provides tenant-wide controls to identify oversharing, reduce clutter, and monitor changes that can affect Copilot results.

Ensure all sites have valid owners

Sites without active owners often become overshared or outdated.

  • Use a Site ownership policy to identify sites that don't have at least two owners.
  • Run the policy in simulation mode first, and then switch to active mode to notify potential owners.

Having accountable site owners ensures permissions, access reviews, and lifecycle actions are completed.

Find and clean up inactive sites

Inactive SharePoint sites can still surface content in Copilot responses.

  1. Create a site lifecycle management policy to detect inactive sites and generate reports.

  2. Notify site owners and ask them to confirm whether the site is still needed.

  3. If a site is no longer required, take one of the following steps:

Archived sites aren't accessible to users and aren't used by Copilot, which improves response accuracy.

Identify overshared or sensitive sites

Use Data access governance (DAG) reports in the SharePoint admin center to find risk areas. Here are some examples:

Review these reports regularly, especially during early Copilot adoption.

Control access to high-risk SharePoint sites

When oversharing is identified, you can limit exposure with SharePoint Advanced Management controls:

  1. Initiate site access reviews. Ask site owners to validate members and sharing links.

  2. Use Restricted Access Control (RAC). Grant appropriate access to sites through groups.

  3. Set up Restricted Content Discoverability (RCD). Prevent high-risk site content from appearing in Copilot and organization-wide search results without changing permissions.

Tip

Communicate clearly with site owners and users before applying RAC or RCD to avoid unexpected disruptions.

Monitor changes that affect Copilot

Use the Change history reports to track:

  • Site-level changes (sharing, access, and settings)
  • Organization-level changes (external sharing, site creation settings)

Review these reports regularly to catch changes that could introduce oversharing or expose sensitive data.

(Optional) Restrict SharePoint search during remediation

If your organization needs time to review permissions at scale:

RSS is a temporary control. Your long-term goal should be to correct permissions and disable RSS so Copilot can access a complete, accurate data set.

Step 2: Classify and protect data with Microsoft Purview

Microsoft Purview helps ensure Copilot only surfaces data that's appropriately classified and protected.

Create and apply sensitivity labels

Sensitivity labels classify data and enforce protection such as encryption, access restrictions, and visual markings.

  1. Create and publish sensitivity labels for files, emails, and other data assets.

  2. Enable sensitivity labels for files in SharePoint and OneDrive, which is required for Copilot to access encrypted files.

  3. (Optional) Enable labels for content in Teams, Microsoft 365 Groups, and SharePoint sites to control access at the container level.

When Copilot uses labeled content:

  • It respects encryption and usage rights.
  • Returned responses display the highest-priority label.
  • New content generated by Copilot inherits the source label.

Apply default and automatic labeling

To reduce reliance on manual user action:

Automatic labeling improves consistency and reduces the risk of sensitive content appearing in Copilot responses.

Prevent data leakage with Data Loss Prevention (DLP)

Use Microsoft Purview DLP to prevent unintentional or risky sharing:

  1. Protect data across Exchange, SharePoint, OneDrive, Teams, and endpoints. See Create a DLP policy to protect documents with FCI or other properties.

  2. Block or audit actions such as copying, downloading, or sharing sensitive data. See Protective actions of DLP policies.

  3. Prevent Copilot from summarizing or referencing content that violates DLP policies. See Learn about using Microsoft Purview Data Loss Prevention to protect interactions with Microsoft 365 Copilot and Copilot Chat.

Advanced capabilities. such as Endpoint DLP and Adaptive Protection, require Microsoft 365 E5 or equivalent licensing.

Remove data you no longer need

Stale data increases noise and risk. Use retention policies and retention labels to comply with industry regulations and internal policies, remove old content you're not required to keep, and helps ensure users are working with content that's current and relevant.

Cleaning up outdated data helps improves the relevance and accuracy of Copilot responses.

Step 3: Monitor and investigate Copilot activity

Even with strong controls, monitoring Copilot usage is essential. Reports and tools are available to help you monitor Copilot usage and activity. See Copilot Analytics introduction.

Review Copilot prompts and responses

Use Microsoft Purview tools to analyze Copilot interactions:

These tools help you:

  • Detect sensitive or inappropriate content.
  • Investigate potential data spillage.
  • Support compliance and legal requirements.

Monitor communication risks

Use Communication Compliance policies to detect risky or inappropriate Copilot interactions, such as:

  • Sharing confidential information
  • Harassment or abusive language
  • Policy violations

Predefined templates make it easier to get started quickly. See Get started with recommended actions.

Next steps

After completing the steps in this article:

Well-governed data not only reduces risk, it also significantly improves the quality and usefulness of Microsoft 365 Copilot responses.