azure-devops-cli-extension
Azure DevOps Extension for Azure CLI is an official Microsoft command-line tool that extends the Azure CLI with commands for managing Azure Pipelines, Boards, Repos, Artifacts, and DevOps operations. It replaces the deprecated VSTS CLI and provides scriptable access to Azure DevOps resources via terminal commands.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | Azure/azure-devops-cli-extension |
| Owner | Azure |
| Primary language | Python |
| License | MIT — OSI-approved |
| Stars | 677 |
| Forks | 269 |
| Open issues | 326 |
| Latest release | 20260702.1 (2026-07-06) |
| Last updated | 2026-07-06 |
| Source | https://github.com/Azure/azure-devops-cli-extension |
What azure-devops-cli-extension is
Python-based Azure CLI extension that adds subcommands for devops, pipelines, artifacts, boards, and repos management. Integrates with Azure CLI 2.0.69+ and uses Personal Access Token (PAT) authentication via az login and az devops login workflows. Supports JSON output and invocation of raw Azure DevOps REST API endpoints.
Get the azure-devops-cli-extension source
Clone the repository and explore it locally.
git clone https://github.com/Azure/azure-devops-cli-extension.gitcd azure-devops-cli-extension# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires Azure CLI 2.0.69 or later; verify version compatibility before rollout across teams.
- PAT-based authentication must be managed securely in scripts; use environment variables or credential stores, never hardcode tokens in version control.
- Command output varies by subcommand and version; always parse JSON output programmatically rather than relying on text formatting.
- Error handling must account for transient Azure DevOps service issues; implement retry logic and logging in automation scripts.
- Team members need familiarity with command-line tooling and Azure DevOps REST API concepts; training or documentation may be necessary.
When to avoid it — and what to weigh
- Complex GUI-driven workflows required — If your team relies heavily on Azure DevOps web portal visual features (kanban boards, advanced drag-and-drop), CLI may not provide equivalent UX; hybrid approach needed.
- Offline or air-gapped environments — The extension requires connectivity to Azure DevOps services and Azure CLI infrastructure; not suitable for disconnected deployments.
- Real-time event streaming or webhooks — CLI is command-driven, not event-driven; for reactive automation, consider Azure DevOps service hooks or Logic Apps instead.
- Non-Azure DevOps platforms — Extension is locked to Microsoft Azure DevOps; if you use GitHub, GitLab, or Jira, use their native CLIs or APIs instead.
License & commercial use
Licensed under MIT (MIT License), a permissive open-source license allowing commercial use, modification, and distribution with minimal restrictions.
MIT license permits commercial use without restriction. However, this is a Microsoft-maintained extension tied to Azure DevOps subscription; commercial adoption requires valid Azure DevOps licenses for the underlying service. No additional licensing fees for the CLI tool itself.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Strong |
| Assessment confidence | High |
Requires secure handling of Personal Access Tokens (PATs) used for authentication; PATs should not be logged, hardcoded, or exposed in version control. Ensure Azure CLI and extension are kept updated to receive security patches. Validate that organization-level commands enforce appropriate role-based access controls in Azure DevOps backend. Consider audit logging of CLI invocations if used for sensitive operations.
Alternatives to consider
Azure DevOps REST API (direct HTTP clients)
Offers more granular control and is not subject to CLI versioning; suitable for teams that prefer programmatic SDK integration over CLI scripting.
Azure DevOps Server/on-premises CLI
For organizations requiring on-premises or air-gapped deployments; requires separate infrastructure but avoids cloud dependency.
GitHub CLI (gh) + Actions
If your primary VCS is GitHub; provides tighter GitHub-native automation and may reduce multi-platform integration complexity.
Build on azure-devops-cli-extension with DEV.co software developers
Start with the quick-start guide at docs.microsoft.com. Assess PAT security policies and script error handling before deploying in production CI/CD systems.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
azure-devops-cli-extension FAQ
Can I use this in CI/CD pipelines (GitHub Actions, GitLab CI, etc.)?
What's the difference between this and the deprecated VSTS CLI?
How do I authenticate without interactive login?
Is this extension free?
Software development & web development with DEV.co
Adopting azure-devops-cli-extension is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source devops software in production.
Ready to automate your Azure DevOps workflow?
Start with the quick-start guide at docs.microsoft.com. Assess PAT security policies and script error handling before deploying in production CI/CD systems.