ADO Release Notes Auto-Generator

Overview

A weekly scheduled cloud flow that queries Azure DevOps for work items completed in the last 7 days using a WIQL query via the ADO connector's HttpRequest action, retrieves full details for each work item, builds a styled HTML release notes document, saves it to a SharePoint document library, and emails the formatted notes to a stakeholder distribution list. Designed as a portable demo: every connector-specific value (site URL, library name, ADO org, project, recipient list) is exposed as a Dataverse environment variable.

Use Case

Engineering and project management teams need a low-touch way to communicate what shipped each week without manually combing through ADO boards. This flow turns the WIQL query into a one-click weekly digest stakeholders can rely on. The same pattern can drop into any ALM pipeline by re-pointing the env vars at a new project, organization, or SharePoint site — no flow edits required.

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.

Configure the five environment variables

Edit the five environment variables in the solution (ADO organization, ADO project, SharePoint site URL, recipient email, release notes library name). No flow edits are required to point the digest at a different project, tenant, or distribution list.

Re-point the three connection references

Replace the Azure DevOps, SharePoint Online, and Office 365 Outlook connection references with connections authorized for your tenant before turning the flow on.

Wire up your version source

Adjust the varReleaseVersion default if you maintain a manual version registry, or replace it with an HTTP call to your release pipeline so the digest header always matches the actual deployed build.

Switch from scheduled to event-driven

Optionally swap the Recurrence trigger for the Azure DevOps "When a build completes" trigger so the release notes go out per deployment instead of on a weekly cadence.

Turn the flow on

The flow ships in Stopped state. Toggle it to On once env vars and connections are configured and you've verified the WIQL query returns the expected work items.

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.

@parameters('flowlibs_AdoOrganization')

@{utcNow('yyyy-MM-dd')}

@{concat(variables('varAdoProject'), '/_apis/wit/wiql?api-version=7.0')}

@{concat(variables('varAdoProject'), '/_apis/wit/workitems/', items('Loop_Through_Work_Items')?['id'], '?$expand=all&api-version=7.0')}

@{concat('ReleaseNotes-v', variables('varReleaseVersion'), '-', variables('varReleaseDate'), '.html')}

SELECT [System.Id], [System.Title], [System.WorkItemType], [System.State], [System.AssignedTo]
FROM WorkItems
WHERE [System.TeamProject] = @project
  AND [System.ChangedDate] >= @today - 7
  AND [System.State] IN ('Closed', 'Resolved', 'Done')
ORDER BY [System.WorkItemType] ASC