ADO Daily Standup Summary Email

Overview

ADO Daily Standup Summary Email is a scheduled Power Automate Cloud Flow that runs every weekday morning before standup. It queries Azure DevOps for work items completed yesterday, in progress today, and any blocked items across the project. The flow compiles a formatted HTML email with per-section breakdowns and sends it to the team, making standups faster and more focused.

Use Case

Development teams running daily standups often spend the first few minutes asking each person what they completed, what they're working on, and what's blocking them. This flow automates that pre-standup data collection by querying Azure DevOps directly and delivering a formatted summary to the team's inbox before the meeting starts.

Target Audience: Project Managers, Developers, Scrum Masters

The flow is ideal for teams that:

• Project Managers
• Developers
• Scrum Masters

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 and authorize

Import the solution into your target environment, then open the flow in the designer to authorize the Azure DevOps and Office 365 Outlook connections.

Set environment variable values

In the solution's environment variables, set flowlibs_AdoOrganization to your ADO org name, flowlibs_AdoProject to your ADO project name, flowlibs_StandupRecipientEmail to your team's distribution list or individual email, flowlibs_StandupTeamMemberEmails to comma-separated team member emails, and customize flowlibs_StandupEmailSubject if desired.

Adjust the schedule

Edit the Recurrence trigger to match your standup time and timezone, then turn the flow on.

Add per-person sections

Split varTeamMemberEmails and filter WIQL results by AssignedTo to produce per-person breakdowns in the email.

Cross-post to Teams

Add a Teams posting action to also send the summary to a Teams channel alongside the email.

Include richer work item fields

Include story points or remaining work fields in the work item detail fetch to surface more context in the digest.

Sprint scope filtering

Add sprint scope filtering using @currentIteration in the WIQL queries to limit results to the active sprint.

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.

SELECT [System.Id] FROM workitems 
WHERE [System.TeamProject] = @project 
AND [System.ChangedDate] >= @today - 1 
ORDER BY [System.AssignedTo] ASC

@{concat(variables('varAdoProject'), '/_apis/wit/workitems?ids=', join(body('Build_Work_Item_ID_List'), ','), '&fields=System.Id,System.Title,System.AssignedTo,System.WorkItemType,System.State&api-version=7.0')}

@concat('<tr><td>', string(item()?['id']), '</td><td>', item()?['fields']?['System.WorkItemType'], '</td><td>', item()?['fields']?['System.Title'], '</td><td>', item()?['fields']?['System.AssignedTo']?['displayName'], '</td></tr>')