Deploy and use Data Security Posture Management in Microsoft Purview.

You run DLP, Insider Risk Management and sensitivity labels, but nothing shows you in one place where sensitive data sits unprotected or who is putting it at risk. Data Security Posture Management (DSPM) does: it gives you reports, weekly trends and recommendations for DLP and Insider Risk Management policies.

This guide follows Microsoft’s four-step model. You set the foundations, assign roles and turn on analytics, review what DSPM finds, then act on it and repeat the review every month. It’s written for the Purview administrators who run DLP, Insider Risk Management and Information Protection, and for the analysts who act on what DSPM reports. After Step 2, allow up to three days for DSPM’s first scan, and seven days for DLP analytics’ first recommendations.

Microsoft’s model on one page.

Microsoft’s blueprint shows what DSPM draws on and what it gives back. Analytics from DLP, Information Protection and Insider Risk Management feed it. It returns reports and trends, recommendations, and investigation with Security Copilot.5

Microsoft Purview DSPM blueprint: analytics, classifiers and five stages
Microsoft’s blueprint for the model, shown whole: the signals DSPM uses, the three things it returns, and the five stages of using it. Diagram · Microsoft Learn, Deploy and use Data Security Posture Management
  1. The blueprint shows Security Copilot as one of three outputs. It’s optional: the reports and recommendations work without it.5, 10
  2. The bottom band puts investigating with Security Copilot before creating policies. Step 4 creates policies first, then investigates, and this guide follows the step.5, 11

Microsoft’s steps at a glance

StepWhat it doesOutcome
Step 1Establish foundational elementsFull data estate is understood and accessible
Step 2Configure access and analyticsDSPM starts pulling insights
Step 3Understand data landscape and risksRisks are assessed and data security posture is understood
Step 4Take action and investigate with Security CopilotActions taken to secure the environment

Check the licence for each part before you start.

DSPM (classic) needs Microsoft 365 E5 or Microsoft Purview Suite. The solutions it draws on, and Security Copilot, each have their own terms. Check Information Protection in the service description too.4, 5, 12

Licences by feature 4, 9, 12, 13, 14, 15, 16, 17

FeatureLicenceNotes
Data Security Posture Management (classic)Microsoft 365 E5 or Microsoft Purview Suite (formerly Microsoft 365 E5 Compliance).The version this guide follows. Microsoft has replaced it with a new DSPM.
DLP for Exchange Online, SharePoint Online and OneDriveMicrosoft 365 E5/A5/G5/E3/A3/G3, Microsoft 365 Business Premium, SharePoint Online Plan 2, OneDrive for Business (Plan 2), Exchange Online Plan 2; Office 365 E5/A5/G5/E3/A3/G3; Microsoft Purview Suite/EDU/GOV/FLW and Microsoft Defender + Purview Suite FLW.Preview: DLP analytics, which DSPM relies on.
Insider Risk ManagementMicrosoft 365 E5/A5/G5, Microsoft Purview Suite/EDU/GOV/FLW and Microsoft Defender + Purview Suite FLW, and Microsoft 365 E5/A5/F5/G5 Insider Risk Management.Pay-as-you-go: some indicators. Available only in regions that support its Azure service dependencies.
Security Copilot (optional) with Microsoft 365 E5 or E7Included once Microsoft rolls it out to your tenant: 400 Security Compute Units (SCUs) a month for every 1,000 paid user licences, up to 10,000.The allowance resets each month and doesn’t roll over.
Security Copilot (optional) with other plansProvisioned SCUs, bought separately: at least 1, at most 100.Billed per hour. When provisioned SCUs run out, requests stop unless another capacity type is available.

Every user who benefits from the service needs a licence, including people assigned a Purview role in the portal.12

Give DSPM the context it needs.

Outcome
Full data estate is understood and accessible

Nothing here happens inside DSPM. You decide which sensitive data matters, label it, and set up insider risk, so that DSPM’s recommendations have something to work from.10

