Deploy

Install the extension, point it at your pipeline, and trigger your first deploy straight from a work item — no backend, account, or stored secrets required.

Requirements

• An Azure DevOps organisation on dev.azure.com.
• Azure Repos in the project with a branch or PR linked to a work item.
• An Azure Pipeline the current user can queue.
• Permission to install Marketplace extensions, or an admin who can.

Setup

Available across every project in the organisation. Three steps: install → configure → deploy.

1. Install from the Marketplace

• Open BranchDeploy in the Azure DevOps Marketplace ↗.
• Click Get it free, select your organisation, and install.
• The extension is available immediately across all projects in the organisation.

2. Configure your project

• Go to Project Settings → BranchDeploy.
• Enter your pipeline ID and environment name, then save.
• Optionally restrict which branches can be deployed using glob patterns.

3. Deploy from a work item

• Open a work item that has a linked branch or PR in Azure Repos.
• Click the BranchDeploy action in the toolbar and confirm the deploy.
• The pipeline run ID and a direct link to the run appear immediately.

BranchDeploy follows Development links only — not work item titles, commit messages, or Related Work links. Link your branch or PR from the Development section of the work item.

Permissions

BranchDeploy queues pipelines as the current Azure DevOps user. If you cannot queue the pipeline manually, BranchDeploy cannot queue it either.

Queue builds — Required on the target pipeline.

Branch filters — Pipeline branch filters must allow the linked branch.

Next steps

• Configuration guide — Set up pipeline parameters and branch rules.
• Pipeline YAML examples — Use BranchDeploy parameters in YAML.
• Troubleshooting — Fix the most common problems.