Azure DevOps Pipelines Enhanced

Real-time Azure DevOps pipeline visibility directly in VS Code. Monitor your pipeline runs, explore stage/job/task hierarchies, and manage builds without leaving your editor.

Screenshots

Pipeline tree view

Log viewing

Pipeline actions

Trigger, cancel, re-run, or open a run in the browser from the right-click menu:

Status bar indicator

Features

Pipeline Tree View

Browse all YAML pipelines in your Azure DevOps project from the sidebar. Each pipeline expands to show recent runs with their full stage, job, and task hierarchy.

• Colored status icons: green (succeeded), red (failed), yellow (warnings), blue (in progress)
• Commit messages and branch names shown inline
• Duration displayed for completed stages, jobs, and tasks

Current Branch View

Automatically filters pipeline runs to match your currently checked-out git branch. In multi-folder workspaces, the branch follows the folder of your active editor — switch to a file in a different repo folder and the Current Branch view updates to that folder's branch.

Status Bar Indicator

Always-visible pipeline status in the VS Code status bar — no need to open the sidebar:

• Spinning icon when a build is running
• Green checkmark when the latest build succeeded
• Red background when the latest build failed
• Click it to jump to the Pipelines sidebar

Desktop Notifications

Get notified when builds on your current branch complete:

• Success, failure, and warning notifications with build duration
• "Open in Browser" action button on each notification
• Only triggers for builds on your current branch — no noise from other branches
• Deduplication prevents repeat notifications

Live Updates

Pipeline status refreshes automatically:

• New and updated builds polled every 15 seconds
• In-progress build timelines polled every 5 seconds
• Rate limit aware: automatically backs off when approaching Azure DevOps API limits

Pipeline Actions

• Trigger Run - Start a new pipeline run from VS Code (with branch selection and validation)
• Cancel Run - Cancel an in-progress build (with confirmation dialog)
• Re-run - Retry a failed or completed build
• Open in Browser - Jump to the build in the Azure DevOps web portal

Log Viewing

Click any task step to open its log directly in a VS Code editor tab. Azure DevOps ##[section], ##[command], ##[warning], and ##[error] markers are color-coded. When a log contains ##[group]/##[endgroup] markers, those blocks become collapsible sections and their headers populate the breadcrumb navigation — note that most per-step logs contain no groups, so folding only appears for steps that emit them (e.g. some setup/checkout tasks).

Multi-Remote Support

If your repository has multiple Azure DevOps remotes (e.g., origin pointing to a dev org and contoso pointing to production), the extension detects all of them and lets you choose which organizations to connect to.

Zero Configuration

The extension detects your Azure DevOps organization and project automatically from your git remote URL. Just sign in with your Microsoft account and you're ready to go.

Supported remote URL formats:

• https://dev.azure.com/{org}/{project}/_git/{repo}
• https://{user}@dev.azure.com/{org}/{project}/_git/{repo}
• https://{org}.visualstudio.com/{project}/_git/{repo}
• git@ssh.dev.azure.com:v3/{org}/{project}/{repo}

Getting Started

1. Install the extension
2. Open a workspace containing a git repository cloned from Azure DevOps
3. Click the Azure Pipelines icon in the Activity Bar
4. Sign in with your Microsoft account when prompted
5. If multiple Azure DevOps organizations are detected, select which to connect to
6. Your pipelines appear automatically

Requirements

• VS Code 1.85.0 or later
• A git repository with an Azure DevOps remote
• An Azure DevOps Services (cloud) account at dev.azure.com

Note: Azure DevOps Server (on-premises) is not currently supported.

Commands

Additional commands are available via right-click context menus on pipeline and run nodes in the tree view.

Troubleshooting

Extension not showing pipelines

• Verify your workspace has a git remote pointing to Azure DevOps
• Check the Output panel (Terminal > Output > "Azure Pipelines") for diagnostic logs
• Ensure you're signed in (look for the sign-in prompt in the Azure Pipelines sidebar)

Authentication issues

The extension uses VS Code's built-in Microsoft authentication provider. If you encounter issues:

• Getting a 401 Unauthorized / TF400813 ... is not authorized? VS Code silently signed you in with an account that lacks access to the organization. Run "Azure Pipelines: Sign Out of Azure DevOps", then "Azure Pipelines: Sign In to Azure DevOps" — sign-in now always shows the account picker so you can select (or add) the correct account.
• Click "Try Different Account" on the error notification to re-run sign-in with a fresh account picker
• Use the command palette: "Azure Pipelines: Sign In to Azure DevOps" — this forces a fresh account picker even if a session exists
• If you have multiple remotes on different Entra ID tenants, ensure you're signed in with the account that has access to the selected organization
• You can also sign out via the Accounts menu in the VS Code status bar and sign in again

Multiple remotes / organizations

If your repo has remotes pointing to different Azure DevOps organizations, the extension will prompt you to choose which to connect to. Your selection is remembered per workspace — you won't be asked again unless you switch workspaces or use the "Azure Pipelines: Select Organization" command to change it.

If you accidentally dismiss the picker, use the command palette (Ctrl+Shift+P) and search for "Azure Pipelines: Select Organization" to re-open it.

If one org fails authentication, the extension will skip it and load the others with a warning message.

Rate limiting

The extension respects Azure DevOps API rate limits automatically. If you see reduced refresh rates, this is normal and will recover on its own.

Known Limitations

• Only YAML pipelines are supported (Classic/GUI pipelines are not shown)
• Azure DevOps Server (on-premises) is not supported
• Multiple remotes on different Entra ID tenants require switching accounts via "Sign In to Azure DevOps" (forces fresh account picker)
• Log viewing color-codes Azure DevOps ##[...] command markers; raw ANSI escape sequences in tool output are stripped rather than rendered

Contributing

See CONTRIBUTING.md for development setup and contribution guidelines.

License

This project is licensed under the MIT License - see the LICENSE file for details.