In today’s portal These foundations are set up in their own solutions, so nothing here moves.3

  1. Identify the sensitive information types that matter

    Microsoft Purview portal › Information Protection › Classifiers › Sensitive info types

    A sensitive information type (SIT) is a pattern Purview uses to recognise one kind of sensitive data, such as a credit card or bank account number.18

    1. List the built-in SITs that match the data your organisation holds. They’re a good starting point, and you can improve them after investigation.10
    2. Where no built-in SIT fits, select Create sensitive info type and build your own for data unique to you, such as internal project codes or employee IDs. You can also copy a built-in SIT and change it.10, 18, 19
    3. Test each custom SIT by uploading a sample file. The results show the matches at each confidence level.18

    Why When you review DSPM’s recommendations later, this list tells you which findings to deal with first.10

  2. Configure a labelling schema

    Labelling isn’t required for DSPM, but it improves DSPM’s recommendations and reports, and your DLP policies will build on it later.10, 20

    If you haven’t deployed sensitivity labels yet, work through our Secure by default with Microsoft Purview guide first. It follows Microsoft’s own model for labelling at scale.10

    Why In DSPM, a file holding sensitive data counts as protected only if a DLP policy restricts it or it carries a label that controls access.21

  3. Define your Insider Risk Management programme

    Microsoft Purview portal › Insider Risk Management › Overview

    1. Work through the recommended actions on the Overview page, from Turn on auditing to Create your first policy.9
    2. Create at least one policy. Risky activity can’t raise an alert until a policy exists.9
    3. On the Policy template page, choose a category, then a template. Check its prerequisites, triggering events and detected activities fit your needs.9
    4. For the Data theft by departing users template, set up the Microsoft 365 HR connector, or select User account deleted from Microsoft Entra when you configure the policy’s trigger events.22, 23

    Users are pseudonymised by default, and role-based access controls and audit logs are in place.9

    Insider risk management top actions, four of six getting started steps done
    The recommended actions on the Insider Risk Management Overview page, each marked Required or Optional. Screenshot · Microsoft Learn, Get started with Insider Risk Management

    Why With a programme in place, DSPM can recommend Insider Risk Management policies about risky users alongside its DLP recommendations.10

    Watch out

    Insider Risk Management points to risk; it doesn’t prove it. You must run your own full investigation of a person’s behaviour, not rely on its insights alone.9

  4. Decide on Security Copilot (optional)

    Security Copilot adds investigations in plain-language prompts, DSPM promptbooks (fixed sequences of prompts for one kind of investigation) and AI-assisted analysis.10

    • Microsoft 365 E5 or E7. Security Copilot is included, but only once Microsoft has rolled it out to your tenant.14, 15
    • Other plans. Buy provisioned capacity in Security Compute Units (SCUs), at least one, and onboard manually.15, 16

    Configure your organisation for Security Copilot before you use it in DSPM. The promptbooks work only once DSPM’s first scan is complete, so this can wait until after Step 2.4, 24

    Watch out

    Everyone who runs Security Copilot in DSPM needs the Data Security Viewer role, even a Global Administrator.4, 10, 25

Done when Your priority SITs are listed and tested, labels are in place or planned, and Insider Risk Management has at least one policy.

Next Configure access and analytics (step 2)

Give people access and turn on the analytics.

Outcome
DSPM starts pulling insights

This step assigns the roles DSPM needs and turns on the DLP and Insider Risk Management analytics it builds on. Once analytics are on, DSPM starts its first scan.7

In today’s portal In the new DSPM, you opt in at DSPM › Getting Started the first time you open it, through the Auditing and analytics setup task. Setup tasks stay under DSPM › Actions › Setup tasks. Access needs Entra Compliance Administrator, Global Administrator or the Purview Compliance Administrator role group. Administrators restricted to administrative units see data only for users in their own units. Allow a day or so before data appears.2, 3, 25, 26, 27

  1. Assign a role with least privilege

    Microsoft Purview portal › Settings › Roles and scopes › Role groups

    Roles that give access to DSPM 4, 7

    Role or role groupWhat it gives
    Data Security Management role groupFull access to DSPM management.
    Data Security Viewer roleNeeded to use Security Copilot in DSPM. Once DSPM is opted in, it also shows all the insights.
    Insider Risk Management AdminsAccess to the DSPM features that relate to Insider Risk Management.
    Microsoft Entra Compliance AdministratorCompliance-focused access to DSPM.
    Microsoft Entra Global AdministratorFull access. Use sparingly.
    1. Select the role group you want to add people to, then select Edit.6
    2. On Edit members of the role group, select Choose users or Choose groups.6
    3. Select each user or group to add, then select Next and Save.6

    The Data Security Viewer role comes with the Data Security Viewers role group, for read-only access, and with Data Security Management. Give each person the role with the fewest permissions that does the job, and keep Global Administrator to a few people.7, 8

    Watch out

    An administrator whose permissions are restricted to administrative units can’t open DSPM (classic) at all. And where someone holds both an Entra role and a scoped Purview role group, the Entra role takes precedence.4, 6

  2. Turn on DLP and Insider Risk Management analytics

    DSPM correlates what DLP and Insider Risk Management already know, so their analytics must be on. Turn them on together or one at a time.7

    • Together. Opt in to DSPM analytics processing and scanning. Learn gives no portal path for the classic opt-in; in the new DSPM, it appears the first time you open it. Opting in turns on DLP and Insider Risk Management analytics if they aren’t already on. Turning both on separately opts you in to DSPM as well.2, 4, 7
    • DLP analytics (preview). In Data loss prevention › Overview, check Turn on analytics for risk detection and policy refinement opportunities (preview), then select Turn on analytics. You need Global Administrator or Compliance Administrator.13
    • Insider Risk Management analytics. In Insider Risk Management › Overview, scroll to the Insider risk analytics card and select Run scan. You need the Insider Risk Management, Insider Risk Management Admins or Global admin role group. Results can take up to 48 hours.28

    Check In Settings › Data Loss Prevention › Analytics (preview), the Activate analytics toggle is on. In Insider Risk Management, Settings › Analytics shows the setting on.7, 13, 28

    Watch out

    DLP analytics is a preview feature and off by default. It takes seven days to produce its first recommendations, then refreshes weekly.13

  3. Confirm the first scan has started

    Once analytics are on, DSPM starts its first scan by itself. It scans your organisation’s data and activities and produces baseline insights and its first recommendations.7

    The scan can take up to three days. Scanning time depends on your organisation’s size and how much data and activity it has.4, 7

    Check When the scan is done, the Overview page in Data Security Posture Management (classic) shows the top two recommendations and View all recommendations.29

    We recommend

    We recommend using the wait to test access. Sign in once with an account for each role you assigned, and check it opens what that person needs and nothing more.

