The price gap, in one table
Azure DevOps charges per user, per access level. The jump from Basic to Basic + Test Plans is the largest single line item in most orgs' licensing — and the one most often assigned by habit rather than need.
| Access level | Cost | What you get |
|---|---|---|
| Stakeholder | Free | Work items & dashboards, limited access |
| Basic | ~$6/mo | Full features except Test Plans |
| Basic + Test Plans | ~$52/mo | Everything in Basic, plus Test Plans |
Basic + Test Plans is about 9× the cost of Basic — a delta of roughly $46 per user per month, or ~$552 per user per year. On a single over-tiered seat that's noise; across a dozen of them, it's real budget.
What Test Plans actually adds
Everything in Basic — repos, pipelines, boards, pull requests, dashboards — is included in both tiers. The only thing the extra ~$46 buys is the Azure Test Plans capability set:
- Test-case management — authoring and maintaining structured, reusable test cases.
- Test suites and test plans — organizing those cases into suites and plans mapped to work.
- Manual test execution & tracking — running test cases by hand and recording pass/fail outcomes and results over time.
If none of that describes a person's day, they are paying ~9× for features they never open.
Who genuinely needs it — and who doesn't
The dividing line is simple: does this person author or run test plans?
| Role / behavior | Needs Test Plans? | Right tier |
|---|---|---|
| QA engineer authoring & running test cases | Yes | Basic + Test Plans |
| Tester managing suites & manual runs | Yes | Basic + Test Plans |
| Developer writing code & reviewing PRs | No | Basic |
| Manager reading dashboards only | No | Stakeholder (free) |
The key case is the third row. A developer who only writes code and reviews pull requests generally does not need Test Plans — everything they do is covered by Basic. Yet these are exactly the users who often end up on Basic + Test Plans, because a team was licensed as a block or the higher tier was assigned "to be safe."
How to spot over-tiered users
An over-tiered user is active — so you can't find them by looking at inactivity — but assigned Basic + Test Plans without doing test-management work. To find them:
- List every user currently on Basic + Test Plans.
- For each, ask the simple question: are they authoring test cases, organizing test suites, or executing and tracking manual test runs?
- If the honest answer is no — their work is coding, PR review, or dashboard-watching — they're over-tiered.
Because these seats belong to active users, over-tiering is contingent savings: it depends on a quick check of who really uses Test Plans, rather than on a hard signal like a stale last-access date.
How to downgrade safely
Downgrading is low-risk. Changing a user's access level from Basic + Test Plans to Basic does not delete any work items, commits, or history. The user keeps every Basic feature and simply loses the Test Plans capability — which, for an over-tiered user, they weren't using. If someone turns out to need it later, you re-assign the tier in a couple of clicks. Each downgrade recovers ~$46/user/month.
See who's over-tiered on Test Plans — free
HALA (Helix ADO License Auditor) scans your Azure DevOps org with a read-only token and flags every Basic + Test Plans seat that could drop to Basic — with the recoverable spend attached. The headline scan is free.
Run a free audit →Frequently asked questions
What is the difference between Basic and Basic + Test Plans?
Basic gives full Azure DevOps features except Test Plans. Basic + Test Plans adds test-case management, test suites and plans, and manual test execution and tracking. Basic is about $6 per user per month; Basic + Test Plans is about $52 — roughly nine times the cost, a delta of about $46 per user per month.
Who actually needs a Basic + Test Plans license?
People who author or run test plans: QA engineers and testers who manage test cases, organize test suites, and execute and track manual test runs. A developer who only writes code and reviews pull requests generally does not need Test Plans and can run on Basic.
How do I spot over-tiered Test Plans users?
Look for active users assigned Basic + Test Plans who are not authoring test cases or executing test runs. Their day-to-day work is coding and PR review, not test management. Those seats are over-tiered and can be downgraded to Basic, saving about $46 per user per month.
Is it safe to downgrade from Basic + Test Plans to Basic?
Yes. Downgrading a user's access level does not delete any work items, commits, or history. The user keeps full Basic functionality and only loses Test Plans features — which, for an over-tiered user, they were not using anyway.