Use Sensitivity Labels with Microsoft 365 DLP to Protect Documents and Email
Question details
Learn how to combine sensitivity labels and data loss prevention policies to protect confidential documents and control email or sharing.

- Product
- Microsoft 365 and Microsoft Purview
- Device & OS
- not provided
- Scenario
- An organization wants to classify confidential content, apply appropriate access restrictions, and prevent unauthorized distribution through email, SharePoint, or OneDrive.
- Observed behavior
- The desired outcome is consistent classification and protection, with DLP rules that detect the intended content and restrict its distribution without unexpectedly disrupting collaboration.
Confirm that your Microsoft 365 subscription supports the labeling and DLP features you plan to use and that your account has the required Microsoft Purview permissions. Identify the users, storage locations, and external-sharing scenarios to cover before configuring policies.
Configure sensitivity labels and DLP rules for confidential content
Use labels to classify and optionally protect content, then use DLP rules to control how that content can be distributed.
Sensitivity labels and sensitive information types are different. Labels classify content and can apply protection; sensitive information types detect patterns such as account numbers, sometimes using supporting keywords. A file labeled Confidential does not necessarily contain information that matches a sensitive information type.
Where supported, choose a sensitivity-label condition if the DLP rule must act on an applied label. Use sensitive information type conditions when the rule should detect the underlying content instead.
Open the Microsoft Purview portal and go to Solutions > Information Protection > Sensitivity labels. Create a label, select the scope for files and email, and configure encryption or access permissions if required.
In Information Protection, open the label publishing policies area and publish the label to the intended users or groups. After the policy becomes available, users can apply it through the Sensitivity control in supported Microsoft 365 apps.
Go to Solutions > Data Loss Prevention > Policies and select Create policy. Choose a template or custom policy, then select the locations to protect, such as Exchange email, SharePoint sites, and OneDrive accounts.
In the policy's rule editor, add a sensitivity-label condition if it is supported for the selected location. Alternatively, select the relevant sensitive information types and configure their detection thresholds. Review whether multiple conditions must all match or whether any one can trigger the rule.
In the rule's Actions section, select the available restriction for the chosen location. For example, configure blocking or access restrictions for external recipients or sharing, and add policy tips or override options if your organization's policy permits them.

Test DLP enforcement and encryption before a broad rollout
Use this approach to confirm that rules match the right content and that protection does not disrupt required Microsoft 365 workflows.
Use WPS Office for Everyday Editing of Unrestricted Office Files
WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format compatibility for an easy transition to everyday document work. It does not configure or replace Microsoft Purview sensitivity labels or DLP; use your organization's approved Microsoft 365 tools for protected-content workflows.

Frequently Asked Questions
Is a sensitivity label the same as a sensitive information type?
No. A sensitivity label classifies content and can apply protection. A sensitive information type detects content patterns, sometimes with supporting keywords. In the Microsoft Purview DLP rule editor, choose the condition that matches your goal rather than assuming a content detector recognizes the applied label.
Can DLP stop a confidential email from being sent?
Yes, when an enforced DLP policy covers Exchange email, the message matches the rule conditions, and the configured action blocks sending to the relevant recipients. In Microsoft Purview > Solutions > Data Loss Prevention > Policies, review the policy's locations, conditions, actions, and override settings.
Why does a Confidential label not trigger my DLP rule?
The rule may be looking for sensitive information types rather than the label, or the file's location may be outside the policy scope. Open the DLP policy's rule editor and check its conditions, location support, and enforcement status. A label-only test file helps distinguish label detection from content detection.
Will label encryption prevent SharePoint or OneDrive collaboration?
Not necessarily. Support depends on the encryption configuration and your tenant's sensitivity-label integration settings. Test a protected file in SharePoint or OneDrive with authorized users and verify coauthoring, search, and compliance workflows before deploying the label widely.
Can WPS Office replace Microsoft Purview DLP?
No. WPS Office is an alternative for everyday document editing, not a replacement for Microsoft 365 tenant-level DLP or sensitivity-label administration. Configure those controls in Microsoft Purview and use approved apps for encrypted or rights-managed files.




