Cloud Portal ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
User Community Service Desk Downloads

Power BI Connection

This article describes how to connect to Power BI for data processing and catalog.

If you’re looking to connect Power BI for lineage, see Power BI Lineage Scanner.

Availability

Data processing & catalog Edge processing Lineage Exceptions

✗

✗

✔

Doesn’t support:

  • Profiling and DQ evaluation

  • Data- or rule-based term detection

  • Anomaly detection

  • Creating SQL catalog items

  • Data transformation plans (read or write)

Prerequisites

Configure Power BI API access

To connect ONE to Power BI, you need to configure a service principal with the required permissions.

Follow the Microsoft documentation to complete these steps:

  1. Register an application in Microsoft Entra ID and create a client secret.

  2. Create a security group and add your application as a member.

  3. Enable Power BI service admin settings – In the Power BI Admin portal, enable the following for your security group:

    • Service principals can use Fabric APIs

    • Allow service principals to create and use profiles

    • Allow service principals to use read-only Power BI admin APIs

  4. Add the service principal to your workspace as a member or admin.

After completing these steps, note the Application (client) ID, Client secret, and Directory (tenant) ID from your app registration. You’ll need these when configuring credentials in ONE.

Add a connection

  1. Go to [your source] > Connections and select Add Connection.

  2. In Connection type, select Power BI.

  3. Fill in the following:

    • Name: A meaningful name for your connection. Used to indicate the location of catalog items.

    • Description (Optional): A short description of the connection.

    • Power BI app URI: The URL of the Power BI portal (for example, https://app.powerbi.com).

    • Power BI integration URI: The URL of the Power BI backend APIs (for example, https://api.powerbi.com).

Add credentials

Only Entra ID authentication is supported.

  1. Select Add Credentials.

  2. Fill in the following:

    • Name: Provide a clear name for this set of credentials.

    • Description (Optional): Explain what the credentials are used for or provide other useful information.

    • Client ID: The Application (client) ID from your app registration in Azure.

    • Client Secret: The client secret value from your app registration.

      Use the secret Value, not the Secret ID.
      Client secrets expire (maximum 24 months). Plan to renew them before expiration to avoid connection failures.

  3. To use this set of credentials by default when connecting to the data source, select Set as default.

One set of credentials must be defined as default for each connection. Otherwise, DQ evaluation fails and previewing data in the catalog (including report previews) is not possible.

Known limitations

Currently, report thumbnails aren’t shown when viewing all reports (Catalog > Report items).

Next steps

Test and save your connection to complete setup.

Was this page useful?