Stop data leaks quickly with labels and DLP in Microsoft Purview.
You need sensitivity labels and data loss prevention working across email, files and devices, and you don’t have a team or a year to get there. This guide follows Microsoft’s three-step lightweight model. You label new documents and block confidential content from leaving by email and sharing links. Then you cover devices and Teams. Then you add encryption, automatic labelling and controls that tighten for risky users.
It’s written for a small team, or one administrator, who knows the Microsoft 365 admin centres. You don’t need to have used Purview Information Protection or DLP (data loss prevention, the policies that stop sensitive content leaving).
Where this guide ends up.
The table below carries the model’s three steps. The screen shows where the guide ends up: DLP policies for devices, email and Teams that apply stricter actions as a user’s insider risk level rises.1, 8, 15
Microsoft’s steps at a glance
| Step | What it does | Outcome |
|---|---|---|
| Step 1 | Establish foundational data security | Good: create sensitivity labels, set defaults, deploy basic DLP policies and enable auditing |
| Step 2 | Expand protection to endpoints | Better: create custom SITs, configure client-side auto-labelling, and deploy DLP for Teams, endpoints and email |
| Step 3 | Continuous improvement | Best: encrypt files, extend service-side auto-labelling and enable Adaptive Protection |
Each step needs a larger licence than the last.
Microsoft’s guide puts Step 1 at Business Premium, Step 2 at Microsoft 365 Information Protection and Governance (IPG), and Step 3 at E5 Compliance. Treat those as planning shorthand: some features need more than their step, and the service description lists Microsoft Purview Suite where the guide says E5 Compliance. The table gives each feature’s plans as the service description or Learn states them.1, 2, 15, 16, 17
Licences by feature 2, 8, 18, 19, 20, 21
| Feature | Step | Plans that include it | Notes |
|---|---|---|---|
| Manual sensitivity labelling | 1 | Microsoft 365 E5, A5, G5, E3, A3, G3, F1, F3 and Business Premium. | |
| Default sensitivity label for a SharePoint document library | 1 | Microsoft 365 E5, A5, G5, Microsoft Purview Suite, IPG, and Office 365 E5, A5, G5. | Not Business Premium. Step 1 needs it only if you want documents to take a library’s label. |
| DLP for Exchange Online, SharePoint and OneDrive | 1 and 2 | Microsoft 365 E5, A5, G5, E3, A3, G3 and Business Premium. Office 365 E5, A5, G5, E3, A3, G3. Exchange Online Plan 2, SharePoint Online Plan 2 and OneDrive for Business Plan 2. Microsoft Purview Suite (EDU, GOV and FLW too) and Microsoft Defender + Purview Suite FLW. | |
| Audit (Standard) | 1 | Microsoft 365 E3, A3, A1, G3, F3, F1 and Business Basic, Standard and Premium; Office 365 E3, E1, A3, A1, G3, G1, F3. | Off by default for Business plans. |
| Automatic labelling in Office apps (client-side) | 2 | Microsoft 365 E5, A5, G5, Microsoft Purview Suite (GOV and FLW too), Microsoft Defender + Purview Suite FLW, Microsoft 365 E5 IPG, and Office 365 E5, A5, G5. Enterprise Mobility + Security E5, A5, G5 include the client-side part only. | Not E3 or Business Premium. |
| Endpoint DLP | 2 | Microsoft 365 E5, A5, G5, Microsoft Purview Suite (EDU, GOV and FLW too), Microsoft Defender + Purview Suite FLW, and Microsoft 365 E5, A5, F5, G5 IPG. | Not Business Premium. |
| DLP for Teams | 2 | Microsoft 365 E5, A5, G5, Microsoft Purview Suite (EDU, GOV and FLW too), Microsoft Defender + Purview Suite FLW, Microsoft 365 E5, A5, F5, G5 IPG, and Office 365 E5, A5, G5. | The Microsoft Communications DLP service must be turned on in the user’s licence. |
| Automatic labelling in Exchange, SharePoint and OneDrive (service-side) | 3 | Microsoft 365 E5, A5, G5, Microsoft Purview Suite (GOV and FLW too), Microsoft Defender + Purview Suite FLW, Microsoft 365 E5 IPG, and Office 365 E5, A5, G5. | |
| Encryption with sensitivity labels | 3 | No separate row in the service description. | Microsoft’s guide places it with Step 3 at E5 Compliance. Check your agreement before you plan on a lower plan. |
| Insider Risk Management, including analytics | 3 | Microsoft 365 E5, A5, G5, Microsoft Purview Suite (EDU, GOV and FLW too), Microsoft Defender + Purview Suite FLW, and Microsoft 365 E5, A5, F5, G5 Insider Risk Management. | Not IPG. |
| Adaptive Protection | 3 | No row of its own. It runs inside Insider Risk Management. | Its DLP integration is generally available. |
| Insider risk condition in Conditional Access | 3 | Microsoft Entra ID P2. | Preview. Conditional Access itself needs Entra ID P1, or Business Premium. |
Label new documents and block confidential content leaving.
- Outcome
- Good: create sensitivity labels, set defaults, deploy basic DLP policies and enable auditing
By the end of this step, every new document carries the Confidential/AllEmployees label unless someone changes it. DLP stops content with that label being shared outside the organisation by email, SharePoint or OneDrive. Microsoft puts this step at Business Premium or above. The one exception is a library’s default label, which needs a larger plan and which this step doesn’t rely on.1, 2, 16
-
Create the parent labels
Microsoft Purview portal › Solutions › Information Protection › Sensitivity labels
Create a top-level label for each broad level of sensitivity, for example Confidential and General.16
- Classic scheme. Select + Create a label, name it and scope it to Files & other data assets. Repeat for each parent label.12, 13
- Modern scheme. Select + Create, then Label group. A label group has only a name, descriptions, a colour and a priority.12, 13
Why Leave content marking off the parent label. A parent label can’t be applied to content, and its sublabels inherit only its colour, so the marking would never show. Put content marking on the sublabel instead.13
Watch out
Purview offers to migrate classic parent labels to label groups. Migration can’t be undone, so don’t start it as part of this step.14
-
Create the AllEmployees sublabel
Microsoft Purview portal › Solutions › Information Protection › Sensitivity labels
- Classic scheme. Select the Confidential label, select ... for Actions, then Create sublabel. Name it AllEmployees.12, 16
- Modern scheme. Select + Create, then Label, and name it AllEmployees. Then select it, select ... for Actions and Move into group, and choose the Confidential group.12
- On the scope page, select Files & other data assets. The default label for documents needs it.13, 18
- Select Groups & sites only if you also want this label on SharePoint sites and Teams. It labels the site, not the files in it.13
- Turn on content marking, such as a header or footer, so people can see the label on the document.16
The four label scopes as the label wizard names them. Screenshot · Microsoft Learn, Create and configure sensitivity labels and their policies -
Order the labels by priority
Microsoft Purview portal › Solutions › Information Protection › Sensitivity labels
- Select ... for Actions on a label, then Move up or Move down. You can also assign a priority number directly.12, 13
- Put the least sensitive labels, such as General, at the top of the list, with the lowest numbers.13
- Put the most restrictive labels at the bottom, with the highest numbers.13, 16
Why Priority decides which label wins when two could apply, and which change counts as lowering a document’s sensitivity.13
Check Your most restrictive label is the last one in the list.13
-
Publish the labels and set the default
Microsoft Purview portal › Solutions › Information Protection › Publishing policies
- On the Label policies page, select Publish label.12
- Choose all your labels. In the classic scheme, choose each parent label as well as its sublabels.12, 16
- Publish to All users and groups.16
- Set the default label for documents to Confidential/AllEmployees.16
- Name the policy and finish. Finishing the wizard publishes the policy.12, 16
Check Allow 24 hours, and up to 48, for the policy to reach the apps. A new Word document then opens with the Confidential/AllEmployees label.12
-
Turn on sensitivity labels for SharePoint and OneDrive
Microsoft Purview portal › Solutions › Information Protection › Sensitivity labels
This lets SharePoint and OneDrive read labelled Office files, and lets documents take the label of the library they’re saved in.5, 16
- Sign in as a Global Administrator.5
- If a message offers to turn on the ability to process content in Office online files, select Turn on now.5
The banner on the Sensitivity labels page that turns the setting on. Screenshot · Microsoft Learn, Enable sensitivity labels for files in SharePoint and OneDrive Check The change takes about 15 minutes. If no banner appears, the feature is most likely on already.5, 16
-
Create the email and SharePoint DLP policies
Microsoft Purview portal › Solutions › Data loss prevention › Policies › + Create policy
Create two custom policies: one for Exchange email, one for SharePoint sites and OneDrive accounts. Microsoft recommends keeping email in a policy of its own.16
- Select Enterprise applications & devices, then Custom from both the Categories and Regulations lists.23
- Name the policy. You can’t rename a DLP policy later.23
- For the email policy, select only Exchange email. For the second policy, select only SharePoint sites and OneDrive accounts.16, 23, 24
- Add the conditions Content is shared from Microsoft 365 with people outside my organization, and Content contains > Sensitivity labels > Confidential/AllEmployees.16, 23, 25
- Add the action Restrict access or encrypt the content in Microsoft 365 locations. In both policies, choose Block users from receiving email or accessing shared SharePoint, OneDrive, and Teams files, then Block only people outside your organization.16, 23, 30
- On the policy mode page, select Turn it on right away, as Microsoft’s step says, or Run the policy in simulation mode. The table compares the two.4, 16, 26
Two Microsoft positions on when to turn a DLP policy on 4, 16
This guide, Step 1 Microsoft’s DLP deployment guidance Mode to choose Turn it on right away (full enforcement). Keep it off, then run the policy in simulation mode. Before enforcement Nothing. Review simulation results, tune the policy, then run it in simulation with policy tips for a pilot group and gather feedback. What you get Protection starts as soon as the policy reaches each service. You see what the policy would block before it blocks anything. Both policies block only people outside your organisation, and only for content labelled Confidential/AllEmployees. That label is the default for every new document, so the block reaches every new document someone tries to share externally.16, 23
We recommend
We recommend running both policies in simulation mode first, even on this fast path, and reading the simulation results for external sharing the business needs to keep. Turn them on once you have checked those cases.26
-
Confirm audit logging is on
Microsoft Purview portal › Solutions › Audit
Auditing gives you the record of what users and policies did. Confirm it’s active, so there’s no gap in what you can see.16
If you followed Before you start, this is done. If the Start recording user and admin activity banner still appears, select it now.10
Check The Audit page shows no banner asking you to start recording. The PowerShell check is in Before you start.10
Watch out
Auditing isn’t on by default for Business Premium, the plan this step is written for. Don’t assume it’s on.10
Done when New documents open with the Confidential/AllEmployees label, external sharing of that label is blocked or under simulation in email, SharePoint and OneDrive, and auditing is recording.
Extend protection to devices, Teams and email.
- Outcome
- Better: create custom SITs, configure client-side auto-labelling, and deploy DLP for Teams, endpoints and email
This step teaches Purview what your own sensitive data looks like, then extends DLP to devices, Teams messages and email. Microsoft puts it at IPG or above, and its DLP policies can run in simulation first.1, 17
-
Create custom sensitive information types
Microsoft Purview portal › Solutions › Information Protection › Classifiers › Sensitive info types
A sensitive information type (SIT) is a pattern Purview uses to find data such as an employee ID. Microsoft’s guide suggests three to start with.17, 27
Microsoft’s example custom SITs 17
SIT Primary element Example Employee ID Regular expression EMP-123456 Internal project code Keyword list Your project names Proprietary source code Regular expression and keywords Code headers and terms - Select Create sensitive info type, then enter a name and description.27
- Select Create pattern and choose the default confidence level.27
- Define the Primary element: a regular expression, keyword list or function.17, 27
- Enter a Character proximity, and add supporting elements if you need them.27
- Choose the recommended confidence level, check your settings and select Save. There’s no separate publish step.27
-
Recommend the label in Office apps
Microsoft Purview portal › Solutions › Information Protection › Sensitivity labels
- Edit the Confidential/AllEmployees label and check that both Files & other data assets and Emails are in its scope.17, 18
- On the Auto-labeling for files and emails page, turn auto-labelling on.17, 18
- Add the condition Content contains and choose your custom SITs.17
- Under When content matches these conditions, select Recommend that users apply the label.17, 18
Step 1 already makes this label the default for new documents. In practice, the recommendation shows on items that don’t have it yet, such as older documents and emails. Microsoft suggests recommending a label before you apply it automatically.16, 17, 18
Automatic labelling in the Office apps is set on the label itself. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data Choose to recommend the label rather than apply it. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data What people see in Word: a recommended label and the content that triggered it. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data Watch out
Automatic and recommended labelling in Office apps might not trigger if you also make labelling mandatory.18
-
Onboard devices for Endpoint DLP
Microsoft Purview portal › Settings › Device onboarding › Devices
Endpoint DLP protects only onboarded devices. Devices already onboarded to Microsoft Defender for Endpoint appear in the list with no further steps.6, 11
- Select Turn on device onboarding. It usually takes about 60 seconds, and can take up to 30 minutes.6
- Select Onboarding and choose a method. Windows devices can use Group Policy, Configuration Manager, Intune, a local script or a VDI script. Mac devices use Intune or JAMF Pro.6, 11
Check Each onboarded device appears in the devices list and starts reporting activity to Activity explorer.11
Watch out
Onboarding needs a Microsoft Entra role: Security Administrator, Compliance Administrator or Global Administrator. Purview role groups aren’t enough.6
-
Create a DLP policy for endpoints
Microsoft Purview portal › Solutions › Data loss prevention › Policies › + Create policy
- Create a custom policy with Devices as its only location.17
- Add the condition Content contains, with your custom SITs or the Confidential/AllEmployees label.17
- Add actions to block Copy to USB removable device, Print, Copy to clipboard and Upload to a restricted cloud service domain or access from an unallowed browser.17, 28
- Run it in simulation mode, or turn it on straight away.17
Check In simulation, only items that are new during the simulation are evaluated on devices, so test with fresh files.29
Watch out
A clipboard block doesn’t stop pasting within the same Microsoft 365 Office app.28
-
Create a DLP policy for Teams
Microsoft Purview portal › Solutions › Data loss prevention › Policies › + Create policy
- Create a custom policy with Teams chat and channel messages as its only location.17, 30
- Add the condition Content contains with your custom SITs.17, 30
- Add the condition Content is shared from Microsoft 365 with people outside my organization.17, 30
- Add the action Restrict access or encrypt the content in Microsoft 365 locations and choose Block only people outside your organization.17, 30
- Run it in simulation mode, or turn it on straight away.17
Files shared in Teams are protected by the Step 1 SharePoint and OneDrive policy. A Teams policy covers documents only when it includes SharePoint and OneDrive.19
Watch out
A DLP policy can’t match Teams messages on a sensitivity label, so leave out the Confidential/AllEmployees condition that Microsoft’s step includes and use custom SITs only. Keep Teams in a policy of its own: a policy that includes Teams can detect only by SIT, so the label condition isn’t available.25, 30
-
Apply DLP to email with custom SITs and label inheritance
Microsoft Purview portal › Solutions › Information Protection › Publishing policies
Label inheritance makes an email take the highest-priority label of the files attached to it. It’s a setting in the label policy, not in DLP.17, 31
- Select your label policy, then Edit policy.12
- On the Default settings for emails page, under Inherit label from attachments, select Email inherits highest priority label from attachments.31
- In Data loss prevention > Policies, create a custom policy with Exchange email as its only location.17
- Add the condition Content is shared from Microsoft 365 with people outside my organization.17
- Add the condition Content contains and choose your custom SITs under Sensitive info types.17, 30
- Add the action Restrict access or encrypt the content in Microsoft 365 locations.17
- Run the policy in simulation mode. You can choose to turn it on automatically if it isn’t edited within 15 days of the simulation.17, 26
Microsoft’s step gives this policy the Confidential/AllEmployees condition, which your Step 1 email policy already enforces. Detecting your custom SITs is what this policy adds: it catches your own data in emails that don’t carry the label.16, 17
Open the label policy to change its email settings. Screenshot · Microsoft Learn, Create and configure sensitivity labels and their policies Check Simulation results stay for 30 days. For email, only messages sent during the simulation are evaluated.26, 29
Watch out
Inheritance works only for files attached to the email, never for links to files. It doesn’t replace a label someone has already chosen for the email.31
Done when Your custom SITs are saved, Office apps recommend the label, devices are onboarded, and the device, Teams and email policies are running in simulation or turned on.
Encrypt, auto-label and tighten controls for risky users.
- Outcome
- Best: encrypt files, extend service-side auto-labelling and enable Adaptive Protection
This step protects the most sensitive content wherever it goes, labels content already stored in Microsoft 365, and makes DLP stricter for users whose behaviour looks risky. Microsoft puts it at E5 Compliance or above.1, 15
-
Create and encrypt a high-sensitivity sublabel
Microsoft Purview portal › Solutions › Information Protection › Sensitivity labels
Microsoft’s step encrypts high-sensitivity sublabels. Steps 1 and 2 create none, so create one first.15, 16
- Create a sublabel for your most sensitive content, such as Highly Confidential/Restricted, the way you created Confidential/AllEmployees in Step 1.12, 15
- Check that Files & other data assets is in its scope.15, 32
- On Choose protection settings for the types of items you selected, select Control access.15, 32
- On the Access control page, select Configure access control settings, then Assign permissions now.15, 32
- Set User access to content expires to Never unless the content has a real time limit.32
- Set Allow offline access. Microsoft suggests 7 days for sensitive business data, and Never for very sensitive data.32
- Select Assign permissions and add the users or groups who need access.15, 32
- Put the new label below Confidential/AllEmployees in priority, and add it to your label policy so people can use it.12, 13
The encryption settings on a sensitivity label. This example allows offline access Always. For sensitive data, choose 7 days or Never instead. Screenshot · Microsoft Learn, Restrict access to content by using sensitivity labels to apply encryption Choose who can open content with this label, and with which permissions. Screenshot · Microsoft Learn, Restrict access to content by using sensitivity labels to apply encryption Why Don’t turn on encryption for Confidential/AllEmployees. It’s the default label for new documents, and Microsoft advises against an encrypting default label.13, 22
-
Test encrypted content before you rely on it
Purview doesn’t check that encryption prerequisites are in place. The Azure Rights Management service must be active, which it is by default in newer tenants.32
- Without Exchange set up for Rights Management, people can’t read encrypted email in Outlook on the web.32
- Sharing encrypted files with people outside the organisation can need guest accounts and changes to Conditional Access.32
- Unless co-authoring is turned on for encrypted files, AutoSave is off for them in Office apps.32
We recommend
We recommend opening a labelled file and a labelled email in each business app, and with each outside partner who must read them, before you apply the label widely.32
-
Extend auto-labelling to Exchange, SharePoint and OneDrive
Microsoft Purview portal › Solutions › Information Protection › Policies › Auto-labeling policies
- Select + Create auto-labeling policy and choose to apply a label.18
- On Choose info you want this label applied to, select Custom > Custom policy, then name the policy.18
- On Choose a label to auto-apply, select + Choose a label and choose your encrypting sublabel. It can’t be a parent label.15, 18
- On Assign admin units, keep Full directory unless you use administrative units.18
- Choose the locations Exchange, SharePoint sites and OneDrive accounts.15, 18
- On Set up common or advanced rules, keep Common rules. Under Content contains, select Add > Sensitive info types and choose your custom SITs.15, 18
- Select Run policy in simulation mode. You can choose to turn it on automatically if it isn’t edited for 7 days.15, 18
Auditing and labels for SharePoint and OneDrive, both from Step 1, must be on first. Turning the policy on needs Compliance Administrator or Compliance Data Administrator.18
Choose where the policy labels content. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data Every auto-labelling policy runs in simulation before it labels anything. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data Check A policy can’t label anything until it has run at least one simulation. Review the simulation’s matched items before you turn it on.18
Watch out
Auto-labelling doesn’t apply a label’s headers, footers or watermarks. Files it labels are protected but not visibly marked.18
-
Run Insider Risk Management analytics
Microsoft Purview portal › Solutions › Insider Risk Management › Overview
- Scroll to the Insider risk analytics card and select Run scan.7, 15
- When results arrive, open them in Reports > Analytics and select View details for recommended policies.7, 15
- Create a policy that names the users or groups to watch, and adjust its triggers.15
Insider risk analytics and policies read the audit log, which you turned on before Step 1. Analytics results are aggregated and anonymised.7, 33
Check Scan results can take up to 48 hours to appear.7
-
Set the risk levels and turn on Adaptive Protection
Microsoft Purview portal › Solutions › Insider Risk Management › Adaptive Protection › Insider risk levels
Adaptive Protection gives each user an insider risk level from their activity. DLP policies can then apply stricter actions to higher-risk users.8
- On the Insider risk levels tab, select the Insider Risk Management policy whose activity sets the levels.8
- Review the built-in conditions for Elevated, Moderate and Minor, and select Edit to change a threshold.8, 15
- On the Adaptive Protection settings tab, turn Adaptive Protection on.8, 15
Choose the policy that feeds the levels, then review each level’s condition. Screenshot · Microsoft Learn, Help dynamically mitigate risks with Adaptive Protection The switch that turns Adaptive Protection on. Screenshot · Microsoft Learn, Help dynamically mitigate risks with Adaptive Protection Video · Microsoft Learn · 2 min 17 s
How insider risk levels feed DLP and Conditional Access, and how controls tighten and relax as a user’s risk changes. The Conditional Access integration it shows is in preview. From Help dynamically mitigate risks with Adaptive Protection, Microsoft Learn. Video by Microsoft, with Microsoft's captions in the player. Check Allow up to 36 hours before risk levels start to apply to users.8
Watch out
Turning Adaptive Protection off takes up to six hours and resets every user’s risk level.8
-
Add the insider risk condition to DLP policies
Microsoft Purview portal › Solutions › Data loss prevention › Policies
- Edit a DLP policy and add the condition Insider risk level for Adaptive Protection is, set to Elevated risk level.15, 34
- Set actions that block file activities for those users. For Exchange and Teams, use Restrict access or encrypt the content in Microsoft 365 locations with Block only people outside your organization.15, 34
- For devices, block Upload to a restricted cloud service domain or access from unallowed browsers, Copy to clipboard, Copy to removable USB device, Copy to network share and Print.34
- For a device policy, also turn on advanced classification scanning and protection, or add the File type is condition.34
Microsoft suggests testing the policy with policy tips before you enable Adaptive Protection on it.8
-
Block the riskiest users with Conditional Access (preview)
Microsoft Purview portal › Solutions › Insider Risk Management › Adaptive Protection › Conditional Access › Create Policy
This integration is in preview, and the insider risk condition needs Microsoft Entra ID P2. Adaptive Protection must be set up first.8, 9, 20
- In the Microsoft Entra admin center, sign in as at least a Conditional Access Administrator.9
- Under Assignments > Users or workload identities, include All users and exclude your emergency access (break-glass) accounts.9
- Under Target resources > Resources (formerly cloud apps) > Include, choose what to protect. Microsoft’s step targets SharePoint and OneDrive; Learn’s example policy selects All resources.9, 15
- Under Conditions > Insider risk, set Configure to Yes and select Elevated.9, 15
- Under Access controls > Grant, select Block access.9, 15
- Set Enable policy to Report-only, or On.9, 15
Done when Your high-sensitivity sublabel encrypts, the auto-labelling policy has run in simulation, and DLP, with Conditional Access in report-only, responds to users at the Elevated risk level.
What these controls don’t cover.
- Labels in SharePoint and OneDrive. DLP’s ability to detect sensitivity labels in SharePoint and OneDrive is limited. Test the Step 1 policy on real files before you rely on it.25
- Multi-Geo tenants. With Microsoft 365 Multi-Geo, turn on labels for SharePoint and OneDrive with PowerShell, not the portal.5
- Teams chats. DLP deletes a message to an external user only when your tenant started the chat or thread. Teams DLP sends no notification emails to users.19
- Recommended labels. Not every Office app supports automatic or recommended labelling, and a label can’t be recommended for an item that already has a higher one.18
- Exact data match. If a label’s auto-labelling condition uses only exact data match SITs, auto-labelling turns itself off for that label.18
- Auto-labelling volume. A tenant can automatically label up to 500,000 files a day and hold up to 100 auto-labelling policies. A simulation covers up to 20,000,000 matched files.18
- Custom SIT support. Microsoft support can’t help write custom classifications or regular expressions.27
- Number of labels. Labels work noticeably less well when people see more than five main labels or more than five sublabels under one label.13
- Insider risk alerts. Insider Risk Management raises no alerts from DLP policies whose incident reports are set to Low or Medium.33
- Region. Insider Risk Management is available only in regions its Azure service dependencies support.33
- Evidence. A policy that’s turned on, a scan result or an alert shows what’s configured and what it found. None of them proves data can’t leave by another route.
Where each step comes from.
- 1 Microsoft Learn Lightweight guide to mitigate data leakage
- 2 Microsoft Learn Microsoft Purview service description
- 3 Microsoft Learn Get started with sensitivity labels
- 4 Microsoft Learn Create and deploy data loss prevention policies
- 5 Microsoft Learn Enable sensitivity labels for files in SharePoint and OneDrive
- 6 Microsoft Learn Onboard Windows devices into Microsoft 365 overview
- 7 Microsoft Learn Enable analytics in Insider Risk Management
- 8 Microsoft Learn Help dynamically mitigate risks with Adaptive Protection
- 9 Microsoft Learn Block access for users with elevated insider risk
- 10 Microsoft Learn Turn auditing on or off
- 11 Microsoft Learn Get started with endpoint data loss prevention
- 12 Microsoft Learn Create and configure sensitivity labels and their policies
- 13 Microsoft Learn Learn about sensitivity labels
- 14 Microsoft Learn Migrate parent sensitivity labels to sensitivity label groups
- 15 Microsoft Learn Step 3: Continuous improvement
- 16 Microsoft Learn Step 1: Establish foundational data security
- 17 Microsoft Learn Step 2: Expand protection to endpoints
- 18 Microsoft Learn Automatically apply a sensitivity label to Microsoft 365 data
- 19 Microsoft Learn Data loss prevention and Microsoft Teams
- 20 Microsoft Learn Protect your tenant with Insider Risk in Conditional Access
- 21 Microsoft Learn Microsoft Entra Conditional Access: Zero Trust Policy Engine
- 22 Microsoft Learn Default sensitivity labels and policies to protect your data
- 23 Microsoft Learn Help prevent sharing sensitive items via SharePoint and OneDrive with external users
- 24 Microsoft Learn Help prevent sharing credit card numbers through email
- 25 Microsoft Learn Use sensitivity labels as conditions in DLP policies
- 26 Microsoft Learn Get started with the data loss prevention simulation mode
- 27 Microsoft Learn Create custom sensitive information types
- 28 Microsoft Learn Learn about Endpoint data loss prevention
- 29 Microsoft Learn Learn about data loss prevention simulation mode
- 30 Microsoft Learn Data Loss Prevention policy reference
- 31 Microsoft Learn Manage sensitivity labels in Office apps
- 32 Microsoft Learn Restrict access to content by using sensitivity labels to apply encryption
- 33 Microsoft Learn Get started with Insider Risk Management
- 34 Microsoft Learn Learn about Adaptive Protection in data loss prevention
Have your labels and DLP policies checked.
LensIQ reviews your labels, DLP policies and audit settings against this model. We tell you which steps are in place, which are only in simulation, and where data can still leave.