Microsoft Purview: review the Classifiers preview

Microsoft has documented the new Classifiers experience in Microsoft Purview as a public preview. Supported classification types no longer have to be inspected across several separate administration areas; administrators can discover, create, inspect and manage classifiers in one place. For smaller organisations this matters because classification is the foundation for labels, data loss prevention and data protection controls.

What Microsoft now brings together in Purview

The new Classifiers page in the Microsoft Purview portal brings multiple classification capabilities into a unified experience. Microsoft explicitly lists Information Protection, Data Loss Prevention and Data Security Posture Management as entry points. Changes made in either the new or existing experience are reflected in the other, so the preview runs alongside the administration paths already in use. That gives administrators a safer starting point for understanding existing classification before creating yet another rule.

  • Supported capabilities include sensitive information types, named entities, exact data match and trainable classifiers.
  • Credentials, document fingerprinting, OCR and on-demand classification are also included in the overview.
  • The classified-items count shows how many items were found with a specific classifier.
  • Administrators can also see how many policies use a classifier before editing or deleting it.

Why this matters for SMBs

Many Microsoft 365 environments grow in layers: labels first, DLP later, and then exceptions for specific teams or departments. Without a current inventory, it becomes difficult to know which classifier is actually used in production and which policy depends on it. The new Purview view does not solve governance automatically, but it makes the inventory easier. Companies without a dedicated compliance team can check whether a DLP rule, label or report is affected before a change is made.

This remains a technical topic, not legal advice: the point is not to assess GDPR obligations, but to improve visibility into the Microsoft 365 configuration. That distinction matters in practice. A classifier does not decide whether a business process is lawful. It helps identify personal data, credentials or recurring document templates more reliably, so the protection controls built on top of those signals can be operated and reviewed consistently.

Deadline and status of the change

Microsoft Learn lists the new Classifiers experience with a documentation date of 29 September 2026 and an update on 30 September 2026. The Microsoft Purview blog post was published on 1 October 2026 and describes the capability as a public preview with an administrator playbook. Microsoft also states that features might change before general availability. There is therefore no hard migration deadline, but there is a clear action: inventory existing classifiers now, review dependencies and make changes only after testing and approval. Waiting for general availability is safe for production changes, but it should not stop administrators from using the preview to find unclear ownership or duplicate classifier logic.

Which roles need access

Microsoft describes two permission paths: Microsoft Entra administrator roles and Microsoft Purview role groups. Access can be granted through roles such as Global Administrator, Compliance Administrator, Security Administrator and Compliance Data Administrator. In Purview, relevant roles include Information Protection Admin, Analyst, Investigator and Reader, plus matching role groups. Microsoft’s least-privilege note is important: not everyone who needs to inspect classifiers also needs permission to change them. A practical setup separates read access for inventory work, change access for technical maintenance and business approval from data or process owners.

What administrators should check now

  • Open Microsoft Purview and check whether the Classifiers page is available in your tenant.
  • Create an inventory of classifiers that are used in production labels, DLP policies or reports.
  • Before making changes, review the displayed policy dependencies and classified-items counts.
  • Test new or changed classifiers with a limited scope first and with documented approval.
  • Assign owners for classifiers, Data Loss Prevention policies and recurring reviews.

Official Microsoft sources

If you want to understand which classifiers actually work in your tenant and where DLP or label dependencies exist, we can review that as part of a Microsoft Security Assessment – get in touch.

Recommended Next Step

What does this mean for your environment?

Assess the topic in the context of your Microsoft 365 environment and define a practical next step.

Sebastian Kerssen, Managing Director of ReByteIT

You speak directly with Sebastian Kerssen – working in the Microsoft ecosystem since 2014, with personal consulting and a dedicated point of contact.

Leave a comment