Data Governance · 5 min read
Microsoft Purview Data Governance Hits End of Support in 2027
Microsoft ends Purview Data Governance support on November 12, 2027; new accounts are blocked and Fabric OneLake is the stated destination, with no disclosed migration price.
Key takeaways
- Support for Microsoft Purview Data Governance ends November 12, 2027; new account creation is already blocked.
- Affected scope: Unified Catalog, Data Map, Workflows and Azure Purview solutions; Data Security and Compliance are unchanged.
- Microsoft directs customers to Fabric OneLake but names Atlan, Alation, Collibra and Informatica integrations for gaps.
- Governance is included in Fabric capacity; no universal migration price is disclosed.
- Azure F capacities bill per second with a one-minute minimum; annual capacity reservations available.
Microsoft will end support for Purview Data Governance on November 12, 2027, and new account creation is already blocked. The Partner Center notice, dated November 12, 2026, sets the retirement date and confirms that existing capabilities stay in maintenance mode until the deadline. For enterprise buyers, that turns the Microsoft Fabric OneLake catalog into a procurement and technical assessment priority, not an assumed replacement.
What exactly is Microsoft retiring?
The affected scope covers the Unified Catalog, Data Map, Workflows and Microsoft Azure Purview solutions. Two boundaries matter for contract review. Purview Data Security and Compliance offerings remain unchanged by the announcement, so a security subscription carrying the Purview name should not automatically trigger a governance replacement project. And Microsoft says governance is included in Fabric capacity, but it discloses no universal migration price.
A data team should start by asking application owners to identify the actual capability in use, its business purpose and the contract covering it. Shared Microsoft branding does not establish shared retirement scope.
How should teams build the migration inventory?
Start with registered sources, scans, ownership assignments, business terms and downstream dependencies. Microsoft's setup documentation describes governance domains, data products, glossary terms and administrator roles. Treat these as inventory categories to investigate. Do not assume 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 the associated ownership and access processes still work. One long sentence to keep in mind: an inventory that stops at object counts, without tracing maintainers, consumers and failure-detection paths into the destination environment, will not survive an audit or a real incident.
Keep this review separate from broader productivity procurement. A Microsoft 365 versus Google Workspace comparison addresses a different buying decision entirely.
Which transition routes exist, and what do they cost?
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.
Four routes serve different purposes:
- Maintain existing Purview temporarily: capabilities stay in maintenance mode through the deadline; remaining customer-specific cost not disclosed. Buys time to validate a destination.
- Fabric OneLake catalog: Microsoft's stated governance destination, with governance included in Fabric capacity; capacity and migration totals not disclosed.
- Fabric plus another enterprise catalog: third-party integrations named by Microsoft; combined licensing and integration totals not disclosed.
- Partner transition engagement: the partner notice explicitly calls for scoping OneLake transition services; service fees not disclosed.
Note that "not disclosed" means unavailable in the reviewed sources, not free.
How should the budget be built?
Microsoft's Fabric licensing documentation treats 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 provides no 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. "Included in capacity" should not become "no additional project cost": ask the supplier what existing capacity can support, what assumptions underpin the estimate and which changes would trigger a revised quote.
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 design does move data, assess the transfer path separately, including egress fees. Maintain a separate cost line for any AI workload under evaluation; catalog migration alone does not establish an inference requirement.
What acceptance gates should buyers use?
Choose a Fabric-first assessment only if the team already operates Fabric and can demonstrate the required governance workflows in the proposed configuration. Evaluate a complementary catalog when documented requirements remain unmet. Organizations with contractual obligations or regulated operations should engage their Microsoft account team early, as Microsoft explicitly advises.
Proposed acceptance gates for the 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.
Regulatory context reinforces the records gate. The UK Information Commissioner's documentation guidance says processing records must stay current and describes obligations for controllers and processors, with limited exemptions; that page is under review following legislative changes. NIST describes its Privacy Framework as a voluntary enterprise privacy-risk tool. It can inform the risk review without certifying a migration.
When tendering, 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. Request an itemized proposal covering assessment, implementation, testing, training and support, and reject any fixed completion promise that lacks a dependency inventory.
The verdict for buyers is straightforward. 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.
Google News: Data Governance (Source)
More from Rebecca Stone
Show full bio
Senior reporter covering regulation, policy and their impact on Analytics Digest is a professional daily at Analytics Digest.
12 articles