Microsoft Power BI (Azure) lineage configuration

Last updated: May 06, 2025

To import lineage metadata from Microsoft Power BI (Azure), create a connection, data source definition and metadata import job.

To import lineage metadata for Microsoft Power BI (Azure), complete these steps:

Creating a data source definition

Create a data source definition. Select Microsoft Power BI (Azure) as the data source type.

Creating a connection to Microsoft Power BI (Azure)

Create a connection to the data source in a project. For connection details, see Microsoft Power BI (Azure) connection.

Creating a metadata import

Create a metadata import. Learn more about options that are specific to Microsoft Power BI (Azure) data source:

Include and exclude lists
External inputs

Include and exclude lists

You can include or exclude assets up to the the report level. Provide workspaces and reports in the format workspace/report. Each part is evaluated as a regular expression. Assets which are added later in the data source will also be included or excluded if they match the conditions specified in the lists. Example values:

myWorkspace/: all reports in myWorkspace,
myWorkspace2/.*: all reports in myWorkspace2,
myWorkspace3/myReport1: myReport1 from myWorkspace3,
myWorkspace4/myReport[1-5]: any report in myWorkspace4 with a name that starts with myReport and ends with a digit between 1 and 5.

External inputs

You can add Microsoft Power BI (Azure) Reports, Dataflows, and PowerQuery script as external inputs. The file can have the following structure:

<workspace_name> - A folder with the workspace name.
  [report_name].pbix - A PowerBI report.
  [dataflow_ID].dataflow - A PowerBI dataflow.
  [report_name].txt - Manually extracted PowerQuery scripts for a specific report.
  [report_name].rdl - A paginated report.
  metadata.json - A file with metadata. If this file is provided, it overrides metadata that is extracted automatically for the specified workspace.