Done when Each person has the least-privileged role they need, both analytics are on, and the first scan has finished.

Next Review what DSPM found (step 3)

See where sensitive data sits unprotected.

Outcome
Risks are assessed and data security posture is understood

This step changes nothing. You read DSPM’s reports, trends and recommendations, and keep a record to measure later months against.30

In today’s portal In the new DSPM, reports are at DSPM › Reports, with headline posture metrics on DSPM › Posture. Recommendations are now DSPM › Actions › Remediation actions. Check the report names there before you rely on the ones below.2, 3

  1. Review the two analytics reports

    Microsoft Purview portal › Data Security Posture Management (classic) › Reports

    1. Open Unprotected sensitive assets across data sources. It lists files across your data estate that hold sensitive data with no DLP policy restricting exfiltration and no label that controls access, with each file’s location and classifiers.21, 30
    2. Open Users performing top risk-related activities on unprotected sensitive assets. It shows users Insider Risk Management has flagged, such as departing or high-risk users, including activity on classifiers your DLP policies don’t use.21, 30
    3. Use the charts, filters and Customize columns to narrow each report to the SITs you prioritised in Step 1.21
    4. Select Export to save each report as a .csv file.21

    We recommend

    We recommend keeping both exports from the first scan as your baseline. Rank the gaps they show against the SITs you prioritised, so Step 4 starts with the ones that matter most.21

  2. Read the weekly trends

    Microsoft Purview portal › Data Security Posture Management (classic) › Overview

    • Sensitive assets labeled (automatically and manually). The percentage of sensitive assets each week with a sensitivity label, applied by users or by auto-labelling policies.21, 30
    • Sensitive assets protected by at least one DLP policy. The percentage of sensitive assets covered by one or more DLP policies.30
    • Potentially risky users. The number of users each week assigned an insider risk severity level of low, medium or high.30

    Hover over a point on a trend to see the detail for that week.21

    Watch out

    We treat these numbers as coverage, not proof that controls work. An asset counts as protected when a DLP policy covers it or a label that controls access is applied. That doesn’t show the policy blocks anything: a DLP policy in simulation enforces no action. A flagged user is a lead for your own investigation, not a finding.9, 21, 29, 31

  3. Review the recommendations

    Microsoft Purview portal › Data Security Posture Management (classic) › Recommendations

    Each recommendation comes from the last 30 days of user activity and the current state of unprotected sensitive assets. It shows the number of activities, the type of protection involved and the number of users.29

    Use them to find gaps in your existing DLP and Insider Risk Management policies. Review the list at least every 30 days.30

    Watch out

    The list updates itself and removes recommendations older than 30 days. We don’t read a shorter list as fewer risks: check the reports before you close anything.29, 30

Done when Both reports are exported as your baseline, you’ve read the trends, and you know which recommendations to act on first.

Next Act on the recommendations (step 4)

Act on the recommendations, then repeat every month.

