Azure DevOps Pricing Explained: What You Pay for and What You Get

How much does Azure DevOps cost? For many small teams, nothing: the first five Basic users are free, and so are Stakeholders. After that, ADO pricing is $6 per Basic user per month, $52 for users who need Test Plans, and $40 for each extra Microsoft-hosted pipeline job. Storage for packages and GitHub Advanced Security are billed on top.

Below you will find how Azure DevOps pricing works in practice: what the free tier really covers, how each access level is priced, how parallel jobs work, and worked examples of the monthly bill for teams of 5, 13, 25 and 50 people. All prices were checked on Microsoft’s pricing pages on October 23, 2026.

This table covers everything that usually shows up on an Azure DevOps bill. The sections below explain each line.

Prices are US list prices from Microsoft’s Azure DevOps pricing page, checked on October 23, 2026. Taxes, currency and enterprise agreements can change your final bill.

Is Azure DevOps free? Yes, for a team of up to five developers plus any number of Stakeholders, as long as you can live with a few limits. The Azure DevOps free tier gives every organization:

• five Basic users with access to Boards, Repos, Pipelines, dashboards and wiki;
• unlimited Stakeholders who can view and comment on work items, dashboards and the wiki;
• unlimited private Git repositories;
• one Microsoft-hosted parallel job with 1,800 minutes per month, and no single run can go past 60 minutes;
• one self-hosted parallel job with no limit on minutes;
• 2 GiB of Azure Artifacts storage.

There is one condition people often miss. To receive the free Microsoft-hosted grant, the organization has to be linked to an Azure subscription for billing. You won’t be charged for the grant itself, but the link has to be there.

Test Plans are not part of the free tier. Basic users can run tests and review results, but creating and managing test plans requires Basic + Test Plans.

Public projects used to be the loophole for open-source work, since they came with unlimited free build minutes. According to Microsoft’s public projects retirement notice, nobody can create new public projects since April 2026. Existing ones will turn private during 2027 (Microsoft hasn’t announced exact dates) and will move to the standard 1,800 minutes per month.

Azure DevOps licensing is per user, and licenses are the part of ADO pricing that grows with headcount. Each person gets one access level, and an Azure DevOps license is billed monthly, so moving someone from Basic to Stakeholder lowers the next bill.

The Azure DevOps basic license cost applies from the sixth seat: a 20-developer team pays 15 × $6 = $90 per month, and $6 is the whole Azure DevOps cost per user for most engineers. Basic + Test Plans has no free seats, so after the 30-day trial the Azure DevOps license cost for each QA engineer who manages test plans is $52 per month. The access levels documentation lists every feature by level.

Stakeholder access is free with no user limit, which makes it the easiest way to keep the ADO license cost down for managers, designers and clients who only view and comment. The limits are real, though. In private projects a Stakeholder can only change the State of a work item on a board, so they can’t drag cards between columns or edit fields. They can’t plan sprints, and they can save queries only under My Queries. Someone who actively runs the backlog will hit these limits quickly, and that person needs Basic.

Visual Studio Professional maps to Basic; Enterprise, Test Professional and MSDN Platforms map to Basic + Test Plans; GitHub Enterprise users get Basic when they sign in. None of them use the five free seats. Microsoft’s Visual Studio subscriptions guide advises assigning subscribers the “Visual Studio Subscriber” access level, not Basic. Otherwise the Azure DevOps price includes $6 for each of them until their first sign-in.

Pipelines are billed by parallel jobs, not by users or minutes alone. A parallel job is one pipeline run that can happen at a time. If you have one job and two developers push at once, the second run waits in the queue.

Prices from the Azure DevOps Services pricing page, checked October 23, 2026.

Is 1,800 minutes enough? Do the math for your team. A team running 10-minute builds six times a day uses about 1,320 minutes over 22 working days, which fits within the free 1,800. Add a 15-minute test stage to every run and the same team goes past the limit. Watch the 60-minute cap per run too: a long test suite can fail at minute 60 on the free tier, while a paid job allows 360 minutes.

