Learn about data loss prevention
Organizations have sensitive information under their control such as financial data, proprietary data, credit card numbers, health records, or social security numbers. To help protect this sensitive data and reduce risk, they need a way to prevent their users from inappropriately sharing it with people who shouldn't have it. This practice is called data loss prevention (DLP).
In Microsoft Purview, you implement data loss prevention by defining and applying DLP policies. With a DLP policy, you can identify, monitor, and automatically protect sensitive items across:
- Microsoft 365 services such as Teams, Exchange, SharePoint, and OneDrive
- Office applications such as Word, Excel, and PowerPoint
- Windows 10, Windows 11 and macOS (three latest released versions) endpoints
- non-Microsoft cloud apps
- on-premises file shares and on-premises SharePoint.
DLP detects sensitive items by using deep content analysis, not by just a simple text scan. Content is analyzed for primary data matches to keywords, by the evaluation of regular expressions, by internal function validation, and by secondary data matches that are in proximity to the primary data match. Beyond that DLP also uses machine learning algorithms and other methods to detect content that matches your DLP policies.
If you're not an E5 customer, use the 90-day Microsoft Purview solutions trial to explore how additional Purview capabilities can help your organization manage data security and compliance needs. Start now at the Microsoft Purview compliance portal trials hub. Learn details about signing up and trial terms.
Before you begin
If you're new to Microsoft Purview DLP, here's a list of the core articles you'll need as you implement DLP:
- Administrative units (preview)
- Learn about Microsoft Purview Data Loss Prevention - the article you're reading now introduces you to the data loss prevention discipline and Microsoft's implementation of DLP
- Plan for data loss prevention (DLP) - by working through this article you will:
- Data Loss Prevention policy reference - this article introduces all the components of a DLP policy and how each one influences the behavior of a policy
- Design a DLP policy - this article walks you through creating a policy intent statement and mapping it to a specific policy configuration.
- Create and Deploy data loss prevention policies - This article presents some common policy intent scenarios that you'll map to configuration options, then it walks you through configuring those options.
Licensing and Subscriptions
See the licensing requirements for Information Protection for details on the subscriptions that support DLP.
DLP is part of the larger Microsoft Purview offering
DLP is just one of the Microsoft Purview tools that you'll use to help protect your sensitive items wherever they live or travel. You should understand the other tools in the Microsoft Purview tools set, how they interrelate, and work better together. See, Microsoft Purview tools to learn more about the information protection process.
Protective actions of DLP policies
DLP policies are how you monitor the activities that users take on sensitive items at rest, sensitive items in transit, or sensitive items in use and take protective actions. For example, when a user attempts to take a prohibited action, like copying a sensitive item to an unapproved location or sharing medical information in an email or other conditions laid out in a policy, DLP can:
- show a pop-up policy tip to the user that warns them that they may be trying to share a sensitive item inappropriately
- block the sharing and, via a policy tip, allow the user to override the block and capture the users' justification
- block the sharing without the override option
- for data at rest, sensitive items can be locked and moved to a secure quarantine location
- for Teams chat, the sensitive information won't be displayed
All DLP monitored activities are recorded to the Microsoft 365 Audit log by default and routed to Activity explorer. When a user performs an action that meets the criteria of a DLP policy, and you have alerts configured, DLP provides alerts in the DLP alert management dashboard.
A DLP implementation typically follows these major phases.
Plan for DLP
DLP monitoring and protection are native to the applications that users use every day. This helps to protect your organization's sensitive items from risky activities, even if your users are unaccustomed to data loss prevention thinking and practices. If your organization and your users are new to data loss prevention practices, the adoption of DLP may require a change to your business processes, and there will be a culture shift for your users. But, with proper planning, testing and tuning, your DLP policies will protect your sensitive items while minimizing any potential business process disruptions.
Technology planning for DLP
Keep in mind that DLP as a technology can monitor and protect your data at rest, data in use and data in motion across Microsoft 365 services, Windows 10, Windows 11, and macOS (three latest released versions) devices, on-premises file shares, and on-premises SharePoint. There are planning implications for the different locations, the type of data you want to monitor and protect, and the actions to be taken when a policy match occurs.
Business processes planning for DLP
DLP policies can block prohibited activities, like inappropriate sharing of sensitive information via email. As you plan your DLP policies, you must identify the business processes that touch your sensitive items. The business process owners can help you identify appropriate user behaviors that should be allowed and inappropriate user behaviors that should be protected against. You should plan your policies and deploy them in test mode, and evaluate their impact via activity explorer first, before applying them in more restrictive modes.
Organizational culture planning for DLP
A successful DLP implementation is as much dependent on getting your users trained and acclimated to data loss prevention practices as it is on well planned and tuned policies. Since your users are heavily involved, be sure to plan for training for them too. You can strategically use policy tips to raise awareness with your users before changing the policy enforcement from test mode to more restrictive modes.
Prepare for DLP
You can apply DLP policies to data at rest, data in use, and data in motion in locations, such as:
- Exchange Online email
- SharePoint Online sites
- OneDrive accounts
- Teams chat and channel messages
- Microsoft Defender for Cloud Apps
- Windows 10, Windows 11, and macOS (three latest released versions) devices
- On-premises repositories
- Power BI sites
Each one has different pre-requisites. Sensitive items in some locations, like Exchange online, can be brought under the DLP umbrella by just configuring a policy that applies to them. Others, such as on-premises file repositories require a deployment of Azure Information Protection (AIP) scanner. You'll need to prepare your environment, code draft policies, and test them thoroughly before activating any blocking actions.
Deploy your policies in production
Design your policies
Start by defining your control objectives, and how they apply across each respective workload. Draft a policy that embodies your objectives. Feel free to start with one workload at a time, or across all workloads - there's no impact yet.
Implement policy in test mode
Evaluate the impact of the controls by implementing them with a DLP policy in test mode. Actions defined in a policy aren't applied while the policy is in test mode. It's ok to apply the policy to all workloads in test mode, so that you can get the full breadth of results, but you can start with one workload if you need to.
Monitor outcomes and fine-tune the policy
While in test mode, monitor the outcomes of the policy and fine-tune it so that it meets your control objectives while ensuring you aren't adversely or inadvertently impacting valid user workflows and productivity. Here are some examples of things to fine-tune:
- adjusting the locations and people/places that are in or out of scope
- tune the conditions that are used to determine if an item and what is being done with it matches the policy
- the sensitive information definition/s
- add new controls
- add new people
- add new restricted apps
- add new restricted sites
Stop processing more rules doesn't work in test mode, even when it's turned on.
Enable the control and tune your policies
Once the policy meets all your objectives, turn it on. Continue to monitor the outcomes of the policy application and tune as needed.
In general, policies take effect about an hour after being turned on.
DLP policy configuration overview
You have flexibility in how you create and configure your DLP policies. You can start from a predefined template and create a policy in just a few clicks or you can design your own from the ground up. No matter which you choose, all DLP policies require the same information from you.
Choose what you want to monitor - DLP comes with many predefined policy templates to help you get started or you can create a custom policy.
- A predefined policy template: Financial data, Medical and health data, Privacy data all for various countries and regions.
- A custom policy that uses the available sensitive information types, retention labels, and sensitivity labels.
Choose administrative scoping - DLP supports assigning Administrative Units to policies (preview). Administrators who are assigned to an administrative unit can only create and manage policies for the users, groups, distribution groups, and accounts that they're assigned to. So, policies can be applied to all users and groups by an unrestricted administrator, or they can be scoped to administrative units. See, Policy Scoping for more DLP specific details. See, Administrative units (preview) for the details on administrative units across Microsoft Purview Information Protection.
Choose where you want to monitor - You pick one or more locations that you want DLP to monitor for sensitive information. You can monitor:
|Exchange email||distribution groups|
|OneDrive accounts||accounts or distribution groups|
|Teams chat and channel messages||account or distribution group|
|Windows 10, Windows 11, and macOS (three latest released versions) devices||user or group|
|Microsoft Cloud App Security||instance|
|On-premises repositories||repository file path|
|Power BI (preview)||workspaces|
- Choose the conditions that must be matched for a policy to be applied to an item - You can accept pre-configured conditions or define custom conditions. Some examples are:
- item contains a specified kind of sensitive information that is being used in a certain context. For example, 95 social security numbers being emailed to recipient outside your org.
- item has a specified sensitivity label
- item with sensitive information is shared either internally or externally
- Choose the action to take when the policy conditions are met - The actions depend on the location where the activity is happening. Some examples are:
- SharePoint/Exchange/OneDrive: Block people who are outside your organization form accessing the content. Show the user a tip and send them an email notification that they're taking an action that is prohibited by the DLP policy.
- Teams Chat and Channel: Block sensitive information from being shared in the chat or channel
- Windows 10, Windows 11, and macOS (three latest released versions) Devices: Audit or restrict copying a sensitive item to a removeable USB device
- Office Apps: Show a popup notifying the user that they're engaging in a risky behavior and block or block but allow override.
- On-premises file shares: move the file from where it's stored to a quarantine folder
The conditions and the actions to take are defined in an object called a Rule.
Create and deploy a DLP policy
All DLP policies are created and maintained in the Microsoft Purview center. See, Create and Deploy data loss prevention policies for more information.
After you create a DLP policy in the compliance portal, it's stored in a central policy store, and then synced to the various content sources, including:
- Exchange Online, and from there to Outlook on the web and Outlook.
- OneDrive for Business sites.
- SharePoint Online sites.
- Office desktop programs (Excel, PowerPoint, and Word).
- Microsoft Teams channels and chat messages.
After the policy's synced to the right locations, it starts to evaluate content and enforce actions.
Viewing policy application results
DLP reports a vast amount of information into Microsoft Purview from monitoring, policy matches and actions, and user activities. You'll need to consume and act on that information to tune your policies and triage actions taken on sensitive items. The telemetry goes into the Microsoft Purview compliance portal Audit Logs first, is processed, and makes its way to different reporting tools. Each reporting tool has a different purpose.
DLP Alerts Dashboard
When DLP takes an action on a sensitive item, you can be notified of that action via a configurable alert. Rather than having these alerts pile up in a mailbox for you to sift through, the compliance portal makes them available in the DLP Alerts Management Dashboard. Use the DLP Alerts dashboard to configure alerts, review them, triage them and track resolution of DLP Alerts. Here's an example of alerts generated by policy matches and activities from Windows 10 devices.
You can also view details of the associated event with rich metadata in the same dashboard
The DLP reports show broad trends over time and give specific insights into:
- DLP Policy Matches over time and filter by date range, location, policy, or action
- DLP incident matches also shows matches over time, but pivots on the items rather than the policy rules.
- DLP false positives and overrides shows the count of false positives and, if configured, user-overrides along with the user justification.
DLP Activity Explorer
The Activity explorer tab on the DLP page has the Activity filter preset to DLPRuleMatch. Use this tool to review activity related to content that contains sensitive info or has labels applied, such as what labels were changed, files were modified, and matched a rule.
You can see the text that surrounds the matched content, like a credit card number in a DLPRuleMatch event in Activity explorer. To do this you must first enable Advanced classification scanning and protection.
DLPRuleMatch events are paired with the user activity event. The should be right next to (or at least very close to) each other in Activity explorer. You'll want to look at both because the user activity event contains details about the matched policy and the DLPRuleMatch event contains the details about the text that surrounds the matched content.
For endpoint, be sure that you have applied KB5016688 for Windows 10 devices and KB5016691 for Windows 11 devices or above
For more information, see Get started with activity explorer
To learn more about Microsoft Purview DLP, see:
- Learn about Endpoint data loss prevention
- Learn about the default data loss prevention policy in Microsoft Teams (preview)
- Learn about data loss prevention on-premises scanner
- Learn about the Microsoft Compliance Extension
- Learn about the data loss prevention Alerts dashboard
To learn how to use data loss prevention to comply with data privacy regulations, see Deploy information protection for data privacy regulations with Microsoft Purview (aka.ms/m365dataprivacy).
Submit and view feedback for