Deployment audit log

BranchDeploy Pro keeps a 90-day record of every deployment: the work item, branch, target environment, who triggered it, where it came from, and when. Older records are deleted automatically.

Each record starts as queued when the pipeline run is queued. BranchDeploy then checks Azure DevOps every few minutes and updates it to running, then succeeded, partially succeeded, failed, or cancelled, with the time the run finished. This uses the Azure DevOps PAT saved on the Credentials tab, which needs Build (Read) access. Without a saved PAT, records stay queued. You can view it on your account page under the Audit log tab, filter by environment, status or source, load older entries, and click any row for the full detail.

Deployment requests approved through the Teams bot and deployments triggered through AI assistant (MCP) are recorded automatically — they authenticate with their own credentials. To also record deployments triggered from the Azure DevOps extension (the deploy button on a work item), you need to connect the extension to your account with a connection token.

Why a connection token is needed

When you deploy from a work item, the extension runs inside your browser as you. To attribute that deployment to you in a central log, the extension has to authenticate to BranchDeploy. A connection token does this — it links the extension to your organisation.

Until a token is connected, deployments from the extension are not recorded. The extension shows a warning in Project Settings → BranchDeploy when this is the case.

Step 1 — Generate a connection token

1. Open your account page and go to the Credentials tab.
2. Under Extension connection token, click Generate token.
3. Copy the token (it starts with bd_ext_). It is shown only once.

Step 2 — Connect the extension

1. In Azure DevOps, open Project Settings → BranchDeploy.
2. In the BranchDeploy account section at the top, paste the token.
3. Click Test & connect.

Once connected, every deployment from that organisation is recorded with the team member who triggered it. The connection applies organisation-wide — you only need to do this once, from any project.

Connecting also links the Azure DevOps organisation to your BranchDeploy workspace. If it is already linked to a different workspace, that workspace’s owners and admins are emailed to approve the move, and the extension shows that it’s waiting. The move goes ahead after 7 days unless they decline; until then, deployments keep being recorded in the current workspace.

Step 3 — View the log

1. Open your account page and go to the Audit log tab.
2. Filter by environment, status or source, click Load more for older entries, and click any row to see the full deployment detail — pipeline run, work item, branch, project, and timestamps.

Troubleshooting

The extension warns that deployments aren’t being recorded — No connection token is linked. Follow Steps 1–2 above.

“Token is invalid or revoked” — The token was revoked or regenerated on the account page. Generate a new one in the Credentials tab and reconnect.

Teams approvals or MCP deployments appear, but not extension deployments — That’s expected until you connect a token. Teams and MCP authenticate separately; the extension needs its own connection token.