BranchDeploy

Add a deploy action to Azure Boards. Open a work item, confirm the linked Azure Repos branch or PR, and queue your existing Azure Pipeline. No clipboard, no tab switching.

Ticket to pipeline in one click.

Deploy linked branches from Azure Boards.

BranchDeploy adds a deploy action to Azure Boards work items. Open a ticket, confirm the linked Azure Repos branch or PR, and queue your existing Azure Pipeline without copying branch names or switching tabs.

→ Install free See how it works

Free forever for one project and one environment. No BranchDeploy account required for the free extension workflow.

// No clipboard. No tab switching. No branch-name guesswork. Azure DevOps
Marketplace extension

00—See the flow Open ticket, confirm branch, queue pipeline.

See the whole flow in seconds.

Open a linked work item, click BranchDeploy, confirm the branch and environment, then queue the pipeline. The run ID and pipeline link appear immediately.

Work item

#1234 — Add checkout flow

Linked branch: feature/checkout-flow

BranchDeploy ↗

Confirm

Branchfeature/checkout-flow

EnvironmentUAT

Work item#1234

Deploy

Queued

Run #4821

View pipeline run →

Diagram showing the work item to queued pipeline run flow via BranchDeploy.

01—What you get A button in the work item, not another workflow.

The deploy button Azure DevOps was missing.

In the work item

The action lives in the work item toolbar. No tab switching, no copying branch names from a separate page.

Always confirmed

You see the resolved branch, target environment, and ticket number before the pipeline runs. No surprises.

No new infrastructure

Wraps your existing Azure Pipeline. No webhooks, no backend to host, no BranchDeploy account on the free tier.

5-minute setup

Install from the Marketplace, open Project Settings, enter a pipeline ID. That's it — unlimited free deploys from day one.

Link resolution

Reads linked Azure Repos branches and PRs from the work item.
Resolves PR source branch automatically.
Queues immediately when there is one clear candidate.
No branch-name typing, no clipboard.

Safety

Explicit confirmation before every deploy — branch, environment, ticket.
Branch allowlist per environment using glob patterns.
Blocks deploys if no linked branch can be resolved.
Queues as the current Azure DevOps user — respects existing permissions.

Pipeline

Queues your existing Azure Pipeline — no YAML changes required.
Passes environment name and work item ID as parameters.
Parameter names are configurable to match your existing YAML.
Shows the run ID and a direct link the moment it's queued.

Pro

Unlimited projects and environments per organisation.
Multi-branch picker — when a work item links to more than one branch or PR, choose which to deploy.
Deploy from Microsoft Teams — @BranchDeploy deploy #1234 to UAT in any channel.
Deploy from your AI assistant — Claude, Cursor, or any MCP client. AI deployment docs →
Deployment audit log, 90 days.
Priority support — 2 business day email SLA.
View Pro pricing →

02—How it works Resolve, confirm, queue.

From ticket
to deploy.

ticket → deploy

· one confirmation, no typing

Resolve

Confirm

Queue

01 Open the work item Use any work item linked to an Azure Repos branch or pull request. →

02 Click BranchDeploy The action lives in the work item toolbar. →

03 Branch resolves BranchDeploy reads the linked Azure Repos branch or PR source branch automatically. →

04 Review & confirm Check branch, environment, and work item before the pipeline runs. Nothing queues without confirmation. →

05 Pipeline queued The run ID and a direct link to the pipeline run appear immediately. →

03—Before and after Same result, less friction.

Stop turning a ticket into a manual pipeline hunt.

Before BranchDeploy

Open the work item.
Find the linked branch or PR.
Copy the branch name.
Open Azure Pipelines in a new tab.
Find the right pipeline.
Select branch and environment parameters.
Queue the run.
Share the run link back to the ticket.

With BranchDeploy

Open the work item.
Click BranchDeploy.
Confirm branch and environment.
Pipeline queued — run ID in front of you.

04—Who it's for Everyone involved in getting a ticket tested.

Built for everyone involved in getting a ticket tested.

Developers

Reduce deployment interruptions and avoid manually copying branch names into pipeline runs. Deploy the branch you're working on from the ticket it's tracked in.

How developers use it →

Deploy the exact branch linked to the ticket you are about to test. No more guessing which branch is in UAT or asking a developer to queue a pipeline for you.

Deploy from a work item →

Delivery managers

Give UAT a clearer handoff from ticket to deployed branch. The branch, environment, and work item are confirmed before anything runs.

