GUIDE, read 13 Nov 2026
Sensitivity labels follow a field downstream inside Power BI, but the inheritance rules and the shift from Purview to Fabric limit how far
Where Euno is behind
Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices.
Labels are the Microsoft estate's way to follow a field, and they start from three sources
Microsoft documents that a Power BI semantic model inherits a sensitivity label from only three source types: Excel on OneDrive or SharePoint, Azure Synapse Analytics and Azure SQL Database. Labels in Azure SQL and Synapse are applied through a two-step Purview flow, and a tenant setting must be on in Power BI. A Snowflake, Databricks or BigQuery column labeled somewhere else does not arrive this way. Microsoft Purview reads documented at the column stage and partial at the BI field in the exposure map. The Microsoft estate view ranks the tools for this stack.
The stage table shows how far Microsoft's own features reach
Each row is one stage of the path from the source column to the person and the agent.
| Stage | What Microsoft's own features do | Where it stops |
|---|---|---|
| Column | Purview Data Map classifies assets in scans with more than 200 built-in classifications | Applying labels to Data Map assets is in preview, with pay-as-you-go billing |
| Transformation | A label on a semantic model flows to dependent models, reports and dashboards, shown in lineage view | Stops entirely above 80 downstream items; never overwrites a manual label or applies a less restrictive one |
| BI field | Column-level Power BI lineage in Purview | Only when Azure SQL Database is the source; none found on 13 Nov 2026: Snowflake column to Power BI field lineage |
| Report | New reports and dashboards inherit the parent label; Power BI applies the label to Excel, PDF and PowerPoint exports | Encryption applies only to supported export paths; the admin must block the rest. Protection policies cover semantic models but not reports or dashboards |
| Viewer | The Power BI activity log records who took which action on which item | Events can arrive up to 60 minutes late, and the API returns one day per request; RLS does not restrict workspace Admin, Member or Contributor roles |
| Agent | AI interaction events reach the unified audit log; Copilot for Power BI is supported, other Fabric Copilots in preview | The Power BI Authoring MCP server can edit security roles and is not for consumption |
Row-level security and labels answer different questions
Microsoft's RLS page says row-level security only restricts data access for users with Viewer permissions and does not apply to workspace Admin, Member or Contributor roles. A label says how a file must be handled once it leaves; RLS decides which rows a Viewer sees. The label overview adds that users granted access to a report reach the entire underlying semantic model unless RLS limits them.
Labeled content inside the service is visible, but the encryption settings are not applied there. They apply to data that leaves through a supported export path. The overview says the admin can block export from unsupported paths. So a sensitive field in a Power BI report is only as protected as the export settings on the tenant. Ask the Power BI admin for the export setting before you rely on any label as a control.
Purview's governance catalog is retiring, so the label source and the governance surface now split
Microsoft's 2026 announcement says Purview Data Governance will be retired, that Microsoft Fabric is now its data governance solution, and that support ends Nov. 12, 2027. Microsoft's Learn banner says new Unified Catalog accounts can no longer be created and existing capabilities stay in maintenance mode through that date. Microsoft also says the Purview brand stays focused on data security and compliance: classifying, labeling, protecting data, DLP and AI. Labels and the activity log therefore remain in Purview, while the catalog side moves.
For a plan that runs past 2027, treat Information Protection labels and the Power BI activity log as the durable parts, and do not build new work on the Unified Catalog. DSPM for AI is a separate piece: Microsoft's what's-new page says the new DSPM is generally available while partner solutions for non-Microsoft sources and the Data Security Posture Agent remain in preview.
Which ranked tools extend it
Euno, a context platform that reads metadata and query logs only, says in its docs that its Purview integration discovers Purview DLP policies and links them to Power BI resources, and that it collects Power BI impressions from the Fabric user activity log with distinct users over 14, 30 and 60 days. It ranks 1 of 16 here, with BI field documented and viewer partial.
Immuta says it ingests tags from Microsoft Purview and requires personal credentials for Power BI after publishing, so its policies follow the viewer (BI field none found). Atlan documents a Power BI miner that reads activity events for usage metrics (partial at the report stage). Securiti says it can import sensitivity labels from a Microsoft security center (viewer partial). Informatica says it pushes policies into Power BI. Alation documents column-level lineage for its Power BI scanner (documented). Select Star and Ataccama document Power BI metadata and lineage, with Ataccama's connection one-way.
Check the inheritance mode, the 80-item limit and the export setting first
Three items decide how far a label travels. Open the downstream inheritance setting: labels from data sources propagate downstream only in fully automated mode, and the default asks the user for consent. Count the downstream items of your most sensitive semantic model against the limit of 80. Then ask for the tenant's export setting. Add a calendar line for 12 Nov 2027 to any plan that depends on the Unified Catalog.
Sources
- Microsoft Learn: label inheritance from data sources, read 13 Nov 2026
- Microsoft Learn: downstream inheritance, read 13 Nov 2026
- Microsoft Learn: sensitivity labels in Power BI, read 13 Nov 2026
- Microsoft Learn: row-level security in Fabric and Power BI, read 13 Nov 2026
- Microsoft Learn: Power BI auditing, read 13 Nov 2026
- Microsoft Learn: protection policies, read 13 Nov 2026
- Microsoft Learn: Purview for AI interactions, read 13 Nov 2026
- Microsoft: next step in data governance strategy, read 13 Nov 2026
- Microsoft Learn: Purview what's new, read 13 Nov 2026
- Euno docs: Microsoft Purview integration, read 13 Nov 2026
Last reviewed 13 Nov 2026.