Set up Microsoft Purview DLP, phase by phase.
The Microsoft 365 admin center has a guided setup for Microsoft Purview Data Loss Prevention (DLP): four phases and 18 tasks, from checking licences to reviewing live alerts. This playbook takes you through the same tasks in the same order. Each one has its click path in the Microsoft Purview portal, why it matters, how you know it worked, and the Microsoft Learn article behind it. Where the in-portal guide has fallen behind Microsoft's own documentation, we say what changed and what to do instead.1
It is written for the Microsoft 365 or Purview administrator doing this for the first time, with a privacy or risk owner beside them for the decisions.
What DLP does.
A DLP policy says what sensitive information to look for, where to look and what to do when it finds it. Locations include Exchange email, SharePoint sites, OneDrive accounts, and Teams chat and channel messages. They also include Windows 10 and 11 devices, the three most recent macOS versions, on-premises file shares and Microsoft 365 Copilot (preview).5
When a policy matches, it can show a policy tip, block with an override, block outright, quarantine stored files or hide a Teams message. Every monitored activity goes to the Microsoft 365 audit log and to Activity explorer, which shows the last 30 days. Encryption and visual markings come from sensitivity labels, a separate Information Protection feature, not from DLP.5
Phase 1 · Piloting.
Outcome you know which workloads your licences cover, and the right people can open DLP without changing anything for users.
-
Verify your licences and roles
Confirm the licences and roles before you build anything. You can then create, test and watch policies in simulation without affecting anyone.1
Licensing by workload 2, 3, 5, 6, 7, 8
Workload Included in Notes Exchange, SharePoint, OneDrive Microsoft 365 E3 and E5 (and A, G), Microsoft 365 Business Premium, Office 365 E3 and E5, Exchange Online Plan 2, SharePoint Online Plan 2, OneDrive for Business (Plan 2), Microsoft Purview Suite On for all users by default. Covers files shared in Teams, because Teams stores them in SharePoint and OneDrive. Teams chat and channel messages Office 365 E5/A5/G5, Microsoft 365 E5/A5/G5, Microsoft 365 E5/A5/G5 Information Protection and Governance, E5/A5/G5/F5 Compliance, F5 Security & Compliance, Microsoft Purview Suite Not in E3. The Microsoft Communications DLP service plan must be on under one of these licences. Devices (endpoint) Microsoft 365 E5/A5/G5, Microsoft Purview Suite, Microsoft 365 E5 Information Protection and Governance Office 365 E5 is not listed. Windows 10, Windows 11 and the three most recent macOS versions. Microsoft 365 Copilot and Copilot Chat Blocking Copilot from processing files and emails: Microsoft 365 E5/A5, Microsoft Purview Suite, Microsoft 365 E5 Information Protection and Governance, Office 365 E5/A5 DLP for prompts is available to every Copilot and Copilot Chat user. The Copilot location is in preview. Activity explorer and Content explorer Microsoft 365 E5/A5/G5, E5 Compliance, Microsoft 365 E5 Information Protection and Governance, Office 365 E5 E3 tenants keep collecting the data, but can't open the explorers. DLP incidents in Defender XDR Microsoft 365 E5/A5, Office 365 E5/A5, Microsoft 365 E5/A5 Compliance, Microsoft 365 E5/A5 Information Protection and Governance Defender XDR is Microsoft's recommended place to investigate DLP alerts, once its alert tuning rule is set (Phase 4). Alerts work on any DLP subscription, one alert per matching event. Alerts that group many events need E5, or E3 with an add-on such as Microsoft Purview Suite. Microsoft 365 F1 and Office 365 E1 are not licensed for DLP in Exchange, SharePoint or OneDrive. Copilot prompt DLP still applies to those users.2, 8
DLP doesn't skip unlicensed users: every location is on for everyone by default. Scope each policy to licensed users with include and exclude settings when you create it in Phase 3.2
Start a trial if you are short of licences
The Microsoft Purview Suite trial adds 25 Purview Suite licences for 90 days. Purview Suite was formerly Microsoft 365 E5 Compliance. It extends DLP to Teams and devices. Tenants on Microsoft 365 E3, or Office 365 E3 with EMS E3, are eligible. Government tenants are not.9
Watch out
When the trial ends, you can no longer edit or add the Teams or Devices locations in your policies. Plan the licence decision before day 90.9
- In the Microsoft Purview portal, stay on Home and go to Trials and recommendations > View all trials and recommendations.9
- Under Purview and Priva trials, find the Microsoft Purview setup card and select Get started.9
The Trials and recommendations card on the portal's Home page, where Purview trials are offered. Screenshot · Microsoft Learn, Learn about the Microsoft Purview portal A Billing Administrator, Compliance Administrator, Compliance Data Administrator or Global Administrator can start it. You can extend it once, in its last 15 days, for two periods in all.9, 10
Role group Can do Compliance Administrator, Compliance Data Administrator, Security Administrator Create and deploy DLP policies Information Protection Full control of information protection: labels, DLP, classifiers, both explorers and their reports Information Protection Admins Create, edit and delete DLP policies, labels and classifiers Information Protection Analysts Manage DLP alerts and Activity explorer; view DLP policies only Information Protection Investigators Manage DLP alerts, Activity explorer and Content explorer; view DLP policies only Information Protection Readers View DLP and label reports only Organization Management Holds the Role Management role, which assigns Purview role groups Use one of these roles rather than Global Administrator, which Microsoft asks you to keep to as few people as possible. None of these Information Protection role groups opens Data Security Posture Management (DSPM). Phase 2 covers that.1, 12
In PowerShell
Check which licences the tenant holds, and whether Teams DLP is switched on in each. Connect with Microsoft Graph PowerShell, then list the subscriptions.13, 14, 15
PowerShell Connect-MgGraph -Scopes "LicenseAssignment.Read.All" # Each licence the tenant holds, and how many are assigned Get-MgSubscribedSku | Select-Object SkuPartNumber, ConsumedUnits, CapabilityStatus # Which licences carry Microsoft Communications DLP (needed for Teams chat DLP) Get-MgSubscribedSku | Where-Object { $_.ServicePlans.ServicePlanName -contains "COMMUNICATIONS_DLP" } | Select-Object SkuPartNumberList who holds each role group. Connect to Security & Compliance PowerShell first.16, 17, 18
PowerShell Connect-IPPSSession -UserPrincipalName {admin-upn} # The exact role group names in your tenant Get-RoleGroup | Select-Object Name Get-RoleGroupMember -Identity "{role-group-name}"Check each admin opens Data loss prevention > Policies and Data loss prevention > Alerts in the Purview portal. If you hold E5-level licences, they also open Activity explorer.2, 19, 20, 21
Tip
Don't turn any policy on in this phase. Microsoft's guidance is to start from the least impactful simulation and move to enforcement in steps.1
Done when the tenant's licences are confirmed by workload, admins and analysts hold the right Purview roles, and each can open policies, alerts and Activity explorer.
Phase 2 · Preparation.
Outcome scope, people, data and plan are settled before you create a single policy.
Use this phase to decide which workloads are in scope, who does what and where your sensitive data sits. Finish it before you move to policy creation.22
-
Why tenant location matters
Your tenant's location is set by the country you signed up in. It decides where Microsoft stores your Microsoft 365 data at rest. Microsoft's residency commitments are for data at rest only, and some requests can be handled in another region.23, 24
A residency commitment for Purview DLP data needs the Advanced Data Residency (ADR) add-on. ADR must cover every paid licence in the tenant. Australia is an eligible region. With ADR, DLP policies, monitored activities, Activity explorer data, quarantine storage and DLP alerts stay in Australia at rest.24, 25, 26
A Global Administrator sees the tenant's locations in the Microsoft 365 admin center > Settings > Org settings > Organization profile > Data location. That card doesn't list Purview services yet. Until it does, read your Exchange Online location to see where Purview stores its data.24
-
Set up workloads
Confirm which workloads are in scope and that every pilot user is licensed for them.2
Exchange, SharePoint and OneDrive are already on as DLP locations for every user. Roles don't switch workloads on. Licences do. For Teams chat, make sure the Microsoft Communications DLP service plan is selected under a qualifying licence in the Microsoft 365 admin center.2
You won't set up Endpoint DLP here. It needs E5-level licences and device onboarding, and comes in Phase 3.2
In PowerShell
Check each pilot user's licences and service plans.27
PowerShell Connect-MgGraph -Scopes "User.Read.All" Get-MgUserLicenseDetail -UserId "{user-upn-or-id}" | Select-Object SkuPartNumber, ServicePlansCheck every pilot user holds a licence from the table under Phase 1 for each workload in scope.2
Done when the workloads and pilot users are approved, and every in-scope user's licence is confirmed for those workloads.
-
Add or update roles
Give each admin and analyst the least role they need.11
In the portal
- Go to Settings > Roles and scopes > Role groups in the Purview portal.4
- Select the role group, then select Edit.4
- Select Choose users or Choose groups, tick the people or groups, then select Select.4
- Select Next, then Save, then Done.4
Settings, Roles and scopes, Role groups: the Purview role groups you add admins and analysts to. Screenshot · Microsoft Learn, Permissions in the Microsoft Purview portal Seeing role groups here needs the Role Management role or Global Administrator. The admin center's guide also has an Add users and roles tool. It assigns Microsoft Entra roles only: Compliance Administrator, Compliance Data Administrator, Global Administrator, Security Administrator and Security Reader.4
Condition, What happens 4, 21, 28
Condition What happens Someone holds an Entra role and a scoped Purview role group The Entra role takes precedence You need someone for a set period Make the assignment temporary, from one day to two years You assign Entra roles A Privileged Role Administrator can manage them, in Entra ID and Privileged Identity Management (PIM) An Information Protection Reader needs Activity explorer Assign Information Protection Admins as well In PowerShell
Run
Get-RoleGroupMember -Identity "{role-group-name}"for each group you changed, as in Phase 1.17Check each operator signs in and opens the features their role needs. An analyst sees DLP alerts but can't edit a policy.11
Done when each administrator and analyst has least-privilege access that works. You have reviewed Entra roles, Purview role groups, nested groups and PIM, and opened each feature as those operators.
-
Set up discovery and awareness
The explorers show where sensitive data is and how people use it, before any policy runs.21, 29
In the portal
- Open Solutions > Information Protection > Explorers > Data explorer in the Purview portal to see labels, sensitive information types and trainable classifiers.30, 31
- For the older view, go to Solutions > Data Lifecycle Management > Explorers > Content explorer. Microsoft now calls it Content explorer (classic).29
- Go to Information protection > Explorers > Activity explorer to see what people do with labelled content, and DLP events.5, 21
Explorer, Who sees the tab, Who sees the items, Delay 21, 29, 30
Explorer Who sees the tab Who sees the items Delay Content explorer (classic) Compliance Administrator, Security Administrator, Compliance Data Administrator, or an Information Protection role Content Explorer List viewer, Content Explorer Content viewer Up to 7 days, 14 for SharePoint Data explorer As above, plus Global Administrator Data Explorer List viewer, Data Explorer Content viewer Not published by Microsoft Activity explorer Information Protection Admin, Analyst or Investigator; Compliance Administrator, Security Administrator, Security Reader Same roles 60 to 90 minutes for Exchange, SharePoint, OneDrive and Teams; 30 days kept All three explorers need E5-level licences.2
Why an admin role isn't enough. It opens the tab, but without the viewer role groups the lists stay empty.29
Check the explorers show counts for your pilot workloads.
Done when you have reviewed both explorers for the approved scope, and recorded where sensitive data sits and the risks. A licence or role check alone doesn't count.
-
Plan for implementation
Decide how each policy will be introduced, tested and supported before you build it.22
- Name the stakeholders: security, compliance, legal, the data owners and the service desk.22
- List the kinds of sensitive information you hold, and set the goals each policy must meet.22
- Choose a template for each policy.32
- Plan each policy's first mode and the steps to enforcement.1
- Plan how users are told, and where they go for help when a tip or block appears.22
Microsoft's usual order for deploying DLP. Diagram · Microsoft Learn, Plan for data loss prevention Microsoft offers five types of policy template: enhanced, financial, medical and health, privacy, and custom. For Australian data, start with Australia Privacy Act or its Enhanced version. Microsoft also ships Australia Financial Data, Australia Health Records Act (HRIP Act) and its Enhanced version, and Australia Personally Identifiable Information (PII) Data.32
Policy mode, What happens 1
Policy mode What happens Leave the policy turned off Nothing runs Run the policy in simulation mode Events are audited; no actions are enforced Run the policy in simulation mode with Show policy tips while in simulation mode. ticked As above, and users see tips Turn the policy on immediately Actions are enforced Why simulation with policy tips teaches users the rules before anything is blocked.22
Check each planned policy has a template, a scope, an owner, a first mode and a gate for moving to the next.
Tip
Start each policy's actions at the least impactful setting: Allow for devices and Audit only everywhere else.1
Done when scope, owners, simulation plan, user support and communications, and rollout gates are recorded, and operations have approved phased enforcement.
-
Complete the interactive guide
Microsoft's click-through guide walks you through applying Endpoint DLP policies to devices, before you touch your own tenant.2
The guide this task opens is the Microsoft Endpoint DLP interactive guide for devices. It covers devices only, which you set up in Phase 3, not DLP for email and files.2
Done when you have completed the interactive guide and recorded that you did.
-
Assess data security posture in DSPM (classic)
Data Security Posture Management (DSPM) shows what sensitive data you have, where it is stored, who can reach it and how it is protected. Use it to decide where labels or DLP policies are needed before Copilot use grows.33
The portal names the classic version, which Microsoft has replaced and will not improve. Use the current DSPM.33, 34
In the portal
- In the Purview portal, go to Solutions > DSPM. Don't confuse it with Data Security Posture Management (classic).33
- Complete the initial Setup tasks. Allow a day or so before data appears.33
- Review Posture, then Objectives, starting with Prevent oversharing of sensitive data.33
- Open Asset explorer and Reports for the locations behind each finding.33
The current DSPM's Posture page, shown here with Microsoft's sample data. Screenshot · Microsoft Learn, Learn about Microsoft Purview Data Security Posture Management (DSPM) Viewing and changing DSPM needs Microsoft Entra Compliance Administrator, Entra Global Administrator or the Purview Compliance Administrator role group. For view-only access, use the Security Reader role group or the Data Security Viewer role.12
Check Posture shows findings for your own locations.33
Done when you have reviewed the DSPM findings and recorded priorities, affected locations and what you will fix.
-
Review AI data exposure in DSPM for AI (classic)
This shows which sensitive data Copilot and other AI tools could reach, before you turn them on or widen them.33, 35
The portal names DSPM for AI (classic), which the current DSPM replaces.33, 35
In the portal
- Open Solutions > DSPM > AI observability in the Purview portal.33
- Under Objectives, open Prevent data exposure in Microsoft 365 Copilot and Microsoft Copilot interactions.33
- Go to Discover > Data risk assessments to see overshared locations.33
DSPM Objectives, shown with Microsoft's sample data. Open Prevent data exposure in Microsoft 365 Copilot and Microsoft Copilot interactions from here. Screenshot · Microsoft Learn, Learn about Microsoft Purview Data Security Posture Management (DSPM) Microsoft's DSPM for AI (classic) article says insights on Microsoft 365 Copilot need auditing on and Copilot licences assigned to users. Admins restricted to an administrative unit can't create its one-click policies.36
Check AI observability lists the AI apps in use, and Data risk assessments lists your top sites.33
Done when you have reviewed AI and Copilot exposure for your real scope, and recorded decisions on high-risk content and the protection it needs.
Next with scope, roles and a plan approved, create your first policy in Phase 3, switched off.
Phase 3 · Deploying.
Outcome your DLP policies are created, tested and validated in simulation, then turned on in stages to limit disruption. They protect only the locations and groups in each policy's scope, and only users licensed for those locations.1, 2, 32
This phase is where policies are created, run in simulation, tuned and then turned on in stages. Simulation lets you check what a policy detects and who it would affect before anything is enforced. Once your core policies behave, you extend them to Teams, Copilot and devices.1, 5
-
Create a DLP policy
Required
A DLP policy says what to look for, where to look and what to do when it finds it. Each policy holds one or more rules, and a tenant can hold up to 600 rules in all. Start with one policy, a narrow scope and simple rules, then widen it once simulation shows it behaves.1, 32
In the portal
The wizard lists its pages down the left: Template or custom policy, Name, Admin units, Locations, Policy settings (with Info to protect, Protection actions and Customize access and override settings under it), Policy mode and Finish. The steps follow it page by page.
- In the Microsoft Purview portal, go to Solutions > Data loss prevention > Policies and select + Create policy.37
- Select Enterprise applications & devices.37
- Template or custom policy. Choose a template from Categories and Regulations. For Australian personal information, start with Australia Privacy Act Enhanced. Microsoft also ships templates for Australian financial data, health records under Victoria's Health Records Act, and personally identifiable information.32, 38
- Name. Enter a Name (64 characters at most) and a Description (1,024 at most) that say what the policy protects and for whom. Renaming policies and rules is still in preview, so choose the name carefully.1, 32, 37
- Admin units. The page opens on Full directory, which covers your whole organisation. Keep it unless you delegate DLP by administrative unit, in which case select Add or remove admin units and pick the unit. Admin units aren't supported for every location. Once you pick one, you can't apply the policy to Fabric and Power BI or to Microsoft 365 Copilot and Copilot Chat on the next page, and Instances and on-premises repositories don't support them either. An admin restricted to an administrative unit sees only the units they're assigned to.32, 39
Admin units: Full directory covers the whole organisation. Picking a unit takes some locations off the next page. Screenshot · LensIQ demo tenant - Locations. Turn on each location the policy should cover. A location that's off reads Turn on location to scope. Once it's on, the Scope column shows its default: All groups for Exchange email, All sites for SharePoint sites, All users & groups for OneDrive accounts and for Teams chat and channel messages, All instances and All repositories. Select Edit in the Actions column to narrow a location to your pilot group or sites. Read the banners at the top of the page before you go on (see the Watch out below).32, 39
Locations with six ticked: each row shows its default scope, and Edit narrows it. The banners at the top are the ones the Watch out below covers. Screenshot · LensIQ demo tenant - Policy settings. Select Review and customize default settings from the template to keep the template's sensitive information types and actions, which is what steps 8 to 10 describe. Create or customize advanced DLP rules shows the template's rules instead. Each Australian template has a low-count rule that sends a notification, and a high-count rule that blocks access, allows an override with a business justification and sends an incident report. On a first policy, take the default.37, 38
Policy settings: keep the template's defaults, or open its rules. Screenshot · LensIQ demo tenant - Info to protect. The sensitive information types the template detects are listed under Content contains any of these sensitive info types. Select Edit to add or remove one. Leave Detect when this content is shared from Microsoft 365 ticked and choose With people outside my organization to catch external sharing, or Only with people inside my organization.38
Info to protect: the template's sensitive info types, and whether to catch sharing inside or outside your organisation. Screenshot · LensIQ demo tenant - Protection actions. Tick the actions the policy takes when content matches:32, 38
- When content matches the policy conditions, show policy tips to users and send them an email notification, with Customize the tip and email for your own wording.
- Detect when a specific amount of sensitive info is being shared at one time, set to At least 10 instances of the same sensitive info type. This is the template's high-count threshold.
- Send incident reports in email. Incident reports are supported for Exchange, SharePoint, OneDrive and Teams only.
- Send alerts if any of the DLP rules match. By default you and the global admins are alerted; Customize alert configuration changes who else is told, and when.
- Restrict access or encrypt the content in Microsoft 365 locations, which you set on the next page.
Protection actions: tips and email, the high-count threshold, incident reports and alerts. Restricting access is set on the next page. Screenshot · LensIQ demo tenant - Customize access and override settings. Under Restrict access or encrypt the content in Microsoft 365 locations, select Block users from receiving email, or accessing shared SharePoint, OneDrive, Teams files, Fabric and Power BI items, then Block everyone or Block only people outside your organization. Block everyone still leaves the content's owner, the last person who changed it and the site admin with access. To let users go ahead after a tip, tick Let people who see the tip override the policy, then Require a business justification to override. If you want it, also tick Override the rule automatically if they report it as a false positive. Encrypt email messages (applies only to content in Exchange) encrypts mail in place of blocking it. Restricting third-party apps such as Box and Dropbox stays greyed out for these locations.32
Customize access and override settings: who is blocked and how people override. Shown with overrides allowed on a false-positive report and no justification asked; step 10 recommends asking for one. Screenshot · LensIQ demo tenant - Policy mode. Select Leave the policy turned off, then Next. The other two options are Run the policy in simulation mode, with its own tick boxes Show policy tips while in simulation mode. and Turn the policy on if it's not edited within fifteen days of simulation, and Turn the policy on immediately.1
Policy mode, with the portal's three options. Shown with simulation selected. Screenshot · LensIQ demo tenant - Finish. Check the summary, then select Submit and Done.37
Microsoft Learn's articles still name the policy modes Keep it off, Run the policy in simulation mode and Turn it on right away. The portal now reads Leave the policy turned off, Run the policy in simulation mode and Turn the policy on immediately, and this page uses the portal's words.1, 40
Video · Microsoft Learn · 2:58
How a DLP rule is built from conditions, condition groups and actions, before you write your own. From Design a data loss prevention policy, Microsoft Learn. Video by Microsoft, with Microsoft's captions in the player. In PowerShell
Connect to Security & Compliance PowerShell with the ExchangeOnlineManagement module, then create the policy switched off and add one rule. The pilot group limits Exchange only, so SharePoint and OneDrive are scoped to named pilot sites and accounts.42, 43, 44
PowerShell Connect-IPPSSession -UserPrincipalName {admin-upn} # Find the exact name of each sensitive information type you want to detect Get-DlpSensitiveInformationType | Where-Object Name -like "Australia*" | Select-Object Name New-DlpCompliancePolicy -Name "{policy-name}" ` -ExchangeLocation All -ExchangeSenderMemberOf "{pilot-group}" ` -SharePointLocation "{pilot-site-url}" ` -OneDriveLocation "{pilot-onedrive-url}" ` -Mode Disable New-DlpComplianceRule -Name "{rule-name}" -Policy "{policy-name}" ` -ContentContainsSensitiveInformation @{Name="{sit-name}"; minCount="1"} ` -NotifyUser Owner -GenerateIncidentReport SiteAdminParameter, What it sets, Values 43
Parameter What it sets Values -Mode Whether the policy runs, and how Disable, TestWithoutNotifications (simulation), TestWithNotifications (simulation with policy tips), Enable -ExchangeLocation, -SharePointLocation, -OneDriveLocation, -TeamsLocation, -EndpointDlpLocation Where it applies All, or named sites, accounts or users -ContentContainsSensitiveInformation What a rule detects One or more hashtables: Name, and optionally minCount, minConfidence -BlockAccess Whether a match is blocked $true or $false Why Microsoft's guidance is to finish a new policy switched off, so the people who own the data can review it before it runs at all.1
Check the policy appears in the Policies list as off, and
Get-DlpCompliancePolicy -Identity "{policy-name}" | Select-Object Name, ModereturnsDisable.45Your tenant may already hold default policies. The default Office 365 policy and the default devices policy both watch for credit card numbers and are on. First-time Teams customers get a default Teams policy, and the default Copilot policy starts in simulation with policy tips. Review them before you add your own.40, 46, 47, 48
Watch out
The Locations page warns you when something the listed locations need is missing. If you still run Defender for Cloud Apps file policies for non-Microsoft locations, turn them off or delete them before you create this policy, or enforcement can be unexpected. The Instances location retires in early 2027 along with those file policies. The Conditional Access and Edge for Business banners apply to the cloud app locations only, and locations outside Microsoft 365 need pay-as-you-go billing.49
One location or several in one policy
A policy can cover one location or many, but what it can do shrinks to what every selected location supports. So the locations you combine decide which detections, conditions, actions and notifications you get.32
What changes, One location, Several locations in one policy 32
What changes One location Several locations in one policy What you can detect Everything that location supports (next table) Only what every selected location supports: a "no" for any one of them wins Conditions The location's full set Only the conditions the locations have in common Actions The location's own actions Restrict access or encrypt the content in Microsoft 365 locations, plus the actions of the locations other than Exchange Email notifications to users Sent where the location supports them Sent only for the locations that support them on their own Scope Set with Edit on that location's row Still set row by row, each location with its own kind of scope Admin units Supported or not by that location Picking one takes the unsupported locations out of the policy What each location can detect 32
Location Sensitive info type Sensitivity label Retention label Exchange email Yes Yes No SharePoint sites Yes Yes Yes OneDrive accounts Yes Yes Yes Teams chat and channel messages Yes No No Devices Yes Yes No Instances Yes Yes Yes On-premises repositories Yes Yes No Fabric and Power BI Yes Yes No Microsoft 365 Copilot and Copilot Chat No Yes No SharePoint on its own can detect by sensitive info type, sensitivity label or retention label. Add Teams chat and channel messages to the same policy and it can detect by sensitive info type only. Copilot can't share a policy with any other location. In its own policy it detects sensitivity labels on files and email, and sensitive info types in prompt text only.32
Exchange email alone. The rows you leave off read Turn on location to scope. Screenshot · LensIQ demo tenant SharePoint sites and OneDrive accounts together: this pair also covers files shared in Teams. Screenshot · LensIQ demo tenant Teams chat and channel messages alone: message text only, detected by sensitive info type. Screenshot · LensIQ demo tenant Email notifications. Exchange, SharePoint and OneDrive send them. Teams, Devices, Instances, on-premises repositories, Fabric and Power BI, and Copilot don't. In a combined policy, a user is emailed only when the match is in a location that supports it: with Exchange and Devices together, Exchange users are emailed and device users are not.32
Actions. With Exchange and one other location, Learn lists Restrict access or encrypt the content in Microsoft 365 locations and the other location's actions. Exchange's own mail actions, such as setting headers, redirecting or forwarding a message for approval, aren't in that list, so a rule that needs them belongs in an Exchange-only policy.32
Scope by location. Exchange is scoped by groups (distribution, security and Microsoft 365 groups, assigned or dynamic), and when a group is both included and excluded, the exclude wins. SharePoint is scoped by sites (adaptive scopes are in preview); if the policy is assigned to an admin unit that holds sites, it covers all of that unit's sites and can't be narrowed further. OneDrive is scoped by groups or by up to 100 named users. Teams is scoped by groups; a named user covers their 1:1 and group chats but not channel messages. An Exchange policy holds no more than 50 group inclusions and exclusions.3, 32
What you don't need to select. Files shared in Teams are stored in SharePoint (channels) and OneDrive (chats), so a policy on SharePoint and OneDrive already covers them. The Teams location covers the message text.3, 50
We recommend
Grouping locations that behave alike, the way Microsoft's own default policies do: one policy for Exchange, SharePoint and OneDrive, one for Teams chat and channel messages, one for devices, and one for Copilot. The three Microsoft 365 locations share detection by sensitive info type and sensitivity label, and all send email notifications. Teams detects by sensitive info type only and sends none. Devices have their own actions, and Copilot detects by sensitivity label only and is available in the Custom template alone. Split Exchange out as well if a rule needs a mail action.32, 40
More policies means more to put in order. When an item matches several policies with the same actions, the actions of the highest-priority policy apply, so set the priority of each new policy as you create it.32
Done when each rule's conditions, thresholds, actions, users, locations and exceptions match the approved design, checked rule by rule. A policy that exists with the right number of rules is not proof on its own.
-
Test DLP policies
Required
Simulation runs the policy as though it were enforced, but nobody is blocked or notified. You see every match before anyone else does.51
- Open the policy, select Edit policy and step through to the policy mode page.
- Select Run the policy in simulation mode, then Submit. Leave Show policy tips while in simulation mode off for the first run.52
- Go to Data loss prevention > Policies, select the policy (status In simulation) and select View simulation. Viewing it needs the Information Protection Admin role.52
- Work through the three tabs: Simulation overview for totals, Items for review for each matched item, and Alerts for what it would have raised.51
- Tune the rules, then run the simulation again until the results match what you intended. Adjust conditions, thresholds, confidence levels, exceptions or scope. The actions you can choose are Audit only, Block with override and Block.1, 5
The Simulation overview tab: progress, items scanned and total matches. Screenshot · Microsoft Learn, Learn about data loss prevention simulation mode In PowerShell, the same change is one line:
PowerShell Set-DlpCompliancePolicy -Identity "{policy-name}" -Mode TestWithoutNotificationsCmdlet reference 53
How simulation evaluates content
Location What is evaluated Shown as SharePoint, OneDrive Existing items, and new or changed ones Completed or In progress Exchange, Teams, devices New items only, from the start of simulation Real-time Scan results are kept for 30 days. Only the first 100 matched SharePoint and OneDrive items are listed for review. After you take a policy out of simulation, its insights can take up to 24 hours to leave the Overview page.51, 52
A rule set to Stop processing more rules keeps processing in simulation, so later rules can still match.5
Why simulation alerts appear only on that Alerts tab. They don't reach the DLP alerts dashboard or the Microsoft Defender portal, so your security operations team is not paged while you tune.51
Check Simulation overview shows items scanned and matches. In Activity explorer, filter Policy mode to
TestWithoutNotifyUserto see each match as an event.52To test a single SharePoint or OneDrive file, use
Test-DlpPoliciesin Exchange Online PowerShell. It reports only policies scoped to SharePoint or OneDrive, handles simple conditions only (not grouped or nested ones), and emails the result.54PowerShell Connect-ExchangeOnline -UserPrincipalName {admin-upn} Test-DlpPolicies -SiteId {site-id} -FileUrl "{direct-link-to-file}" -Workload SPO -SendReportTo {your-email}Cmdlet reference 54
Tip
The policy mode page also offers to turn the policy on automatically if it hasn't been edited within 15 days. We recommend leaving that off on a first policy: turning on should be a decision someone makes after reading the results.52
Done when you have run the approved pilot scenarios with safe test content and read the simulation results. Each true and false positive is recorded, and you have retested after tuning. A policy sitting in simulation does not prove it was tested.
-
Review alerts
Required
Reading what the simulation matched shows how the policy will behave once it is on. It is where you find false positives, conditions that are too broad and business processes that need an exception.51, 54
In the portal
- In the Microsoft Purview portal, go to Data loss prevention > Policies, select the policy and select View simulation.52
- On Items for review, open each matched item to see the content that triggered the policy.51
- On Alerts, read each alert the policy would have raised. The list has the same format as the DLP alerts console.51
- Mark each match as expected or unexpected, and note the business process behind each unexpected one.
- Tune the policy: raise thresholds or confidence levels to cut unwanted matches, and add scoped exceptions for known business processes.1, 32
- Once the matches look right, select Edit policy, step through to the policy mode page and turn on Show policy tips while in simulation mode. Narrow the scope to your pilot group at the same time.1, 52
Items for review: each item the policy matched in simulation, with the item itself beside its metadata. Screenshot · Microsoft Learn, Learn about data loss prevention simulation mode The simulation's Alerts tab, in the same format as the DLP alerts console. These alerts go nowhere else. Screenshot · Microsoft Learn, Learn about data loss prevention simulation mode In PowerShell, simulation with policy tips is the
TestWithNotificationsmode:PowerShell Set-DlpCompliancePolicy -Identity "{policy-name}" -Mode TestWithNotificationsWhy in plain simulation, users notice nothing, so you can rehearse your investigation and incident review process at no risk. Once policy tips are on, pilot users see tips and receive notification emails, so tell them first.1
Check the policy's status reads In simulation with notifications. In Activity explorer, the pilot group's matches carry the policy mode
TestWithNotifyUser.52Watch out
Alerts can take up to 3 hours to appear after you configure or change a policy's alert settings. Wait that long before you decide a rule is silent.8
Done when you have read the actual simulated matches, alerts and business exceptions, recorded each tuning decision, and kept the evidence of the retest that followed.
-
Turn the policy on
Required
Turning the policy on replaces simulation, so its actions apply when it detects sensitive content. Do it only once detections, alerts and actions match what you set out to do.1
Stage Portal option -Mode value Who is affected 1. Simulation Run the policy in simulation mode TestWithoutNotifications Nobody: no actions, no tips, events audited 2. Simulation with policy tips Show policy tips while in simulation mode TestWithNotifications Your pilot group sees policy tips and notification emails; nothing is blocked 3. On Turn the policy on immediately Enable Everyone in scope: actions are enforced In the portal
- In the Microsoft Purview portal, go to Data loss prevention > Policies and select the policy.1, 52
- Select Edit policy and step through to the policy mode page.1
- Widen the locations from the pilot group to everyone the policy is meant to cover, if you narrowed it for stage 2.1
- Select Turn the policy on immediately, then Next > Submit > Done.1
In PowerShell
PowerShell Set-DlpCompliancePolicy -Identity "{policy-name}" -Mode Enable # Read back the mode and the distribution status Get-DlpCompliancePolicy -Identity "{policy-name}" -DistributionDetail | Format-List Name, Mode, DistributionStatusWhy turning on after a piloted policy tips stage means the first people blocked have already seen the tip and know why.1
What a pilot user sees once policy tips are on: a tip at the top of an email they are writing. Screenshot · Microsoft Learn, Send Email Notifications and Show Policy Tips for DLP Policies Check a policy generally takes effect about an hour after it is turned on. After that, Activity explorer shows its matches with the policy mode
enforce, and its alerts reach the DLP alerts dashboard. Monitor DLP alerts and Activity explorer closely in the first weeks.1, 5, 51, 52Tip
You can change a policy's mode, actions and scope at any time. If the business impact is larger than expected, return it to simulation with policy tips while you tune.1
Done when the rollout is approved and the enforced scope is the one intended. You have waited for the change to apply and seen the expected actions and user impact. A mode of Enable is not proof on its own.
-
Deploy Teams DLP
Recommended
Teams DLP checks chat and channel messages for sensitive information as they are sent. If the rule blocks, a matching message is blocked, and the sender sees a policy tip and may override it if the rule allows.3
Licences for Teams chat and channel DLP 2, 3
Licence Teams chat and channel messages Files shared in Teams Office 365 E3, Microsoft 365 E3 Not included Included, through the SharePoint and OneDrive locations Office 365 E5/A5/G5, Microsoft 365 E5/A5/G5 Included Included Microsoft 365 E5/A5/G5 Information Protection and Governance, E5/A5/G5/F5 Compliance, F5 Security & Compliance, Microsoft Purview Suite Included Included The licence's Microsoft Communications DLP service must also be selected for each user.2
In the portal
- In the Microsoft Purview portal, go to Data loss prevention > Policies and look for the default Teams policy. First-time customers get one that tracks credit card numbers shared internally and externally, and raises a low severity alert with no policy tips.47
- Select the policy you want to extend, then select Edit policy.3
- On Choose locations to apply the policy, turn on Teams chat and channel messages. Scope it to groups, not individual accounts.3
- To change what senders see, open Customize advanced DLP rules, then the rule, turn on User notifications and select Notify users in Office 365 service with a policy tip. Then select Customize the policy tip text and Save.3
- On the policy mode page, select Show policy tips while in simulation mode, then Submit.3
The notice a sender sees in Teams when DLP blocks their message. Screenshot · Microsoft Learn, Data loss prevention and Microsoft Teams Who is protected, by scope and chat type 3
Situation What applies Scoped to individual accounts One-to-one and group chats are protected; channel messages are not Scoped to groups Chats and channel messages are both protected Message to a guest Deleted if it matches, but only when your tenant started the chat or thread Shared channel Each sender's messages are checked against their own tenant's policies External access chat The hosting tenant's policies apply In PowerShell
Create a separate Teams policy for your pilot group, in simulation:
PowerShell New-DlpCompliancePolicy -Name "{teams-policy-name}" ` -TeamsLocation "{pilot-group-email}" ` -Mode TestWithoutNotifications # Simulation needs a rule to evaluate: add one with New-DlpComplianceRule, # as in the Create a DLP policy taskCmdlet reference 43
Why Teams sends no notification emails to users, so the policy tip on the message is the only thing the sender sees.3
Check allow about an hour for changes to apply. Then a test message from a pilot user that matches the rule shows as blocked, with a policy tip.
Get-DlpCompliancePolicy -Identity "{teams-policy-name}" | Format-List Name, Mode, TeamsLocationlists the pilot group.3, 45Watch out
A Teams location protects messages only. Files shared in Teams are stored in SharePoint and OneDrive, so they are protected only when your policy also covers those locations.3
Done when licences are confirmed for everyone in scope. You have checked which messages the scope actually covers, tested guest and external chats, and seen enforcement happen. Shared files are confirmed separately under your SharePoint and OneDrive policies.
-
Apply Copilot-ready protections
Recommended
Microsoft 365 Copilot answers from content the user can already open, because every prompt runs in that user's security context. A DLP policy on the Copilot location stops Copilot using labelled content or responding to sensitive prompts.6
The location is called Microsoft 365 Copilot and Copilot Chat. It covers four controls, and some are in preview.6, 32
Control, Condition and action, Status
Control Condition and action Status Skip labelled files and emails Content contains > Sensitivity labels, with Prevent Copilot from processing content Available Block sensitive prompts Content contains > Sensitive information types, with Prevent Copilot from processing content > Processing prompts Preview, rolling out to tenants Block web search for sensitive prompts Content contains > Sensitive information types, with Prevent Copilot from processing content > Performing Web Searches Available Skip external email Email is received from > External users, with Prevent Copilot from processing content Preview The policy reference still lists the location itself as preview.5, 6, 32
Licences. Stopping Copilot from processing labelled files and emails needs Microsoft 365 E5/A5, Microsoft Purview Suite, E5 Information Protection and Governance, or Office 365 E5/A5. Microsoft 365 E3, Office 365 E3 and Business plans don't include it. DLP for prompts is available to every user of Microsoft 365 Copilot and Copilot Chat.2
In the portal
- In the Microsoft Purview portal, go to Data loss prevention > Policies and look for Default DLP policy - Protect sensitive M365 Copilot interactions. It starts in simulation with policy tips and covers all users, with Australian identifiers such as Tax File Number in its list.48
- Edit the default policy to turn on Incident reports and add your security team as recipients. Microsoft recommends this as a minimum.48
- For your own policy, select + Create policy, then the Custom template and Custom policy.6
- On the Locations page, turn on Microsoft 365 Copilot and Copilot Chat. All other locations are turned off for this policy.6
- Add a rule with one condition and its action from the table. Put sensitivity labels and sensitive information types in separate rules.6
- Choose the policy mode. Start in simulation with your pilot group, then turn it on.1, 6
Limits of the Copilot location 6
Limit What it means Custom template only No predefined template offers this location One location No other location can share the policy No admin units The policy covers the full directory or named users and groups Up to four hours Changes can take that long to reach Copilot Prompt text only Files uploaded into a prompt are not scanned Email from 1 January 2025 Label protection covers emails sent on or after that date; calendar invites are not covered Besides the DLP roles in Phase 1, Microsoft Entra AI Admin and Purview Data Security AI Admin (or the Purview Data Security AI Admins role group) can create and edit policies for this location.6
In PowerShell
The Copilot location is set with
-Locationsand-EnforcementPlanes. This follows Learn's example, plus-Mode TestWithoutNotifications: without it the policy is created on, becauseEnableis the default. It covers the whole tenant and has no rules yet. Add a rule in the portal or withNew-DlpComplianceRule -AdvancedRule, and keep the policy in simulation until you have read the results.43, 44PowerShell $loc = '[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{"Type":"Tenant","Identity":"All"}]}]' New-DlpCompliancePolicy -Name "{copilot-policy-name}" ` -Locations $loc -EnforcementPlanes @("CopilotExperiences") ` -Mode TestWithoutNotificationsCmdlet reference 43
Why DLP does not change who can open a file. Copilot shows only what the user can already reach, so labels and sharing controls still do the main work.6
Check a pilot user who enters a blocked type of information gets a message that the request can't be completed because it contains sensitive information. A labelled file can still appear in citations, but its content is not used in the answer.6
Tip
Each block message carries a Learn about access restrictions link. In the rule's policy tip settings, select Provide a compliance URL for the end user to learn more about your organization's policies and point it at your own guidance page.6
Done when labels are applied to the content that matters, and access and sharing controls reduce the exposure you set out to reduce. You have tested the approved Copilot scenario and seen the block. Label definitions or publishing policies alone are not enough.
-
Apply endpoint DLP policies to devices
Optional
Endpoint DLP extends your policies to Windows and macOS devices. It can audit or restrict copying to USB storage, uploads to cloud services, printing, the clipboard, network shares, Bluetooth and remote desktop sessions.55
Requirement Detail Licence Microsoft 365 E5/A5/G5, Microsoft Purview Suite, or Microsoft 365 E5/A5/F5/G5 Information Protection & Governance Windows Windows 10 1809 and later, Windows 11, Windows Server 2019 and later macOS The three latest released major versions Anti-malware client Version 4.18.2110 or newer Role to turn on device monitoring Compliance admin, Security admin or Global admin In the portal
- In the Microsoft Purview portal, go to Settings > Device onboarding > Devices.57
- Select Turn on device onboarding, then allow up to 30 minutes for it to apply.57
- Devices already onboarded to Microsoft Defender for Endpoint appear in the list automatically. They need only device monitoring turned on.55, 57
- For other devices, select Onboarding, choose a Deployment method and download the package. Windows supports Group Policy, Configuration Manager, Intune, a local script or non-persistent VDI. macOS supports Intune or JAMF Pro.56, 57
- Check browser and domain rules at Data loss prevention > Overview > Data loss prevention settings > Endpoint settings.58
- Create or edit a policy, turn on the Devices location and scope it to your pilot users. Use the action Audit or restrict activities on devices.55
Microsoft's interactive guide "Apply Microsoft Purview Endpoint DLP policies to devices" walks through the same flow as a click-through demo.
In PowerShell
The
-EndpointDlpLocationparameter needs the Compliance Administrator or Compliance Data Administrator role in Microsoft Entra ID.43PowerShell New-DlpCompliancePolicy -Name "{device-policy-name}" ` -EndpointDlpLocation "{pilot-user-email}" ` -Mode TestWithoutNotifications # Simulation needs a rule to evaluate: add one with New-DlpComplianceRule, # as in the Create a DLP policy taskCmdlet reference 43
Why an onboarded device sends audited activity to Activity explorer even before any policy targets it. You can see how sensitive files are handled before you decide what to restrict.55
Check each onboarded device appears in the devices list and reports audit activity to Activity explorer. Policy updates generally reach devices in about an hour.55, 56
Tip
DLP in Microsoft Edge for Business needs no device onboarding. It covers Windows 10 and 11 devices managed by Microsoft Intune. Protection for unmanaged cloud apps is billed pay-as-you-go.2, 59
The default devices policy already audits credit card numbers on every onboarded device, without blocking anything.46
Done when supported, licensed devices are onboarded and reporting. You have tested the intended app, browser and removable media behaviour with pilot users and seen the activity. A policy scoped to devices does not prove the devices are protected.
-
Migrate policies from other platforms
Optional
If you are moving from Symantec or Forcepoint DLP, Microsoft's migration assistant converts your existing policies into Purview DLP policies. It is a Windows desktop application that maps each policy and creates the equivalent through PowerShell, in simulation mode.60
What the assistant needs 60, 61
Requirement Detail Source Symantec DLP 15.0 to 16.0 (policy XML export), or Forcepoint DLP 8.0 to 10.0 (policy backup) Target workloads Exchange, SharePoint, OneDrive, Teams and endpoint devices, each licensed for DLP Role Global Administrator or Compliance Administrator Software PowerShell 7.2.6 or higher, and .NET desktop runtime 6.0.13 or higher Steps
- Export your policies from the source: an XML export from Symantec, or a policy backup from Forcepoint.60
- Download and install the assistant from the link in the Get started with the migration assistant article.61
- Work through its five steps: Input, Analyze, Rationalize, Migrate and Report.60
- Read the report, which lists policies as migrated, partially migrated or failed.60
- Review each migrated policy in the Microsoft Purview portal while it runs in simulation, then take it through the stages above.1, 60
The migration assistant's five stages, from the source export to the report. Diagram · Microsoft Learn, Learn about the Microsoft Purview Data Loss Prevention migration assistant for Symantec and Forcepoint Check each migrated policy appears in Data loss prevention > Policies in simulation.
Get-DlpComplianceRule -Policy "{policy-name}"lists the rules it created.60, 62Tip
If you also use Microsoft Defender for Cloud Apps, its file policies are retiring on 6 January 2027. Recreate them as Purview DLP or auto-labelling policies before then. The Defender portal has its own DLP to Purview migration tool at Cloud apps > Policies > Policy management, which creates the new policies in test mode with notifications.49
Done when the migration report and the source controls have been compared with the new rules and exceptions. Every intended behaviour has been retested and the source-to-target mapping recorded. Similar policy names do not prove the policies are equivalent.
Phase 4 · Operating.
Outcome you monitor DLP alerts and incidents, tune policies on real activity, and DLP is part of your security operations work.7, 63
Phase 4 is running DLP day to day. You review the alerts your policies raise, check that each policy matches what you expect, and feed what you find back into the rules. The DLP alert lifecycle has six stages: trigger, notify, triage, investigate, remediate and tune. This phase covers the last four.63
Watch out
A built-in alert tuning rule in Microsoft Defender XDR now turns DLP signals into behaviors. A behavior raises no alert and never reaches the incident queue, so the queue can look empty while your policies match. The signals stay in advanced hunting, in the BehaviorInfo and BehaviorEntities tables. To work DLP alerts in Defender, disable the rule under System > Settings > Microsoft Defender XDR > Rules > Alert tuning. Otherwise, work them from Data loss prevention > Alerts in the Microsoft Purview portal.7, 64
-
Alerts and incidents
An alert is raised when a rule match meets the rule's alert settings. An incident in the Microsoft Defender portal groups related alerts so an analyst can work them together.7, 63
Where DLP alerts show up 7, 8, 63, 64, 65
Where What you see Retention Licence Microsoft Defender portal, Incidents & alerts > Incidents DLP incidents and their alerts, only once the built-in DLP alert tuning rule is disabled 6 months Office 365 E5/A5, Microsoft 365 E5/A5, Microsoft 365 E5/A5 Compliance, or Microsoft 365 E5/A5 Information Protection and Governance Microsoft Defender portal, advanced hunting (BehaviorInfo, BehaviorEntities) DLP signals kept as behaviors while the tuning rule is on 30 days Not published for DLP behaviors Microsoft Purview portal, Data loss prevention > Alerts DLP alerts with their events, status and a Copilot summary 30 days Single-event alerts: any DLP subscription. Aggregated (threshold) alerts: E5, A5 or G5, or a listed add-on -
Review alerts and incidents
Required
Reviewing alerts shows how your policies behave in real work and which matches need a response. Each alert carries the content, location and conditions that triggered it.20, 63
In the portal: Microsoft Defender
- In the Microsoft Defender portal, go to System > Settings > Microsoft Defender XDR > Rules > Alert tuning. Select the built-in DLP rule, then Disable, if DLP alerts should reach the incident queue.7, 64
- Go to Incidents & alerts > Incidents.66
- Select Add filter > Service/detection sources > Microsoft Data Loss Prevention.7
- Open an incident, then open one of its alerts. Read the Alert story and its Related Events for the policy, the rule, the user and the device.7
- Open the Sensitive info types tab to see what was detected, and the Source tab to see the content. The Source tab needs the Data classification content viewer role.7
- Decide whether the match is a true positive or a false positive, from the content and its business context.63, 67
- Select Manage incident. Set Status to In progress while you work and Resolved when you finish, set the Classification, and add a comment recording what you found.7, 67
A built-in alert tuning rule's details pane, with Disable at the top. Learn shows a different rule here; the DLP rule has the same pane. Screenshot · Microsoft Learn, Investigate alerts in Microsoft Defender XDR Incidents start as Active. The classifications are True positive, Informational, expected activity and False positive.67
Manage incident in the Defender portal: status, classification and a comment recording the outcome. Screenshot · Microsoft Learn, Manage incidents in the Microsoft Defender portal (legacy) In the portal: Microsoft Purview
- In the Microsoft Purview portal, go to Data loss prevention > Alerts.20
- Select an alert, then Summarize with Copilot for a short summary.20
- Select View details. Read the Overview tab for the policy and rule, and the Events tab for each matched event.20
- Assign the alert, add a comment and set its status to Investigating. Set it to Resolved once you have decided.20, 63
Roles and licences
- Defender portal: Office 365 E5/A5, Microsoft 365 E5/A5, Microsoft 365 E5/A5 Compliance, or Microsoft 365 E5/A5 Information Protection and Governance.7
- Defender roles: Manage Alerts or View-Only Manage Alerts, with DLP Compliance Management or View-Only DLP Compliance Management. Information Protection Analyst also works.7
- Purview Alerts dashboard: Manage alerts, plus DLP Compliance Management or View-Only DLP Compliance Management.20
Why each outcome tells you whether a threshold, scope or exception needs changing. That decision is the tune stage of the lifecycle.63
Check a DLP incident in Defender shows Resolved with a classification and a comment, or a Purview alert shows Resolved with a comment.20, 67
Done when you have triaged, investigated and closed the DLP incidents in your scope and recorded each outcome. An alert that exists is not proof that someone investigated it.
-
Verify policies are working
Recommended
Verification shows whether each policy detects the content you expect, in the locations you scoped. Do it before you tune, so changes rest on evidence rather than guesses.5, 21
In the portal
- In the Microsoft Purview portal, go to Data loss prevention > Activity explorer. Set the date range.21, 68
- Filter the activity to DLP rule matched, or apply the filter set DLP policies that detected activities.5, 21
- Open an event to see the matched policy, the rule and the other conditions that matched.21
- Pair each
DLPRuleMatchevent with the user activity beside it, such asCopyToClipboardorCloudEgress. The activity names the policy, and theDLPRuleMatchevent holds the text around the match.5 - Go to Solutions > Data Lifecycle Management > Explorers > Content explorer, now labelled classic. Type the sensitive information type or label from your policy into the filter.29
- Drill into the locations and confirm they line up with the workloads the policy covers.29
- For the newer view, go to Solutions > Information Protection > Explorers > Data explorer.30
- Compare what you see with your alert outcomes, and record false positives, missed locations and scopes that are too broad.
In PowerShell
Read-only checks confirm a policy's mode, that it has reached each location, and its rules.42, 45, 62
PowerShell Connect-IPPSSession -UserPrincipalName {admin-upn} # Mode and distribution status of one policy Get-DlpCompliancePolicy -Identity "{policy-name}" -DistributionDetail | Format-List Name, Mode, DistributionStatus # Every rule in that policy Get-DlpComplianceRule -Policy "{policy-name}"Cmdlet reference 45
View, What it shows, Data window, Access 21, 29, 30
View What it shows Data window Access Activity explorer DLP rule matches and other activity from the Microsoft 365 unified audit log 30 days, with a 60 to 90 minute lag Information Protection Admin, Analyst or Investigator, or role groups such as Compliance Administrator, Security Administrator or Security Reader Content explorer (classic) Items classified by sensitive information type or label, not policy matches Counts can take up to 7 days to update (14 for SharePoint) Content Explorer List viewer to list items, Content Explorer Content viewer to open them Data explorer The newer view of classified items Not published by Microsoft Data Explorer List viewer and Data Explorer Content viewer The Content explorer and Activity explorer views need E5, A5 or G5 licensing. On E3, A3 or G3 the data is still gathered, so it is there when you upgrade.2
Why an alert shows only what a rule's alert settings report, while Activity explorer shows every match.5, 21
Check Activity explorer lists DLP rule matched events for your pilot users under the policy name.
Get-DlpCompliancePolicyreturns the mode you expect.5, 45Tip
An empty Activity explorer right after you turn a policy on usually means the data hasn't caught up, not that the policy failed. Wait 60 to 90 minutes before you look again.21
Done when classification, activity, alert and user or device outcomes agree for your pilot, and you have recorded detections, expected enforcement and any missed or unexpected matches.
-
Accelerate DLP investigations with Security Copilot
Recommended
Security Copilot shortens triage. It summarises an alert in plain language and draws related signals together, so the analyst starts with context.20, 69
In the portal
- Check your entitlement. Security Copilot is included with Microsoft 365 E5 and E7, at 400 Security Compute Units (SCUs) a month per 1,000 paid user licences, up to 10,000 SCUs a month. It is turned on automatically in a phased rollout.70
- Without E5 or E7, buy SCUs under the existing pricing model.70
- Open Microsoft Security Copilot at securitycopilot.microsoft.com, select Sources in the prompt bar, and on Manage plugins confirm the Purview toggle is On. It is on by default.69
- In the Microsoft Purview portal, go to Data loss prevention > Alerts, select an alert and select Summarize with Copilot.20
- In the Microsoft Defender portal, open a DLP alert and select Summarize (preview).7
- To ask your own questions, select the Copilot icon in the Purview top navigation bar.69
- Check every summary for accuracy and completeness before you act on it.21, 69
The Copilot control in the Purview portal's top bar, for your own questions. Screenshot · Microsoft Learn, Security Copilot in Microsoft Purview Security Copilot's incident summary in the Defender portal (preview). Screenshot · Microsoft Learn, Summarize incidents with Microsoft Copilot in Microsoft Defender Feature, Where, Status 7, 20, 21
Feature Where Status Summarize with Copilot on a DLP alert Purview, Data loss prevention > Alerts Available Summarize on an alert Defender alert page Preview Security Copilot in Activity explorer Purview, Activity explorer Preview Alert Triage Agent view Purview, Data loss prevention > Alerts Preview Why a summary gives the analyst the policy, rule, file, user and status at a glance, which speeds the true or false positive call.20
Check Summarize with Copilot returns a summary that names the alert's policy, file and user.20
Watch out
The Triage Agent in Data Loss Prevention uses SCUs and won't run without them. Once set up, it starts within 30 to 60 minutes and works through DLP alerts from the past 30 days. Check your SCU allowance before you deploy it.71
Done when you have confirmed licensing and access, and your analysts use Security Copilot in the approved investigation workflow while still reviewing each summary and decision themselves.
Review your plan.
The planner keeps each task's status and due date in this browser. Review lists all 18 tasks by phase, each with its status and due date. At the top it counts tasks Not started, In progress, Completed, Backlog and Not applicable, and shows how many are overdue. It then reads "Completed X of Y applicable tasks". A task marked Not applicable needs a short reason, and it leaves the count. Completed is your own record that the work is done, not a compliance certificate.
Save and resume
- Select Export plan to save the plan as a JSON file on your device. It holds each task's id, status, due date, reason and when it changed. Nothing else.
- To pick up later, on another browser or another machine, select Import plan and choose the same file. Every task returns to the status and due date it had when you exported it.
- An import replaces the plan in this browser. A file that is damaged, too large or not a LensIQ DLP plan is refused whole, and your current plan stays as it was.
- Select Clear saved progress to remove the plan from this browser.
The file never leaves your device unless you send it somewhere. Without JavaScript the page still reads in full; only the planner needs it.
- Not started
- 0
- In progress
- 0
- Completed
- 0
- Backlog
- 0
- Not applicable
- 0
- Overdue
- 0
| Task | Status | Due | Evidence |
|---|---|---|---|
| Phase 2 · Preparation | |||
| Set up workloads | · Overdue | · | |
| Add or update roles | · Overdue | · | |
| Set up discovery and awareness | · Overdue | · | |
| Plan for implementation | · Overdue | · | |
| Complete the interactive guide | · Overdue | · | |
| Assess data security posture in DSPM (classic) | · Overdue | · | |
| Review AI data exposure in DSPM for AI (classic) | · Overdue | · | |
| Phase 3 · Deploying | |||
| Create a DLP policy | · Overdue | · | |
| Test DLP policies | · Overdue | · | |
| Review alerts | · Overdue | · | |
| Turn the policy on | · Overdue | · | |
| Deploy Teams DLP | · Overdue | · | |
| Apply Copilot-ready protections | · Overdue | · | |
| Apply endpoint DLP policies to devices | · Overdue | · | |
| Migrate policies from other platforms | · Overdue | · | |
| Phase 4 · Operating | |||
| Review alerts and incidents | · Overdue | · | |
| Verify policies are working | · Overdue | · | |
| Accelerate DLP investigations with Security Copilot | · Overdue | · | |
Evidence comes from a report written by playbook-dlp-collect-evidence.ps1 (Verified, Not met, Needs baseline, Unknown, Manual review). It is shown beside each task while this page is open, never saved, and never changes a status.
The evidence collector.
The evidence collector is a PowerShell script you download and run yourself. It only reads, and it writes one JSON report on your own machine. It never signs in, installs modules, assigns roles or changes a policy.
What it reads
- DLP policies and their rules, with
Get-DlpCompliancePolicyandGet-DlpComplianceRule. It compares one named policy's mode, scope and rule count with the values you expect.45, 62 - Role group membership counts, with
Get-RoleGroupMember, for the groups you name. The report holds counts, never names.17 - Optionally, sensitivity label definitions and label policies, with
Get-LabelandGet-LabelPolicy.72, 73 - Optionally, the tenant's subscribed licences, with
Get-MgSubscribedSkufrom Microsoft Graph PowerShell.14
It needs PowerShell 7 with the ExchangeOnlineManagement module, and a Security & Compliance session you have already opened with Connect-IPPSSession. The licence read also needs a Microsoft Graph session from Connect-MgGraph.42, 74
What each result means
| Result | Meaning |
|---|---|
| Verified | The setting you expected matched what the tenant returned |
| NotMet | The data came back, but the setting you expected did not match |
| NeedsBaseline | You didn't supply an expected value, or the baseline names a setting the collector doesn't compare |
| Unknown | The read failed: the cmdlet was missing, access was refused, or a value was too complex to compare |
| ManualReview | An inventory was collected, and a person has to judge it. It is not a pass |
Unknown is neither a pass nor a failure.
How to run it
- Connect to Security & Compliance PowerShell. Connect to Microsoft Graph too if you turn on the licence inventory.14, 42, 74
- Copy
playbook-dlp-baseline.template.jsontobaseline.json, and fill in your exact policy name, expected mode, expected scope and minimum rule count. The role group, label and licence reads run only when you list the groups inpurviewRoleGroupsand setincludeLabelInventoryorincludeLicenseInventorytotrue. Leave a field empty until you know the state you want. A value of the wrong type stops the run before anything is read. - In the same PowerShell window, run the script and point it at your baseline.
# Step 1: connect (the Graph line is optional, for the licence inventory)
Connect-IPPSSession -UserPrincipalName {admin-upn}
Connect-MgGraph -Scopes "LicenseAssignment.Read.All"
# Step 3: run the collector
./playbook-dlp-collect-evidence.ps1 -BaselinePath ./baseline.json -OutputPath ./dlp-evidence.json Scope values in the report can name users and groups, so keep the report on your machine. Don't upload it anywhere or commit it to source control.
What it can never prove
- That a policy detects real content correctly, or that tips and blocks reach users.
- That anyone reviewed an alert, ran a pilot or approved a rollout.
- That devices are onboarded and reporting.
- Which tenant it read, or a named admin's effective permissions.
- That labels are applied to content.
The report is plain JSON that anyone can edit, not a signed attestation. Select Import evidence in the planner to show each result beside its task. It is held only while the page is open, and it never changes a task's status.
The collector was tested against mocked cmdlets, not a live tenant. In a live tenant some scope values may come back as objects, and those checks report Unknown. Run it in a test tenant first.
After deployment.
Microsoft publishes four more guided setups for after DLP. Each builds on the policies and alerts you now run.
- Data Security Posture Management (DSPM): finds where sensitive data lives, who can reach it and how it is exposed, then ranks the risks and suggests fixes.33
- Manage data exfiltration with Purview: extends DLP to removable storage, printers, browsers, cloud apps and remote sessions on onboarded devices.55, 75
- Microsoft Purview Information Protection: discovers and classifies sensitive information, then protects it with sensitivity labels, encryption and access controls.76
- Insider Risk Management: detects risky user activity such as data theft, with users pseudonymised by default, and opens cases for investigation.77
Microsoft lists all of these, and this DLP guide, on its Advanced deployment guides page.78
Limits and edge cases.
- Alert timing. Alerts can take up to 3 hours to appear after you set up or change a policy's alert settings.8
- Alert grouping. Events from one rule within a minute of each other are grouped into one alert on E5, and within 15 minutes on E3.8
- Purview alert retention. Your audit log retention policy also controls how long an alert stays visible on the Alerts dashboard.20
- Matches need an action. A DLP rule matched event appears only when a user attempts an activity that matches a policy. DLP does not scan email that existed before the policy.5, 32
- Devices. For endpoint events, Activity explorer shows only the most restrictive DLP rule that matched.21
- Explorer access. A role that opens the Content explorer tab doesn't let you see items. Item access needs Content Explorer List viewer or Content Explorer Content viewer.29
- Administrative units. Administrative units set in DLP carry through to the Defender portal.7
- Triage Agent scope. The Triage Agent handles alerts only from policies scoped to Exchange, Teams, OneDrive, SharePoint and devices.71
- Advanced hunting window. Advanced hunting queries reach back 30 days. To keep Defender data longer, onboard a Microsoft Sentinel workspace.65
Where each step comes from.
- 1 Microsoft Learn Create and deploy a data loss prevention policy
- 2 Microsoft Learn Microsoft Purview service description
- 3 Microsoft Learn Data loss prevention and Microsoft Teams
- 4 Microsoft Learn Permissions in the Microsoft Purview portal
- 5 Microsoft Learn Learn about data loss prevention
- 6 Microsoft Learn Microsoft Purview DLP for Microsoft 365 Copilot and Cowork
- 7 Microsoft Learn Investigate data loss alerts with Microsoft Defender XDR
- 8 Microsoft Learn Get started with data loss prevention alerts
- 9 Microsoft Learn Free trial of Microsoft Purview Suite solutions
- 10 Microsoft Learn User roles for starting Microsoft 365 trials
- 11 Microsoft Learn Roles and role groups in Microsoft Defender for Office 365 and Microsoft Purview
- 12 Microsoft Learn Permissions for Microsoft Purview Data Security Posture Management
- 13 Microsoft Learn Connect-MgGraph
- 14 Microsoft Learn Get-MgSubscribedSku
- 15 Microsoft Learn Product names and service plan identifiers for licensing
- 16 Microsoft Learn Connect to Security & Compliance PowerShell
- 17 Microsoft Learn Get-RoleGroupMember
- 18 Microsoft Learn Get-RoleGroup
- 19 Microsoft Learn Get started with the Microsoft Purview extension for Chrome
- 20 Microsoft Learn Get started with the DLP Alerts dashboard
- 21 Microsoft Learn Get started with Activity explorer
- 22 Microsoft Learn Plan for data loss prevention
- 23 Microsoft Learn What is Microsoft 365 Data Residency?
- 24 Microsoft Learn Data Residency for Microsoft Purview
- 25 Microsoft Learn Advanced Data Residency: Overview and requirements
- 26 Microsoft Learn Advanced Data Residency: Data commitments
- 27 Microsoft Learn Get-MgUserLicenseDetail
- 28 Microsoft Learn Microsoft Entra Built-in Roles
- 29 Microsoft Learn Get started with content explorer
- 30 Microsoft Learn Get started with data explorer
- 31 Microsoft Learn Microsoft Purview Classifiers Overview
- 32 Microsoft Learn Data Loss Prevention policy reference
- 33 Microsoft Learn Learn about Microsoft Purview Data Security Posture Management (DSPM)
- 34 Microsoft Learn Learn about Data Security Posture Management (classic)
- 35 Microsoft Learn Learn how Microsoft Purview Data Security Posture Management for AI provides data security and compliance protections for Copilots and other generative AI apps - (classic)
- 36 Microsoft Learn Considerations for deploying Microsoft Purview Data Security Posture Management (DSPM) for AI
- 37 Microsoft Learn Help prevent sharing credit card numbers through email
- 38 Microsoft Learn What DLP policy templates include
- 39 Microsoft Learn Help prevent sharing sensitive items via SharePoint and OneDrive with external users
- 40 Microsoft Learn Learn about the default Office 365 DLP policy
- 41 Microsoft Learn Design a data loss prevention policy
- 42 Microsoft Learn Connect-IPPSSession
- 43 Microsoft Learn New-DlpCompliancePolicy
- 44 Microsoft Learn New-DlpComplianceRule
- 45 Microsoft Learn Get-DlpCompliancePolicy
- 46 Microsoft Learn Learn about the default DLP policy for devices
- 47 Microsoft Learn Learn about the default DLP policy in Microsoft Teams
- 48 Microsoft Learn Learn about the default DLP policy for Microsoft 365 Copilot location
- 49 Microsoft Learn Migrate file policies to Microsoft Purview
- 50 Microsoft Learn Use sensitivity labels as conditions in DLP policies
- 51 Microsoft Learn Learn about data loss prevention simulation mode
- 52 Microsoft Learn Get started with data loss prevention simulation mode
- 53 Microsoft Learn Set-DlpCompliancePolicy
- 54 Microsoft Learn Test your DLP policies
- 55 Microsoft Learn Learn about Endpoint data loss prevention
- 56 Microsoft Learn Get started with endpoint data loss prevention
- 57 Microsoft Learn Onboard Windows devices into Microsoft 365 overview
- 58 Microsoft Learn Configure endpoint DLP settings
- 59 Microsoft Learn Learn about Data Loss Prevention for Cloud Apps in Edge for Business
- 60 Microsoft Learn Learn about the Microsoft Purview Data Loss Prevention migration assistant for Symantec and Forcepoint
- 61 Microsoft Learn Get started with the Microsoft Purview Data Loss Prevention migration assistant for Symantec and Forcepoint
- 62 Microsoft Learn Get-DlpComplianceRule
- 63 Microsoft Learn Learn about investigating data loss prevention alerts
- 64 Microsoft Learn Investigate alerts in Microsoft Defender XDR
- 65 Microsoft Learn Advanced hunting overview in Microsoft Defender XDR
- 66 Microsoft Learn Prioritize incidents in the Microsoft Defender portal (Legacy)
- 67 Microsoft Learn Manage incidents in the Microsoft Defender portal (legacy)
- 68 Microsoft Learn Get started with collecting files that match data loss prevention policies from devices
- 69 Microsoft Learn Security Copilot in Microsoft Purview
- 70 Microsoft Learn Learn about Security Copilot for Microsoft 365 E5 and E7 customers
- 71 Microsoft Learn Get started with the Microsoft Purview Triage Agent in Data Loss Prevention
- 72 Microsoft Learn Get-Label
- 73 Microsoft Learn Get-LabelPolicy
- 74 Microsoft Learn Get started with the Microsoft Graph PowerShell SDK
- 75 Microsoft Learn Microsoft Purview setup guides
- 76 Microsoft Learn Microsoft Purview Information Protection
- 77 Microsoft Learn Learn about Insider Risk Management
- 78 Microsoft Learn Advanced deployment guides for Microsoft 365 and Office 365 products
Have your DLP rollout checked.
LensIQ reviews your DLP policies, simulation results and alert handling against this playbook, and tells you what to fix before enforcement reaches your users.