For enterprise IT teams, the immediate task is to establish what needs replacing, what can remain in service during the transition, and what the destination must demonstrably support. A new catalog screen is not, by itself, a completed migration.
What is retiring—and what is not
Microsoft’s governance overview says new accounts can no longer be created, while existing capabilities remain in maintenance mode through November 12, 2027. That distinction matters: the announcement starts a transition period rather than describing an immediate shutdown. Maintenance mode should not be mistaken for a promise of continuing feature expansion.
The Partner Center notice separately states that Purview Data Security and Compliance offerings are unchanged. Administrators should therefore avoid sweeping every Purview-branded subscription into a replacement project.
A sensible first control is a capability-level inventory: record the product used, its business owner, its purpose and the contract covering it. Let that evidence define the project boundary—not the shared branding.
Start with metadata, not a wholesale data move
Microsoft documents an important architectural distinction: Data Map and Unified Catalog contain metadata rather than the underlying datasets, and their roles and permissions do not themselves grant access to that underlying data.
That changes the migration questions. Ask separately:
- Which catalog records and business definitions must be preserved?
- Which ownership assignments and approval processes must continue?
- How will users obtain access to the actual source data?
- Does the proposed architecture require moving datasets at all?
Do not authorize a wholesale data transfer simply because the catalog is changing. Equally, do not assume that moving metadata transfers source-system permissions.
Microsoft’s existing setup documentation provides useful inventory categories: registered sources and scans, governance domains, data products, glossary terms, custom metadata, quality rules and accountable owners. These are features to investigate—not evidence that every object has a direct OneLake equivalent.
For each category, add your own operational details: consumers, dependencies, business criticality and a test that would reveal a failed transition.
Fabric is the direction, not a parity guarantee
In its strategy announcement, Microsoft positions Fabric as its governance destination. It also names integrations with Atlan, Alation, Collibra and Informatica, and advises customers with contractual obligations or highly regulated operations to engage their Microsoft account team early.
Those statements support a requirements assessment, not an assumption that any particular configuration replaces every existing process.
The practical purchasing question is therefore: Can this proposed solution perform our required governance work, with evidence?
Consider these assessment routes:
| Route | Evidence to require before committing |
|---|---|
| Fabric-first transition | Representative discovery, ownership, permissions and stewardship tests |
| Fabric with a complementary catalog | A defined division of responsibilities and demonstrated integration |
| Partner-led implementation | Itemized deliverables, exclusions, acceptance tests and named operational owners |
These are recommended evaluation paths, not Microsoft-mandated migration steps. Continuing to use the existing deployment during assessment should be treated as a temporary transition arrangement, not the destination.
Budget for the implementation, not just the subscription
Microsoft’s Fabric licensing documentation distinguishes capacity from per-user licensing. Azure F capacities have regional pricing, per-second billing with a one-minute minimum, and a yearly reservation option. A customer-specific estimate must therefore reflect the intended deployment rather than a generic migration figure.
There is another procurement trap worth checking: Power BI Premium Per User does not provision Fabric capacity. Microsoft says non-Power BI Fabric workloads require an F capacity or trial capacity. An existing PPU subscription should not be treated as proof that the organization already has the required Fabric infrastructure.
Request separate estimates for:
- Applicable capacity and user licensing.
- Assessment and implementation.
- Configuration or custom integration.
- Validation, training and operational handover.
- Parallel operation and any necessary data movement.
These are proposed budget categories, not a claim that every organization will incur every cost. Ask suppliers to document assumptions and identify what would change the estimate. A licensing inclusion is not a migration statement of work.
A practical 2027 migration checklist
The following are recommended acceptance controls, not additional deadlines announced by Microsoft.
- Approve the scope. Identify affected governance capabilities and explicitly exclude unrelated security and compliance services.
- Baseline the inventory. Obtain owner confirmation of sources, metadata, business concepts, permissions, workflows and downstream dependencies.
- Test complete user journeys. Have representative users find an asset, understand its meaning, identify its owner and complete the relevant access process. Test unsuccessful requests as well as successful ones.
- Record gaps honestly. Distinguish working functionality from configuration, custom development, third-party integration and unresolved requirements.
- Approve commercial and operational ownership. Document costs, exclusions, support responsibilities and responsibility for maintaining each integration.
- Authorize cutover using evidence. Require recorded test results, retained accountability information, a recovery procedure and named owners before removing old dependencies.
The strongest success measure is not the number of imported catalog entries. It is whether people can still discover, understand and appropriately use the data their work depends on.
Microsoft has established the deadline and strategic direction. Customers should now turn those into a tested transition plan—without confusing a familiar product name, an existing license or a successful metadata import with a finished governance migration.
References
- Microsoft Purview Data Governance Retirement: 2027 Checklist - JournalArta JournalArta · 2026-11-17T06:23:05+00:00
- Learn about data governance with Microsoft Purview | Microsoft Learn learn.microsoft.com
- A next step in the evolution of the Microsoft Data Governance strategy | Microsoft Community Hub techcommunity.microsoft.com