BranchDeploy

Deploy the branch linked to an Azure DevOps work item — without leaving the ticket.

BranchDeploy adds a deploy button directly to Azure Boards work items. Click it, confirm the branch, and your pipeline runs. No switching tabs, no copy-pasting branch names, no guesswork.

How it works

1. Open a work item in Azure Boards.
2. Click BranchDeploy in the toolbar.
3. BranchDeploy detects the linked Azure Repos branch or pull request.
4. Review the branch, repository, and target environment in the confirmation step.
5. Confirm — your Azure Pipeline is queued against that branch.

If more than one branch or pull request is linked to the work item, BranchDeploy shows a picker so you choose the right one before anything runs.

What's included

Free

• Deploy button on every Azure Boards work item
• Automatic branch detection from linked PRs and branches
• Branch picker when multiple options are linked
• Branch allowlist — restrict which branches can be deployed
• Manual confirmation before every deployment
• One pipeline and one environment per project
• Project-level settings in Project Settings → BranchDeploy

Pro

• Unlimited projects and environments — configure staging, UAT, and production as separate targets
• Branch allowlists per environment — different rules for each target
• Microsoft Teams bot — trigger deployments and approve them directly from a Teams channel
• AI assistant integration (MCP) — deploy from Claude, Cursor, or any MCP client by asking in natural language
• 90-day audit log — see every deployment, who triggered it, and what branch was used
• Priority support (2 business day SLA)

To upgrade, open Project Settings → BranchDeploy and click Upgrade to Pro.

View pricing at branch-deploy.dev

Set up

Full setup guide: branch-deploy.dev/docs/setup

Quick start:

1. Install the extension into your Azure DevOps organisation.
2. Open the target project.
3. Go to Project Settings → BranchDeploy.
4. Enter the pipeline ID, environment name, and allowed branch patterns.
5. Save settings.

BranchDeploy will not queue deployments for a project until settings have been saved by a project administrator.

Finding your pipeline ID:

Open the pipeline in Azure DevOps and read the numeric ID from the URL.

.../_build?definitionId=17 → use 17

Microsoft Teams bot

With a Pro account, deploy from Microsoft Teams without opening Azure DevOps at all.

@BranchDeploy deploy feature/my-work to staging

BranchDeploy posts a confirmation card in the channel. Approve or cancel it there. The deployment result posts back when the pipeline finishes.

Teams setup guide

AI assistant (MCP)

With a Pro account, connect BranchDeploy to your AI assistant through the Model Context Protocol, and deploy from Claude, Cursor, VS Code, or any MCP client just by giving the work item number.

"Deploy ticket 1482"

You only provide the ticket. BranchDeploy resolves its linked branch and the target environment's pipeline, applies the same branch rules as the deploy button, and asks you to confirm before anything is queued — so the assistant can't deploy an unlinked branch or bypass your rules. Name an environment ("Deploy ticket 1482 to Staging") only when a project has more than one.

AI deployment (MCP) guide

Audit log

With a Pro account, every deployment can be recorded — who triggered it, which branch, and when — and viewed on your account page for 90 days.

To record deployments made from this extension, generate a connection token on your BranchDeploy account (Credentials tab) and paste it into Project Settings → BranchDeploy → Connect to BranchDeploy. Teams and MCP deployments are recorded automatically.

Audit log guide

Requirements

• Azure DevOps Services
• Azure Boards
• Azure Repos
• Azure Pipelines
• A pipeline already configured to build or deploy a branch
• A user with permission to queue the target pipeline
• A project administrator who has configured BranchDeploy in Project Settings → BranchDeploy

Anonymous usage telemetry

BranchDeploy collects limited anonymous telemetry (extension version, event type, success/failure status, broad error codes, coarse branch/environment categories, and hashed Azure DevOps identifiers) to understand usage and diagnose reliability issues. We never collect repository, branch, organisation, or project names, emails, access tokens, commit messages, or pipeline variables. Telemetry is best-effort, never blocks deployments, and can be disabled in Project Settings → BranchDeploy under Anonymous usage telemetry. See the privacy policy for details.

Support

• Documentation: branch-deploy.dev/docs/setup
• Support: branch-deploy.dev/support
• Privacy policy: branch-deploy.dev/privacy