Azure DevOps Pricing: How Microsoft Charges
Overpaying for Microsoft? We handle Microsoft EA, NCE, and Azure negotiation on a 25% gainshare basis — you keep 75% of every dollar saved. No retainer. No risk.
Get a free Microsoft savings estimate →Azure DevOps pricing is more complex than it first appears. Microsoft structures the cost around three independent dimensions: user plans (who has access), parallel pipeline jobs (how much CI/CD capacity you have), and artifact/storage consumption. These three dimensions are priced and invoiced separately — but all sit within your overall Microsoft EA commitment, which creates both confusion and consolidation opportunity.
User Plans: Basic vs Basic + Test Plans
The standard Azure DevOps user plan — called the Basic plan — is priced at $6 per user per month at list price. This gives users access to Azure Boards, Azure Repos, Azure Pipelines, and Azure Artifacts.
The Basic + Test Plans tier, which adds Azure Test Plans for manual testing and test case management, is priced at $52 per user per month — nearly 9x the cost of Basic. For organisations with large QA teams, this tier can represent a disproportionate share of Azure DevOps spend.
⚠️ The Visual Studio Subscription Overlap
This is the most expensive Azure DevOps oversight. Visual Studio Professional and Enterprise subscriptions already include Azure DevOps Basic plan access. Developers with VS subscriptions do not need to be assigned a paid Basic plan. Yet in most enterprises, a significant portion of Azure DevOps Basic plan licences are assigned to users who already have VS subscriptions. This is direct duplicate spend — typically 20-40% of the Basic plan licence count.
Parallel Jobs: Where the Real Cost Hides
For organisations using Azure Pipelines at scale, parallel jobs are often the largest Azure DevOps cost driver — and the one most frequently overlooked during EA negotiations.
| Job Type | List Price | Included Free | Notes |
|---|---|---|---|
| Microsoft-hosted parallel jobs | $40 / job / month | 1 free job (public) / 1 free job (private, 1,800 min/month) | Runs on Microsoft Azure infrastructure |
| Self-hosted parallel jobs | $15 / job / month | 1 free job | Runs on your own agents |
| GitHub Actions (via GitHub Enterprise) | Included in GHEC | Varies by plan | Alternative if GitHub Enterprise licensed |
A large software development organisation with 200 active developers and a robust CI/CD pipeline might require 20-40 parallel jobs to avoid queue bottlenecks. At $40/job/month, that's $800–$1,600 per month — or $9,600–$19,200 per year — just in pipeline capacity. Multiply this across multiple Azure DevOps organisations (a common pattern in large enterprises), and parallel job costs can reach $200,000–$500,000 annually.
Azure DevOps vs GitHub Enterprise: The Overlap Problem
Microsoft's acquisition of GitHub in 2018 created a strategic dilemma that Microsoft has not fully resolved: it now sells two overlapping developer platforms that enterprises increasingly run in parallel, paying for both. Azure DevOps (Boards, Repos, Pipelines, Artifacts, Test Plans) and GitHub Enterprise (Issues, Repos, Actions, Packages, Advanced Security) have significant functional overlap. Many enterprises have ended up with both because different teams adopted different toolchains over time.
Azure DevOps is priced separately from GitHub Enterprise. GitHub Enterprise Cloud is priced at $21 per user per month, while Azure DevOps Basic is $6/user/month. Organisations that have fully or partially migrated to GitHub Actions are often still paying for Azure Pipelines parallel jobs they no longer use. A rationalisation exercise — mapping actual usage of each service against licence assignment — typically identifies 15-25% of combined Azure DevOps + GitHub spend as redundant.
Azure DevOps costs buried inside a larger Microsoft EA?
Our Microsoft negotiation team conducts forensic analysis of your full Microsoft commercial relationship — EA, NCE, GitHub, Azure commitments — and identifies every dollar of duplicate or excess spend. We work on a 25% gainshare basis: if we don't save you money, you pay nothing.
Get Your Free Microsoft Cost AnalysisGitHub Advanced Security: The Security Add-On Cost
GitHub Advanced Security (GHAS) is Microsoft's code security scanning product — covering secret scanning, code scanning (SAST), and dependency review. For enterprises that need GHAS capabilities, it is priced at $49 per active committer per month on top of the GitHub Enterprise licence cost.
In a 500-developer organisation where 60% are active committers, GHAS adds approximately $176,000 per year. This is a substantial additional cost — and it's one where Microsoft has shown meaningful flexibility during EA negotiations, particularly for organisations that are also expanding their broader Microsoft Azure commitment. GHAS discounts of 20-35% are achievable when negotiated as part of a consolidated Microsoft commercial conversation rather than a standalone add-on purchase.
What's Actually Included in Your Microsoft EA
The relationship between Azure DevOps, Visual Studio subscriptions, and the Microsoft EA is poorly understood by most enterprise procurement teams. This confusion is expensive. The key inclusions to verify before purchasing any Azure DevOps licences are:
- Visual Studio Enterprise subscription — includes Azure DevOps Basic + Test Plans ($52/month value per user)
- Visual Studio Professional subscription — includes Azure DevOps Basic plan ($6/month value per user)
- MSDN Platforms subscription — includes Azure DevOps Basic plan
- GitHub Enterprise — includes GitHub Actions minutes (variable by plan tier)
Before your next Azure DevOps renewal or expansion, run a cross-reference of your VS subscription holders against your Azure DevOps user assignments. Any developer with a VS Pro or VS Enterprise subscription who is also assigned a paid Azure DevOps Basic plan is a double-charge. In a 500-developer organisation, eliminating this overlap saves on average $50,000–$120,000 annually.
Azure DevOps Negotiation Tactics
1. Include Azure DevOps in Your EA Negotiation, Not as an Afterthought
Most enterprises negotiate their Microsoft EA around core products — Microsoft 365, Azure commitments, Windows/Server. Azure DevOps and GitHub are often treated as procurement afterthoughts, purchased at list price through the Azure portal rather than negotiated into the EA. This is a mistake. When Azure DevOps and GitHub spend is included in the EA negotiation as a defined workload, standard EA discounts of 15-25% apply. At $200,000+ annual Azure DevOps spend, this is not a trivial saving.
2. Consolidate Around GitHub or Azure DevOps — Not Both
The most effective long-term cost management strategy is to choose a primary developer platform and migrate workloads to it. Organisations that consolidate around GitHub Enterprise typically achieve 10-20% lower total developer tooling costs than those running hybrid Azure DevOps + GitHub environments. Microsoft will also provide consolidation incentives — including migration support credits and parallel licensing during transition — for organisations that commit to a single platform strategy.
3. Right-Size Parallel Job Allocation
Parallel job consumption can be right-sized through pipeline audits. Most large organisations have a small number of pipelines that consume the majority of parallel job capacity — often batch jobs, release pipelines, or integration test suites. Identifying and optimising these high-consumption pipelines (through caching, parallelisation tuning, or migrating to self-hosted agents) consistently reduces parallel job requirements by 30-50%, generating direct subscription savings.
4. Use the MACC Framework for Azure DevOps Consolidation
If your organisation has an Azure MACC commitment, Azure DevOps spend can be counted against that commitment. This creates a path to consolidating Azure DevOps, GitHub Enterprise, and core Azure services into a single commercial structure with unified volume discounting. Organisations that restructure their Microsoft commercial agreements this way typically achieve 8-15% lower effective cost across the combined portfolio versus purchasing each component separately.
💡 NCE and Azure DevOps: Watch the Lock-In
Under Microsoft's New Commerce Experience (NCE), annual Azure DevOps subscriptions carry early termination restrictions. If you over-provision Azure DevOps licences on NCE annual terms, you cannot reduce mid-term. Always purchase through EA where possible — EA Azure DevOps has more flexible true-up provisions than NCE annual subscriptions.
Related Microsoft and Developer Platform Resources
- Microsoft EA Renewal 2026: 15 Tactics to Reduce Your Cost
- Microsoft GitHub Enterprise Licensing: What to Negotiate
- Microsoft NCE: What the New Commerce Experience Means for Your Costs
- Microsoft MACC Commitments: When They Help and When They Hurt
- Microsoft 365 E3 vs E5: Total Cost of Ownership for Enterprise
- Our Microsoft Negotiation Service
- SaaS Contract Negotiation
- Get a Free Microsoft Cost Assessment