The first Microsoft-hosted job you buy replaces the free one. It removes the 1,800-minute cap and the 60-minute limit, but it doesn’t add a second job. If you’re on the free tier and want two builds to run at the same time on Microsoft-hosted agents, you need to buy two parallel jobs ($80 per month), not one. Three concurrent builds cost $120. Buy jobs when runs regularly wait in the queue, as the parallel jobs documentation explains.

Self-hosted agents change the Azure DevOps pipeline pricing a lot: an extra job costs $15 instead of $40, and minutes are unlimited. The catch is that the machines, their patching and monitoring become your cost and your team’s time. If your pipelines need a redesign before you can tell which option fits, AppRecode’s CI/CD consulting team can review the setup, and our guide to CI/CD best practices that work in production covers how to shorten build times first.

Azure Artifacts hosts NuGet, Maven, npm and Python packages. Each organization gets 2 GiB free. Above that, you pay by tier per month:

• 2–10 GiB: $2 per GiB
• 10–100 GiB: $1 per GiB
• 100–1,000 GiB: $0.50 per GiB
• over 1,000 GiB: $0.25 per GiB

The limit applies to the whole organization, not to each project or feed, so every team’s packages count toward the same 2 GiB. Storage grows fastest when CI publishes a new package version on every build and nobody deletes the old ones. Set retention policies on your feeds to keep only the last N versions, and the bill tends to stay close to zero.

Three more items can appear on the invoice.

GitHub Advanced Security for Azure DevOps is sold in two parts: Code Security at $30 and Secret Protection at $19 per active committer per month. For a team with 20 active committers, Code Security alone costs $600 per month, which is more than the user licenses of most of the teams in the examples below.

Paid extensions from the Visual Studio Marketplace are billed by their own price lists. Check what is installed in your organization, because some extensions charge per user.

All charges go through the Azure subscription linked to your organization. Your Azure DevOps subscription is not a separate contract: user licenses, parallel jobs, Artifacts storage and GHAS all show up on the same Azure bill, and you can watch them in Cost Management.

The examples below show the Azure DevOps price for typical team setups, using list prices from October 23, 2026. They count user licenses, Microsoft-hosted parallel jobs and Artifacts storage.

These numbers leave out GitHub Advanced Security, paid extensions and taxes. GHAS can easily become the largest line: 20 active committers × $30 = $600 per month for Code Security. The biggest savings in the larger examples come from giving managers Stakeholder access, using the Visual Studio Subscriber level for anyone with a subscription, and moving long builds to self-hosted agents.

To estimate your monthly bill, you need a list of people and a look at your pipeline queue. Start with people, because user licenses are the most predictable part. Then add pipelines, which depend on how your team works, not on headcount. Storage and add-ons come last.

1. Sort everyone into access levels: Stakeholder, Basic, Basic + Test Plans, and Visual Studio or GitHub Enterprise users. Subtract the five free Basic seats.
2. Decide how many builds need to run at the same time. Look at the pipeline queue during your busiest hours, not at the average day.
3. Estimate how much package storage you’ll keep after retention policies, and subtract the free 2 GiB.
4. Add GitHub Advanced Security per active committer, plus any paid extensions.
5. Enter the numbers in the Microsoft pricing calculator under Azure DevOps to get a monthly figure in your currency.

Review the estimate after the first two or three months, when you can compare it with the real bill in Azure Cost Management.

