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
- Open a work item in Azure Boards.
- Click BranchDeploy in the toolbar.
- BranchDeploy detects the linked Azure Repos branch or pull request.
- Review the branch, repository, and target environment in the confirmation step.
- 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
- Manual confirmation before every deployment
- One pipeline and one environment per project
- Project-level settings in
Project Settings → BranchDeploy
Pro
- Multiple environments per project — configure staging, UAT, and production as separate targets
- Microsoft Teams bot — trigger deployments and approve them directly from a Teams channel
- 90-day audit log — see every deployment, who triggered it, and what branch was used
- Priority support
- Unlimited projects
View pricing at branch-deploy.dev
Set up
Full setup guide: branch-deploy.dev/docs/setup
Quick start:
- Install the extension into your Azure DevOps organisation.
- Open the target project.
- Go to
Project Settings → BranchDeploy.
- Enter the pipeline ID, environment name, and allowed branch patterns.
- 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
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
Support
