Secure and govern Microsoft 365 Copilot agents with Microsoft Purview.

An agent in Microsoft 365 Copilot answers from what it can reach in SharePoint and Dataverse. That content is its grounding data, and the sites and tables it’s set to draw on are its knowledge sources. If a site is overshared, the agent can hand that content to people who were never meant to see it, or answer from files that are years out of date. This guide follows Microsoft’s four-step model for that problem. You find the gaps, keep sensitive files out of agents’ answers, protect the conversations themselves, then keep a record you can search and investigate.

It’s written for the Purview, SharePoint and compliance administrators who share the work. The model uses Information Protection, Data Loss Prevention (DLP), Insider Risk Management, Data Lifecycle Management, Communication Compliance, eDiscovery and Compliance Manager.

Microsoft’s four steps on one page.

The blueprint lays out the activities in each step and the outcome each one should reach. It has no effort estimates, so this guide gives none.3

Purview blueprint to secure Microsoft 365 Copilot agents: discover to govern
Microsoft’s blueprint for the model, shown whole. Each column is one step, with its activities above the line and its outcome below. Diagram · Microsoft Learn, Secure and govern Microsoft 365 Copilot agents
  1. For the blueprint’s “DLP policies for SPO and Data policies for Dataverse”, Learn documents no DLP condition for “anyone” links and no how-to for Dataverse data policies. Step 2 uses the documented routes instead, and Limits covers Dataverse.13, 15
  2. The blueprint says Unified Catalog and DSPM for AI. Unified Catalog is pay-as-you-go and still rolling out by region, and DSPM for AI is now the classic version. Step 1 gives today’s locations.1, 16, 17

Microsoft’s steps at a glance

StepWhat it doesOutcome
Step 1Discover risks and identify gapsPotential gaps in data security are discovered
Step 2Protect sensitive info in grounding dataSensitive info in grounding data isn’t used as a knowledge source
Step 3Protect interactionsInteractions are protected from data loss and insider risk
Step 4Govern interactionsInteractions with agents are retained for future investigations

Copilot licences first, then each feature on its own terms.

Microsoft’s model names the Purview features but no single plan. Most of the Copilot-specific features need a Microsoft 365 Copilot licence on top of the plan. Some are billed pay-as-you-go, instead of or on top of a licence.3, 5

Licences by feature 4, 5, 7, 10, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25

