
“Where do we start?” It is the question I get asked in nearly every Microsoft Purview engagement. Purview has a huge toolset - sensitivity labels, data loss prevention, insider risk, retention, Data Security Posture Management - but none of it works until the organisation has told Purview what it needs to protect. Purview does not know that a design specification is Contoso’s crown jewels. Contoso has to tell it.
That is classification, and it is where most projects stall. Workshops ask the business to list its sensitive data, the business lists what it can remember, and the result is a handful of sensitive information types (SITs) that miss most of what matters.
This series takes a different route. Instead of asking people what they think is sensitive, we ask the data. I use a Microsoft CDX demo tenant, Microsoft Security Copilot and the Data Security Posture Agent (preview) to discover what Contoso actually holds, and then turn those findings into classifiers. The series runs in five short parts:
- Part 1 - Let the data tell you: what Purview already sees, and why the Posture Agent changes the starting point (this post)
- Part 2 - Getting the Posture Agent running: prerequisites, gotchas and what it actually cost
- Part 3 - From discovery to definition: using the agent to find the sensitive information types you did not know you needed
- Part 4 - Teaching Purview what matters: trainable classifiers (coming soon)
- Part 5 - From classification to protection: labels, DLP and the evidence trail (coming soon)
All data in this series is fictional and lives in a Microsoft CDX demo tenant. Every script and template will be published to GitHub at the end of the series.
Start with what Purview already sees
Before building anything, look at what Purview has already found. Out of the box, Purview scans Microsoft 365 content against hundreds of built-in SITs and Microsoft’s pre-trained classifiers. In the Contoso tenant the Purview home page reported 1,866 items containing sensitive information. The top three types were All Full Names (301 items), a custom SIT called Proseware Merger (152 items) and EU Tax Identification Number (130 items).
The second most common sensitive type in this tenant is not a regulatory identifier. It is a custom type someone built to find a confidential merger. That is intellectual property, and built-in rules will never find it on their own.
The unified Classifiers page
Microsoft is rolling out a unified Classifiers page (preview) under Information Protection > Classifiers. It brings SITs, exact data match, trainable classifiers and document fingerprinting into one list, and runs alongside the classic pages.

The most useful change is two columns side by side: Classified items and Affected policies. Filter to trainable classifiers and custom SITs and the gap is obvious. Finance matched 134 items, HR 52. The custom Proseware Merger and Mark 8 Project types matched 152 and 101 items. Every one shows 0 affected policies.

That single view is a ready-made gap analysis: Purview has found the data and nothing is protecting it. It is also the limit of what you get for free. These columns only count what an existing classifier already recognises. Anything Contoso has never defined does not appear at all.
Why starting from SITs is backwards
Most guidance on the Posture Agent shows it searching for a SIT you already have: “find files containing credit card numbers that are shared externally”. That is useful for remediation, but it does not answer “where do we start?”. If you already knew your SITs, you would not be asking.
I learned this the hard way in the lab. My first prompt asked the agent to find unlabelled Mark 8 confidential data. It ran successfully and found 0 items. The prompt was turned into a literal keyword query, limited to the default 30-day window, over content that did not use those words. Searching for what you think exists finds nothing new.
The real value is the other way round. Describe the kind of content that would hurt the organisation if it leaked, let the agent find it by meaning, and then look for the patterns that repeat. Those patterns are your candidate SITs.
The Data Security Posture Agent (preview)
The Posture Agent is a Security Copilot agent in Microsoft Purview. It has two capabilities in two places:
- Data discovery, in DSPM > Discover > Asset explorer > Posture Agent tab. You describe what you are looking for in natural language, choose the people, groups or sites to search, and the agent analyses files, emails and messages for that content.
- Credential scanning, in Data Security Investigations > Posture agent. It scans selected locations for exposed passwords, keys and tokens and tracks each scan on a task board.

Note the banner: DSPM (classic) and DSPM for AI (classic) retire on 30 November 2026, and the agent only lives in the new unified DSPM. If you have been waiting to move, this is the push.
Things worth knowing before you plan around it:
- It finds and reports. It does not act on its own. You can label selected files from the results, export a report or schedule the prompt to run daily, weekly or monthly.
- Only two prompts can run at once, and a run may be capped at 5 GB or 10,000 items, returning the top 1,000 matches. It is a fast, targeted discovery tool, not a full-tenant inventory.
- The default time range is the last 30 days. Ask for a wider range in the prompt if your content is older.
- It needs Security Copilot capacity, and every run consumes it. Part 2 covers what that took and cost.
The agent is a non-human identity
Expand Permissions and roles in the setup dialogue and you will see that starting the agent creates its own identity, with permission to access, read and see metadata for documents and content.

That is a non-human identity with broad read access to your most sensitive data. Treat it like one: know who deployed it, review it with your other agent identities and make sure its activity is in your audit process. In the lab, the credential scanning task card even reads “Started by Data security posture agent” - the agent, not the admin, is the actor.
Role design matters too. Compliance Administrator and Security Reader can run the agent and see summaries. Viewing matched snippets or opening matched files needs content-level roles such as Data Classification Content Viewer or Purview Content Analyst. Our audit log showed exactly that split: the admin was granted the compliance roles and blocked on the content roles.
What we found
Once the prerequisites were in place (Part 2), one discovery-style prompt over a single user’s mailbox and OneDrive returned 20 items, none of them labelled:
- A document named CR-227 Product Overview - a reference number format that no SIT covered.
- Project Tailspin and Customer Purchasing Data for Project 9 - internal codenames that no SIT covered.
- Contoso Patent Template and an R&D expense report - content defined by what it is rather than a pattern, which is a job for a trainable classifier.
- An annual financial report draft, already covered by the built-in Finance classifier.
- Noise: Power BI visual definitions, Outlook task reminders and meeting titles.
None of the useful findings were on anyone’s list. That is the point. Part 3 shows how each one becomes a classifier, and how to deal with the noise.
So where do we start?
- Look at what Purview already sees. The unified Classifiers page shows classified items against affected policies. That is your first gap list.
- Do not start by asking the agent about the SITs you already have. Ask it about the kind of content that would hurt you if it leaked.
- Treat the agent as a non-human identity from day one.
- Get the prerequisites right before you pay for capacity. That is Part 2.
References
- Get started with the Data Security Posture Agent - learn.microsoft.com/purview/copilot-in-purview-posture-agent-get-started
- Posture agent in Data Security Investigations - learn.microsoft.com/purview/data-security-investigations-posture-agent
- Learn about data classification - learn.microsoft.com/purview/data-classification-overview




