Outcome
Actions taken to secure the environment

This step turns recommendations into DLP and Insider Risk Management policies, and uses Security Copilot, if you have it, to look into the users involved.11

In today’s portal In the new DSPM, recommendations are under DSPM › Actions › Remediation actions, and administrators restricted to administrative units can’t create one-click policies. Security Copilot promptbooks appear on DSPM › Posture, within objectives. Check which promptbooks it offers before you plan around the two below.3, 27

  1. Create policies from a recommendation

    Microsoft Purview portal › Data Security Posture Management (classic) › Recommendations

    1. Select a recommendation, then select View recommendation.29
    2. On the flyout pane, choose to create one policy or several, in DLP, Insider Risk Management or both.29
    3. For an Insider Risk Management policy, enter a Policy name. Set User scope to Include all users and groups, recommended for best coverage, or I want to choose specific users and groups.29
    4. For a DLP policy, enter a Policy name and set Mode to Simulation or On.29
    5. Review Settings we filled in for you. To change them, select Customize.29
    6. Select Create policy.29

    The same guidance can update an existing policy instead of creating a new one.11

    Insider risk workflow: policy, alerts, triage, investigate and action
    What an Insider Risk Management policy leads to: alerts, triage, investigation and action, with compliance, HR, legal and security working on the case together. Diagram · Microsoft Learn, Learn about Insider Risk Management

    Why Start DLP policies in Simulation. No action is enforced, but events are audited, so you see what the policy would catch before it affects anyone.31

    Check Each policy takes a few minutes to create, then appears on the Policies tab in Data loss prevention or Insider Risk Management.11, 29

    Watch out

    Once a policy is active, allow at least 24 hours for the triggering event to occur and user activity to be scored before the first alert.29

  2. Tune each policy in its own solution

    1. Open the new policy from the Policies tab in Data loss prevention or Insider Risk Management.9, 29
    2. Make any change beyond DSPM’s quick settings with that solution’s own policy tools.29
    3. Once you’ve reviewed a few alerts, fine-tune how many alerts the policy raises and which activities it detects.29
    4. Move each DLP policy from simulation towards full enforcement in stages.31

    New policies can produce further recommendations that help you update and tune them.11

  3. Investigate users with Security Copilot

    1. In a recommendation, select Show Users Involved to start a Security Copilot conversation about the users behind it.11
    2. Ask follow-up prompts about the activity around the recommendation.11
    3. To investigate any user or activity, open Security Copilot from the top of the DSPM page instead.11
    • “Provide a list of events where sensitive files were shared externally.”11
    • “List all the sensitive files that were uploaded to cloud in the last week.”11
    • “Show me the data activities for user [UPN] in the last 30 days.”11

    In your own prompts, name the user by user principal name (UPN, the person’s sign-in name). Give the full name of a SIT or label in single quotes, and keep each prompt to one question.24

    Watch out

    Without a date range, a prompt covers only the last 10 days. The furthest a prompt can look back is 30 days.24, 27

  4. Run a promptbook or a gallery prompt

    Microsoft Purview portal › Data Security Posture Management (classic) › Overview

    1. Select one of the suggested prompts.24
    2. Enter the inputs it asks for, then select Submit.24
    • Risky user investigation. Six prompts that show a user’s data activities, anomalies and related alerts. Enter a UPN and a timeframe of up to 30 days.11
    • Sensitive data protection. Six prompts that find sensitive data across the organisation and suggest policy changes and DLP rules. Enter the full name of a SIT, label or trainable classifier, and up to 30 days.11, 24
    • Copilot Prompt Gallery. Sample prompts on alerts and policies, data at risk, potentially risky users, potentially suspicious activity, and sensitive data. Open it with View more in prompt gallery on the Overview page.11, 24

    Check The responses open in a flyout pane. Select New chat to clear them before your next investigation.24

  5. Repeat the cycle every month

    1. Review DSPM’s reports and trends for changes in your data estate.11
    2. Review the recommendations for current risk and next steps.11
    3. Create or update DLP and Insider Risk Management policies from new recommendations.11
    4. Investigate flagged users and activities with Security Copilot, if you use it.11
    5. Assess the overall risk and decide what to strengthen next.11
    DSPM workflow: opt in, evaluate insights, investigate or create policies, track
    The DSPM (classic) loop: opt in to analytics, evaluate insights, investigate or create policies, then track posture with trends and reports. Diagram · Microsoft Learn, Learn about Data Security Posture Management - (classic)

    We recommend

    We recommend fixing a date each month and comparing that month’s exports with the baseline from Step 3. Recommendations draw on the last 30 days only, so the exports are your record of earlier months.29

