Sensitivity labels describe and, where configured, protect information. Microsoft Purview Data Loss Prevention (DLP) adds another control: evaluating content and activity against rules, then taking actions such as notifying users, restricting access or blocking a message. Part 3 of this series moves from classification into practical controls for Exchange Online, SharePoint Online and Microsoft Teams.

The objective is not to block every item containing sensitive information. It is to identify a defined business risk, apply an appropriate control and provide a workable exception process. A policy that generates unexplained interruptions will be difficult to operate, even if its detection logic is technically correct.

Start with one scenario: for example, reducing external disclosure of customer financial information. Establish how that information appears in email, documents and conversations, then design and validate controls for each location. Microsoft Purview provides a shared policy framework, but the workloads do not have identical conditions, actions or processing behaviour.

1. Establish scope, licensing and ownership

Microsoft Purview DLP policies contain locations, rules and settings. Locations determine where the policy applies; rules define the conditions to evaluate and the actions to take. For this deployment, distinguish Exchange email, SharePoint documents and Teams chat and channel messages. Include OneDrive accounts when the intended coverage includes files stored there.

This distinction matters particularly in Teams. Channel files are stored in SharePoint, while files uploaded to a chat are generally stored in the uploader’s OneDrive. A policy targeting Teams messages does not replace DLP coverage for those storage locations. Private and shared channels also use separate SharePoint sites, which must be considered when scoping site coverage.

Confirm licensing before promising coverage. Teams message DLP has different licensing requirements from DLP for Exchange, SharePoint and OneDrive. Check Microsoft’s current service and licensing guidance against the actual subscriptions and users in scope. Availability of a policy option in an administrator’s interface is not, by itself, a licensing assessment.

Assign a business owner to define unacceptable disclosure and approve exceptions.

Assign a technical owner to maintain rules, deployment scope and change records.

Assign an operational owner to review alerts and investigate recurring problems.

Grant administrators and investigators only the Microsoft Purview permissions needed for their tasks. Treat access to matched content as a separate, sensitive permission decision.

2. Translate a business risk into reliable detection

Write a policy statement before configuring the rule: “Customer financial records must not be emailed to external recipients unless an approved exception applies.” This establishes the information, activity and boundary. “Block sensitive data” does not provide enough detail to select conditions or assess whether the result is correct.

Sensitive information types identify information using defined patterns and supporting evidence. Where the selected type supports them, confidence levels and instance counts help tune matching. A low instance threshold may be appropriate for a highly restricted identifier, but inappropriate for routine correspondence that legitimately contains isolated examples.

Sensitivity labels can also be used in supported DLP conditions. This connects the classification work from Part 2 to enforcement, but do not assume that every location supports every label-based condition. In particular, do not treat the label on a Teams-connected site or team as a sensitivity label applied to each chat message.

For a first deployment, choose one or two information categories and build a small, understandable rule set. Use separate policies when workloads require materially different actions or exception handling. Separate policies are not mandatory, but they can make ownership, troubleshooting and staged enforcement easier.

Document each condition, including whether conditions must all match or whether alternatives are permitted.

Record any external-sharing or recipient condition explicitly; detecting sensitive content alone does not establish an unauthorised disclosure.

Use a suitable confidence level and instance threshold, then validate both against representative content.

Make exclusions narrow, justified and reviewable. Avoid excluding a whole department merely because its initial match volume is high.

Create a test set containing expected matches, legitimate non-matches and borderline cases. Use approved synthetic examples rather than copying production personal information into a test document. Measure whether the rule identifies the intended scenario, not merely whether it produces any matches.

3. Design the action for each workload

In Exchange Online, DLP evaluates messages within the supported email policy flow. Depending on the rule configuration, it can restrict delivery, notify users and provide policy tips in supported Outlook experiences. Recipient conditions help distinguish internal communication from external disclosure. Select actions from the options supported for the Exchange location rather than assuming a document-sharing action translates directly to email.

For an initial financial-information scenario, evaluate sensitive information together with the external-recipient condition. Where the policy permits a user override, require a business justification when appropriate and make the permitted use clear. An override is a controlled exception, not proof that the disclosure was acceptable.

In SharePoint Online and OneDrive, DLP can detect sensitive content in supported files and restrict access according to the configured action. Restricting access for people outside the organisation is different from restricting access more broadly. Select the action that addresses the risk without unintentionally preventing necessary internal work.

Do not describe SharePoint and OneDrive DLP as a guaranteed instantaneous pre-upload control. Content evaluation and policy application involve service processing, and supported file types and inspection limits matter. Validate the real user journey: upload, sharing, notification, access restriction and remediation. DLP also does not replace correctly configured sharing settings and permissions.

For Teams, message DLP evaluates chat and channel messages and can block messages containing sensitive information when the configured rule matches. Microsoft provides a notification experience for blocked messages. Files shared through Teams require the relevant SharePoint or OneDrive DLP policy; protecting the message and protecting the linked document are separate requirements.

