Power BI Alert to GitHub Issue

Overview

When a Power BI data alert fires (e.g., test coverage drops below 70% or error rate spikes), this flow automatically creates a labeled GitHub issue in the configured repo, assigns it to the on-call engineer, and posts a handoff message to a Microsoft Teams channel with a link to the issue.

Use Case

Operations and engineering teams monitor Power BI dashboards for critical metrics. When an alert fires, the team needs immediate action — creating an issue, assigning ownership, and notifying the responder. This flow automates all three steps in seconds, reducing mean-time-to-response for dashboard anomalies.

The flow is ideal for teams that:

• Instant GitHub issue creation from Power BI alerts — no manual ticket entry
• Automatic assignment to on-call engineer via email-to-login mapping
• Teams notification keeps responder informed in their primary workflow
• Full alert payload in issue body — responder has complete context
• No GitHub UI needed — responder gets a direct link to the issue

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.

Deploying to another environment

Import the solution, update the six env vars (GitHub owner, repo, alert label, on-call email, Teams group/channel IDs), and bind the two connection references (GitHub, Teams). Save the flow to generate the HTTP Request trigger URL, copy it into the Power BI data alert webhook configuration, turn the flow on, and fire a test alert from Power BI to verify end-to-end.

Dynamic on-call lookup

Replace the email-to-login substring trick with a Dataverse lookup against a rotation table or a PagerDuty API call so the assignee follows the actual on-call schedule instead of a static env var.

Add Slack notification

Insert a Slack PostMessage action after the Teams post for dual-channel coverage when teams use both Teams and Slack.

Custom issue label per alert type

Store an alert type in the Power BI payload and conditionally set the GitHub label based on it (e.g. 'reliability', 'quality', 'performance') so issues triage themselves.

Escalation after 2 hours

Add a separate scheduled flow that queries GitHub for unresolved alert issues older than 2 hours and posts a reminder to Teams so stale alerts don't linger.

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('[Power BI Alert] ', coalesce(triggerBody()?['alertTitle'], 'Unknown'), ' - ', coalesce(triggerBody()?['tileName'], 'N/A'), ' = ', coalesce(triggerBody()?['tileValue'], 'N/A'))

@concat('<a href="', body('Create_GitHub_Issue')?['html_url'], '">View Issue</a>')

@substring(variables('varOnCallEmail'), 0, indexOf(variables('varOnCallEmail'), '@'))