Power BI Dataset Refresh Trigger

Overview

Kicks off a Power BI dataset refresh the moment a new row lands in a SharePoint list (the "data inbox" pattern), polls the Power BI Service for completion, then reports the outcome to Teams and (on failure) to an admin email. The flow ships as a Dataverse-aware solution and is built through an API-first pipeline — no designer authoring required.

Power BI is intentionally not wired in as a Power Platform connector here. The native Power BI connector requires an interactive user license at design time and frequently fails solution import when the target tenant lacks the right license SKU. This flow uses an HTTP action with ActiveDirectoryOAuth against the Power BI REST API instead — all it needs is an Entra app registration with Tenant.Read.All and workspace contributor rights on the target workspace.

The flow ships in the Stopped state. Consumers wire up the 12 flowlibs_-prefixed environment variables (workspace, dataset, SharePoint site/list, Teams group/channel, admin email, tenant/client/secret, polling budgets), authorize the SharePoint / Teams / Office 365 connection references, grant the Entra app Power BI workspace contributor rights, then turn the flow on.

Use Case

Use this flow whenever a Power BI dataset needs to refresh in response to upstream data landing — not on a fixed schedule. A SharePoint list acts as the "data inbox": any system that drops a new row triggers a refresh within minutes, the flow polls the Power BI Service until the refresh reports Completed or Failed, and the outcome is broadcast to a Teams channel (with an admin email escalation on failure). Because the Power BI call is HTTP + service principal, the same pattern works in tenants where the Power BI Power Automate connector is unlicensed or blocked.

The flow is ideal for teams that:

• Data engineering and BI teams who need dashboards to reflect upstream data without waiting for a scheduled refresh window
• Operations teams whose downstream reports must be current the moment new source data lands
• Tenants where the native Power BI Power Automate connector is unlicensed, blocked, or unreliable and a service-principal HTTP pattern is preferred
• Admins who want Teams + email visibility into every refresh outcome (success or failure) without opening the Power BI Service UI

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.

Switch from SharePoint trigger to a recurrence

If you want refreshes on a fixed cadence instead of on data arrival, swap the SharePoint GetOnNewItems trigger for a Recurrence trigger and remove the varTriggeringItemTitle coalesce in the Teams/email message bodies.

Tune the polling budget

flowlibs_RefreshPollMaxAttempts x flowlibs_RefreshPollDelaySeconds is the worst-case wait time before the flow gives up. Defaults are 10 x 30 s = 5 minutes. Increase for large datasets; decrease to fail fast on small ones.

Mark HTTP actions as Secure Inputs/Outputs

ActiveDirectoryOAuth blocks are not redacted by default, so workspace and dataset GUIDs (and the bearer token in transit) appear in run history. If your tenant treats those as sensitive, enable Secure Inputs and Secure Outputs on both HTTP actions.

Replace HTTP + service principal with the native Power BI connector

If your tenant has the right Power BI license SKU and you prefer a user-delegated connection, replace the two HTTP actions with the Power BI connector's Refresh a dataset and Get refresh history actions. You can then drop the four flowlibs_Graph* env vars.

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.

@{concat('https://api.powerbi.com/v1.0/myorg/groups/', variables('varPowerBIWorkspaceId'), '/datasets/', variables('varPowerBIDatasetId'), '/refreshes')}

@{concat('https://api.powerbi.com/v1.0/myorg/groups/', variables('varPowerBIWorkspaceId'), '/datasets/', variables('varPowerBIDatasetId'), '/refreshes?$top=1')}

@or(or(equals(variables('varRefreshStatus'), 'Completed'), equals(variables('varRefreshStatus'), 'Failed')), greaterOrEquals(variables('varPollAttempt'), variables('varMaxPollAttempts')))

@{coalesce(first(body('Parse_Refresh_History')?['value'])?['status'], 'Unknown')}