← Back to blog

Microsoft 365 DLP Setup: A Step-by-Step Guide for 2026

November 7, 2026
Microsoft 365 DLP Setup: A Step-by-Step Guide for 2026

Setting up data loss prevention (DLP) in Microsoft 365 means creating a policy in the Microsoft Purview portal that defines where to protect data (locations), what counts as sensitive (conditions) and what happens when a match is found (actions). The safe sequence is simple: confirm your admin role and licenses, start from a template, run the policy in simulation mode, then enforce it and tune it from real alerts. This guide walks through each step for small and mid-size organizations, including those handling HIPAA, financial or legal data.

Securetechie
Protect Sensitive Data in Microsoft 365
Securetechie provides proactive IT management and enterprise-grade cybersecurity for small and mid-size businesses handling sensitive data.
Explore Securetechie

TL;DR

  • A DLP policy has three parts: locations, conditions and actions. Design them on paper before you open the portal.
  • The account that creates the policy needs a compliance or security role. Licensing decides which features you get, so check it first.
  • Start with a built-in template and run it in simulation mode before any blocking is turned on.
  • After go-live, review alerts, mark false positives and tune the policy on a schedule.
  • DLP supports HIPAA-related protection through templates, but it is one control within a wider compliance program.

Table of Contents

What Microsoft 365 DLP does

A DLP policy helps identify, monitor and automatically protect sensitive information. According to Microsoft Learn, policies can cover Microsoft 365 services such as Exchange, SharePoint, OneDrive and Teams, Office apps like Word, Excel and PowerPoint, Windows 10 and 11 devices and the three most recent macOS versions, non-Microsoft cloud apps, on-premises file shares, Microsoft Fabric and Power BI workspaces, and Microsoft 365 Copilot and Copilot Chat (in preview).

DLP does not simply scan for text. The same Microsoft documentation describes deep content analysis that combines keyword matches, regular expressions, internal function validation, secondary matches found in proximity and machine learning. In practice, this means a nine-digit number is far less likely to be flagged as a Social Security number than a nine-digit number that sits next to the words "SSN" or a person's name.

Every DLP-monitored activity is recorded in the Microsoft 365 audit log by default and routed to Activity explorer, so you have a trail to review even before you enforce anything.

Before you start: roles, licensing and scope

Admin roles

The account you use to create and deploy policies must belong to one of these role groups, per Microsoft's policy deployment guide: Compliance administrator, Compliance data administrator, Information Protection, Information Protection Admin, or Security administrator.

Microsoft also recommends using the role with the fewest permissions that can do the job. Its guidance for on-premises repositories notes that Global Administrator is highly privileged and should be used only where a lesser role cannot. The same principle applies to everyday DLP work. Our Microsoft 365 global admin best practices cover how to separate day-to-day compliance work from tenant-wide admin rights.

If you want to work with alerts, you need more. The DLP alerts documentation states that the alert management dashboard requires the Manage alerts role plus either the DLP Compliance Management or View-Only DLP Compliance Management role.

Licensing

Licensing determines how far you can go. A few points from Microsoft's own documentation:

  • Single-event alert configuration is available to organizations with a DLP subscription (E1, E3, E5, F1, G1, G3 or G5). Aggregated alerts need an A5, E5 or G5 subscription, or an E1/F1/G1 or E3/G3 subscription with an add-on such as Office 365 ATP Plan 2, Microsoft Purview Suite or the eDiscovery and Audit add-on, per the alerts page.
  • DLP file quarantine for SharePoint and OneDrive is available only with E5 licenses.
  • For on-premises repositories, every user who adds or consumes files in the scanned location needs a license, not only the scanner account.
  • For Fabric and Power BI, the admin account needs Microsoft 365 E5, E5 Compliance, E5 Information Protection & Governance, or Purview capacities.

Before you design anything, map your plan to these features. If you are weighing plans, our comparison of Microsoft 365 Business Premium vs E3 and our Microsoft 365 licensing guide explain how the tiers differ. For the authoritative per-feature list, Microsoft points to its Enterprise Plans and Service Descriptions pages.

Housekeeping that saves rework

Before building policies, complete a few basics:

  1. Inventory where sensitive data lives: shared mailboxes, SharePoint sites, OneDrive, Teams channels, laptops and file servers.
  2. Decide who owns the policy outcome. DLP alerts need someone who triages them within a business day.
  3. Confirm the tenant itself is hardened. DLP works best on top of MFA, conditional access and sensible sharing settings. Our Microsoft 365 security checklist covers that baseline.
  4. Write down the regulations that apply: HIPAA for patient data, GLBA for financial records, state privacy rules, client confidentiality obligations for law firms.

Design the policy: locations, conditions, actions