FeatureLicenceNotes
Audit (Standard) for Copilot interactionsMicrosoft 365 E3, A3, A1, G3, F3 and F1; Office 365 E3 and E1; Microsoft 365 Business Basic, Standard and Premium.Records are created only when Microsoft 365 Copilot is licensed and in use. Audit (Premium) adds longer retention.
DSPM (current version)A supporting licence for the solution: see the Microsoft Purview service description. Users need Microsoft 365 Copilot licences to monitor Copilot and agents.AI apps other than Microsoft 365 Copilot need pay-as-you-go billing.
DSPM for AI (classic)Learn names no plan. Users need Microsoft 365 Copilot licences, and auditing must be on.The version Microsoft’s Step 1 was written for.
DSPM (classic)Microsoft 365 E5 or Microsoft Purview Suite.A different classic product from DSPM for AI (classic). This guide doesn’t use it.
Restricted Content DiscoverySharePoint Advanced Management prerequisites and a Microsoft Copilot licence.SharePoint only. Meant as a temporary control.
Unified Catalog (Dataverse discovery)Pay-as-you-go, with an Azure subscription in the same tenant.Rolling out by region. Needs the enterprise version of the new Purview experience.
Sensitivity labels on Dataverse data (Data Map)A Microsoft 365 licence that includes automatic labelling, plus pay-as-you-go.Preview.
Label inheritance from input to outputMicrosoft 365 E5, A5, G5, E3, A3, G3, F1, F3 or Business Premium; Office 365 E5, A5, E3 or A3; OneDrive for Business (Plan 2); EMS E3 or E5; AIP P1 or P2. Each with Microsoft 365 Copilot.
DLP to stop Copilot processing labelled files and emailsMicrosoft 365 E5 or A5; Microsoft Purview Suite; Microsoft 365 E5, A5 or F5 Information Protection and Governance; Office 365 E5 or A5.Not in Microsoft 365 E3, Office 365 E3 or the Business plans.
DLP for promptsAll users of Microsoft Copilot and Copilot Chat.Blocking Copilot from processing sensitive prompts is Preview.
Retention policies for Copilot interactionsMicrosoft 365 E3 or E5 with Microsoft 365 Copilot. Or E3 with Microsoft Purview Suite or E5 Information Protection and Governance, plus Microsoft 365 Copilot.Adaptive scopes, and keeping the exact version of a shared file, need E5 with Copilot or E3 with one of those add-ons and Copilot.
Insider Risk ManagementMicrosoft 365 E5, A5 or G5; Microsoft Purview Suite; Microsoft 365 E5, A5, F5 or G5 Insider Risk Management.The Risky Agents template is Preview.
Communication Compliance analysis of Copilot prompts and responsesMicrosoft 365 E5 with Microsoft 365 Copilot, or Microsoft Purview Suite with Microsoft 365 Copilot.Not in E5 or Purview Suite without Copilot. Copilot Studio interactions need pay-as-you-go.
eDiscovery search, hold and export for Copilot interactionsMicrosoft 365 E3 or E5, Microsoft Purview Suite, or Microsoft 365 E5 eDiscovery & Audit, each with Microsoft 365 Copilot.Premium search needs E5, Purview Suite or E5 eDiscovery & Audit, with Copilot. The two add-ons also need Microsoft 365 E3.
Data Security InvestigationsNot licensed. Billed on stored data and the compute used for AI analysis.Pay-as-you-go.
Compliance ManagerOffice 365 and Microsoft 365 plans, including Business Premium. The Data Protection Baseline is at every level.The four AI regulation templates are premium and count against purchased premium licences.

For a SharePoint site, every owner and member needs the required licence when a Purview policy or feature is used on the site.5

Find where agents could reach content they shouldn’t.

Outcome
Potential gaps in data security are discovered

This step blocks nothing. By the end, you know which sites are overshared, where sensitive data sits in Dataverse, what agents are touching, and which AI regulation controls you haven’t met.26

