Microsoft's November 12, 2026 announcement moves its data governance strategy toward Microsoft Fabric and the OneLake catalog. It sets November 12, 2027 as the support-end date for Purview Data Governance. Microsoft announcement.
For an Azure data team, my proposed first deliverable is a transition inventory with named owners. Establish which governance capabilities the organization actually uses and which evidence the business needs before accepting a replacement workflow.
Establish the Affected Scope
Microsoft's Partner Center notice includes Unified Catalog, Data Map, Workflows, and Microsoft Azure Purview solutions in the retirement. It says Purview Data Security and Compliance offerings are unchanged. Retirement scope.
I would ask the platform and governance owners to identify the deployed services, integrations, operating procedures, and business teams associated with the affected capabilities. Give each inventory item a responsible person and a documented purpose.
Keep the resulting scope attached to the transition plan. Review it with the people who operate the estate so the project estimate reflects the work and dependencies that must move through acceptance.
Map the Governance Work People Perform
Microsoft identifies the OneLake catalog as its governance foundation and acknowledges that some customer requirements extend beyond Fabric's current capabilities. Strategy and capability boundary.
My evaluation would begin with representative tasks: finding an approved dataset, identifying its owner, reviewing lineage, and establishing the access or stewardship decision associated with it. Ask business users to define the evidence that makes each task successful.
For every task, record the current procedure, proposed future procedure, available capability, and unresolved requirement. Assign a decision owner to each gap before treating that part of the transition as ready.
Review Integrations at Their Actual Boundary
I would inventory the systems that publish metadata, consume catalog information, or depend on the governance process. Include their owners, authentication assumptions, update frequency, and the evidence they use to detect an unsuccessful exchange.
Choose one representative integration for an approved test environment. Rehearse its proposed workflow using synthetic or approved sample metadata and retain both the input and the expected downstream result.
Have a second engineer reproduce the result from the documented instructions. Record missing information and unexpected behavior as preparation work with an owner, then use that evidence to improve the proposed migration sequence.
Build an Evidence-Based Acceptance Record
My acceptance sheet would connect each business requirement to a demonstrated workflow and the person authorized to accept it. Preserve the observation date, configuration context, and any dependency on a future capability.
Ask the governance owner to review a sample from the perspective of someone who did not build the pilot. The reviewer should be able to establish where ownership, lineage, and policy decisions are recorded and how a user finds the appropriate evidence.
Retain unresolved questions explicitly. A roadmap entry can inform planning; the delivery decision should identify which required behavior has been demonstrated in the proposed environment and which work remains.
Put the Support Deadline into the Delivery Plan
Microsoft asks customers with contractual obligations or highly regulated requirements to engage their account team early for an individual assessment. Transition engagement guidance.
I would work backward from November 12, 2027 with separate milestones for inventory, capability decisions, integration rehearsal, user acceptance, and operational handover. Give each milestone an owner and an explicit completion condition.
Include time to resolve gaps and repeat a failed rehearsal. Keep the existing governance operating procedure available during the evaluation, and document who accepts the later cutover and the conditions that would stop it.
Practical Cloud Engineer Takeaway
Confirm the affected governance products and dependent workflows.
Map real business tasks to current Fabric capabilities and open gaps.
Rehearse representative integrations with approved sample metadata.
Preserve requirement-level acceptance evidence and named owners.
Plan milestones ahead of the November 12, 2027 support deadline.
Who Should Care?
Azure data platform engineers, Purview Data Governance administrators, data stewards, enterprise architects, and teams responsible for governance integrations and operating procedures.
Bottom Line
The announcement creates a dated transition decision for Purview Data Governance customers. A useful plan establishes the actual scope, tests the proposed workflows, and gives business and operations owners evidence they can review before cutover.
No Purview account, Fabric capacity, catalog, governance workflow, integration, or Azure resource was changed for this article.
Sources
Stay radical, stay curious, and keep pushing the boundaries of what is possible in the cloud.
Chriz
Beyond Cloud with Chriz
Comments