Azure DevOps Pricing, Decoded for the Broke Founder (2026)

The Contract That Made Me Read the Azure DevOps Pricing Page Twice

Sometime in 2022, I took on contract work for a company that ran everything on Microsoft. Windows laptops, Outlook calendars, and — the part I dreaded — the whole software delivery pipeline on Azure DevOps. I’d lived in GitHub for years by then. Muscle memory. So when they handed me an Azure DevOps org and said “your repos and pipelines are in here,” I felt like someone had rearranged my kitchen while I was asleep.

I did what I always do when a big-company tool makes me uneasy: I opened the pricing page and started doing math in my head, converting every dollar to rupees like it was a silent exam. And here’s the thing — Azure DevOps pricing is genuinely not that expensive. It’s just structured in a way that catches you off guard, because it doesn’t bill the way GitHub trained you to expect. Two different products cost you money, and they’re not the two you’d guess.

Let me hand you the version of this that takes ten minutes instead of a contract’s worth of confusion.

---

What Azure DevOps Actually Is (Five Tools in One Login)

Azure DevOps isn’t one product. It’s five, bundled behind a single organization and a single bill. That bundling is the whole personality of the thing, and it’s why the pricing looks weird until it clicks.

• Azure Boards — work tracking. Kanban boards, backlogs, sprints. Think Jira, but from Microsoft.
• Azure Repos — Git hosting. Push code, open pull requests, protect branches. This is the GitHub-equivalent core.
• Azure Pipelines — CI/CD. Build, test, deploy. This is where the parallel-jobs pricing lives, and where most of the confusion starts.
• Azure Artifacts — a package feed. Host your npm, NuGet, Maven, or Python packages privately.
• Azure Test Plans — manual and exploratory testing tools for QA teams.

For a solo founder, that’s four tools you’ll never open and one (Repos + Pipelines) that GitHub already does. Keep that in your head — it’s the lens for every number below. You are not the customer this product was designed for, and the pricing quietly tells you so.

---

The Free Tier: Better Than You’d Expect

Here’s where Azure DevOps genuinely surprises people who assume “Microsoft = expensive.”

The first 5 users are free, and that free tier is not a crippled demo. Those five users get Azure Boards, Azure Repos with unlimited private repositories, and Azure Pipelines. That’s a real, working software delivery stack for a small team, at zero dollars. It’s roughly in line with what the rest of the industry offers — GitLab and Bitbucket both cap their free tiers at 5 users too, and I broke down that whole GitLab comparison here.

Past five users, you buy Basic access at $6 per user per month. That’s the seat cost for Boards and Repos. It’s more than GitHub’s cheapest paid seat — GitHub Team runs about $4 a user — but it’s not outrageous, and for the first five people it’s free where GitHub charges from the first paid feature.

There’s also a Stakeholder access level that’s free for unlimited users. Stakeholders get limited features — view and edit work items, see dashboards, run pipelines — but not full Repos or Boards. For a non-technical co-founder who just wants to peek at the board, that’s a free seat that doesn’t count against anything.

The free tier isn’t a trial you graduate from next week. For a small team it’s the plan you live on for a year. Azure DevOps’s five-free-users tier is one you genuinely can.

So far, so reasonable. Then you get to Pipelines, and the pricing model changes shape entirely.

---

Azure Pipelines: The Parallel-Jobs Model Nobody Explains Well

This is the part that made me read the page twice.

Azure Pipelines does not charge you per build minute the way GitHub Actions meters overage. It charges you for parallel jobs — the number of pipeline jobs that can run at the same time. Microsoft’s own analogy is a swimming pool: one parallel job is one lane. You can queue up as many swimmers (pipeline runs) as you want, but with one lane, only one swims at a time. The rest line up and wait. Want more people in the water at once? Buy more lanes.

There are two kinds of lanes, and they’re priced completely differently.

Microsoft-hosted jobs (Microsoft’s servers)

This is the zero-setup option — Microsoft runs the build agent for you. The free tier gives you one Microsoft-hosted parallel job, capped at 1,800 minutes a month (that’s 30 hours), with each individual job limited to 60 minutes. For a solo founder pushing a handful of builds a day, 30 hours is plenty.

When you outgrow it, each extra Microsoft-hosted parallel job costs $40 a month — and buying it also lifts the limits: paid jobs run up to 360 minutes each with no monthly cap. Here’s the catch that trips people up: buying your first paid job doesn’t give you two lanes. It just removes the time limit on the one lane you already had. To actually run two builds concurrently, you buy two parallel jobs.

Self-hosted jobs (your own machine)

If you bring your own build machine — a spare VPS, a beefy desktop in the corner — the math shifts hard in your favor. For private projects, the free tier is one self-hosted parallel job with no time limits at all, plus one extra free job for every active Visual Studio Enterprise subscriber on the team. Unlimited minutes. And each additional self-hosted parallel job is $15 a month, versus $40 for Microsoft-hosted.

So the real Pipelines decision is: pay Microsoft $40 to not think about the build agent, or run your own hardware and pay $15 (or nothing) for the same concurrency. For a broke founder who already has a cheap server lying around, self-hosted is the obvious lever. For everyone whose time is worth more than the setup, Microsoft-hosted is the “just make it work” button.

