Updated October 2026
Am I ready for DSPM? If you can’t say where your client data lives or who can open it today, yes. That gap is exactly what data security posture management exists to close, so a messy tenant is a reason to start.
What you need on day one is smaller than most firms expect. Someone with the right Purview admin role, and a named owner for each place sensitive data sits. Clean permissions and finished labels come later. They’re what the work produces.
This checklist is written for firms with a few dozen to a few hundred users, with law firms and professional services firms in mind. Most of them keep sensitive data in Microsoft 365 plus a document management system, so the checks lean on Microsoft Purview and SharePoint. Each item is one action, why it matters, and how to confirm it’s done.
Work through it in order the first time. Sections 1 and 2 tell you how big the problem is. Section 3 protects what matters most while permissions get fixed, and section 4 covers the data side of a Copilot rollout. Section 5 keeps the gains from sliding back.
You won’t finish everything in a week, and that’s fine. A firm that completes sections 1 and 2 and knows its ten worst sites is in a far better spot than one that bought a tool and stopped there.
Why: a DSPM tool only sees the locations it’s connected to. In Purview’s DSPM, Microsoft says the Asset explorer’s Microsoft locations currently include Microsoft 365 only, and non-Microsoft sources depend on partner integrations.
How to check: you have a one-page list covering client matter files, HR, finance and partner material, with a storage location and a named owner for each. The DMS and file servers belong on it.
Why: built-in sensitive information types cover common identifiers. Your client and matter numbers follow your own format, and Purview supports custom sensitive information types built from regular expressions and keyword lists.
How to check: each firm-specific identifier has a custom type, and you’ve tested it against a handful of known files before relying on it.
Why: Microsoft says to allow a day or so after the initial setup tasks before tenant data appears. The default data risk assessment has a four-day delay the first time it’s created.
How to check: the Posture page shows your tenant’s data, and the default assessment shows a summary of items found, sensitive items and links shared with anyone.
Why: this data access governance report finds the SharePoint and OneDrive sites with the broadest access. Think sites open to thousands of users, guests or “Everyone except external users.” Our SharePoint oversharing guide explains every report.
How to check: a dated export exists. One licensing catch: per Microsoft, E5 admins without SharePoint Advanced Management don’t get snapshot reports, though assigning at least one Copilot license unlocks the SAM features built for Copilot deployments.
Why: Microsoft runs a default assessment every week for your top 100 SharePoint sites by usage, and it counts items shared through links that work for anyone.
How to check: you export it (Excel, CSV, JSON or TSV are offered) and compare this week’s numbers with last week’s. For sites outside the top 100, run a custom assessment.
Why: SharePoint lets admins set a more restrictive default link type at the organization level and per site, while still letting users pick another type when they need it. Fewer broad links get created by accident.
How to check: share a test file from a normal user account and confirm which link type is preselected. Then do the same on your most sensitive site.
Why: Microsoft notes that compliance rules can keep IT from seeing item-level detail, and site owners understand the business context. Site access review sends each owner an email tied to the specific oversharing finding.
How to check: no site on your sensitive list is ownerless, and reviews started from the data access governance reports show as completed. A site ownership policy in SharePoint Advanced Management can flag sites that fall below your minimum owner count.
Why: when a label applies encryption, Microsoft says Copilot and other AI apps return the data only if the user holds both the VIEW and EXTRACT usage rights. That protects your most sensitive files even where a permission is wrong.
How to check: label a test file with your highest label, then confirm that a user without rights to it can’t get Copilot to summarize it.
Why: data risk assessments flag sensitive files that were never labeled, and an auto-labeling policy for SharePoint, OneDrive and Exchange can label them. Simulation mode shows what would match before anything changes.
How to check: you’ve reviewed the simulation results with the data owner, adjusted the policy where matches looked wrong, and then turned it on.
Why: a Purview DLP policy on the Microsoft 365 Copilot location can stop Copilot from using files and emails with selected sensitivity labels. Policy updates can take up to four hours to apply. Our Purview DLP for Copilot guide covers the details.
How to check: run the policy in simulation first. After the four-hour window, test with a labeled file and confirm Copilot won’t use it.
Why: it keeps selected SharePoint sites out of organization-wide search and Copilot responses. Microsoft describes it as a temporary control that doesn’t change permissions, and it doesn’t apply to OneDrive.
How to check: every restricted site is on a list with a cleanup owner and a date to lift the restriction. If that list only grows, the cleanup has stalled.
Why: DSPM’s AI observability page lists AI apps and agents with activity in the last 30 days, how many are high risk, and how many had sensitive interactions.
How to check: compare that inventory with your approved-tools list and chase anything that isn’t on it. The rest of Copilot readiness, including pilots and agent settings, is on our Copilot readiness checklist.
See what DSPM for AI in Purview reports once Copilot is on, and whether to start with DSPM or CSPM.
Why: Microsoft turns auditing on by default for Microsoft 365 organizations but says to verify it for new tenants. Copilot and AI app interactions are logged automatically as part of Audit (Standard).
How to check: run an audit search for Copilot activity from the past week and confirm results come back. Name the person who reviews them.
Why: oversharing comes back because the habits behind it are convenient. Microsoft suggests running the snapshot reports quarterly and the activity reports monthly.
How to check: a recurring task exists for the weekly assessment, the monthly activity reports and the quarterly snapshot, each with one named person.
Why: stale sites widen what an AI assistant can surface. Data risk assessments suggest retention policies for content not accessed in at least three years, and an inactive site policy can flag dormant sites to their owners.
How to check: records and legal hold requirements are signed off before any deletion policy goes live. For law firms, the file retention policy and engagement letters come first.
The tools are rarely the bottleneck. Scans finish in days. The slow part is deciding what to do about each finding, and that needs someone with authority over access, usually not the IT team alone.
At a law firm the stakes are specific. Ethical walls and client confidentiality depend on permissions being right, and any assistant connected to Microsoft 365 reads with the signed-in user’s access. If you want the conceptual side first, our DSPM vs DLP comparison explains how the two split the work.
Probably. If you can’t say where sensitive data lives or who can open it, DSPM is how you find out. You need an admin with a suitable Purview role, such as Compliance Administrator, and owners for your sensitive locations. Clean data isn’t a prerequisite.
Check before you plan. Microsoft points to its service descriptions for Purview licensing. Some items depend on SharePoint Advanced Management, which comes with at least one Copilot license. E5 admins without it get data access governance reports without snapshot reports or remediation actions.
Microsoft says to allow a day or so after the initial setup before tenant data appears. The default data risk assessment takes four days the first time. A custom assessment needs at least 48 hours before its results are ready.
You don’t need every item done. I’d want sections 1 and 2 complete for your most sensitive sites and your top label encrypting. Anything you can’t fix yet can sit behind Restricted Content Discovery for now. Copilot only surfaces what a user can already view.
Yes, if the firm assigns owners. IT can run the scans and reports. Decisions about who should see a matter site or an HR folder belong to the people who own that data, and site access reviews are built for that handoff.
Want a second set of eyes on your Microsoft 365 data exposure before more AI seats go out? Start with the free AI Readiness Snapshot. It’s a first look at selected priorities. If it finds real exposure, our paid AI Readiness Assessment (3 to 4 weeks) goes deeper and is scoped separately.
Cocha Technology Inc. is a Houston-based AI governance and security advisory firm, serving organizations across the US, Canada and the EU.