In today’s portal Data risk assessments and the apps and agents view are now under Solutions › DSPM › Discover. Microsoft’s Step 1 links to Solutions › DSPM for AI (classic), which has the same weekly assessment and an Apps and agents page.1, 2, 27

  1. Turn on Microsoft Purview Audit

    Microsoft Purview portal › Audit

    1. Open the Audit solution card, or find Audit under View all solutions.6
    2. If you see the Start recording user and admin activity banner, select it.6, 26
    3. Wait up to 60 minutes for auditing to take effect. Events can take several hours more to become searchable.6

    Copilot and agent activity is part of Audit (Standard), so there’s nothing else to turn on. Each record carries the operation CopilotInteraction, the files and sites the interaction accessed, and the agent’s AgentId and AgentName.28

    Check In Exchange Online PowerShell, run Get-AdminAuditLogConfig | Format-List UnifiedAuditLogIngestionEnabled. True means auditing is on. Don’t run it in Security & Compliance PowerShell, where the value is always False.6

    We recommend

    We recommend running one test chat with an agent once auditing is on, then searching the audit log for its CopilotInteraction record. Check that the record names the agent and lists the files it used, and their labels. You’ll know the evidence trail works before you need it.28, 29

  2. Find oversharing with data risk assessments

    Microsoft Purview portal › Solutions › DSPM › Discover › Data risk assessments

    1. Open the Default assessment. It runs weekly on your top 100 SharePoint sites by usage, with no setup, and its summary counts the links that share data with anyone.26, 27
    2. Select View details, then select a site. Its flyout has Overview, Identify, Protect and Monitor tabs.27
    3. On Protect, choose a fix. Restrict access by label creates a DLP policy that stops Copilot and agents summarising labelled data. Restrict all items turns on Restricted Content Discovery. You can also Create an auto-labeling policy, or Create retention policies to delete content nobody has opened in three years.27
    4. On Monitor, see how many items are shared with anyone, with everyone in the organisation, and externally. Select Start a SharePoint site access review to have the site’s access reviewed.27
    5. For sites outside the top 100, create a custom assessment. Its results appear after at least 48 hours and don’t update, so run a new one to see changes. Each one expires after 30 days.27

    Why An agent answers only from content the user can open. Oversharing is what turns that into a leak, so these are the sites to fix first.13

    Watch out

    The first default assessment takes four days to show results, and it only ever covers the top 100 sites. A clean result says nothing about the sites it didn’t scan.27

  3. Find sensitive data in Dataverse

    Microsoft Purview governance portal (classic) › Data Map › Sources

    Register Dataverse as a Data Map source and scan it, so the Data Map classifies the sensitive data it finds. Microsoft’s blueprint names Unified Catalog, which is where you browse the results. The setup itself runs in the classic Microsoft Purview governance portal.26, 30, 31

    1. Check the prerequisites: an Azure subscription, an active Microsoft Purview account, the Data Source Administrator and Data Reader roles, and permission to create an application user in the Dataverse environment.30
    2. Select Register, choose Dataverse, then select Continue.30
    3. For Environment URL, enter the Web API endpoint of your Dataverse environment, choose a collection, then select Apply. The endpoint is under Developer resources in the Power Apps maker portal.30
    4. Select the New Scan icon under the source. For Credential, select Microsoft Purview MSI (system), then Show more, and record the managed identity’s application ID.30
    5. In the Power Platform admin center, create an application user with that application ID, and give it the Service Reader security role.30
    6. Back in the scan, select Test connection, then Continue. Choose the tables and a trigger, then select Save and run.30

    A service principal works in place of the managed identity, with its secret kept in Azure Key Vault.30

    Check Open the source in its collection and select View details. Last run status moves from In progress to Completed, with the number of assets scanned and classified. Then browse the Dataverse assets in Unified Catalog.30

    Watch out

    This isn’t a step every tenant can take. Unified Catalog, where the results appear, is still rolling out by region. It needs the enterprise version of the new Purview experience, and it’s billed pay-as-you-go against an Azure subscription in your tenant. Dataverse integration with Data Map isn’t available in sovereign clouds.16, 17, 30

  4. Review what agents are touching

    Microsoft Purview portal › Solutions › DSPM › Discover › Apps and agents

    1. Open the dashboard of AI apps and their agents.2, 26
    2. For each of the 20 most recently used agents, review the sensitive data it accessed and the policies that protect it.2
    3. For agents in Agent 365, use the AI observability page instead. It lists every AI app and agent with activity in the last 30 days.2

    Check Allow a day or so after you start using DSPM before data appears.2

  5. Check your gaps against AI regulations

    Compliance Manager › Assessments

    1. Find the baseline assessment for Microsoft 365 Copilot and Copilot Chat. Learn says it’s provisioned automatically, in the Microsoft 365 admin center, when you buy either licence.25
    2. To assess against an AI regulation, find its template on the Regulations page under Premium AI templates. There are four: the EU Artificial Intelligence Act, ISO/IEC 23894, ISO/IEC 42001 and the NIST AI Risk Management Framework.25
    3. On Assessments, select Add assessment. Select the template with Select regulation, then name the assessment, choose a group and services, and select Create assessment.25
    4. Work through the improvement actions each assessment recommends.26

    Watch out

    Each AI template you use counts toward your purchased premium licences.25

Done when Auditing is on, you have a list of overshared sites and what agents accessed, and your AI regulation gaps have improvement actions.

Next Keep sensitive content out of agents’ answers (step 2)

Keep sensitive files out of what agents answer from.

Outcome
Sensitive info in grounding data isn’t used as a knowledge source