1. Azure DevOps Server is the on-premises version. It makes sense when data has to stay in your own data center, or when the build network has no internet access. According to Microsoft’s Server pricing page, there are two ways to license it.The first is a monthly payment through Azure, with no long-term commitment. You can cancel any time, and the same licenses give users access to Azure DevOps in the cloud as well:
   • Basic: $6 per user per month
   • Basic + Test Plans: $52 per user per month
   • Visual Studio Professional: $45 per user per month
   • Visual Studio Enterprise: $250 per user per month

   The second is the classic model: a server license plus client access licenses (CALs) bought through an authorized reseller with a three-year commitment. Microsoft doesn’t publish these prices, so ask a reseller for a quote. A Visual Studio subscription already includes one server license and a CAL for the subscriber.

   The license is only part of the Azure DevOps Server pricing. Both options need a Windows or Windows Server license, plus your own servers, backups, upgrades and the people who maintain all of it. For teams without strict hosting requirements, those running costs are often higher than paying for the cloud service.

Most savings come from cleaning up access and buying pipeline capacity based on data. A short list to go through each quarter:

• Review users. Remove people who left and downgrade those who haven’t committed code in months.
• Use Stakeholder access for managers, designers and clients who only view and comment.
• Assign the Visual Studio Subscriber level to subscribers, so you don’t pay for Basic before their first sign-in.
• Buy parallel jobs based on the queue. Add a job when builds wait for agents, not “just in case.”
• Run long builds on self-hosted agents, where an extra job costs $15 and minutes are unlimited.
• Set retention policies on Artifacts feeds and pipeline runs.
• Set Azure budgets and cost alerts on the subscription that pays for Azure DevOps, so a jump in usage shows up before the invoice.

If you’d rather have someone else watch the bill and the access list, AppRecode’s Azure managed cloud services cover Azure DevOps administration together with the rest of your Azure environment.

Azure DevOps pricing is simple once you split it into users, pipelines and storage. A team of five developers pays nothing. Beyond that, each Basic user costs $6 a month, QA engineers who manage test plans cost $52, and each Microsoft-hosted parallel job costs $40. GitHub Advanced Security is the add-on that can change the total the most, so price it separately before you turn it on.

Azure DevOps Basic is free for the first five users. Starting with the sixth Basic user, Microsoft’s current US list price is $6 per user per month. That means a team with six Basic users pays $6 monthly, not $36. A team with 20 Basic users pays for 15 seats, or $90 per month at the current list price. The calculation changes if some people qualify for other access types. Stakeholders are free but have limited capabilities, while eligible Visual Studio subscribers and qualifying GitHub Enterprise users can receive Azure DevOps access without consuming one of the five free Basic seats.

Do not apply the five-user allowance to every license type. Basic + Test Plans is currently listed at $52 per assigned user per month and does not have five free production seats, although Microsoft offers a 30-day trial. Pipeline capacity, artifact storage above 2 GiB, GitHub Advanced Security features, and some extensions are also billed separately from user access.

There is one less obvious exception for companies using several Azure DevOps organizations. With multi-organization billing enabled under the same Azure subscription, Microsoft can charge a human user only once across those organizations. Before you count five free Basic users in each linked organization, check how Microsoft’s billing documentation applies the free seats to your setup. For a reliable estimate, count actual access assignments, remove free entitlements, and price the separately metered services before applying regional taxes or contract discounts.

Yes, Azure DevOps Services can be used without a paid user plan, but “free” comes with specific limits. Each organization can assign Basic access to its first five users at no charge. Basic covers the everyday collaboration features most small development teams need, including Boards, private Git repositories in Repos, and access to Pipelines. An organization can also add unlimited Stakeholder users for free. Stakeholder access is intended for people who mainly work with items and dashboards; it is not a free substitute for a developer’s Basic license because several Agile planning, repository, and administrative capabilities are unavailable.

The service allowances matter too. Microsoft currently includes 2 GiB of Azure Artifacts storage per organization, one self-hosted pipeline parallel job with unlimited minutes, and one Microsoft-hosted parallel job with 1,800 minutes per month for private projects. A Microsoft-hosted job is limited to 60 minutes per run while it uses the free grant. Microsoft’s documentation also says an eligible Azure subscription must be linked to the organization to request the free Microsoft-hosted grant, so teams should not assume hosted capacity will always appear automatically.

