Key takeaways
- Microsoft is retiring Purview Data Governance, including the Unified Catalog, Data Map, Workflows and the Azure Purview solutions. New accounts can no longer be created, existing capabilities stay in maintenance mode, and support ends on 12 November 2027.
- Purview’s data security and compliance features are unchanged: sensitivity labels, data loss prevention, audit and insider risk management stay in Purview.
- Microsoft names the OneLake catalog in Microsoft Fabric as its data governance solution. It covers discovery, domains, ownership, endorsement, tags, lineage for supported items and governance insights, but Microsoft’s own transition guide says the business glossary, data products, data quality and scanning of sources outside Fabric need to be preserved, redesigned or bridged with other tools.
- In the UAE, check where your data will sit: Microsoft lists UAE North as a region with all Fabric workloads and UAE Central as a Power BI-only region. If you have contractual obligations or work in a regulated sector, Microsoft asks you to talk to your account team early.
What Microsoft is retiring, and when
Microsoft announced on 12 November 2026 that it is retiring Microsoft Purview Data Governance and moving data governance into Microsoft Fabric, where the OneLake catalog becomes its data governance solution. The retirement covers the Unified Catalog, the Data Map, Workflows and the Microsoft Azure Purview solutions. Microsoft Learn describes it as the retirement of Purview Unified Catalog and classic Purview data governance, formerly Azure Purview.
| Date | What happens |
|---|---|
| 12 November 2026 | Microsoft announces the retirement. New Purview data governance accounts can no longer be created, and existing capabilities are in maintenance mode. |
| 12 November 2026 to 12 November 2027 | Existing capabilities stay in maintenance mode. Microsoft says it is supporting customers in moving to Microsoft Fabric and has published transition guidance. |
| 12 November 2027 | Support for Purview Data Governance ends. |
Microsoft says Purview Data Governance will be retired a year after the announcement, so treat 12 November 2027 as the date by which your catalog, glossary, lineage and workflows must run somewhere else.
What stays in Microsoft Purview
Only data governance is retiring. Microsoft says Purview’s data security and compliance offerings are unchanged, and that Purview stays focused on classifying, labelling and protecting sensitive data, preventing data loss across your estate and AI, and keeping up with compliance changes, with integration across Microsoft 365, Azure and Fabric. In Microsoft’s transition guide, the OneLake catalog discovers and governs Fabric data, while Purview protects, audits and monitors it.
- Sensitivity labels and data loss prevention (DLP), including on supported Fabric items.
- Audit and insider risk management.
If you classify or label data in Azure sources through Purview Data Map scans, ask Microsoft how that will continue, because the Data Map is part of the retirement.
What the OneLake catalog covers, and where it falls short
The OneLake catalog is the central place in Microsoft Fabric to discover data, understand its governance status and manage security. It has three tabs: Explore, for finding and using Fabric items; Govern, which shows the governance posture of the data you own and recommends actions to improve it; and Secure, for workspace roles and OneLake security roles. A Catalog Search REST API gives programs the same discovery.
Microsoft says the catalog can also govern data held outside OneLake, in Azure and third-party sources, through shortcuts, mirroring and supported connectors, without copying or moving it. It supports a federated model, is embedded in Teams, Excel and Foundry, and works with third-party tools including Atlan, Alation, Collibra and Informatica. Governance is included in Fabric capacity rather than billed through separate meters.
Microsoft’s own transition guide is frank about the gaps. It puts each requirement on one of four routes: move now to a documented Fabric capability, run the old and new side by side for a while, bridge the gap with a process or a partner tool, or redesign the requirement. This is how it maps the main Purview features:
| In Purview | Where it goes in Fabric today | Microsoft’s advice |
|---|---|---|
| Catalog search and browse | OneLake catalog Explore tab, item details, filters and the Catalog Search API | Move discovery of Fabric data now; keep separate discovery for sources outside Fabric. |
| Collections, domains and ownership | Fabric domains and subdomains, workspace assignment, domain admins and owners | Map your organizational boundaries, and keep a responsibility matrix for stewardship duties. |
| Business glossary, critical data elements and custom attributes | Tags, descriptions and endorsement | Export and keep your terms and their owners; Microsoft says not to claim full parity. |
| Data products | Domains, endorsement, sharing and discoverable semantic models | Define each product’s contract, owner, health, lifecycle and access process, outside the catalog where needed. |
| Lineage and impact analysis | Lineage and impact analysis for supported Fabric items | Move supported paths; keep another method for lineage across systems or for unsupported items. |
| Data quality | Freshness and curation insights, plus the tools in each workload and source | The governance view is not a data quality rules or scoring engine; check before treating it as a replacement. |
| Access requests and workflows | Item sharing, access requests on semantic models and controls in the source | Keep request, approval, revocation and evidence processes where Fabric does not cover them end to end. |
| Scanning sources outside Fabric | Shortcuts, mirroring, external sharing, and scanner and admin APIs | Connecting data is not enterprise metadata scanning; plan a bridge or a partner tool for sources that are not covered. |
| Classification and sensitive data | Purview sensitivity labels and DLP on supported items | Keep Purview here; check item types, label inheritance, export behaviour and licensing. |
| APIs and integrations | The Catalog Search REST API, and Fabric metadata and scanner APIs | Check fields, identities and scale; do not assume existing Purview API integrations will work. |
The table paraphrases Microsoft’s transition guide of 13 November 2026, updated on 16 November. Fabric changes often, so check the Fabric roadmap before you design around a gap.
What it means for UAE organizations
- Where your data sits: Microsoft lists UAE North as a region with all Fabric workloads, while UAE Central is a Power BI-only region. If your data must stay in the UAE, check your tenant’s home region and the region of each Fabric capacity before you move governance into Fabric.
- Contracts and regulated sectors: Microsoft asks customers with contractual obligations or in highly regulated industries to engage their Microsoft account team early, and says it will assess those cases one by one. Government entities, banks, insurers and healthcare providers should raise it before their 2027 budgets and contracts are fixed.
- Arabic and English glossaries: Fabric maps Purview glossary terms only to tags, descriptions and endorsement. If your glossary holds terms in both languages, export both, with owners and approval status, and decide where approved definitions will live before you switch anything off.
- Evidence for auditors: Microsoft advises correlating evidence across identity, data, action and retention, because no single report proves compliance. Keep records of access requests, approvals and revocations through the move, especially where Fabric does not cover them end to end.
- Data outside Fabric: if you also run SAP, Oracle, on-premises databases or Databricks, plan how those sources stay in your catalog. Microsoft’s guide says connecting data to Fabric is not the same as scanning its metadata, and suggests a bridge or a partner tool for sources Fabric does not cover.
- Cost: governance itself is included in Fabric capacity, so the cost questions are the size and region of your Fabric capacity, the licensing of the Purview security features you keep, and any partner catalog you add.
Where to move: the OneLake catalog, Unity Catalog or a cross-platform catalog
There is no single right answer: it depends on where your data lives and how much you rely on a glossary and data products. In every case, Purview stays for sensitivity labels, DLP and audit.
| If most of your data is… | Govern it in | What to plan for |
|---|---|---|
| In Microsoft Fabric and Power BI | The OneLake catalog | Microsoft’s own path, included in Fabric capacity. Decide where the glossary, data product definitions and data quality rules will live. |
| In Azure Databricks | Unity Catalog, with data shared into Fabric through shortcuts or mirroring | Unity Catalog gives access control, auditing, lineage and discovery across Databricks workspaces. Agree which catalog is the authority for each piece of metadata. |
| Spread across many platforms, or you depend on a large glossary and data products | A cross-platform catalog alongside the OneLake catalog | Microsoft names Atlan, Alation, Collibra and Informatica among the third-party tools the OneLake catalog works with. Budget for the extra licence and the connectors. |
A step-by-step plan to move before 12 November 2027
The method comes from Microsoft’s transition guide; the timing is our suggestion, and leaves room for audits, contract changes and surprises.
Take stock now
List what you built in Purview: registered sources, scans and integration runtimes, collections and domains, owners, glossary terms and critical data elements, custom attributes, data products, lineage, quality rules, workflows, access policies, API integrations, reports, licences and retention needs. Export the glossary and owners early.
Sort every item
Put each requirement on one of Microsoft’s four routes: move now, run side by side for a while, bridge with a process or a partner tool, or redesign.
Design the target
Domains and subdomains, workspaces and capacities and their regions, domain admins, owners and certifiers, the tag taxonomy, OneLake security roles, Fabric policies (in preview), and what stays in Purview for security and compliance.
Pilot one domain end to end
Take one business domain with a producer, a consumer and an analytics or AI use case. Check discovery, context, lineage, access, labels, DLP and audit evidence, and test an identity that should be refused: proving that access is blocked matters as much as proving that it works.
Move the rest in waves
Move metadata and owners domain by domain, train users, and run old and new processes side by side only as long as needed. Retire each Purview dependency only after documented acceptance criteria pass.
Finish with time to spare
Plan to complete the last wave well before 12 November 2027, when support ends.
A schedule that leaves room for audits: inventory and target design in the first quarter of 2027, the pilot domain in the second, the remaining waves in the third, and the last weeks before 12 November 2027 kept free. Microsoft’s guide does not set acceptance criteria, so agree them with your data owners before the pilot.
Where Birbal AI fits
Birbal AI is an Emirati national company that sets up and moves data governance for UAE organizations. For a move off Purview, we take stock of what you built, decide with you where each piece goes (the OneLake catalog, Unity Catalog or a cross-platform catalog such as Collibra), move one domain end to end as a pilot and then the rest in waves, keeping Purview for sensitivity labels, DLP and audit. Glossaries can stay in Arabic and English. Start with a free 60-minute session with a senior consultant; you get a fixed-price proposal after that. See data governance consulting.
Questions and answers
Is Microsoft Purview being retired?
No, only its data governance part. Microsoft is retiring Purview Data Governance, including the Unified Catalog, Data Map, Workflows and the Azure Purview solutions, with support ending on 12 November 2027. Purview’s data security and compliance features, such as sensitivity labels, data loss prevention, audit and insider risk management, are unchanged.
When does support for Purview data governance end?
On 12 November 2027. Microsoft announced the retirement on 12 November 2026. New accounts can no longer be created, and existing capabilities stay in maintenance mode until support ends.
What replaces Purview Unified Catalog?
Microsoft names the OneLake catalog in Microsoft Fabric as its data governance solution. Microsoft says it can also govern data in Azure and third-party sources through shortcuts, mirroring and supported connectors, and that it works with third-party tools such as Atlan, Alation, Collibra and Informatica.
Is Azure Purview part of the retirement?
Yes. Azure Purview was the earlier name of Purview’s data governance service, which Microsoft Learn now calls classic Purview data governance. Both it and the newer Unified Catalog are retiring.
What is the OneLake catalog?
The central place in Microsoft Fabric to discover data, see its governance status and manage security, with three tabs: Explore, Govern and Secure. Microsoft now names it as its data governance solution.
Does the OneLake catalog have a business glossary?
Not one that matches Purview’s. Microsoft’s transition guide maps the glossary and critical data elements to tags, descriptions and endorsement, says not to claim full parity, and advises exporting and keeping your terms and their owners.
What happens to our Purview data products?
Microsoft’s guide maps them to Fabric domains, endorsement, sharing and discoverable semantic models, and advises defining each product’s contract, owner, health, lifecycle and access process outside the catalog where needed.
Do we still need Purview after moving to the OneLake catalog?
Yes, if you use its security and compliance features. In Microsoft’s guide, Purview is the layer that protects, audits and monitors data, including sensitivity labels and DLP on supported Fabric items.
Does governance in Fabric cost extra?
Microsoft says governance is included in Fabric capacity rather than billed through separate meters. You still pay for the capacity itself, and should check the licensing of the Purview security features you keep.
Can Fabric keep our data in the UAE?
Microsoft lists UAE North as a region with all Fabric workloads, and UAE Central as a Power BI-only region. Check your tenant’s home region and each capacity’s region before you move.
Can we move to Unity Catalog or Collibra instead?
Yes. Unity Catalog suits data that lives mainly in Databricks, and a cross-platform catalog such as Collibra suits data spread across many platforms; Microsoft names Collibra among the third-party tools the OneLake catalog works with. Purview stays for security and compliance either way.
How long does a move off Purview take?
It depends on the number of sources, glossary terms, data products and integrations. Microsoft’s method is to pilot one domain end to end and then move the rest in waves; starting the inventory now leaves time for both before 12 November 2027.
Sources
- Update on the Microsoft Data Governance strategy, November 2026 announcements (Microsoft Partner Center)
- A next step in the evolution of the Microsoft Data Governance strategy (Microsoft Security blog, 12 November 2026)
- Microsoft Purview data governance solutions, with the retirement notice (Microsoft Learn)
- From Purview Data Governance to the Fabric OneLake catalog (Microsoft Tech Community, 13 November 2026)
- OneLake catalog overview (Microsoft Learn)
- Govern Fabric data in the OneLake catalog (Microsoft Learn)
- Fabric region availability (Microsoft Learn)
- What is Unity Catalog? (Databricks documentation)
Birbal AI is an independent company based in Abu Dhabi. Facts about third parties come from the sources above; check them for the latest position.