Grounding data is the content an agent draws on to answer, here SharePoint sites and Dataverse. This step labels it, clears out stale content, and stops Copilot using the most sensitive files at all.13

  1. Turn on and publish sensitivity labels for SharePoint

    Microsoft Purview portal › Solutions › Information Protection › Sensitivity labels

    1. If you see a message to turn on the ability to process content in Office online files, select Turn on now. You need to be a Global Administrator, and the change takes about 15 minutes.32
    2. Select + Create a label for each label you need. On Define the scope for this label, choose where it can be used.33
    3. Add the labels to a label policy so people can use them. Allow up to 24 hours for them to reach every app and service.33
    4. Apply labels to the content in the sites your agents use as knowledge sources.13
    Purview banner to turn on processing of encrypted Office online files
    The Turn on now message. If you don’t see it, labels are already on for SharePoint and OneDrive. With Microsoft 365 Multi-Geo, use PowerShell instead, in each geo-location. Screenshot · Microsoft Learn, Enable sensitivity labels for files in SharePoint and OneDrive

    Why Copilot answers only from content the user has permission to see, and shows the most restrictive label of the content it used. Labels give it something to show, and give DLP something to act on.13

    Watch out

    A label on a site isn’t inherited by the files in it. Label the files themselves.34

  2. Label Dataverse data in the Data Map (preview)

    Microsoft Purview portal › Information Protection › Sensitivity labels › + Create a label

    1. On Define the scope for this label, select Files & other data assets.21
    2. Go to Information Protection › Policies › Auto-labeling policies, and select + Create auto-labeling policy.21
    3. Choose a label with the Files & other data assets scope, then select your registered Dataverse source as the location.21, 35
    4. Build the rules from Microsoft’s built-in classifiers. Custom sensitive information types, trainable classifiers and Exact Data Match aren’t supported.21
    5. Select Create policy. Data Map locations don’t support simulation, so the policy applies when the next scan runs.21
    6. Wait 15 minutes, then scan the source in the Data Map. Labels are applied only by a scan.21
    Purview label scope page with files, emails, meetings, groups and sites ticked
    The label scope page. Files & other data assets is the scope the Data Map needs. Screenshot · Microsoft Learn, Create and configure sensitivity labels and their policies

    Watch out

    Labelling in the Data Map is in preview and billed pay-as-you-go. It’s how Copilot Studio agents recognise labels on Dataverse knowledge.21, 35

  3. Delete stale content with a retention policy

    Microsoft Purview portal › Solutions › Data Lifecycle Management › Policies › Retention policies › New retention policy

    1. Choose Static or Adaptive scope.36
    2. With a static scope, turn on SharePoint classic and communication sites and OneDrive accounts. With an adaptive scope, the location is SharePoint sites. Include the sites and accounts your agents use as knowledge sources.13, 36
    3. If a knowledge source is a team site connected to a Microsoft 365 group, also turn on Microsoft 365 Group mailboxes & sites. Learn lists it as a separate location for group-connected sites.36
    4. Set the retention and deletion periods to match how fresh your agents’ answers need to be.13
    Retention policy timing: distributed within a day, applied within seven days
    How long a retention policy takes to apply. Diagram · Microsoft Learn, Create and configure retention policies

    Why Out-of-date files give agents out-of-date answers.3

    Watch out

    A retention policy can take up to seven days to apply.36

  4. Stop Copilot processing labelled files with DLP

    Microsoft Purview portal › Data Loss Prevention › Policies › + Create policy

    1. Choose the Custom template, then Custom policy.7
    2. On Locations, turn on Microsoft 365 Copilot and Copilot Chat. Selecting it turns off every other location.7
    3. Add a rule with the condition Content contains › Sensitivity labels, and choose the labels to exclude, for example Highly Confidential.7, 13
    4. Set the action to Prevent Copilot from processing content.7
    5. Run the policy in simulation mode. Nothing is enforced and events are audited.13, 37
    6. Review DLP activity explorer to see which files would be restricted, then turn the policy on.13

    Check Ask an agent about a labelled file. The file still appears in the citations, but its content isn’t in the answer. Judge the result by the answer, not the citation list.7

    Watch out

    A policy change can take up to four hours to reach Copilot. You can’t put a sensitivity label condition and a sensitive information type condition in the same rule, so use one rule for each in the same policy.7

  5. Block external sharing of labelled content with DLP

    Microsoft Purview portal › Data Loss Prevention › Policies › + Create policy

    1. Choose the SharePoint sites and OneDrive accounts locations.38
    2. Add the condition Content is shared from Microsoft 365 › with people outside my organization, and the condition Content contains › Sensitivity labels.38
    3. Set the action to Restrict access or encrypt the content in Microsoft 365 locations.38
    4. Choose Run the policy in simulation mode. Review the results in the DLP simulation mode overview and activity explorer, then turn the policy on.37, 38

    Watch out

    No DLP condition targets “anyone” links on their own. To see them, use the Monitor tab of a data risk assessment from Step 1. A custom assessment with item-level scanning can also remove a sharing link.15, 27

  6. Hide a site from Copilot while you fix it

    SharePoint admin center › Sites › Active sites

    1. Select the site, then the Settings tab.20
    2. Turn on Restrict content from Microsoft Copilot, then select Save.20

    In PowerShell, the same setting is Set-SPOSite -Identity <site-url> -RestrictContentOrgWideSearch $true.20

    Watch out

    Restricted Content Discovery doesn’t change anyone’s permissions, and it doesn’t work for OneDrive. It’s designed as a temporary control, and changes can take time to apply.20

