Power BI
Connect Power BI to Ploy to see every shared workspace in your Power BI tenant, who holds a role on each one, and to grant, change and remove workspace access from Ploy.
This integration is in beta
The Power BI integration is in beta. It was built from Microsoft's published Power BI REST API documentation and has not yet been run against a live Power BI tenant. It works the same as any other integration, with one extra step.
The first page of the setup asks you to tick a consent checkbox. Ticking it lets Ploy record redacted error details when a call to Power BI fails. Redacted means names, emails, IDs and secrets are removed before anything is stored, so what we keep is the shape of the error, such as the status code and which field Power BI complained about. We use it only to fix the integration faster. You can connect only after ticking it.
What Ploy reads
Every shared workspace in the tenant, including workspaces Ploy's app is not a member of. Personal "My workspace" workspaces are not included.
Everyone who holds a role on each workspace (Admin, Member, Contributor or Viewer): people, including guests, and service principals.
The role each of them holds, shown as the entitlement on the workspace.
Ploy scans every six hours. When someone is removed from a workspace in Power BI, Ploy records their access as ended on the next scan.
Not shown yet: access given to a Microsoft Entra group (connect the Microsoft integration to see who is in each group), and sharing of single reports, dashboards or datasets.
What Ploy can change
On a workspace's page in Ploy you can grant someone access, change their workspace role, or remove them. Ploy can only do this on workspaces where its app is an Admin (see step 6 below). Power BI accounts themselves are Microsoft Entra accounts, so Ploy does not create, disable or delete them in Power BI.
Before you start
You need to be a Microsoft Entra administrator who can register apps, and a Fabric (Power BI) administrator.
In the Microsoft Entra admin center, go to App registrations and create a new registration for Ploy. Note the Application (client) ID and the Directory (tenant) ID on its overview page.
Under Certificates & secrets, create a client secret and copy its value.
Do not add any Power BI API permissions to the app that need admin consent. Power BI rejects admin API calls from an app that has them.
Create a Microsoft Entra security group (for example "Ploy Power BI") and add the app to it.
In the Power BI admin portal, open Tenant settings. Under the developer and admin API settings, allow service principals to use Power BI APIs, and allow service principals to access read-only admin APIs. Apply both settings to the security group from step 4. A change to a tenant setting can take a few minutes to take effect.
Optional, to manage access from Ploy: in each workspace you want Ploy to manage, open Manage access and add the app as an Admin.
Connect Power BI
In Ploy, open Integrations, find Power BI and click Connect.
Tick the beta consent checkbox.
Paste the Directory (tenant) ID, the Application (client) ID and the client secret.
Click Test connection. Ploy reads the first workspace in your tenant to check everything works.
Save. The first scan starts straight away.
Keeping the connection working
Client secrets expire. When you create a new one, update it on the Power BI connection in Ploy before the old one expires.
Troubleshooting
Microsoft rejected that app. Check the tenant ID, client ID and client secret, and that the secret has not expired.
Power BI accepted the app but refused to list workspaces. Check both tenant settings in step 5 are on and apply to a group that contains the app, and that the app has no Power BI permissions that need admin consent. Allow a few minutes after changing a tenant setting.
Power BI refused a change to workspace access. Add Ploy's app as an Admin of that workspace (step 6).
A person is missing from a workspace in Ploy. They may have access through a Microsoft Entra group, which Ploy does not expand on the Power BI connection yet.