---

Artifacts and Test Plans: The Add-Ons You’ll Probably Skip

Two more line items, and they’re the ones most solo founders never touch.

Azure Artifacts is the private package feed. You get 2 GiB of storage free, and past that it’s $2 per GiB per month. If you’re publishing internal npm or NuGet packages across a bunch of services, this is genuinely useful. If you’re one person shipping one app, you’ll never come near the free 2 GiB, so it costs you nothing and you can forget it exists.

Azure Test Plans is the expensive one, and it’s aimed squarely at dedicated QA teams. It runs about $52 per user per month on top of everything else — and Microsoft licenses it per person, so everyone who needs the manual-testing tools needs their own seat. For a founder writing their own tests in code, this is pure enterprise overhead. Skip it entirely. It’s not a tax on you; it’s a tax on the 200-person company with a separate testing department.

---

The Honest Comparison: Azure DevOps vs GitHub

Since Microsoft owns both Azure DevOps and GitHub (it bought GitHub in 2018), the real question isn’t “Azure DevOps vs the world.” It’s “why would a small team pick Azure DevOps over the GitHub that Microsoft is clearly pouring its future into?” Here’s the honest scoreboard for someone small.

Line item	Azure DevOps	GitHub
Free users	First 5 free	Unlimited collaborators
Cheapest paid seat	Basic, $6/user/mo	Team, ~$4/user/mo
Free CI	1 job, 1,800 min/mo	2,000 min/mo (private)
Extra CI capacity	$40/job (hosted), $15 (self)	~$0.006/min over allowance
Ecosystem / AI fluency	Enterprise, Microsoft shops	The whole world
Best for	Big orgs already on Azure/Microsoft	Solo founders, indie hackers, open source

The numbers are close enough that price isn’t the deciding factor. GitHub’s free tier has no user cap, which matters the moment you add a couple of contractors — the same asymmetry I flagged in GitHub vs GitLab. But the real gap is the one that never shows up on a pricing page: ecosystem. Every open-source dependency lives on GitHub. Every developer you hire already has a GitHub account. Every AI coding model was trained on mountains of GitHub code and GitHub-flavored workflows, so when you’re stuck at midnight, the GitHub answer is the first search result and the Azure DevOps answer is the fourth. That’s a quiet time tax you pay on Azure DevOps every single day, and time is the one resource a broke founder can’t buy back.

---

The Broken Engineer Take: You Almost Certainly Want GitHub

Let me be blunt, because that’s the whole point of this blog.

Azure DevOps is enterprise gear. It’s a beautifully complete, single-vendor delivery platform built for companies that already live inside Microsoft — Azure subscriptions, Active Directory logins, Visual Studio Enterprise licenses, a QA team that needs Test Plans, a project manager who lives in Boards. If you’re that company, Azure DevOps is a rational, even excellent choice, and there’s zero reason to fight it. The integration with the rest of Azure is real and it’s good.

But you’re probably not that company. You’re one person, or three, trying to ship a SaaS before the money runs out. For you, Azure DevOps is five tools where you need one and a half, wrapped in a billing model you have to study before you understand it. That’s friction, and friction is the enemy when your scarcest resource is time.

The move is boring and correct: push your code to GitHub. It’s free for your whole tiny team, the CI allowance is generous, the ecosystem saves you an hour a week you didn’t know you were spending, and Copilot is native. If you ever have a reason to leave — privacy, self-hosting, a client contract — I laid out every real alternative in the GitHub alternatives roundup, and the Atlassian-world case in Bitbucket vs GitHub. Azure DevOps isn’t on those “escape from GitHub” lists for a reason: you’d only land on it if your company was already Microsoft to the bone, not because you chose it on the merits as a founder.

I finished that 2022 contract on Azure DevOps, learned Boards and Pipelines well enough to be useful, converted the invoice to rupees one last time, and pushed every one of my own projects — including Clickly, my over-engineered little URL shortener that earns exactly zero paisa — right back to GitHub, where they’ve stayed ever since. Not because Azure DevOps is bad. It genuinely isn’t. But because I’m not the customer it was built for, and neither, probably, are you.

---

Azure DevOps pricing isn’t a trap — it’s just enterprise pricing, honest about who it’s for. Five free users, $6 a seat after, a parallel-jobs model that costs $40 (hosted) or $15 (self-hosted) per lane, and a couple of add-ons you’ll never open. Decode it once and it stops being scary. But decoding it is itself the tell: a tool that needs a study session before you understand the bill was built for a procurement department, not a founder pushing code at 1 AM. Your git host is not your moat — your product is barely your moat either, distribution is. So unless you’re already Microsoft to the core, push to GitHub, wire up a lean pipeline, set your limits so a runaway job can’t quietly bleed you, and go get someone to use the thing you built. (And if you’re stitching the rest of the stack together on fumes, the broke solopreneur’s survival guide is the bigger map.)

This is the Broken Engineer Guide. I over-engineer everything, fail at business, and hand you the shortcut so you don’t lose the same nights I did. Now go commit something that matters.