Free Catalog Transition Assessment · One company a quarterApplications close each quarter0d00h00m00sApply now
The problem

Microsoft is retiring Purview's governance catalog.

0days0hours0minutes0seconds

until Microsoft ends support for Purview Data Governance on November 12, 2027

Purview to OneLake Migration · Early access

Move your governance work before Microsoft ends support.

Microsoft announced on November 12, 2026 that Purview Data Governance is retiring. New accounts are blocked and support ends on November 12, 2027. Microsoft names the OneLake catalog as the destination for Fabric governance, and says it is not a like-for-like replacement. Your glossary, quality rules and approvals have no obvious home. As of November 21, 2026 we found no Microsoft tool to move what you built. AI does the first pass, and your stewards sign every domain.

Your environment · the export and AI both stay in your own Azure tenant
Today, read-only

Purview Data Governance

The catalog Microsoft is retiring

Glossary, domains, data productsScans and lineageQuality rules and policies
Where each object lands

The right home for each kind of contentdecided object by object, not one catalog for everything

OneLake catalog

AI maps Fabric content, with its owners and descriptions

Domains and ownershipTags and descriptionsEndorsement

Partner catalog

AI works out what the OneLake catalog does not hold

Governed glossaryColumn-level lineageScanning outside Fabric

Rules and archive

AI rebuilds quality rules as code; history is kept

Quality rules as codeEvidence archive
Stays in Purview: sensitivity labels, data loss prevention, audit
AI, running in your Azure tenant

The first pass on every objecthosted on Azure through Microsoft Foundry, in your own Azure subscription and geography

Reads every object

The whole export: terms, owners, rules, lineage

Decides where it lands

Move, coexist, bridge, redesign or retire

Drafts what is missing

Mappings, descriptions, quality rules as code

Checks it arrived

Every object, relationship and owner

People decide
  • Consultants reviewEverything AI writes
  • Your governance lead decidesOneLake catalog or partner catalog, under a written rule
  • Stewards sign each domainOn the reconciliation results. Silence is not sign-off
What you get
  • Transition assessmentWhat moves, what needs a new home, what retires, dated before the cutoff
  • Content in its new homesGlossary, owners, rules and descriptions, one domain per wave
  • Purview switched offEach domain signed, nothing left reading it
  • Evidence archiveApprovals and history, queryable for your auditors

AI does the first pass. Your people decide. Silence is not sign-off: a domain without its steward's signature is not switched off.

What you get

Three deliverables. Each is accepted as a whole.

Time frame Four days

  • Catalog inventoryXLSX · Excel workbook

    One sheet for each kind of object, with counts checked against Purview's own.

  • Decision for every objectXLSX · Excel sheet

    Move, coexist, bridge, redesign or retire, with a reason.

  • Gap listPDF · About 6 pages

    What the OneLake catalog does not hold for you, plus a settings checklist.

  • What reads your catalogXLSX · Excel sheet

    A first list of readers, each with an owner and a planned action.

  • Landing decision memoPDF · About 8 pages

    Where each kind of content lands, and why.

  • Wave planPDF · 1 page and a table

    A steward and a switch-off date for each domain.

  • Cost comparisonPDF · 1 page

    Purview billing against your Fabric capacity. Not a cost model.

  • ReadoutPPTX · 45 minutes, about 12 slides

    The answer, the plan and the decisions we need.

Accepted when the counts match Purview's, every object has a decision, and your governance lead has reviewed the memo.

Pricing

Fixed fees. The first step is $12,000.

Weeks12345678910
Catalog Transition Assessment4 days
$12,000 · 4 days
First domain waveFirst governance domain, 6 weeks
6 weeks $48,000
Each extra domainScheduled in the wave plan
+ $16,000 each
Evidence archive and switch-off2 to 3 weeks
$16,000
Fixed-price workEach extra domain: price fixed, timing set in the wave planUp to one more week (the archive takes 2 to 3 weeks)
  1. Catalog Transition Assessment4 days$12,000
  2. First domain wave6 weeks$48,000
  3. Each extra domainScheduled in the wave plan$16,000 each
  4. Evidence archive and switch-off2 to 3 weeks$16,000
