Azure DevOps Release Completed to SharePoint Changelog

Overview

When an Azure DevOps build pipeline finishes (succeeded or partially succeeded), this flow appends a structured changelog entry to a SharePoint list and emails a roll-up summary to the release notification distribution list. It runs on a recurrence trigger that polls the ADO REST API for builds completed in a configurable look-back window, then for each completed build it fetches the associated work items and writes one row per release into the SharePoint changelog list.

Because every external identifier — ADO organization, ADO project, SharePoint site, list name, recipient email, polling window, status filter — is resolved through Dataverse environment variables, the same exported solution can be deployed to a new tenant by only updating the env var values and authorizing the three connection references.

Use Case

Audience: Developers and Project Managers who own release communications.

Typical scenario: An engineering team ships nightly or per-PR builds to production. Stakeholders want a single, queryable changelog of what shipped, when, with which work items, without anyone having to manually copy build numbers and PBI links into a wiki page after every deployment. This flow keeps that changelog fresh automatically and emails a digest the moment any new build crosses the finish line.

The flow is ideal for teams that:

• Developers who own release communications
• Project Managers tracking what shipped in each build
• Engineering teams running nightly or per-PR builds to production
• Stakeholders who want a single queryable changelog of releases

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 unmanaged solution

Import the unmanaged solution into the target environment (or repoint the deployment) so the env vars, connection references, and flow land together.

Set environment variable values

Set values for flowlibs_AdoOrganization, flowlibs_AdoProject, and flowlibs_NotificationEmail. Override the defaults on flowlibs_SharePointSiteURL and flowlibs_ChangelogListName if your changelog lives elsewhere.

Authorize the three connection references

Authorize Azure DevOps, SharePoint Online, and Office 365 Outlook. The Azure DevOps reference uses the raw-GUID connection name format — when the designer first opens the flow it will show 'Invalid connection, please update your connection' on every ADO action; click each one and rebind to your authorized ADO connection.

Create the SharePoint changelog list

Create a list named 'FlowLibs - Release Changelog' (or your override) on the configured site, with columns: Title (Text), ReleaseName (Text), ReleaseDate (DateTime), Environment (Choice: Development, Staging, Production, UAT), PipelineName (Text), WorkItems (Multi-line text), ReleaseNotes (Multi-line text), ReleaseUrl (Hyperlink), Status (Choice: Succeeded, PartiallySucceeded, Failed, Cancelled).

Adjust polling cadence

The trigger is set to every 1 hour. Change recurrence.frequency and recurrence.interval directly in the flow JSON if you need a tighter loop, and keep flowlibs_ReleasePollingMinutes aligned with the recurrence interval so each cycle queries a non-overlapping window.

Switch from build pipelines to classic releases

Edit Get_Recently_Completed_Builds and Get_Build_Work_Items to call vsrm.dev.azure.com/{org}/{project}/_apis/release/... endpoints instead. The ADO connector's HttpRequest action accepts an absolute URL on the parameters/Uri field if you need to override the dev.azure.com/{account} base.

Turn the flow on

Solution ships with the flow Stopped (Off). Turn it on once env vars, connections, and the SharePoint list are all in place.

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.

subtractFromTime(utcNow(), int(variables('varPollingMinutes')), 'Minute')

concat(variables('varAdoProject'), '/_apis/build/builds?statusFilter=completed&resultFilter=', variables('varReleaseStatusFilter'), '&minTime=', encodeUriComponent(variables('varSinceDateTime')), '&queryOrder=finishTimeDescending&api-version=7.0')

concat(variables('varAdoProject'), '/_apis/build/builds/', string(items('For_Each_Completed_Release')?['id']), '/workitems?api-version=7.0')

if(equals(items('For_Each_Completed_Release')?['result'], 'succeeded'), 'Succeeded', if(equals(items('For_Each_Completed_Release')?['result'], 'partiallySucceeded'), 'PartiallySucceeded', if(equals(items('For_Each_Completed_Release')?['result'], 'failed'), 'Failed', 'Cancelled')))

coalesce(items('For_Each_Completed_Release')?['_links']?['web']?['href'], concat('https://dev.azure.com/', variables('varAdoOrganization'), '/', variables('varAdoProject'), '/_build/results?buildId=', string(items('For_Each_Completed_Release')?['id'])))

replace(replace(replace(string(body('Select_Work_Item_Links')), '"},{"html":"', ''), '[{"html":"', ''), '"}]', '')