Linking work items to branches →

DevOps admins

Reuse existing pipelines, permissions, branch filters, and deployment controls. BranchDeploy wraps what you already have — no new infrastructure to maintain.

Security and permissions →

05—Microsoft Teams Pro feature.

Deploy from Teams.
Without opening Azure DevOps.

With a BranchDeploy Pro licence, your whole team can trigger deployments straight from a Teams channel. Type a command, review the confirmation card, click Deploy Now.

Teams bot setup guide →

In any Teams channel

@BranchDeploy deploy #1234 to UAT

Deploy to UAT?

Work item#1234 — Add checkout flow

Branchfeature/checkout-flow

EnvironmentUAT

Deploy Now Cancel

06—Safety and permissions Uses what you already trust.

Safe by default, because it uses what you already trust.

BranchDeploy wraps your existing Azure Pipeline. The free extension workflow queues as the current Azure DevOps user, respects existing queue permissions, and requires confirmation before every deployment.

Queues as you

BranchDeploy queues your existing Azure Pipeline as the current Azure DevOps user and respects existing Azure DevOps permissions. If you cannot queue the pipeline manually, BranchDeploy cannot queue it for you.

Always confirmed

Every deployment shows the resolved branch, environment, and work item before anything runs. There is no way to skip confirmation.

Branch allowlists

Restrict each environment to expected branch patterns using glob rules such as feature/* or release/*. Pro adds per-environment allowlists.

No account needed (Free)

The free Azure DevOps extension workflow requires no BranchDeploy account and no BranchDeploy-hosted backend for the core work-item deploy action.

Read security and permissions details →

07—FAQ Common questions, direct answers.

Questions.

Does BranchDeploy replace Azure Pipelines?

No. BranchDeploy queues your existing Azure Pipeline from an Azure Boards work item. It does not replace your CI/CD pipeline or hosting platform.

Does BranchDeploy require YAML changes?

The core workflow is designed to wrap an existing pipeline. If your pipeline already supports branch-based deployments, BranchDeploy can queue it. Optional parameters can be configured to pass environment name and work item ID.

Can QA deploy from a work item?

Yes, if the QA user has permission to queue the configured pipeline and the project has BranchDeploy configured by a project admin.

What happens if more than one branch or PR is linked?

BranchDeploy Pro shows a branch picker so the user can choose the correct linked branch or PR before deploying. On the free tier, BranchDeploy uses the single linked branch or returns an error if it cannot determine a clear candidate.

Can I restrict which branches can deploy to an environment?

Yes. BranchDeploy supports branch allowlists using glob patterns such as feature/*, bugfix/*, or release/*. Pro adds per-environment allowlists.

Does BranchDeploy support GitHub repositories?

BranchDeploy is built for Azure Repos, Azure Boards, and Azure Pipelines. It does not currently support GitHub repositories.

Can I deploy from an AI assistant?

Yes, in Pro. BranchDeploy includes an MCP server at https://api.branch-deploy.dev/mcp that lets Claude, Cursor, and other MCP-compatible AI assistants trigger branch deployments using a generated API key. See AI deployment docs →

BranchDeploy is built for Azure DevOps teams that use Azure Boards, Azure Repos, and Azure Pipelines together. When a work item is linked to a branch or pull request, BranchDeploy can resolve the linked source branch and queue your configured pipeline for staging, UAT, QA, or preview deployments.

Instead of moving between Azure Boards and Azure Pipelines, your team can deploy from the work item context where the work is already tracked.

How to deploy an Azure Pipeline from a work item → How to deploy a specific Azure Repos branch → How to link a work item to a branch or PR → Azure Boards deployment extension →

Install Free forever for one project.

Ready to ship?

Install the Marketplace extension, add your pipeline ID, and deploy from a work item in minutes.

$ az devops extension install --name branchdeploy

Install free ↗

Requirements

Azure Repos + Azure Pipelines.
Permission to queue the pipeline.
No BranchDeploy account needed (Free).

Setup

Install the extension.
Open Project Settings → BranchDeploy.
Enter your pipeline ID and save.

Free tier

One project, one environment.
Queues as your Azure DevOps session.
Completely free, forever.

Pro

Multiple projects and environments.
90-day audit log.
Branch allowlists per environment.
Teams bot ↗
AI assistant (MCP) ↗

// No clipboard. No tab switching. No branch-name guesswork.