Power BI refreshes
TaskBeacon reads each watched semantic model's refresh history: a Failed refresh becomes a Failed run with Power BI's error code, a refresh in progress shows as Running (and Late when it takes much longer than usual), and a completed one is OK with its duration. The model's scheduled refresh times become the job's schedule, so a refresh that never happened shows as Missed.
You need: a Microsoft Entra app registration (a service principal) in your own tenant, a Fabric / Power BI administrator to allow service principals once, and the workspace's admin to add the app to the workspace.
1. Create the app registration
- In the Microsoft Entra admin center go to App registrations → New registration. Name it e.g. TaskBeacon monitor, single tenant, no redirect URI.
- On its Overview, copy the Application (client) ID and the Directory (tenant) ID.
- Under Certificates & secrets → Client secrets → New client secret, copy the secret's Value right away (it is shown only once). Note its expiry date: when it expires, the integration stops and shows an error until you paste a new one.
- Do not add API permissions for Power BI. Microsoft recommends none for a service principal that calls the Power BI REST API; access comes from the workspace role below.
2. Allow service principals (Fabric administrator, once)
Create a Microsoft Entra security group (e.g. Power BI API apps) and add the app to it. Then in the Fabric admin portal's Tenant settings (in 2026 reached through OneLake catalog → Govern → Configurations → Tenant settings), section Developer settings, enable Service principals can call Fabric public APIs for that security group (older pages call it Allow service principals to use Power BI APIs). Enabling it for a specific group, not the whole organization, keeps it narrow.
3. Add the app to each workspace
In Power BI, open the workspace → Manage access (Workspace access) → Add people or groups, find the app by its name and give it the Contributor role. Contributor is the lowest role that works: reading refresh history needs write permission on the semantic model, which Viewer doesn't have. Member or Admin work too but give more than needed. My workspace can't be used with a service principal.
4. Connect in TaskBeacon
Jobs → ▾ → Add integration… → Power BI. Paste the tenant ID, client ID and secret and press Test connection and continue. Then Choose what to watch: every refreshable model in the workspaces the app can see is listed as workspace / model. Ticked models become jobs.
How runs are read
- The last 5 refreshes are read every poll. Status Completed = OK, Failed = Failed with the error code (e.g. ModelRefreshFailed_CredentialsNotSpecified), Unknown = still running.
- The refresh schedule is read once a day. When it has several evenly spaced times a day they all count; when the times are uneven only the first refresh of the day is planned.
- Models in import mode only: DirectQuery and live connection models have no refresh and are not listed. Refreshes of OneDrive-hosted models are not in the history.
Not yet tested on a real installation — tell us how it went (support@taskbeacon.io).
Use cases: Power BI refresh failure notifications for the whole team. More questions: FAQ.