Done when Knowledge source sites carry labels, stale content has a deletion date, and DLP stops Copilot using your most sensitive labelled files.

Next Protect the conversations themselves (step 3)

Protect what people type and what agents answer.

Outcome
Interactions are protected from data loss and insider risk

Step 2 protected the content agents draw on. This step protects the conversation: the label it shows, the prompts people type, and the risky behaviour around them.39

  1. Confirm conversations show the right label

    1. Confirm labels are applied to your knowledge sources.39
    2. Open a Microsoft 365 Copilot conversation that references labelled content.39
    3. Confirm the response shows the most restrictive label of the content it used. “Most restrictive” means the highest priority in your label list.29, 39

    When people create new content with Copilot in Word, PowerPoint or Outlook, it inherits the label of the file it was built from. If there are several files, it takes the highest priority label.29

    Purview sensitivity labels listed by priority, Personal lowest
    Label priority on the Sensitivity labels page. The higher the number, the more restrictive Copilot treats the label. Microsoft’s red boxes mark a selected label and the edit button, from another Learn task; this guide uses the image for its Priority column. Screenshot · Microsoft Learn, Create and configure sensitivity labels and their policies

    We recommend

    We recommend testing with two files that carry different labels in the same prompt. The response should show the higher priority of the two.29

  2. Block web searches for prompts with sensitive information

    Microsoft Purview portal › Data Loss Prevention › Policies › + Create policy

    DLP for Copilot has separate controls, each set up as its own rule. This one stops a prompt leaving for web search. The label exclusion in Step 2 is another, and the next task is a third.7

    1. Choose the Custom template, then Custom policy.7
    2. On Locations, turn on Microsoft 365 Copilot and Copilot Chat.7
    3. Add a rule with the condition Content contains › Sensitive information types, and choose the types to detect.7
    4. Set the action to Prevent Copilot from processing content › Performing Web Searches.7
    5. Run the policy in simulation mode, which this location supports. Review the results in the DLP simulation mode overview and activity explorer, then turn the policy on.7, 37

    Check Copilot still answers a matching prompt, but only from internal Microsoft 365 content the user can access.7

  3. Block Copilot from processing sensitive prompts (preview)

    Microsoft Purview portal › Data Loss Prevention › Policies › + Create policy

    1. Set up the policy and rule as in the previous task.7
    2. Set the action to Processing prompts. Copilot then doesn’t respond to a matching prompt, and doesn’t use it for internal or web searches.7
    3. Run it in simulation mode and review the results, as in the previous task, before you turn it on.7, 37
    4. Optional: in the rule’s User notifications, turn on policy tips and select Provide a compliance URL for the end user to learn more about your organization’s policies. Enter the full https address of your own guidance page. Only the link’s destination changes.7

    A fourth control, also in preview, stops Copilot processing email received from external users.7

    Purview DLP rule user notifications and policy tip compliance URL option
    Microsoft’s general DLP example of a rule’s User notifications section, from a rule for another location, not a Copilot rule. Learn says a Copilot rule offers the same compliance URL option. Screenshot · Microsoft Learn, Data Loss Prevention policy reference

    Watch out

    This control is in preview and still rolling out, so check it has reached your tenant. It supports only built-in and custom sensitive information types. DLP can’t scan files uploaded straight into a prompt: it checks only the text typed.7

  4. Detect risky AI interactions with Insider Risk Management

    Microsoft Purview portal › Insider Risk Management › Policies › Create policy

    1. First, install the Microsoft Insider risk extension in Edge, or the Microsoft Purview extension in Chrome, on users’ devices. The Risky AI usage template requires one of them.22
    2. Choose the Risky AI usage policy template.9, 39
    3. Enter a name and description, then choose the users and groups: everyone, specific people, or an adaptive scope.9
    4. Set the scope, triggers and thresholds to match your organisation’s risk tolerance, then turn the policy on.39

    The template detects visits to generative AI websites, and prompts and responses with sensitive information in Microsoft 365 Copilot and agents. A separate Risky Agents template, in preview, covers agents hosted in Copilot Studio and Microsoft Foundry.22

    Each alert from the policy is triaged, investigated and acted on, and can become an insider risk case.40

    Insider Risk Management workflow: policy, alerts, triage, investigate, action
    What happens after the policy is on: alerts are triaged, investigated and acted on. Diagram · Microsoft Learn, Learn about Insider Risk Management

    Watch out

    Guest accounts aren’t supported. Insider risk analytics, an optional step, can take up to 48 hours to show results.9

