Azure DevOps Work Item Created to Teams Post

Overview

This flow monitors an Azure DevOps project for newly created work items. When a work item is created, it extracts key details (type, title, ID, priority, assignee, state, area path) and posts a formatted HTML table to a Microsoft Teams channel with a direct link to the work item.

Use Case

Development and project management teams need real-time visibility when new work items (bugs, user stories, tasks, features) are created in Azure DevOps. This flow eliminates the need to constantly check Azure DevOps by pushing structured notifications directly to a Teams channel where the team collaborates.

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.

Set your Azure DevOps details

Update the flowlibs_AzureDevOpsOrgUrl environment variable to your org URL (e.g., https://dev.azure.com/contoso) and flowlibs_AzureDevOpsProjectName to your project name.

Set your Teams target

Update flowlibs_TeamsGroupId and flowlibs_TeamsChannelId to the team and channel where you want notifications posted.

Filter work item types

To only trigger on specific types (e.g., Bug, User Story), open the trigger and set the optional Work Item Type filter.

Customize the message

Edit the "Post Work Item Card to Teams Channel" action to change the HTML table layout, add/remove fields, or adjust formatting.

Adjust polling frequency

The trigger polls every 5 minutes by default. Modify the recurrence interval in the trigger settings.

Turn on the flow

Once all environment variables are configured and connections are authorized, turn the flow on from the flow details page.

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.

coalesce(triggerBody()?['fields']?['System.AssignedTo']?['displayName'], 'Unassigned')

coalesce(triggerBody()?['fields']?['Microsoft.VSTS.Common.Priority'], 'Not Set')

@{variables('varAdoOrgUrl')}/@{variables('varAdoProjectName')}/_workitems/edit/@{outputs('Compose_Work_Item_Details')?['workItemId']}