Power BI Cloud - Lineage

This article outlines the lineage coverage, configuration requirements, supported components, transformation support, supported scenarios, known limitations, and current functional status for lineage extraction in Power BI Cloud.

The Power BI Cloud connector provides automated, production-ready lineage extraction across Power BI reports, datasets, and dataflows. It delivers end-to-end visibility into data flow by tracing dependencies from source systems through M Query transformations, DAX-based semantic models, and report visualizations across multiple workspaces within the Power BI cloud environment.

Lineage Configuration Requirements

Successful lineage extraction depends on proper connector configuration, metadata availability, and valid source connections. The following requirements must be satisfied to ensure accurate source-to-target lineage generation.

Configuration Requirements Table

Configuration	Required Detail
SQL Dialects	SQL dialects must be defined in CrawlerOption.supportingDialects.
Connection Priority	Connection priority for lineage must be configured using CrawlerOption.connectionsPriorityForLineage.
ElastiCube Connection	ElastiCube connection details must be available for schema resolution.
API Access	API tokens or credentials must provide access to extract metadata for dashboards, reports, datasets, and data models.

Missing metadata, unavailable source connections, insufficient API permissions, or invalid credentials may result in incomplete lineage generation.

Lineage Components

Component / Feature	Supported
Reports	✅
Dashboards	⚠️
Datasets (Semantic Models)	✅
Dataflows	✅
Workspaces	✅
Paginated Reports	✅
Measures (DAX)	✅
Calculated Columns	✅
Calculated Tables	✅
Pages	✅
Visuals	✅
Relationships	✅
Parameters	⚠️
Apps	⚠️
Filters	⚠️
Hierarchies	⚠️

The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.

Column Creation Support

This section outlines lineage support for column creation and transformation scenarios.

Column Creation from Lineage

Transformation Type	Supported
Expressions (M Query)	⚠️
Aggregations (DAX)	⚠️
Calculated Fields	⚠️
Renamed Columns	✅
Temporary Columns	✅
Semantic Columns	✅

The ⚠️ icon indicates partially supported functionality where lineage coverage depends on transformation complexity and metadata availability.

Supported Use Cases

The connector supports lineage extraction across standard Power BI Cloud reporting, semantic modeling, and data transformation workloads.

Supported Lineage Scenarios

Supported Scenario	Details
Report → Dataset Lineage	Lineage between report visuals and associated datasets
Dataset → Dataflow → Source Lineage	End-to-end lineage from datasets through dataflows to source systems
Cross-workspace Lineage	Lineage across shared datasets and reports
Import and DirectQuery Models	Lineage for Import and DirectQuery semantic models
M Query (Power Query) Transformations	Lineage for Power Query transformation logic
DAX-based Measures and Calculated Columns	Lineage for DAX measures and calculated columns
Paginated Report (.rdl) Lineage	Lineage extraction for paginated reports
Column-level Lineage	Lineage across tables and report visuals
Composite Model Lineage	Lineage for models combining Import and DirectQuery
Cross-cloud Source Lineage	Lineage across Azure SQL, Snowflake, Databricks, BigQuery, and other supported cloud sources

Lineage extraction is based on metadata available through Power BI Cloud APIs, M Query definitions, DAX expressions, and configured source connections.

Partial or Limited Coverage

Certain scenarios provide partial lineage coverage due to metadata dependencies, runtime behavior, or expression complexity.

Scenarios

Scenario	Limitation Description	Recommendation
Dynamic or Parameterized M Queries	Runtime parameters are not fully resolved during lineage extraction.	Use static M Query definitions where possible.
Nested or Complex DAX Expressions	Dependency parsing may be incomplete for complex expressions.	Simplify DAX logic or validate lineage manually.
Row-Level Security (RLS) Filters	Limited lineage extraction for RLS definitions.	Validate security dependencies separately where required.
Dashboard Tiles	Visual-to-dataset mapping may be incomplete.	Verify dashboard lineage manually where required.
Embedded Analytics and Custom Visuals	Metadata capture is limited for embedded content and custom visuals.	Use standard visuals where possible.
Unrefreshed Datasets	Schema extraction may be incomplete if datasets are not refreshed.	Refresh datasets before lineage extraction.
Cross-workspace Lineage	Lineage may be incomplete when linked workspaces are inaccessible.	Ensure access permissions are available for all referenced workspaces.
Custom Connectors	Limited or no parsing support for metadata exposed through custom connectors.	Use supported connectors or document lineage manually.

Complex DAX expressions, runtime parameters, restricted workspace access, and incomplete metadata may reduce lineage completeness and column-level accuracy.

Unsupported Scenarios

The connector does not support lineage extraction for certain runtime-generated, restricted, or unsupported Power BI Cloud scenarios.

Unsupported Lineage

Not Supported	Description	Recommendation
Cross-tenant Datasets and Dataflows	Lineage cannot be generated across different Power BI tenants.	Document dependencies manually where required.
Dynamic Columns Created by Custom M Functions	Runtime-generated columns are not resolved during lineage extraction.	Use static transformation logic where possible.
Advanced DAX with Circular or Recursive Dependencies	Circular or recursive DAX relationships are not parsed.	Simplify DAX logic where applicable.
Unsupported Custom Connectors	Metadata cannot be extracted from unsupported connectors.	Use supported connectors or document lineage manually.
Unpublished or Embedded (Non-API) Reports	Reports that are unavailable through supported APIs are not analyzed.	Publish reports before lineage extraction.
RLS Evaluation in DirectQuery Mode	Runtime Row-Level Security evaluation is not supported.	Validate security behavior separately where required.
Linked Semantic Models Without Access Permissions	Restricted semantic models cannot be analyzed.	Ensure appropriate access permissions are available.
Data Sources Outside Power BI Cloud	Sources that are not accessible through Power BI Cloud APIs are not included in lineage.	Configure supported source connections where applicable.

Unsupported scenarios do not generate lineage and may appear as disconnected nodes within lineage visualization.

Current Functional Status

This section outlines the current lineage capabilities supported by the Power BI Cloud connector.

Status Area	Details
Overall Coverage	Strong coverage across datasets, dataflows, reports, and semantic models
Lineage Depth	Table-level and column-level lineage through M Query and DAX parsing
Supported Inputs	Reports, dashboards, datasets, dataflows, paginated reports, semantic models, visuals, and relationships
Functional Scope	Lineage extraction across reporting, semantic modeling, and data transformation workflows
Limitation Areas	Complex DAX expressions, runtime parameters, custom connectors, Row-Level Security (RLS), dashboard tiles, and restricted workspace access
Resulting Output	Reliable lineage for standard Power BI Cloud workloads with partial coverage for advanced modeling and transformation scenarios

The Power BI Cloud connector provides strong lineage coverage across reports, datasets, dataflows, semantic models, and visualizations, including column-level lineage through M Query and DAX parsing. Advanced scenarios involving complex DAX expressions, runtime parameters, custom connectors, Row-Level Security (RLS), dashboard tiles, and restricted workspace access have partial or unsupported coverage and may require manual validation.

---

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA