A data platform lead opened the Microsoft Purview Unified Catalog documentation on 13 November and found a new notice at the top of every page. The product their business glossary lives in is in maintenance mode, and support ends on a fixed date. The search for Purview alternatives now comes with a deadline.
Microsoft has named the destination: the OneLake catalog in Microsoft Fabric. So the question has changed. The old one was which catalog to buy instead. The new one is what to carry across, and where the business meaning should live once the catalog that held it is gone.
Purview Data Governance retires on 12 November 2027. Microsoft's replacement is the OneLake catalog, and Microsoft's own architects tell customers to export and preserve terms and ownership because full glossary parity is off the table. TopQuadrant's position is that the exported meaning should land in a governed, open-standard record that outlives any catalog, including the next one.
The announcement went out on 12 November 2026 on the Microsoft Tech Community, and every Purview governance page on Microsoft Learn was updated the same day. The rows below are Microsoft's words.
| Item | Microsoft's words | Source and date |
|---|---|---|
| What retires | "Microsoft Purview Unified Catalog and classic Microsoft Purview data governance capabilities (formerly Azure Purview) are being retired." / "You can no longer create new accounts, and existing capabilities will remain in maintenance mode through November 12, 2027." | Notice on every Purview governance page, Microsoft Learn, updated 12 November 2026 |
| The date | "Support for Purview Data Governance will end Nov. 12, 2027." | Microsoft Tech Community announcement, 12 November 2026 |
| The replacement | "The OneLake catalog is now the single foundation for governing data across your entire estate." | Same announcement |
| How it is paid for | "it's included in Fabric capacity" | Same announcement |
| What continues | "Microsoft Purview stays focused on data security and compliance" | Same announcement |
Microsoft Purview continues as a security and compliance product, so nothing here says Purview is retiring. The retiring part is what Microsoft's blog calls Purview Data Governance: the Unified Catalog and the Data Map.
Three reasons drive the search now, and they lead to different work.
Fabric and a plan answer the first two. The third is this piece.
A team that built on it built on a capable product, and the retirement changes only the timeline.
The Data Map scans wide. Microsoft's source table, dated 13 October 2026, lists 46 source rows, and the non-Microsoft entries include Snowflake, Google BigQuery, Oracle, Teradata and SAP (learn.microsoft.com, data-map-data-sources). Data quality runs on the data itself, with "Out of box rules to measure six industry standards data quality dimensions" (unified-catalog-data-quality, 13 October 2026).
Microsoft's glossary page, dated 13 October 2026, says: "Glossary terms in Microsoft Purview Unified Catalog are active values that provide context. They also apply policies that determine how you manage, govern, and make your data discoverable for use." (unified-catalog-glossary-terms). A term carries policy. A CSV row does not, and that is the first thing an export loses.
The transition post is by Paul Singh and Rafia Aqil, Microsoft architects. It was published on 13 November 2026 and updated on 16 November 2026 (Microsoft Tech Community, 4573422). It maps each Purview outcome to Fabric and defines its own grading word: "Partial means part of the outcome is covered and part is not." Every row below quotes that post.
| Purview outcome | Microsoft's guidance, verbatim | Source |
|---|---|---|
| Glossary and critical data elements | "Export and preserve terms and ownership. Do not claim full glossary or CDE parity." | Tech Community 4573422, 13 November 2026 |
| Data products | "Define the product contract, owner, health, lifecycle, and access process outside the catalog where needed." | Same post |
| Data quality | "Governance Health is not a rules, profiling, and scoring engine." | Same post |
| Lineage | "Retain another method for cross-system, unsupported-workload, or granular lineage." | Same post |
| Workflows | "Keep the request, approval, expiration, revocation, and evidence process where Fabric does not cover it end to end." | Same post |
| Scanning | "Data connectivity is not enterprise metadata scanning." | Same post |
| Stewardship | "Keep a responsibility matrix for stewardship duties without a dedicated role." | Same post |
Read the first row and the last two together. The terms and owners leave as an export. The approval process stays wherever you keep it. The steward becomes a row in a matrix. That is a definition with nobody attached to it by the system.
The OneLake catalog overview on Microsoft Learn is dated 26 August 2026, updated 29 September 2026, before the announcement (onelake-catalog-overview). It names "domains, endorsements, metadata scanning, policies, and governance insights". As of that date it names no glossary terms, data products or critical data elements. Fabric ships monthly, so read that page again before you plan around it.
Microsoft's glossary documentation shows what a term carries today. The page is dated 13 October 2026, updated 12 November 2026 (unified-catalog-glossary-terms-create-manage).
| What the term carries | Microsoft's documentation, verbatim | What a file export keeps |
|---|---|---|
| Name, definition, owner, expert | Bulk import columns: "name (required)", "description (required)", "owners (required): Enter a valid email address", "experts" | Kept, as text and email addresses |
| Who may define it | "To create, edit, and manage glossary terms, you need the Data Steward role in the governance domain where the terms reside." | Lost. The role belongs to the catalog |
| Change control | "If the term is published, select Unpublish, and then select Edit to edit the name, definition, owners, or custom attributes." | Lost. Draft, Published and Expired are catalog states |
| Attached policy | "all the associated policies are automatically applied." (unified-catalog-glossary-terms) | Lost. Policy stays with the catalog |
| Version history | The pages we read document Draft, Published and Expired. They document no version history of a term. | Nothing to export |
So the export preserves the words and some email addresses. It preserves no record of who confirmed the definition, no rule that tests data against it, and no history of what it meant before. Those lived in the catalog around the term, and the catalog is what is being retired.
In our post Metadata Management vs Data Governance: What Each One Decides we state that ownership has to live on the record itself. An owner in column C of a CSV is a document.
Our position, with the same weight as Microsoft's evidence above and open to the same test.
Microsoft's announcement says: "Fabric also integrates with other 3rd party providers such as Atlan, Alation, Collibra and Informatica so customers can decide what works best for their data governance requirements." TopQuadrant is absent from that sentence, and no live TopQuadrant page describes a Purview or OneLake catalog connector. We claim neither. What we answer is the other half of the architects' instruction: the receiving side.
Our usual line is that your catalog stays and syncs from the governed record. The live wording names three catalogs: "Collibra, Informatica, and Alation reflect the same values and effective dates the stewards maintain." The catalog is moving. The meaning should not have to. Fabric becomes the catalog your people search, and the definitions it shows come from a record with a name on it. In our post What Is Metadata Management? we state that a catalog is organized around assets and meaning around concepts. That is why one can be swapped while the other is kept.
Where we do not compete: scanning across 46 source types, pipeline lineage, data quality on the data, and protection. Those stay with Fabric and Microsoft Purview, and a Fabric shop gets the catalog basics within capacity it already pays for. We cannot match "included". We hold the meaning those tools display.
Four questions, in order.
Our post Metadata Management Tools for Governance and AI Readiness covers the wider market. Our What Is Data Governance for AI? post covers why the confirmation record matters once the reader is a model.
As the place the exported meaning lands. Microsoft has decided the catalog. TopQuadrant holds the terms, the owners, the rules and the history those terms need to stay true after the move.
If your Purview estate is scans and lineage, Fabric and a plan are enough. If it is a glossary your business agreed on, the export is the fragile step. Carry the words into TQ Data Foundation. Let the named owner confirm them. Attach the rule. Keep every version. The next catalog retirement then costs you a connector, and never the meaning.