Done when Conversations show the right label, sensitive prompts stay out of web search, and risky AI use raises an alert.

Next Keep a record of interactions (step 4)

Keep a record you can search and investigate.

Outcome
Interactions with agents are retained for future investigations

Copilot prompts and responses are stored in a hidden folder in each user’s mailbox. This step decides how long they stay, watches them for misconduct, and sets up the tools to search them.14, 41

  1. Retain and delete interactions

    Microsoft Purview portal › Solutions › Data Lifecycle Management › Policies › Retention policies › New retention policy

    1. Include the Microsoft Copilot experiences location.14, 29
    2. Set the retention and deletion periods your compliance requirements call for.14

    Watch out

    Deletion runs on a timer that usually takes one to seven days, so a delete after one day can take 16. What people see in Copilot doesn’t show whether a message is retained or deleted. Another retention policy, Litigation Hold or an eDiscovery hold stops deletion.41

  2. Keep the file versions Copilot referenced

    Microsoft Purview portal › Data Lifecycle Management › Retention labels

    1. Create a retention label.29
    2. Under Label policies, auto-apply it with Apply label to cloud attachments and links shared in Exchange, Teams, Viva Engage, and Copilot.29
    Purview label applied to cloud attachments in Exchange, Teams and Copilot
    The auto-apply option that keeps the version of a file Copilot referenced. Screenshot · Microsoft Learn, Use Microsoft Purview to manage data security & compliance for Microsoft 365 Copilot & Microsoft 365 Copilot Chat
  3. Detect inappropriate behaviour with Communication Compliance

    Microsoft Purview portal › Communication Compliance › Policies › Create policy

    1. Choose the Detect Microsoft Copilot interactions template.10
    2. Enter a name, choose the users and groups, and name the reviewers.10
    3. Select Create policy, or Customize policy to change it first.10

    The template reviews all Copilot interactions with the Prompt Shields and Protected material classifiers. Prompt Shields detects prompt injection attacks, also called jailbreak attempts.14, 42

    Watch out

    If you widen the policy to review all generative AI interactions, at 100% with no conditions, it can detect a high volume of messages. That could take your organisation to its storage limit. If it does, narrow the policy.10

  4. Search interactions with eDiscovery

    eDiscovery › Cases › Create case

    1. In the case, create a search.29
    2. Add the Item class condition and select the Copilot activity option. Or search on ItemClass for IPM.SkypeTeams.Message.Copilot.*.11, 29
    3. To narrow it, use IPM.SkypeTeams.Message.Copilot.Studio.* for Copilot Studio or IPM.SkypeTeams.Message.Copilot.BizChat for Copilot Chat.11

    We recommend

    We recommend searching for the test chat from Step 1 now. If you can find it, you can find a real one.11

    Watch out

    Delete only to remove sensitive or inappropriate content, such as after a data spillage, and review the search results first. Deleting needs the Search And Purge role, removes up to 10 items per location, and needs holds and retention policies removed first.11

  5. Investigate with Data Security Investigations (optional)

    1. Agree to the terms and assign permissions.12
    2. Configure billing and usage.12
    3. Create an investigation: from Microsoft Defender XDR, an Insider Risk Management case, DSPM, or by hand.12
    4. Search the sources you need. They include Copilot prompts and responses, Exchange Online, Teams, OneDrive and SharePoint. A query such as ItemClass=IPM.SkypeTeams.Message.Copilot.* finds Copilot interactions.43

    Why It uses AI to investigate both the interactions and the grounding data behind them.14

    Watch out

    Data Security Investigations isn’t licensed. You pay for the data you store and the compute its AI analysis uses.23

  6. Keep your AI regulation gaps under review

    Compliance Manager › Assessments

    Return to the assessments from Step 1 as regulations change, and work through new improvement actions.14

    Watch out

    Compliance Manager’s score is points for completed improvement actions. Its recommendations aren’t a guarantee of compliance: you still have to check your controls work.44, 45

