Azure DevOps Build Failed Escalation Email

Overview

The Azure DevOps Build Failed Escalation Email flow monitors an Azure DevOps build pipeline on an hourly schedule. When failed builds are detected, it sends a richly formatted HTML escalation email to the team lead with build details, a direct link to the build logs, and a retry button — ensuring failed builds never go unnoticed.

Use Case

DevOps teams need immediate visibility when CI/CD pipelines fail. Manual monitoring of build dashboards is unreliable, especially outside business hours. This flow automates the detection-and-escalation loop so that the right people are notified within an hour of any failure, complete with actionable links to investigate and retry.

The flow is ideal for teams that:

• Developers
• DevOps engineers
• IT Admins

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.

Import the solution

Import the solution into your target environment.

Update environment variables

Set flowlibs_AzureDevOpsOrgName to your Azure DevOps org (e.g., "mycompany"); set flowlibs_AzureDevOpsProject to your project name; set flowlibs_AzDoBuildDefinitionId to your pipeline's definition ID (find this in the pipeline URL); set flowlibs_BuildFailureTeamLeadEmail to your team lead's email address.

Update connection references

Authenticate both the Azure DevOps and Office 365 Outlook connections.

Turn on the flow

The flow ships in Stopped state for safety — turn it on after configuration is verified.

Change polling frequency

Edit the Recurrence trigger to run more or less frequently than every hour.

Add more recipients

Modify the Send Email action to include CC/BCC addresses for broader visibility.

Filter by date range

Add a minTime parameter to ListBuilds to only check recent builds and reduce noise.

Add Teams notification

Insert a Post Message to Teams action alongside the email for real-time channel alerts.

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.

items('Apply_to_Each_Failed_Build')?['_links']?['web']?['href']

https://dev.azure.com/@{variables('varOrgName')}/@{variables('varProjectName')}/_build?definitionId=@{variables('varBuildDefId')}&_a=summary

length(body('List_Failed_Builds')?['value'])