Microsoft's training material defines a DLP policy as locations, conditions and actions: locations say where to protect content, conditions say what content must match before a rule is enforced, and actions say what the rule does automatically when it finds a match.

PartQuestion it answersTypical choices
LocationsWhere does the data live or move?Exchange email, SharePoint, OneDrive, Teams chat and channels, devices, Copilot
ConditionsWhat counts as sensitive?Sensitive information types, sensitivity labels, sharing with external recipients
ActionsWhat should happen?Policy tip, block sharing, quarantine, restrict copying to USB or cloud

Microsoft advises choosing locations based on whether data needs protection at rest, in use or in motion, and choosing actions that suit each location, such as policy tips, blocking sharing, quarantine or restricting device copying.

Choose the sensitive information to detect

Purview ships with a large library of built-in sensitive information types, including credit card numbers, Social Security numbers, driver's license numbers, passport numbers, bank account numbers and medical record identifiers. You rarely need to write your own pattern at the start. Begin with the types that match your real risk:

  • Medical practices: medical record numbers, patient identifiers, Social Security numbers.
  • Mortgage companies and banks: bank account numbers, Social Security numbers, tax identifiers, credit card numbers.
  • Law firms: client matter data is often best protected with sensitivity labels, since a case file rarely follows a standard number pattern.
  • Startups: API keys, credentials and customer data exports.

Pick one scenario per policy

A policy only offers conditions that exist in every location you select. If you want a condition built on email recipients and add SharePoint as a location, the option may not appear because SharePoint sharing has no matching activity. This is why it is cleaner to build several focused policies than one policy covering everything. For example:

  1. Block external sharing of files containing Social Security numbers in SharePoint and OneDrive.
  2. Warn users when an email to an outside recipient contains bank account numbers.
  3. Restrict copying of labeled files to removable media on company laptops.

Name rules clearly. Rule names must be unique across all DLP policies and rules, so a naming convention such as "PHI-Email-External-Warn" helps you find things later.

Create the policy in Microsoft Purview

The portal screens change from time to time, so treat the steps below as the logic of the wizard rather than a click-by-click script. Microsoft's create and deploy guide is the reference for the current layout.

  1. Open the DLP policies page. Sign in to the Microsoft Purview portal with an account holding one of the roles listed above, then go to the data loss prevention policies area.
  2. Choose a template or a custom policy. Templates cover common regulatory scenarios. Microsoft says its policy templates address sensitive information subject to HIPAA, GLBA or the Patriot Act, and they can be customized. For a healthcare office, the health-related template is a sensible starting point.
  3. Name the policy and describe its purpose. Write the business reason in the description. In a year, someone else will need it.
  4. Select administrative scope. If different departments or regions have their own admins, scope the policy accordingly.
  5. Select locations. Start narrow: Exchange, SharePoint and OneDrive cover most small-business exposure. Add Teams and devices once the first policy is stable.
  6. Define the rules. Set conditions (sensitive info types, instance count, labels, external sharing) and actions (policy tip, user notification, block, override with justification).
  7. Set alerts. Choose who receives incident reports and whether each match generates an alert.
  8. Choose the mode. Select simulation mode, not enforcement, for the first run.
  9. Review and submit.

Blocking versus warning

Many first policies fail because they block too much on day one. A gentler pattern is to let the user override a block with a written business justification, since the overrides and every step in the alert are audited, as Syskit's DLP strategy article points out. That keeps legitimate work moving while giving your team a record to review. For high-risk data, such as full Social Security numbers sent outside the company, a hard block is reasonable once simulation shows the rule is accurate.

Blocking versus warning

Test with simulation mode before enforcing

Simulation mode is the step that separates a smooth rollout from a week of angry help desk tickets. Per Microsoft's simulation mode guide, it lets you see a policy's impact in production without enforcement, and you review matched items in the simulation dashboard. You can also show policy tips during simulation so users see what would happen.

Two details help you plan the timeline:

  • Results are saved for 30 days. You can keep a policy in simulation longer, but only the most recent 30-day period is displayed.
  • In Microsoft's overview of simulation mode, a simulation run can last up to 15 days. SharePoint Online and OneDrive evaluate all existing and new or changed items, while Exchange, Teams and Devices evaluate only items that are new during the simulation.

That last point matters for expectations. A simulation will show you a full inventory for files in SharePoint and OneDrive, but email findings come only from messages sent while the simulation runs.

A practical rollout schedule

PhaseModeWhat you do
Week 1 to 2Simulation, no tipsReview matches, remove noisy patterns, raise instance thresholds
Week 3Simulation with policy tipsLet users see warnings, collect feedback
Week 4Enforce with overrideTurn on actions that allow justification
After 30 daysEnforce, hardenSwitch the highest-risk rules to hard blocks