Done when Interactions are retained for a set period, misconduct raises an alert for a named reviewer, and you can find any interaction in eDiscovery.

Next Read the limits before you rely on these controls

What these controls don’t cover.

  • Dataverse data policies. Microsoft’s Step 2 names data policies for Dataverse but links to no how-to for them. Power Platform data policies govern connectors, not which Dataverse rows an agent may use. Check this with Microsoft before you plan around it.13, 46
  • A label is a signal. The label on a Copilot response is there to tell the user how sensitive the content is. Inheritance applies only to new content in Word, PowerPoint and Outlook, and the user can change or remove the label unless labelling is mandatory.29
  • Teams and connectors. Copilot and agents don’t recognise labels on Teams meetings and chats, and copying chat data can’t be prevented. Labels on Microsoft Graph connector data aren’t recognised by Copilot Chat.34
  • When inheritance fails. If an inherited label can’t be applied, Copilot doesn’t add the text. That happens when the item is read-only, encrypted without the EXPORT or FULL CONTROL right, or the label isn’t published to the user.34
  • Encryption. For Copilot to use an encrypted file, the user needs the EXTRACT and VIEW usage rights. Items protected with Double Key Encryption aren’t returned at all.29, 34
  • Site pages and lists. Content from SharePoint site pages and lists doesn’t show its site’s label.34
  • DLP for Copilot coverage. Calendar invites aren’t covered, and older email isn’t covered: only email sent after a cut-off date Microsoft sets. In Word, Excel and PowerPoint, the policy is checked when the file opens, so a label added mid-session applies from the next open. The location doesn’t support admin units.7
  • Data risk assessment size. Every data risk assessment, default or custom, covers at most 200,000 items per location.27
  • Item-level scanning. Item-level scanning works in SharePoint only, on up to 10 sites. OneDrive isn’t supported.27
  • Copilot Studio agents. Showing labels in agent responses is in preview. An agent typically has the same protections as its parent app, but managing some agents’ interactions might need pay-as-you-go billing.47, 48
  • A policy isn’t proof. A policy that exists, or a score that went up, doesn’t show a control works. Test each one with a real interaction before you report it as done.

A short list of gaps, fewer exposed files, and a searchable record.

  • For the security team: the data risk assessment results and the agents DSPM reports, with what each one touched.2, 27
  • For the business: labelled knowledge sources and DLP rules that keep the most sensitive content out of answers, tested in simulation first.7
  • For compliance and legal: retained interactions you can search in eDiscovery, and Compliance Manager assessments with their improvement actions.11, 25

