Microsoft Purview Governance Ends in 2027: Migration Checklist
Microsoft will end support for Purview Data Governance on November 12, 2027, requiring existing customers to plan their transition while new account creation is already blocked. For enterprise buyers, the Microsoft Purview Data Governance retirement makes the Microsoft Fabric OneLake catalog a procu

Microsoft will end support for Purview Data Governance on November 12, 2027, requiring existing customers to plan their transition while new account creation is already blocked. For enterprise buyers, the Microsoft Purview Data Governance retirement makes the Microsoft Fabric OneLake catalog a procurement and technical assessment priority, rather than an assumed replacement.
- Affected scope: Unified Catalog, Data Map, Workflows and Microsoft Azure Purview solutions.
- Existing customers: Microsoft says capabilities remain in maintenance mode through November 12, 2027.
- Security boundary: Purview Data Security and Compliance offerings are unchanged by this announcement.
- Budget boundary: Microsoft says governance is included in Fabric capacity; a universal migration price is not disclosed.
What Microsoft Is Retiring—and What Continues
Microsoft’s Partner Center notice dated November 12, 2026 identifies the affected products and end-of-support date. Its governance getting-started documentation confirms that customers can no longer create new accounts and describes the maintenance period for existing capabilities.
That distinction matters when reviewing contracts. A security subscription carrying the Purview name should not automatically enter a governance replacement project. Ask application owners to identify the actual capability used, its business purpose and the contract covering it before procurement changes any subscription.
Start the migration inventory with registered sources, scans, ownership assignments, business terms and downstream dependencies. Microsoft’s existing setup documentation describes governance domains, data products, glossary terms and administrator roles. Treat these as inventory categories to investigate, without assuming that every object has an equivalent destination or an automatic transfer mechanism.
For each dependency, record who maintains it, who consumes it and how the organization would detect a failure after transition. A catalog entry that remains searchable is insufficient evidence that associated ownership and access processes still work.
Keep this review separate from broader productivity procurement. The Microsoft 365 vs Google Workspace for business comparison addresses a different buying decision; shared Microsoft branding does not establish shared retirement scope.
The checklist below is editorial planning guidance. Its acceptance gates are proposed controls for buyers, rather than additional deadlines announced by Microsoft.
Compare Transition Routes Before Signing a Contract
In its November 12 strategy announcement, Microsoft directs governance customers toward Fabric. It also acknowledges requirements beyond Fabric’s current capabilities and names integrations with Atlan, Alation, Collibra and Informatica. That acknowledgement supports a requirements assessment; it does not establish feature parity.
The following routes serve different purposes. User profiles and benefits are editorial assessments. USD amounts marked “not disclosed” are unavailable in the reviewed sources, rather than indications of free service.
| Route | Technical or service basis | USD cost evidence | Main benefit to assess | Suitable buyer profile |
|---|---|---|---|---|
| Maintain existing Purview temporarily | Existing capabilities in maintenance mode through the stated deadline | Remaining customer-specific cost: not disclosed | Time to validate a destination | Existing customers preparing a controlled transition |
| Fabric OneLake catalog | Microsoft’s stated governance destination; governance included in Fabric capacity | Customer-specific capacity and migration total: not disclosed | Governance within the Fabric platform | Teams evaluating Fabric against documented requirements |
| Fabric with another enterprise data catalog | Microsoft names third-party integrations; implementation must be assessed | Combined licensing and integration total: not disclosed | Addressing requirements beyond current Fabric capabilities | Organizations with broader catalog requirements |
| Partner transition engagement | Partner notice explicitly calls for scoping OneLake transition services | Service fees: not disclosed | Defined implementation deliverables | Buyers needing external migration expertise |
Require each bidder to distinguish available functionality, configuration work, custom integration and unresolved gaps. Put export coverage, import validation, ownership mapping and acceptance evidence into the statement of work.
For Microsoft Purview transition services, request an itemized proposal covering assessment, implementation, testing, training and support. Reject a fixed completion promise that lacks a dependency inventory and an agreed process for handling unsupported requirements.
Build a Budget Around Capacity and Verified Data Movement
Microsoft’s Fabric licensing documentation describes capacity and per-user licensing as separate planning elements. Azure F capacities use regional pricing and per-second billing with a one-minute minimum; annual capacity reservations are also available. The documentation does not provide a universal USD migration budget.
Request a dated estimate for the intended region, capacity, user access and operating pattern. Keep implementation labor, parallel operation and ongoing administration visible alongside subscriptions. These are proposed budget categories; their amounts remain not disclosed until the organization obtains applicable pricing and service quotes.
“Included in capacity” should not become “no additional project cost.” Ask the supplier to show what existing capacity can support, what assumptions underpin the estimate and which changes would trigger a revised quote. Avoid booking savings before those assumptions are tested.
Do not automatically budget a wholesale transfer of underlying datasets. Microsoft’s strategy announcement describes supported approaches for governing data without copying or moving it. Whether that applies to a particular source requires validation. If the proposed design does move data, assess the relevant transfer path separately using the AWS and Azure egress fees guide as a procurement checklist.
Maintain a separate cost line for any AI workload under evaluation. Our AI inference pricing across AWS, Azure and Google Cloud comparison concerns another consumption decision; catalog migration alone does not establish an inference requirement.
Choose a Route Using Evidence and Acceptance Gates
Choose a Fabric-first assessment if your team already operates Fabric and can demonstrate that required governance workflows work in the proposed configuration. Evaluate a complementary catalog when documented requirements remain unmet. Organizations with contractual obligations or highly regulated operations should engage their Microsoft account team early, as Microsoft explicitly advises.
Use these acceptance gates for the data governance migration:
- Approve the inventory. Obtain business-owner confirmation of sources, catalog objects, dependencies and critical workflows.
- Test representative cases. Verify discovery, ownership, permissions and required metadata against the destination.
- Preserve accountability records. Check that processing documentation remains accessible, accurate and maintainable.
- Approve commercial scope. Record licensing assumptions, service deliverables, exclusions and responsibility for unresolved gaps.
- Authorize cutover. Require documented results, a recovery procedure and named operational owners before retiring dependencies.
NIST describes its Privacy Framework as a voluntary enterprise privacy-risk tool. It can inform the risk review, without certifying a migration. The UK Information Commissioner’s documentation guidance says processing records must stay current and describes documentation obligations for controllers and processors, with limited exemptions. The page is under review following legislative changes.
The buying decision should follow verified requirements and a priced implementation scope. Microsoft has supplied a support deadline and a strategic destination; customers still need evidence that their chosen configuration preserves the governance processes their business depends on.
Take the quizWhat Kind of Holiday Spender Are You? Take the Black Friday QuizStart →- 1U.S. Emergency Alert Test Nov. 17 Is Not a Power Outage

- 2Women With Autoimmune Diseases Wait About 4 Years for Diagnosis, Study Finds

- 3DUP Chairman Lord Morrow Loses Wife and Daughter Within Hours in NI

- 4Micron Stock Falls 28% as $35.16 Billion Buyback Nears

- 5I’m A Celebrity 2026 Line-Up: Rooney Leads 11 Stars Into Jungle

Lifestyle7 Signs Your Social Battery Is Running Low (and Why You Keep Cancelling Plans)
Lifestyle · Food & HealthThanksgiving Food Safety: How Long Leftovers Last and the Safe Turkey Temperature
Lifestyle7 Quiet Habits of Emotionally Intelligent People, According to Psychologists
LifestylePeople Who Don’t Like Celebrating Their Birthday Often Share These 7 Traits














