Azure DevOps Workflow Automation

Build powerful Azure DevOps automation rules with triggers, conditions and actions.

Take the repetitive work off your Azure Boards. Customize automation rules around your process: triggers from work items (created, updated, commented, and more), a pipeline run or stage (YAML and classic), or a schedule you set. Define the conditions and the chain of actions that should run when they are met.

Automations

All of your automations in one place: create, enable, run, and review results.

Templates

Jump in with starters for the jobs teams do every day. Adjust names, owners, and recipients — then save. Guides for each starter: all templates.

Ready-made templates for common work-item, pipeline, and schedule flows.

Build your own

Choose a trigger — a work item, a schedule, or a pipeline run or stage — add conditions if it should run only in certain cases, then stack the actions: create or update work items, add comments, send an email, queue a pipeline, or load the work items related to that run. Insert fields from the work item into titles, comments, and messages. Apply the actions to the item that started the automation, its parent or children, or a list of items you search for.

Create child Tasks automatically when a User Story is added.

Send a weekly closed-work report by email.

Create a Bug when a pipeline fails.

Triggers, conditions, and actions

Combine any trigger with conditions and one or more actions — mix and match to fit your process.

Looking for more triggers and actions? Contact us.

Automation templates and common use-cases

Browse all templates or pick a starter below.

Requirements and security

• An organization administrator chooses how automations run.
• Setup Automation User: Automations run as that account, in every project the account can use.
• Connect an Entra app: the organization must be connected to Microsoft Entra ID. An organization administrator connects the Automations app once and chooses which projects can run. Automations run as that app, not as the person who saved them.
• Project administrators create and edit automations. Members can view them and logs unless the project restricts that.
• Automations you create in a project stay in that project.

Privacy Policy · Security · License

Get started

Free while the extension is in Preview.

1. Install the extension.
2. An organization administrator opens organization Automations and chooses a setup:
   • Setup Automation User — sign in with a work or school account used for automations. That account should be a Project Administrator where automations should run.
   • Connect an Entra app — available after the organization is connected to Microsoft Entra. Pick the projects, register the Automations Entra app in your organization.
3. Open Automations in the project (as project administrator) and pick a template — or start from scratch to create and manage automations in that project.
4. Observe automation executions in the Logs tab in each project.

Step-by-step: Set up Automations.