Where each step comes from.

  1. 1 Microsoft Learn Learn about Data Security Posture Management for AI - (classic)
  2. 2 Microsoft Learn Learn about Data Security Posture Management
  3. 3 Microsoft Learn Secure and govern Microsoft 365 Copilot agents
  4. 4 Microsoft Learn Considerations for DSPM for AI to manage data security and compliance protections for AI interactions - (classic)
  5. 5 Microsoft Learn Microsoft Purview service description
  6. 6 Microsoft Learn Turn auditing on or off
  7. 7 Microsoft Learn Learn about using Microsoft Purview Data Loss Prevention to protect interactions with Microsoft 365 Copilot, Copilot Chat, and Cowork
  8. 8 Microsoft Learn Permissions for Data Security Posture Management for AI - (classic)
  9. 9 Microsoft Learn Get started with Insider Risk Management
  10. 10 Microsoft Learn Configure a Communication Compliance policy to detect generative AI interactions
  11. 11 Microsoft Learn Search for and delete AI application data in eDiscovery
  12. 12 Microsoft Learn Get started with Data Security Investigations
  13. 13 Microsoft Learn Step 2: Protect sensitive info in grounding data
  14. 14 Microsoft Learn Step 4: Govern interactions
  15. 15 Microsoft Learn Data Loss Prevention policy reference
  16. 16 Microsoft Learn Learn about Microsoft Purview Unified Catalog
  17. 17 Microsoft Learn Learn about data governance billing
  18. 18 Microsoft Learn Considerations for Microsoft Purview Data Security Posture Management
  19. 19 Microsoft Learn Get started with Data Security Posture Management - (classic)
  20. 20 Microsoft Learn Restrict discovery of SharePoint sites and content
  21. 21 Microsoft Learn Apply sensitivity labels to your data in Data Map (preview)
  22. 22 Microsoft Learn Learn about Insider Risk Management policy templates
  23. 23 Microsoft Learn Billing in Data Security Investigations
  24. 24 Microsoft Learn Learn about regulations in Compliance Manager
  25. 25 Microsoft Learn Build and manage assessments in Compliance Manager
  26. 26 Microsoft Learn Step 1: Discover risks and identify gaps
  27. 27 Microsoft Learn Prevent oversharing with data risk assessments from Data Security Posture Management
  28. 28 Microsoft Learn Audit logs for Copilot and AI applications
  29. 29 Microsoft Learn Use Microsoft Purview to manage data security & compliance for Microsoft 365 Copilot & Microsoft 365 Copilot Chat
  30. 30 Microsoft Learn Connect to and manage Microsoft Dataverse in Microsoft Purview
  31. 31 Microsoft Learn Data sources that connect to Data Map
  32. 32 Microsoft Learn Enable sensitivity labels for files in SharePoint and OneDrive
  33. 33 Microsoft Learn Create and configure sensitivity labels and their policies
  34. 34 Microsoft Learn Considerations to manage Microsoft 365 Copilot and Channel Agent in Teams for security and compliance
  35. 35 Microsoft Learn Use Microsoft Purview to manage data security & compliance for Microsoft Copilot Studio
  36. 36 Microsoft Learn Create and configure retention policies
  37. 37 Microsoft Learn Create and deploy data loss prevention policies
  38. 38 Microsoft Learn Help prevent sharing sensitive items via SharePoint and OneDrive with external users
  39. 39 Microsoft Learn Step 3: Protect interactions
  40. 40 Microsoft Learn Learn about Insider Risk Management
  41. 41 Microsoft Learn Learn about retention for Copilot & AI apps
  42. 42 Microsoft Learn Create and manage Communication Compliance policies
  43. 43 Microsoft Learn Search, review, and refine results in Data Security Investigations
  44. 44 Microsoft Learn Microsoft Purview Compliance Manager
  45. 45 Microsoft Learn Compliance Manager scoring
  46. 46 Microsoft Learn Data policies
  47. 47 Microsoft Learn View sensitivity labels in agent responses (preview)
  48. 48 Microsoft Learn Use Microsoft Purview to manage data security & compliance for AI agents

Have your Copilot agent controls checked.

LensIQ reviews your Purview setup against this model. We tell you which sites agents can still overshare, which DLP rules are still in simulation, and whether you can find an interaction when you need it.