Done when Policies built from recommendations are live, DLP ones in simulation or staged towards enforcement, and the monthly review has a date.

Next Read the limits before you report on posture

What DSPM won’t tell you.

  • The classic version. Microsoft gives no retirement date for DSPM (classic), and most new features go only into the new DSPM. Check the classic version is still in your portal before you plan a programme around it.1, 2
  • Paused data. The new DSPM stops refreshing Microsoft 365 data when nobody has opened it for more than 60 days. It resumes when you return, after an initial delay, so the monthly review also keeps the data current.27
  • Anonymised analytics. Insider risk analytics reports return aggregated, anonymised activity, so reviewers can’t identify individual users. Show insights at user level doesn’t change that: it adds user-level risk insights to DLP alerts, Communication Compliance and Microsoft Defender. Sharing them with other security solutions is a separate Data sharing setting.28
  • Short lookback. Insider risk analytics scores up to 10 days of activity, and a Security Copilot prompt looks back 30 days at most.24, 28
  • AI apps and agents. This guide covers your data estate. DSPM for AI (classic) covered Copilot and other generative AI apps, and the new DSPM brings both together. For AI apps and agents, use our guide to securing Microsoft 365 Copilot agents.3, 32

A baseline, policies built on it, and a monthly review.

  • Priority SITs listed and tested, a labelling schema, and an Insider Risk Management programme with at least one policy.10
  • Least-privileged roles for DSPM, analytics on in DLP and Insider Risk Management, and the first scan complete.7
  • Both reports exported as the baseline each later month is compared with.
  • Policies created from recommendations and tuned in their own solutions, with the review repeated every month.11

Where each step comes from.

  1. 1 Microsoft Learn Learn about Data Security Posture Management - (classic)
  2. 2 Microsoft Learn Learn about Data Security Posture Management
  3. 3 Microsoft Learn Find familiar tasks that you did in DSPM for AI or in DSPM
  4. 4 Microsoft Learn Get started with Data Security Posture Management - (classic)
  5. 5 Microsoft Learn Deploy and use Data Security Posture Management
  6. 6 Microsoft Learn Permissions in the Microsoft Purview portal
  7. 7 Microsoft Learn Step 2: Configure access and analytics
  8. 8 Microsoft Learn Roles and role groups in Microsoft Defender for Office 365 and Microsoft Purview
  9. 9 Microsoft Learn Get started with Insider Risk Management
  10. 10 Microsoft Learn Step 1: Establish foundational elements
  11. 11 Microsoft Learn Step 4: Take action and investigate with Security Copilot
  12. 12 Microsoft Learn Microsoft Purview service description
  13. 13 Microsoft Learn Get started with the data loss prevention analytics
  14. 14 Microsoft Learn Learn about Security Copilot for Microsoft 365 E5 and E7 included customers
  15. 15 Microsoft Learn Get started with onboarding to Microsoft Security Copilot
  16. 16 Microsoft Learn Onboarding to Security Copilot for non-Microsoft 365 E5 and E7 customers
  17. 17 Microsoft Learn Microsoft Security Copilot Security Compute Units and capacity
  18. 18 Microsoft Learn Learn about sensitive information types
  19. 19 Microsoft Learn Create custom sensitive information types
  20. 20 Microsoft Learn Learn about sensitivity labels
  21. 21 Microsoft Learn Use Data Security Posture Management analytics trends and reports - (classic)
  22. 22 Microsoft Learn Learn about Insider Risk Management
  23. 23 Microsoft Learn Learn about Insider Risk Management policy templates
  24. 24 Microsoft Learn Use Microsoft Security Copilot with Data Security Posture Management - (classic)
  25. 25 Microsoft Learn Permissions for Data Security Posture Management
  26. 26 Microsoft Learn Setup tasks for Data Security Posture Management
  27. 27 Microsoft Learn Considerations for Microsoft Purview Data Security Posture Management
  28. 28 Microsoft Learn Enable analytics in Insider Risk Management
  29. 29 Microsoft Learn Take action with Data Security Posture Management recommendations - (classic)
  30. 30 Microsoft Learn Step 3: Understand data landscape and risks
  31. 31 Microsoft Learn Create and deploy data loss prevention policies
  32. 32 Microsoft Learn Learn about Data Security Posture Management for AI - (classic)

Have your DSPM findings checked.

LensIQ reviews your DSPM set-up, its reports and the policies built from them against this model, and tells you which gaps are covered in name only.