Skip to content
Merulan

Power BI setup

What an operator supplies to connect the Power BI Source, and the verification the provider requires.

Connecting Power BI accepts a named secret bundle the operator fills in. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

Power BI refuses the connection until every item holds.

  • A Power BI tenant, and an administrator who may register a service principal.
  • A workspace role for that service principal on every Power BI workspace a Pipeline reads.

Credentials

Power BI stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • A tenant identifier, a client identifier, and a client secret, supplied together as one service-principal bundle.

Scopes

Power BI carries no scope list in Merulan: the service principal role assignment holds the requested scopes for this Source.

Power BI carries no consent screen here. Reach is the Power BI workspace role the administrator granted, so narrow the role rather than a scope list.

Verification

Workspace-issued credential governs the Power BI connection. Power BI checks the shape of the service principal on save rather than calling the tenant, so an unusable principal surfaces as a binding fault rather than a healthy connection.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.