Costs begin when the organization adds a sixth paid Basic user, assigns Basic + Test Plans, buys pipeline capacity, exceeds the Artifacts allowance, or activates separately priced security and marketplace services. So the honest answer is that Azure DevOps has a useful free tier, not that every Azure DevOps workload is free indefinitely.

For a small private organization, the free offer combines user access with several service-level allowances. The first five users can receive Basic access. That gives them Azure Boards for work tracking and planning, Azure Repos with unlimited private Git repositories, dashboards and wikis, plus the ability to use Azure Pipelines and Azure Artifacts. Unlimited users can instead be assigned the free Stakeholder level, but their permissions are intentionally narrower. For example, Stakeholders can participate in work tracking, while advanced Agile planning and repository features generally require Basic access.

At the organization level, Azure Artifacts includes the first 2 GiB of storage. For private projects, Azure Pipelines includes one Microsoft-hosted parallel job with up to 1,800 minutes per month and one self-hosted parallel job with unlimited minutes. The hosted free job has a 60-minute limit per run. Microsoft notes that the self-hosted grant is automatic, while the Microsoft-hosted grant must be enabled for an eligible organization linked to an Azure subscription.

The phrase “free Azure Test Plans” needs care. Basic users can perform certain testing-related actions, such as running tests associated with work, but creating and managing full Test Plans requires the separately priced Basic + Test Plans access level. The free tier also does not cover extra pipeline concurrency, storage above 2 GiB, paid extensions, or optional security products. Finally, Microsoft is retiring public projects and plans to convert remaining public projects to private in 2027, so estimates should use the current private-project limits rather than older public-project allowances.

Build the estimate from a real user list. A headcount alone is misleading because not everybody needs the same access. Mark each person as Basic, Basic + Test Plans, Stakeholder, an eligible Visual Studio subscriber, or a qualifying GitHub Enterprise user. With Microsoft’s current US prices, five Basic seats are free and each additional Basic seat is $6 per month. Basic + Test Plans is $52 for every user who receives it. Someone who only checks a dashboard may be fine as a Stakeholder; a tester who maintains formal test suites probably is not.

Now look at pipelines. What matters is the highest number of jobs that must run at once, not how many builds the team starts in a month. Note whether they use Microsoft-hosted or self-hosted agents and whether 1,800 free hosted minutes will cover normal usage. An extra hosted parallel job currently lists at $40 per month; an extra self-hosted slot lists at $15. Include Artifacts storage over the free 2 GiB, paid extensions, and optional GitHub Advanced Security products as separate lines. GitHub Advanced Security currently lists at $30 per active committer per month for Code Security and $19 for Secret Protection, so it is easy to miss when concentrating on user licenses and can outweigh them.

I would calculate three totals: today’s normal month, a heavy release month, and the expected team size six to twelve months from now. If employees work across several organizations, check whether multi-organization billing can stop the same person being billed twice. Compare the estimate with Azure’s actual invoice and access assignments each month. Before publishing a budget, reopen Microsoft’s pricing page in the organization’s billing currency: taxes, regional pricing, enterprise agreements, and negotiated discounts can make the final amount different from a simple USD calculation.

Yes, although one small account detail decides whether the benefit actually appears. The Azure DevOps sign-in must match the identity connected to an active Visual Studio subscription. When it matches, Microsoft assigns subscriber access automatically. The company does not need to purchase another Basic seat, and that person does not use one of the organization’s five free Basic places. Microsoft allows the benefit to follow the subscriber across multiple Azure DevOps organizations.

Suppose a developer’s subscription belongs to alex@company.com, but the administrator invites a personal Microsoft account. Azure DevOps may see two different people and classify the invited account as an ordinary Basic user. The fix is not to buy another license immediately. First, open Organization settings > Users, inspect the displayed access level, and confirm that the invited email is the one listed for the Visual Studio subscription. Microsoft checks eligibility at sign-in and again periodically, so the access level can also change after a subscription expires or moves to someone else.

