Azure DevOps Work Item Created to Teams Post
When a new work item is created in Azure DevOps, post a formatted card to the project's Teams channel with type, priority, and assignee.
Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.
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
When a Work Item Is Created
Azure DevOps (polling, 5 min)Polls the configured ADO project for new work items using OnWorkItemCreated. Uses splitOn to process each item individually.
Initialize Variable - Teams Group ID
Initialize VariableStores the Teams Group ID from the flowlibs_TeamsGroupId environment variable into varTeamsGroupId.
Initialize Variable - Teams Channel ID
Initialize VariableStores the Teams Channel ID from the flowlibs_TeamsChannelId environment variable into varTeamsChannelId.
Initialize Variable - ADO Org URL
Initialize VariableStores the Azure DevOps org URL from the flowlibs_AzureDevOpsOrgUrl environment variable into varAdoOrgUrl.
Initialize Variable - ADO Project Name
Initialize VariableStores the ADO project name from the flowlibs_AzureDevOpsProjectName environment variable into varAdoProjectName.
Compose Work Item Details
ComposeExtracts and organizes work item fields: ID, Title, Type, Assigned To (with fallback to "Unassigned"), Priority (with fallback to "Not Set"), State, and Area Path.
Post Work Item Card to Teams Channel
Post message (Teams)Posts an HTML-formatted table to the configured Teams channel showing all work item details with a clickable link to view the item in Azure DevOps.
Environment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_AzureDevOpsOrgUrl | String | <configure> | Base URL of the Azure DevOps organization (e.g., https://dev.azure.com/myorg). |
| flowlibs_AzureDevOpsProjectName | String | <configure> | Name of the ADO project to monitor for new work items. |
| flowlibs_TeamsGroupId | String | <configure> | The Microsoft 365 Group ID for the target Teams team. |
| flowlibs_TeamsChannelId | String | <configure> | The Channel ID where notifications will be posted. |
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Azure DevOps | shared_visualstudioteamservices | OnWorkItemCreated (trigger) |
| Microsoft Teams | shared_teams | PostMessageToChannel |
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.
EXPR.01Null-safe Assigned To
Falls back to "Unassigned" when the work item has no assignee.
EXPR.02Null-safe Priority
Falls back to "Not Set" when the work item has no priority value.
EXPR.03Work Item Link
Builds the deep-link URL to the work item in Azure DevOps using the configured org and project variables.
Comments
Sign in to join the conversation.
Sign inNo comments yet. Be the first to share your experience with this flow.