Skip to main content
Open in Introw: Integrations

How it works

Power BI is set up from the Integrations settings, where the Power BI card connects your tenant via an Azure AD service principal and OAuth. Once connected, you manage the integration on its own page, registering the reports and dashboards you want to embed and configuring per-partner dataset roles for row-level security. In the Experience builder, a Power BI embed section surfaces a registered report or dashboard. Embeds are rendered with secure embed tokens, and the configured roles ensure each partner sees only their own data. Power BI is a paid module, so it must be enabled on your plan.

Prerequisites

  • The Power BI module enabled on your plan.
  • A Power BI tenant with an Azure AD service principal.
  • Reports or dashboards in Power BI, with row-level security roles if you need per-partner scoping.

Settings & configuration

Power BI is configured from Integrations.

Connect the tenant

Use the Power BI card to connect via OAuth and the Azure AD service principal.

Manage embeds

On the integration page, register the reports and dashboards you want to embed.

Row-level security

Configure per-partner dataset roles so each partner’s embed is scoped to their own rows.

Test the connection

Use the connection test to confirm credentials work before embedding.

Portal embed

In the Experience builder, add a Power BI embed section and select a registered report or dashboard.

Setup walkthrough

1

Open Integrations

Go to Integrations and open the Power BI card.
2

Connect your tenant

Authenticate via OAuth with your service principal.
3

Register embeds

Add the reports and dashboards to embed.
4

Configure roles

Set per-partner row-level security roles.
5

Surface in the portal

Add a Power BI embed to a portal experience.

How-to guides

Surface Power BI in the portal

Connect your Power BI tenant, register a report, scope it per partner with row-level security, and embed it in the partner portal.

Limits & gotchas

Power BI is a paid module and must be enabled on your plan. Per-partner scoping depends on row-level security roles configured in your Power BI dataset; without them, an embed is not partner-scoped. Embedding requires a valid Azure AD service principal with access to the workspace.

Troubleshooting

  • The Power BI card shows an upgrade prompt - the module is not enabled on your plan.
  • The connection test fails - check the service principal credentials and workspace access.
  • A partner sees all the data - row-level security roles are not configured for the embed.