Avoid simply copying the email rule into Teams. First confirm which conditions and actions the Teams location supports. Then test representative chats and channel conversations, including relevant external collaboration scenarios. A successful test of an internal channel message does not demonstrate coverage of every collaboration arrangement.

4. Build the policy and validate it in simulation

In the Microsoft Purview portal, open Data Loss Prevention and create a policy using a suitable template or a custom configuration. Templates provide a starting point, not a completed assessment of your organisation’s obligations. Review the selected information types, locations, conditions and actions before proceeding.

Give the policy a descriptive name, such as “DLP — Customer financial data — Exchange — Pilot”. Record the owner and intended outcome in its description.

Select the required locations and use supported location scoping to identify a manageable pilot population or set of sites. Verify the scope independently for each location.

Configure the detection conditions and the intended enforcement actions. Review notification, override and alert settings separately.

Use simulation mode before enabling enforcement. Where available, choose whether to show policy tips during simulation so that user guidance can also be assessed.

Run documented tests for positive matches, negative matches, permitted activity and attempted exceptions. Check the resulting events and user experience.

Simulation allows you to evaluate policy matches without immediately applying the configured blocking actions. It is not a substitute for a controlled enforcement pilot: an organisation must still verify the actual blocking, access restriction and remediation experience before broad deployment.

Allow for policy distribution and workload processing. Do not conclude that a rule is ineffective after a single immediate test, and do not change multiple variables while waiting for a result. Record when the policy changed, when the test occurred and which location processed the content.

Define promotion criteria in advance. Useful criteria include successful detection of the agreed test cases, acceptable handling of legitimate work, functioning notifications and a named team able to review incidents. Expand coverage only after reviewing those results with the business owner.

5. Operate DLP as an ongoing control

Configure alerting deliberately. A policy match and an alert are not interchangeable: alert configuration determines when matching activity generates an alert for review. Use severity, triggering behaviour and available aggregation options to support investigation rather than treating every match as equally urgent.

Review DLP alerts and relevant Activity explorer data with appropriately authorised accounts. Investigators should establish what matched, which activity occurred, which action was applied and whether an exception or override was involved. Access to sensitive evidence should follow the organisation’s investigation and privacy procedures.

PowerShell can support a configuration inventory. The following read-only commands use Security & Compliance PowerShell through the ExchangeOnlineManagement module. They assume the module is installed and the administrator has the required permissions. The output lists policies and rules; it does not prove that a policy has processed a particular message or file.

Import-Module ExchangeOnlineManagement
Connect-IPPSSession

# Review policy names and configured modes.
Get-DlpCompliancePolicy |
    Select-Object Name, Mode |
    Format-Table -AutoSize

# List rule names for further configuration review.
Get-DlpComplianceRule |
    Select-Object Name |
    Format-Table -AutoSize

Use the inventory alongside the portal to identify unexpected policies, inconsistent naming and policies left in simulation. Inspect detailed configuration before changing anything. Avoid bulk enforcement changes based only on a policy’s name or mode.

During review, separate detection problems from process problems. Repeated false positives may require narrower conditions or better supporting evidence. Repeated justified overrides may indicate a legitimate workflow that needs a safer approved route. Repeated unjustified disclosure attempts require investigation, not an automatic expansion of exclusions.

6. Deployment checklist

The business risk, information categories and external-sharing boundary are documented.

Licensing and administrative permissions have been checked for every selected location.

Teams messages and the SharePoint or OneDrive files shared through Teams have distinct, verified coverage.

Detection thresholds, exceptions and actions have passed representative positive and negative tests.

Simulation results have been reviewed, and a limited enforcement pilot has validated the user experience.

Policy tips, notifications and override instructions provide a clear route to approved assistance.

Alert ownership, evidence-access permissions, review frequency and a rollback procedure are recorded.

7. Conclusion: enforce a defined boundary, then improve it

Effective Microsoft Purview DLP combines accurate detection, workload-appropriate actions and accountable operations. Start with a specific disclosure risk, validate each location independently and move from simulation to enforcement through a controlled pilot. Keep exceptions visible and use operational evidence to improve the policy.

Exchange, SharePoint and Teams DLP address information within those supported services. They do not, by themselves, establish controls over every subsequent device activity. Part 4 examines Endpoint DLP and the additional decisions needed when sensitive information is used on managed endpoints.

Microsoft Learn: Learn about Microsoft Purview Data Loss Prevention

Microsoft Learn: Data Loss Prevention policy reference

Microsoft Learn: Data Loss Prevention and Microsoft Teams

Microsoft Learn: Learn about Data Loss Prevention simulation mode

Microsoft Learn: Get started with the Data Loss Prevention alerts dashboard

Microsoft Learn: Get-DlpCompliancePolicy PowerShell reference


Originally published on Solution Savy. Need help with this? Book a consultation.