Engineering Excellence
Guide · Azure DevOps cost

How to reduce Azure DevOps license costs without losing access

Most Azure DevOps overspend is not a pricing problem but a utilization problem. Paid seats sit assigned to people who left, went inactive, or never needed the tier they are on. Here is how to find that spend and recover it, using data Azure DevOps already keeps.

July 27, 2026, updated November 5, 2026

What you actually pay for in Azure DevOps

Azure DevOps charges per user, per access level. Two of those levels cost money; the rest do not. Knowing the difference is the whole game, because most waste hides in paid seats that should be on a free level, or on no seat at all.

Azure DevOps access levels · monthly cost per user
Access levelCostNotes
StakeholderFreeLimited access: work items and dashboards
Basicabout $6 per monthFull features except Test Plans
Basic + Test Plansabout $52 per monthAdds test-case management & test execution
Visual Studio subscriberFree*Covered by an existing VS subscription

*A user with a Visual Studio subscription is entitled to Basic-level access at no extra Azure DevOps charge. If they are assigned a paid Basic seat anyway, you are paying twice.

The three sources of Azure DevOps license waste

Every dollar of recoverable spend falls into one of three buckets. The first two are firm: you can act on them today. The third needs a quick human check.

1. Inactive paid seats (firm waste)

Azure DevOps records a last-access date for every user under Member Entitlement Management. A paid user (Basic or Basic + Test Plans) who has not accessed the org in six months or more, or has never accessed it at all, is almost certainly recoverable spend. These are people who left, changed teams, or were provisioned "just in case."

2. Trending-stale seats (near-term risk)

Paid users inactive for three to six months are on the way to becoming firm waste. They are worth a review now, before another two quarters of spend go out the door.

3. Over-tiered seats (contingent savings)

Basic + Test Plans costs roughly nine times what Basic costs. Any active Basic + Test Plans user who is not actually authoring or running test plans is over-tiered. Downgrading them to Basic keeps their access intact and cuts about $46 per user per month. This one needs a quick check of who genuinely uses Test Plans, hence "contingent."

Worked example · illustrative 180-user org
FindingActionAnnual recovery
15 Basic seats inactive 6+ monthsRevoke~$1,080
10 Basic seats 3–6 months staleReview & revoke~$720
~8 over-tiered Basic + Test PlansDowngrade to Basic~$4,400

That is roughly $6,200 a year for this example org, recovered without a single person losing the access they actually use. Your figure depends on your own seat mix, so compute it from your own entitlement data.

A phased plan that will not break active work

  • Phase 1, Revoke (days 0–30): remove paid seats inactive 6+ months and never-accessed users. Firm savings, low risk.
  • Phase 2, Right-size (days 30–60): review 3–6 month stale seats, and downgrade over-tiered Basic + Test Plans users to Basic.
  • Phase 3, Prevent recurrence (days 60–90): set a recurring review so reclaimed seats do not quietly refill. Waste is a flow, not a one-time cleanup.

How to do this without a spreadsheet marathon

You can pull user entitlements and last-access dates from the Azure DevOps API yourself and reconcile them by hand each quarter. Or you can point a tool at the org and have the whole picture in a few minutes: every paid seat, its tier, its months of inactivity, and a phased savings plan.

See how Helix reports license use

Helix Delivery Intelligence includes License Utilization, which is designed to report paid Azure DevOps seats by access level and last access.

Book a Product Walkthrough →

Frequently asked questions

How much does an Azure DevOps license cost?

Basic is about $6 per user per month and Basic + Test Plans is about $52 per user per month. Stakeholder access is free, and users covered by a Visual Studio subscription get Basic-level access without a paid seat.

How do I find inactive Azure DevOps users?

Azure DevOps records a last-access date for every user under Member Entitlement Management. Paid users inactive for six months or more (or never accessed) are the clearest candidates to revoke; three-to-six-month inactivity is trending stale.

Will revoking a license delete any work?

No. Removing or downgrading an access level does not delete their work items, commits or history; it only changes what they can do going forward. That is why revoking inactive seats is low-risk.

How much can I typically save?

How much you can save depends on your seat mix. Inactive, never-accessed and over-tiered seats are the three places to look, and last-access data shows which seats fall into each.