Free Catalog Transition Assessment · One company a quarter

Applications close each quarter

0days00hours00min00sec

Get your Purview governance catalog assessed, free

Each quarter we choose one company for a free Catalog Transition Assessment: four days, normally $12,000. We choose by fit and reply to every application.

  • An inventory of every object in your Purview governance catalog, with a decision for each
  • A written recommendation on where each kind of content should land
  • A wave plan with a switch-off date for each domain, finishing before Microsoft ends support
  • A readout with your governance lead

What we need from you: read access to Purview through an application identity your team creates, a named governance lead, a steward for each domain in scope, and an Azure subscription that can run AI. You pay only your own costs, on your own bills: AI usage on your Azure invoice. For US companies that run Purview Data Governance.

Questions

What leaders ask us first

Is Purview being shut down?
No. Purview Data Governance is retiring, and Purview is not. Microsoft ends support for the Unified Catalog, Data Map, workflows and classic Purview governance on November 12, 2027, and as of November 2026 new accounts are blocked. Sensitivity labels, data loss prevention and audit stay in Purview, and we do not change them.
Can't we wait for Microsoft's migration tool?
You can, but as of November 21, 2026 we found no Microsoft tool that moves this content to the OneLake catalog. Even a good tool would not decide where each piece belongs or get your stewards to sign. Starting early gives your stewards time to review before November 12, 2027.
Why not just use the OneLake catalog?
Use it for what it holds. Microsoft names it as the destination for Fabric governance, and says it is not a like-for-like replacement. As of November 2026 it does not hold a governed glossary, column-level lineage, quality rules or scanning of sources outside Fabric. The assessment decides, object by object, what lands there. If the OneLake catalog is enough, the assessment says so.
Do you sell us a catalog?
No. We do not sell or resell any catalog or Fabric capacity. Where a partner catalog fits (for example Alation, Collibra or Atlan), you hold that contract, and the recommendation memo discloses any Data Meaning partner relationship that could bias our advice.
Where does AI run, and who sees our metadata?
In your own Azure subscription, hosted on Azure through Microsoft Foundry, in the geography you select. We use a third-party AI model with our own prompts and checks. By design it reads an export of your catalog metadata, held in your own storage, and never receives your business data. Catalog metadata can still be sensitive, for example an owner's name, so the export stays in your storage. The model's provider is a separate processor under its own terms, so your security review covers those terms. Microsoft's published pages do not describe private networking, role-based access or logging for this deployment, so we confirm them with your security team before any wave begins. Our statement of work names the model.
What does not move?
Sensitivity labels, data loss prevention and audit stay in Purview. Lineage that Fabric cannot regenerate, scan history and the classifications Purview applies when it scans a source have no home in the OneLake catalog, so they go to the archive or a partner catalog and appear as known differences. Microsoft documents ways to write domains and tags. We prove every other route in a pilot first, and content that cannot be loaded by program is quoted separately. We do not promise automated lineage migration.
What do we have to provide?
Access that lets us read every governance object, which means Microsoft's Collection Admin role or equivalent, held by an application identity (a service principal) your team creates. We change nothing in Purview until the switch-off date you agree. You also need a named governance lead, a steward for each domain, and an Azure subscription that can run AI (not free trial, student, credit-only or Cloud Solution Provider). Without these before day one, the four days slip.

Start with the four-day Catalog Transition Assessment.

One fixed fee of $12,000, and no commitment to anything else.

Data Meaning is an independent consultancy. Microsoft, Purview, Fabric, OneLake, Azure and Foundry are trademarks of Microsoft Corporation. Other product names are trademarks of their owners.