The subscription edition matters as well. Visual Studio Professional and Enterprise provide their corresponding subscriber access levels. Each active Visual Studio Enterprise subscriber also contributes one extra self-hosted Azure Pipelines parallel job to every Azure DevOps organization where that person is a member. It is a self-hosted slot, not an extra Microsoft-hosted job. Visual Studio Dev Essentials, despite the similar name, does not automatically provide this paid-subscriber entitlement.

Keep renewal dates and assigned owners in the license inventory. If a subscription ends, decide whether the user still needs Basic or Basic + Test Plans before access is disrupted. That simple check keeps both the permissions and the cost forecast honest.

A parallel job is a concurrency slot: it controls how many pipeline jobs can run at the same time, not how many agent machines are registered. Registering more self-hosted agents does not increase throughput if you only have one parallel job. Each extra Microsoft-hosted job costs $40 per month and each extra self-hosted job costs $15. The first paid hosted job only removes the free slot’s minute and per-run limits, so two concurrent hosted builds need two paid jobs. Before buying capacity, check queue time and peak concurrency. A team whose jobs rarely overlap may get more from caching or better schedules than from another slot. The pipelines section above has the full breakdown.

Basic + Test Plans is meant for the people who run a formal manual-testing practice, not automatically for everyone assigned to a project. A QA lead who builds test plans and suites, organizes reusable test cases, coordinates user-acceptance testing, or needs centralized manual-test reporting is a likely candidate. Microsoft’s current US list price is $52 for each assigned user per month, and there is a 30-day trial. Use that trial during a real testing cycle rather than deciding from a feature list.

Most developers can stay on Basic. It already covers Boards, Repos, Pipelines, dashboards, and normal collaboration. Basic also permits some testing tasks, including web-based test execution and running tests from a Kanban board. The boundary is easy to blur: those capabilities do not give the user the full Azure Test Plans management experience. Microsoft’s comparison table explicitly reserves creating and managing Test Plans for Basic + Test Plans.

A practical way to decide is to ask what the person will do next week. Will they merely see a test result, fix an automated test, or run a test attached to a work item? Basic will often be sufficient. Will they design suites, manage manual cases across configurations, conduct exploratory sessions, and own acceptance-test reporting? The premium level is more plausible. Someone who only reviews status might need only Stakeholder access.

Assign the license by responsibility and review it when roles change. Do not give every engineer Basic + Test Plans just because the project contains test cases. After the trial, record which paid-only functions were actually used and retain premium access only for the people who need them. That produces a defensible license decision instead of a blanket $52-per-person assumption.

Begin with a quarterly access review. Remove departed or dormant identities, downgrade genuine occasional reviewers to Stakeholder, and keep Basic for people who need code, planning, or full collaboration features. Assign Basic + Test Plans only to users who create or manage structured manual test plans. Also match Visual Studio subscribers and qualifying GitHub Enterprise users to the correct identity so their included access is recognized. This reduces spend without sharing accounts or granting broader permissions than a role requires.

For pipelines, buy capacity from measured queue data rather than from the number of agents. Separate waiting caused by insufficient parallel jobs from slow builds caused by poor caching, oversized artifacts, or serial pipeline design. Schedule nonurgent jobs outside release peaks and use self-hosted agents only when their infrastructure, maintenance, patching, and security costs are genuinely lower than the hosted option. Remember that the first paid Microsoft-hosted parallel job removes the free slot’s time limits but does not add a second concurrent slot.

Control storage by setting retention policies for packages and pipeline artifacts, deleting obsolete versions according to your recovery requirements, and monitoring the 2 GiB free Azure Artifacts allowance. If the same employees work in several organizations, evaluate multi-organization billing under one Azure subscription so a human user is not charged repeatedly; check how the five free Basic seats apply once organizations are linked. Finally, set Azure budgets and cost alerts, require an owner for paid extensions and security add-ons, and reconcile invoices with current access assignments monthly. Cost control should come from accurate entitlements and usage, never from shared credentials or excessive Stakeholder permissions.