Purview data governance retires in November 2027. Your labels and retention don’t

On 11 November 2026 Microsoft announced that Purview Data Governance will be retired, with support ending on 12 November 2027. Learn now carries the same notice on its data governance pages: Unified Catalog and classic Purview data governance (formerly Azure Purview) are being retired, no new accounts can be created, and existing capabilities stay in maintenance mode through 12 November 2027. Governance moves to Microsoft Fabric, with the OneLake catalog as the place to govern data.

The word Purview in that sentence is going to cause confusion in records meetings. Worth clearing up early.

What's leaving and what's staying

Microsoft's announcement draws the line itself. Purview stays focused on data security and compliance: classifying, labeling and protecting sensitive data, and preventing data loss across the estate and AI. The retiring half is data governance: Data Map scanning and the Unified Catalog where scanned metadata is curated.

What’s leaving vs. what’s staying in Purview

Support for the items on the left ends 12 November 2027. The capabilities on the right remain in Microsoft Purview.

Leaving
(support ends 12 Nov 2027)
Staying in Purview
Unified Catalog Sensitivity labels and classification
Data Map scanning and metadata Data loss prevention
Classic Azure Purview data governance Retention and records management
(not named in the retirement notice)

Your retention plan isn't part of this

Retention policies, retention labels, adaptive scopes and records management in Microsoft 365 sit on Purview's compliance side, which this notice doesn't cover. If someone proposes pausing a labeling or retention project because Purview is going away, that's the wrong Purview.

Data Map held metadata, so the move is about metadata

Learn is explicit that everything in Data Map and Unified Catalog is metadata, not the underlying data, and that none of its roles grant access to the data itself. What you'd lose by doing nothing is the curation work: glossary terms, owners, classifications applied to assets, and lineage.

SAP shops have one more line to check

Data Map has documented scanners for SAP ECC and SAP S/4HANA. They extract technical metadata such as application components, packages, tables with their fields and keys, views, transactions, programs, function modules, domains and data elements, plus static lineage between tables and views. Both connector pages now carry the retirement notice.

Microsoft's announcement says the OneLake catalog can govern data outside OneLake through shortcuts, mirroring and supported connectors. It doesn't name SAP sources. If your SAP metadata lives in Data Map today, ask your Microsoft account team how that scan carries over, or whether it does, before you plan the move.

Who owns the transition

  • Data governance lead: inventory what's curated in Unified Catalog (domains, glossary, owners, lineage) and decide what's worth carrying.
  • SAP data or Basis owner: confirm which SAP systems are scanned, what the scans feed, and who actually uses them.
  • Records and compliance owner: confirm that labels, DLP and retention plans continue unchanged, and say so to anyone who asks.
  • Contracts or procurement: Microsoft asks customers with contractual obligations, or in highly regulated industries, to engage their account team early.

A year is reasonable runway for a metadata move. The main risk isn't the date. It's two different teams hearing that Purview is retiring and each assuming it means them.

Let's work together.

Where does your landscape stand?

Take the free Assessment. It's about 10 questions, and you get a one-pager with your estimated level of effort and suggested next steps.

McCloy Data

Thought leadership on OpenText, SAP, and practical content and finance automation - from the McCloy Data team.

https://www.mccloydata.com
Next
Next

Content Aviator in Content Management 26.4 can act on workflows: pick which ones first