Syskit also recommends avoiding blocking in the first stage, so the security team can tune out false positives before they erode trust in the tool and make user adoption harder. Communicate with staff before enforcement starts: a short message explaining what DLP flags and how to request an exception prevents most confusion.

Monitor alerts and tune the policy

Policies are not finished at go-live. Microsoft describes an alert lifecycle with six steps: trigger, notify, triage, investigate, remediate and tune.

  • Triage: decide whether an alert is a true or false positive.
  • Investigate: correlate evidence in the Microsoft Defender portal, the DLP alert dashboard and Activity explorer.
  • Remediate: options include resetting a password, disabling an account, removing a document, applying a sensitivity label or quarantining a file.
  • Tune: update scope, conditions, actions and notifications.

Some timing facts to know. After you configure or change alerts in a policy, it can take up to three hours for alerts to be generated, per the alerts guide. Alerts remain in the Microsoft Defender portal for six months but appear in the Purview DLP alerts dashboard for only 30 days, according to Microsoft's DLP overview. If you need evidence for an auditor beyond that window, export the data or document incidents in your own records.

A simple tuning routine

  1. Review new alerts weekly for the first two months, then monthly.
  2. Track the top three rules by alert volume. If most are false positives, raise the minimum instance count or add a supporting keyword condition.
  3. Add exclusions for known, legitimate workflows, such as a billing team that must send payment data to a processor.
  4. Record every change with a date and a reason.
  5. Re-run simulation on any significant rule change before enforcing it.

Common setup mistakes

  • Starting with every location at once. Begin with email and file storage, then expand.
  • Skipping the owner. An alert nobody reads is not protection.
  • Treating DLP as a substitute for access control. DLP catches sensitive content in motion. It works alongside MFA, least-privilege roles and sound sharing settings.
  • Ignoring Copilot. If your organization uses Microsoft 365 Copilot, DLP can be applied to it as a location. Our Copilot security guide explains how to prepare your data first.
  • Expecting email at rest to be scanned. A DLP policy scoped to Exchange Online applies to mail in transit, not to messages already sitting in mailboxes.

DLP and HIPAA: what to expect

Microsoft's HIPAA-oriented template gives healthcare practices a head start by detecting common categories of protected health information. A template is a starting configuration. HIPAA compliance also involves risk analysis, access policies, workforce training, business associate agreements and documentation, none of which a DLP policy handles on its own. Treat DLP as the technical control that enforces rules you have already written down. A formal compliance and security audit is the way to confirm those other pieces are in place, and our practical guide to data loss prevention for IT teams covers the wider program.

Our perspective

Most DLP projects we see stall for the same reason: the policy was built from the tool's menus instead of from the business's workflows. A clinic, a mortgage broker and a law firm all send sensitive data outside the company every day. The goal is not to stop that. It is to make the safe path the easy one.

That is why we run DLP as a managed, proactive service rather than a one-time configuration. We map where sensitive data lives, build narrow policies, run them in simulation, and watch the alerts alongside our 24/7 monitoring so false positives are tuned out before staff lose patience. Preventing the incident is cheaper than explaining it to a regulator or a client afterward.

For Southern California organizations subject to HIPAA, SEC-aligned requirements or CMMC, we pair DLP with the audit work that proves the controls exist. Policies get approved faster when owners can see what the rules will and will not touch.

Alex

Get help with your DLP rollout

If you would rather not build and tune policies alone, Secure Techies manages Microsoft 365 security for small and mid-size businesses in Southern California. Our team can assess your tenant, design DLP policies around your data and compliance obligations, and monitor the alerts after go-live through our managed IT services and cybersecurity solutions.

Securetechie

To discuss your environment, visit Secure Techies and request a consultation.

FAQ

Do I need an E5 license to use Microsoft 365 DLP?

No. Core DLP policies and single-event alerts are available with E1, E3, E5, F1, G1, G3 and G5 subscriptions, according to Microsoft. Some capabilities, such as DLP file quarantine for SharePoint and OneDrive and aggregated alerts, need E5-level licensing or specific add-ons. Check the feature you need against Microsoft's service descriptions before you plan.

How long should I keep a policy in simulation mode?

A simulation run can last up to 15 days, and results are kept for 30 days. Many teams run two to four weeks, long enough to see a full business cycle such as month-end billing. Enforce only when the matches are mostly accurate and users have been told what to expect.

Who can create DLP policies?

Members of the Compliance administrator, Compliance data administrator, Information Protection, Information Protection Admin or Security administrator role groups. Use the least-privileged role that works rather than Global Administrator.

Does DLP make my practice HIPAA compliant?

No single tool does. Microsoft provides a template that detects information subject to HIPAA and can be customized, and it helps enforce your handling rules. HIPAA compliance also depends on risk assessments, policies, training and documentation across the organization.

Sources