Power BI Dataset Refresh Failure Alert

Overview

This flow monitors Power BI dataset refreshes across a specified workspace and alerts the BI admin team when failures occur. It polls the Power BI REST API on a recurring schedule, checks each refreshable dataset's latest refresh status, logs failures to a Dataverse tracking table, and posts a formatted alert to a Teams channel with dataset names, error details, and recommended remediation steps.

Trigger: Recurrence — every 6 hours.

Use Case

Power BI dataset refresh failures often go unnoticed until stakeholders report stale dashboards. This flow provides proactive monitoring by scanning datasets, filtering to refreshable ones, checking their latest refresh status, logging failures to Dataverse for historical tracking, and posting a formatted Teams alert with failure count, dataset details, error messages, and remediation guidance.

The flow is ideal for teams that:

• Scanning all datasets in a workspace every 6 hours
• Filtering to only refreshable datasets (skipping live/DirectQuery)
• Checking the most recent refresh status for each dataset
• Logging every failure to Dataverse for historical tracking and Power BI dashboards
• Posting a formatted Teams alert with failure count, dataset details, error messages, and remediation guidance

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Set the Power BI Workspace ID

Update flowlibs_PowerBIWorkspaceId with the GUID of the workspace you want to monitor. You can find this in the Power BI workspace URL.

Register an Azure AD app for Power BI access

Create an app registration with the Dataset.Read.All application permission on the Power BI Service API. Set flowlibs_GraphClientId, flowlibs_GraphClientSecret, and flowlibs_GraphTenantId with the app's credentials and your tenant ID.

Configure the Teams alert channel

Set flowlibs_TeamsGroupId and flowlibs_TeamsChannelId to point at your BI admin alert channel so failure notifications land in the right place.

Adjust scan frequency

Modify the Recurrence trigger interval (default: every 6 hours) to match how aggressively you want to detect refresh failures.

Authorize connections and turn the flow on

Open the flow in the designer, authorize the Dataverse and Teams connections, then switch the flow state from Off to On.

Provision the Dataverse logging table

Create a flowlibs_pbirefreshfailure table (entity set flowlibs_pbirefreshfailures) with columns: flowlibs_name (PK string), flowlibs_datasetid, flowlibs_datasetname, flowlibs_errordetails (string 4000), flowlibs_workspaceid, flowlibs_refreshstatus, and flowlibs_refreshdate (datetime).

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

ActiveDirectoryOAuth (audience: https://analysis.windows.net/powerbi/api)

@items('For_Each_Dataset')?['isRefreshable']

length(body('Parse_Refresh_Result')?['value']) > 0 AND first(body('Parse_Refresh_Result')?['value'])?['status'] == 'Failed'

@coalesce(first(body('Parse_Refresh_Result')?['value'])?['serviceExceptionJson'], 'No error details available')

@concat(items('For_Each_Dataset')?['name'], ' - ', utcNow('yyyy-MM-dd HH:mm'))