HomeServicesManaged IT ServicesAI DeploymentAccredOneInsightsAnswersAboutFree Consultation
Data Governance & Compliance

Microsoft Purview Data Governance Retirement: Prepare for Fabric

Published Nov 12, 20265 min read
By , Founder & Senior Architect | Company facts

Microsoft is retiring Microsoft Purview Data Governance, with support ending November 12, 2027. Microsoft says its data governance strategy is moving to Microsoft Fabric and the OneLake catalog. The announcement concerns data governance products; Purview data security and compliance offerings remain in place, including capabilities for classifying and protecting sensitive data.

What to do now: identify whether your organization uses Purview Data Governance, inventory the assets and integrations that depend on it, and start a transition assessment with Microsoft. Continue operating existing security and compliance controls.

What is retiring—and what is not

Microsoft's partner announcement identifies Unified Catalog, Data Map, Workflows, and Microsoft Azure Purview solutions within the retirement. Support for Purview Data Governance ends November 12, 2027. Confirm the exact scope for your subscriptions and workloads with Microsoft rather than assuming every feature has an identical replacement.

The Microsoft Security announcement says Purview will continue to focus on data security and compliance, including classification, sensitivity labeling and data loss prevention. An organization using Purview to protect Microsoft 365 data should not interpret this retirement as a reason to disable those protections.

Where Microsoft is taking data governance

Microsoft is making the OneLake catalog in Fabric its foundation for data discovery and governance. The announcement describes supported shortcuts, mirroring and connectors for governing data across Fabric, Azure and third-party sources. Coverage and behavior vary by source and capability; validate the specific integrations you rely on before choosing a transition path.

Microsoft says governance is included in Fabric capacity rather than billed through separate governance meters. That does not establish your total future cost: assess capacity sizing, consumption, existing agreements and any separate Purview licensing. Microsoft Learn notes that Fabric sensitivity labels, protection policies and DLP require additional Purview licensing.

A practical transition plan

  1. Identify ownership and dependencies. Bring together data governance, security, compliance, analytics and finance owners. Inventory cataloged sources, scans, domains, glossary terms, data products, lineage, workflows, access roles and downstream integrations.
  2. Map requirements to available capabilities. Test representative data sources and governance tasks in Fabric, including discovery, permissions, lineage and stewardship. Document gaps, unsupported connectors and any required third-party tooling; do not assume automatic migration or feature parity.
  3. Protect data during the transition. Review sensitivity labels, DLP, retention and audit requirements separately from catalog migration. Keep existing protections active and test permissions and labels on representative data before changing workflows.
  4. Plan cost and implementation. Review Fabric capacity and Purview entitlements with your licensing partner. Establish a pilot, owners, acceptance criteria and a cutover schedule well ahead of November 12, 2027.
  5. Escalate special requirements. Microsoft asks customers with contractual obligations or highly regulated environments to engage their Microsoft account team early for individual assessment. Request current transition guidance, support terms and a written resolution for critical gaps.

Questions to ask Microsoft

  • Which of our Data Map sources, scans, catalog assets and workflows have supported transition paths, and what must be recreated?
  • What happens to our metadata, lineage, APIs, access model and historical records during and after transition?
  • Which Fabric capacity, regions and Purview licenses are required for our scenarios, and what are the expected costs?
  • How will our contractual, data residency and regulatory requirements be met before support ends?

Microsoft says detailed transition guidance is available and recommends contacting your account team for environment-specific questions. Treat the retirement deadline as a planning deadline; validate product-specific guidance and availability before committing to a migration design.

Microsoft sources

Planning the transition? Accred’s Microsoft 365 security team can help map dependencies and data protection requirements before you change governance platforms.