Microsoft will retire Purview Data Governance, with support ending November 12, 2027, and has made Fabric its data governance solution. Microsoft Purview is the Microsoft platform that classifies, protects and, until now, cataloged data, and it now stays focused on security and compliance. Fabric admins and governance leads who plan around its catalog have a year to move before support ends and an ungoverned gap opens. So the answer to “how does Purview govern Fabric and Power BI” has two halves. Until now, Purview protected them with sensitivity labels, data loss prevention (DLP) policies, the audit log, insider risk indicators, and controls for Copilot, and cataloged them through Data Map scans. Going forward, the OneLake catalog is where Fabric and Power BI governance lives. The retirement guide has the full timeline, and the migration plan covers moving catalog content.
| Field | Value |
|---|---|
| Category | Purview and Fabric governance split |
| Retirement | Purview Data Governance support ends Nov 12, 2027 |
| Stays in Purview | Sensitivity labels and DLP, per Microsoft’s Nov 12, 2026 announcement |
| Governance home going forward | OneLake catalog in Fabric |
What did Purview add to Fabric’s built-in governance, and what changes?
Fabric already ships its own governance. The OneLake catalog covers discovery, governance insights, recommended actions, domains, endorsement, and lineage, all inside Fabric.
Microsoft’s own guidance is that Purview comes in when “security, risk, and compliance needs extend beyond Fabric,” and that using it “doesn’t change where Fabric governance lives.” The November 12 announcement makes that split permanent: governance in Fabric, security and compliance in Purview.
How do Fabric and Purview split the work?
So the two split the work. Fabric admins, domain admins, and data stewards work in the Govern section of the OneLake catalog. Purview policies, such as protection policies, are generally configured by the security and compliance team.
What does Purview contribute to Fabric and Power BI today?
Here is what Purview contributes to Fabric and Power BI today, per Microsoft’s documentation, and where each piece stands after the announcement:
| Purview capability | What it does for Fabric and Power BI | After Nov 12, 2026 | Source |
|---|---|---|---|
| Information Protection | Sensitivity labels on all Fabric items; labels and their protection travel through supported export paths | Stays. Microsoft names “classifying, labeling and protecting sensitive data” | Information protection in Fabric |
| Data Loss Prevention | Policies inspect semantic models, lakehouses, warehouses, and databases, then add tips, alerts, or access restrictions | Stays. Microsoft names “preventing data loss” | DLP for Fabric and Power BI |
| Audit | All Fabric user activities are logged in the Purview audit log | Microsoft Learn’s Purview overview lists Audit as a compliance solution; the announcement does not name it. Confirm with your Microsoft account team | Purview with Fabric |
| Insider Risk Management | Ready-made risk indicators for Power BI and lakehouse activity | Microsoft Learn lists it as a data security solution; the announcement does not name it. Confirm with your account team | Purview with Fabric |
| Copilot and agent controls | Audit, eDiscovery, and retention for Copilot prompts and responses | Not named in the announcement. Microsoft Learn says managing these interactions requires the enterprise version of Purview data governance to support the required APIs, so confirm the dependency | Purview for Copilot in Fabric |
| Data Map | Scans Fabric and Power BI items for metadata and lineage | Retiring with Purview Data Governance; support ends Nov 12, 2027 | Connect to a Fabric tenant |
Which part is retiring?
The Data Map row has a date: Microsoft Learn says Unified Catalog and classic Purview data governance capabilities are being retired, existing capabilities stay in maintenance mode through November 12, 2027, and new accounts can no longer be created. Give the Data Map row a plan first, and ask your Microsoft account team about the others.
What does the OneLake catalog do for Fabric and Power BI going forward?
The OneLake catalog is, per Microsoft Learn, the central experience in Fabric for discovering data, understanding governance status, and managing security. It has three tabs: Explore to find items, Govern for governance insights and recommended actions, and Secure for workspace and OneLake security roles.
Domains, endorsement, and lineage sit alongside them.
Microsoft’s announcement widens the claim: the OneLake catalog is “the single foundation for governing data across your entire estate,” and it can govern data across Fabric, Azure, and third-party sources without copying or moving it. Governance is included in Fabric capacity rather than billed through separate meters. Administrators can also use OneLake catalog governance experiences to see where DLP policies apply.
Microsoft says some organizations have needs beyond Fabric today, and that Fabric integrates with third-party providers such as Atlan, Alation, Collibra, and Informatica. See Fabric governance evaluation questions.
For how Fabric and Power BI differ as products, see this comparison. For governance work, start in the OneLake catalog and add a third-party catalog only where a need reaches past Fabric.
How do Purview sensitivity labels protect Fabric and Power BI items?
Labels come from Purview Information Protection. A user needs an Information Protection license, plus Power BI Pro or Premium Per User, to label Power BI items.
Support differs by item type, and the gaps matter when you plan coverage:
- Manual and programmatic labeling work on all Fabric items.
- Mandatory labeling is fully supported for Power BI items.
- Inheritance from a labeled data source works for Power BI semantic models.
- Downstream inheritance runs Fabric to Fabric, Fabric to Power BI, and Power BI to Power BI.
A label stays on the content when it leaves through a supported export path: Excel, PDF, PowerPoint, Analyze in Excel, and a .pbix download.
Protection policies turn a label into access control. Each policy is tied to one label. Users and groups named in the policy keep the permissions they already hold, and everyone else is blocked. The documented details are specific:
- Up to 50 protection policies, each with up to 100 users and groups.
- Up to 24 hours before a new policy starts protecting labeled items.
- Covered item types are native Fabric items and Power BI semantic models.
Protection policies need a Microsoft 365 E3 or E5 license and a label scoped to “Files & other data assets” with “Control access” turned on. Check item-type support before you promise label coverage to your security team.
How do Purview DLP policies work on Fabric and Power BI data?
A DLP policy is defined in the Purview portal. Its conditions are sensitivity labels and a subset of sensitive info types, and its actions fire when an item matches.
Evaluation timing depends on the item. A Power BI semantic model is evaluated on publish, republish, on-demand refresh, and scheduled refresh. Evaluation is skipped when a service principal starts the event or owns the model. A Fabric item, such as a lakehouse or SQL database, is evaluated when its data changes.
Supported item types today are semantic models, lakehouses, warehouses, KQL databases, mirrored databases, SQL databases, and Cosmos databases. When a policy matches, it can:
- Attach a policy tip to the item.
- Raise an alert on the Purview Alerts page.
- Email administrators and named users.
- Restrict access to data owners or members of the organization. The doc marks this action as preview.
The documented scope decides how much of your data estate DLP reaches:
- Only workspaces on Fabric or Premium capacity are in scope.
- Import-mode semantic models are evaluated. Microsoft Learn lists sample models, streaming datasets, and DirectQuery, live-connection or mixed-storage models under considerations.
- Tables stored in Delta format are scanned.
- Conditions are sensitivity labels and a subset of sensitive info types, and each Fabric policy starts as a custom policy.
DLP evaluation also consumes capacity, billed under Purview billing models. Size that cost before turning on broad policies.
How does Purview audit Fabric activity and govern Copilot?
All Fabric user activities land in the Purview audit log. Searching it needs the Audit Logs role in Exchange Online.
PowerShell gives scripted access.
For Insider Risk Management, Microsoft’s September 2025 announcement listed Power BI indicators for viewing, downloading, exporting, and managing sensitivity labels, which feed data theft and data leak policies.
Copilot coverage is documented separately from data coverage. The first Copilot in Fabric that Purview supports is Copilot for Power BI, across all prompts and text responses. Support for other Copilot experiences and for Fabric data agents is in preview. For these AI interactions, Purview supports:
- Data Security Posture Management and DSPM for AI
- Auditing and data classification
- Insider Risk Management and communication compliance
- eDiscovery, Data Lifecycle Management, and Compliance Manager
Two settings gate all of this: the Fabric tenant setting “Allow Microsoft Purview to secure AI interactions,” which is on by default, and pay-as-you-go Purview billing. Retention of Copilot prompts and responses uses a retention policy on the “Microsoft Copilot Experiences” location. Confirm the Copilot dependency with your Microsoft account team before you plan agent governance around it.
Could Purview catalog and trace lineage across Fabric and Power BI, and what replaces it?
Yes, within documented bounds, until Data Map retires. Purview’s Data Map registers a Fabric tenant and runs full, incremental, or scoped scans.
Scanned items include lakehouses, warehouses, notebooks, pipelines, KQL databases, and Power BI dashboards, reports, semantic models, dataflows, and paginated reports.
- For Fabric items other than Power BI, item-level metadata and lineage are scanned.
- Lakehouse tables and files get sub-item metadata.
For Power BI, Purview captures lineage among artifacts, such as dataflow to dataset to report to dashboard. Lineage from Power BI to external sources is supported for Azure SQL Database, Azure Blob Storage, and Azure Data Lake Storage Gen1 and Gen2. Column-level lineage and transformations are supported when the source is Azure SQL Database.
Once metadata reaches Purview, Purview’s permissions, not Fabric’s, decide who can see it, so scan scope needs the same review as any other access grant. The migration plan covers moving it, Microsoft Fabric governance covers what Fabric ships natively, and Power BI column-level lineage covers tracing into reports. Because Data Map and Unified Catalog retire, decide where that metadata goes before support ends.
How does Atlan work with Fabric and Power BI metadata?
When a Power BI semantic model reads from Snowflake, Databricks, or BigQuery, the lineage a team needs starts outside Microsoft. Atlan connects to more than 100 sources.
Its Fabric connector is generally available and catalogs workspaces, lakehouses, warehouses, semantic models, reports, dashboards, dataflows, and data pipelines down to column level, with end-to-end lineage. Atlan’s Power BI connector catalogs workspaces, datasets, tables, columns, measures with their expressions, reports, pages, and dashboards, and its lineage extraction parses each table’s Power Query M expression to trace lineage from upstream sources including Snowflake, Databricks, Google BigQuery, Microsoft SQL Server, and Azure Synapse.
On the Fabric side, Atlan traces column-level lineage from lakehouse and warehouse columns to semantic model columns and measures,. Atlan’s Context Lakehouse stores context as open Apache Iceberg tables in OneLake that Fabric can query directly, and that context reaches people in Microsoft Teams and agents in Copilot Studio. Microsoft names Atlan among the third-party providers Fabric integrates with, and Atlan is available in Microsoft Marketplace. Atlan’s Migration Studio, in private preview, reads Purview Data Governance with read-only access and produces a reconciliation report; the migration plan explains the steps, and Microsoft Purview and Atlan covers how the two fit together.
FAQs about Purview for Fabric and Power BI governance
Short answers to the questions readers ask most about Purview, Fabric, and Power BI.
1. What happens to Purview’s governance of Fabric when Purview Data Governance retires?
Microsoft’s November 12, 2026 announcement says Fabric is now its data governance solution and Purview Data Governance will be retired, with support ending November 12, 2027. Governance for Fabric and Power BI moves to the OneLake catalog. Purview stays focused on security and compliance, and Microsoft names sensitivity labels and Data Loss Prevention among what stays.
2. Do I need Purview to govern Microsoft Fabric?
Not for governance. Fabric’s OneLake catalog handles discovery, domains, endorsement, lineage, and governance insights on its own, and it is where Microsoft is consolidating governance. Microsoft positions Purview for security and compliance needs that extend beyond Fabric: classifying and protecting sensitive data, preventing risky sharing, and meeting broader compliance and risk requirements. Using Purview leaves the OneLake catalog as the primary place to govern Fabric data.
3. Which licenses do Purview controls for Fabric and Power BI need?
Sensitivity labels need a Purview Information Protection license, and labeling Power BI items also needs Power BI Pro or Premium Per User. Protection policies need Microsoft 365 E3 or E5. Copilot governance needs pay-as-you-go Purview billing, and DLP evaluation consumes metered capacity. Confirm current terms against Microsoft’s licensing guidance before you plan a rollout.
4. Do Purview DLP policies work on DirectQuery semantic models?
Microsoft’s DLP documentation covers import-mode semantic models, which are evaluated on publish, republish, and each refresh, unless a service principal starts the event or owns the model. For Fabric, DLP scans tables stored in Delta format. Microsoft Learn lists DirectQuery, live-connection and mixed-storage models under considerations.
5. Does Purview capture column-level lineage for Power BI?
Partly, and only through Data Map, which is part of the retiring Purview Data Governance. Purview captures column-level lineage and transformations inside Power BI datasets when the source is Azure SQL Database. Lineage to external sources at the asset level covers Azure SQL Database, Azure Blob Storage, and Azure Data Lake Storage Gen1 and Gen2. Going forward, lineage lives in the OneLake catalog or a third-party catalog.
6. Do sensitivity labels apply to Copilot for Power BI conversations?
Microsoft’s Purview table for Copilot in Fabric lists auditing, data classification, insider risk, communication compliance, eDiscovery, and retention as supported for AI interactions. Copilot for Power BI is covered for all prompts and text responses, while other Fabric Copilots and data agents are in preview.
Sources
- A next step in the evolution of the Microsoft data governance strategy, Microsoft Security Blog, November 12, 2026
- Learn about data governance with Microsoft Purview (retirement notice), Microsoft Learn
- OneLake catalog overview, Microsoft Learn
- Learn about Microsoft Purview, Microsoft Learn
- Use Microsoft Purview with Microsoft Fabric, Microsoft Learn
- Connect to your Microsoft Fabric tenant in same tenant as Microsoft Purview, Microsoft Learn
- Protection policies in Microsoft Fabric, Microsoft Learn
- Information protection in Fabric, Microsoft Learn
- Get started with DLP for Fabric and Power BI, Microsoft Learn
- Use Microsoft Purview to manage data security and compliance for Copilot in Fabric, Microsoft Learn
- Learn about Microsoft Purview billing models, Microsoft Learn
- Track user activities in Microsoft Fabric, Microsoft Learn
- Unifying Data Security and Governance for the AI Era: Microsoft Purview Innovations for Your Fabric Data, Microsoft Security Blog
- Metadata and lineage from Power BI into Microsoft Purview, Microsoft Learn