BranchDeploy - Deploy linked branches from work itemsDeploy the linked Azure Repos branch from an Azure DevOps work item. |
BranchDeployDeploy 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
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 includedFree
Pro
To upgrade, open View pricing at branch-deploy.dev Set upFull setup guide: branch-deploy.dev/docs/setup Quick start:
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.
Microsoft Teams botWith a Pro account, request and approve deployments from a Microsoft Teams channel. BranchDeploy resolves the branch linked to the work item, checks it against the environment's branch rules, and posts a confirmation card in the channel. Approve or cancel it there; approvals are recorded in your audit log. The Teams bot records approvals today; it does not queue the pipeline itself. AI assistant (MCP)With a Pro account, connect BranchDeploy to your AI assistant through the Model Context Protocol, and deploy from ChatGPT, Claude, Cursor, VS Code, or any MCP client just by giving the work item number. 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 ( Connecting to your BranchDeploy accountTo record deployments made from this extension, generate a connection token in the Credentials tab of your BranchDeploy account and paste it into the BranchDeploy account section at the top of Project Settings → BranchDeploy. You only need to do this once, from any project. Connecting links this Azure DevOps organisation to your BranchDeploy workspace. If the organisation is already linked to a different workspace, that workspace's owners are asked to approve the move; it goes ahead after 7 days unless they decline. Audit logWith a Pro account, every deployment is recorded — who triggered it, which branch, and when — and viewed on your account page for 90 days. Save an Azure DevOps PAT with Build (Read) access on the Credentials tab and each record also shows whether the pipeline run succeeded or failed. Deployments from this extension are recorded once it is connected (see above). Teams and MCP deployments are recorded automatically. Release notesWith a Pro account, turn what you deployed into customer-facing "What's new" notes. Each deployment from this extension records the work item's title and type, which you pick from when writing a note on your account page. A person writes and approves every note, and nothing is public until someone clicks Publish. Publish to a page BranchDeploy hosts for you, or fetch the read-only JSON feed and render it in your own app. Branch names, work item IDs, pipeline details and requester names never appear in public output. Your AI assistant can also draft notes over MCP for you to review. A feed is created for each project the first time its settings sync from this extension. Requirements
Anonymous usage telemetryBranchDeploy 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
|