Atlas AVD Pricing Explained: Flat-Rate Licensing That Scales With You

Atlas AVD pricing licenses the management platform per tenant, not your user count. Here is how flat-rate AVD licensing works, why unlimited AVD users lowers total cost of ownership as you grow, and answers to the Azure Virtual Desktop pricing questions buyers ask most.

By David,

✓ Unlimited AVD users · ✓ Unlimited technician seats · ✓ Flat monthly pricing · ✓ No growth penalty

That is the whole model in one line: Atlas AVD licenses the management platform, not your headcount. What you pay to manage 200 desktops is what you pay to manage 2,000.

Most Azure Virtual Desktop evaluations begin with features and end with a spreadsheet. Somewhere between the demo and the purchase order, someone asks the question that actually decides the outcome: what does this cost once we have 900 users instead of 200?

Atlas AVD answers that question the same way at every size, because Atlas AVD pricing is not calculated from your user count. This article explains the licensing philosophy behind that decision, what it means for your budget, and how we answer the Azure Virtual Desktop pricing questions prospective customers ask us most.

The short version: Atlas AVD licenses the management platform, not the people who use your desktops.

Every plan includes unlimited AVD users and unlimited technician seats. When your organization grows, your Atlas AVD invoice does not.


How Azure Virtual Desktop management is usually priced

The AVD management category has largely converged on two billing shapes, and both are legitimate business models built by serious engineering teams:

  • Per-user licensing. The platform bills per named user, per concurrent user, or per managed desktop. Your management cost tracks headcount.
  • Consumption-based licensing. The platform bills as a share of Azure spend or against metered activity. Your management cost tracks usage.

There is real logic to both. They tie the vendor's revenue to the value the customer is getting, which is a defensible way to build a software company, and organizations with stable headcount often find them perfectly workable. Plenty of good AVD teams run happily on per-user platforms.

They do share one characteristic that is worth understanding before you sign, and it is a structural fact rather than a criticism: the cost of managing Azure Virtual Desktop moves in the same direction as your AVD estate. Onboard a division, close an acquisition, or migrate another 400 people off physical desktops, and the management line item moves with them. That is the model working exactly as designed. It just means growth carries a software cost as well as an infrastructure cost.

Side by side, the two approaches to Azure Virtual Desktop pricing line up like this:

What you compareTypical per-user licensingAtlas AVD
Billing basisPer user, per desktop, or a share of Azure spendFlat rate, per tenant, per month
Cost when you add usersRises with headcountUnchanged
Monthly costVariablePredictable
Cut of your Azure billA percentage, in some modelsNone
Growth penaltyCost rises with each user addedNone

Comparison based on publicly listed per-user pricing models, not on any single vendor's quote.

Neither column is wrong; they simply optimize for different customers. Atlas AVD was designed around the right-hand column, from a different starting assumption.


What Atlas AVD licenses instead

The premise is simple: the work the platform performs does not change much when you add users to a host pool.

Autoscaling a pool of 40 session hosts is the same orchestration problem whether 300 or 3,000 people connect to it. Watching for quota exhaustion, right-sizing SKUs, draining hosts before an update, keeping an audit trail, surfacing cost anomalies: none of it gets structurally harder because headcount went up. So Atlas AVD prices the thing it actually delivers: the management platform, licensed flat, per tenant, per month.

"We would rather earn more customers than more users per customer."

Your plan determines the capabilities you get, and your licensed tenant quantity how many Azure tenants you manage. Neither counts the people connecting to your desktops.

In practice that means:

  • Unlimited AVD end users on every plan, including the free Community edition
  • Unlimited technician seats on every plan: every admin, engineer, and technician on your team can sign in, with no per-seat charge
  • No per-user, per-desktop, or per-session-host platform fee
  • No percentage-of-Azure-spend fee: Atlas AVD does not take a cut of your cloud bill
  • A published monthly price you can put in a budget before you talk to anyone

Why this matters for planning: flat-rate AVD licensing turns your management platform from a variable cost into a fixed one. Fixed costs are easy to forecast, easy to defend in a budget review, and easy to compare across three-year horizons.

The one limit that counts users, stated plainly

We would rather you hear this from us than find it in a contract.

The User Portal (the branded portal where your end users sign in to see and launch their assigned desktops) is available on every plan and metered by use: $1 per distinct active portal user per calendar month, drawn from your plan's included pooled unit allowance, shared across every metered module (10 units a month on Community and 50 per licensed tenant on Atlas AVD). That meter is separate from the flat platform fee, and separate again from your unlimited AVD users. A person only costs anything in a month they actually sign in to the portal. On top of the meter, Community caps the number of distinct active portal users per calendar month, while every paid plan is unlimited:

PlanSelf-service portal users
CommunityUp to 10 active users per month
Atlas AVDUnlimited

An "active user" is a distinct person who signs in at least once in a calendar month, counted once no matter how often they connect, and billed $1 for that month. Past the limit, additional portal users need a plan upgrade rather than an overage charge: a user turned away at the cap never signs in, so is never billed.

The core platform (host pool management, automation, cost intelligence, governance, everything you use to operate AVD) is licensed flat and is never billed per user, on any plan. Four optional modules are the deliberate exception, all metered in units drawn from your plan's included pooled unit allowance, which they share (10 units a month on Community and 50 per licensed tenant on Atlas AVD): the End User Portal above at $1 per active user per month, Atlas Ink managed email signatures at $1 per active user per month, Atlas Reach at $1 a month per managed device that is not an AVD session host (an Azure VM that is not a session host is billed), and Atlas Spool at 5 units per managed printer, charged once. Atlas Resolve DNS filtering is included with Atlas Reach and uses no units of its own. You are billed for them only in the months people actually use them, so they never turn the flat platform license into a per-headcount bill.


Atlas AVD pricing at a glance

One paid plan, every AVD feature, one flat price per tenant: $199 per tenant, unlimited AVD users, every AVD feature, and MSP capabilities for $50 more per tenant if you want them. Community stays free for one tenant.

What you buyMonthly price per tenantTenantsAVD users
Community$01Unlimited
Atlas AVD$199From 1, as many as you licenseUnlimited
MSP Capabilities (optional upgrade)+$50Every licensed tenantUnlimited

Every tenant you manage counts, including your own home tenant.

The full plan-by-plan feature matrix lives on the Atlas AVD pricing page.

Azure costs are separate, and they stay yours. Atlas AVD deploys into your own Azure tenant via ARM templates. Microsoft bills your subscription directly for compute, storage, and networking. Atlas AVD never resells, marks up, or takes a percentage of your Azure spend; it works to reduce it.


Why flat-rate licensing lowers total cost of ownership

The interesting arithmetic is not the sticker price. It is the effective platform cost per user, which under a flat-rate model falls every time you grow, because the numerator holds still while the denominator rises.

Take one Atlas AVD tenant at $199 per month:

AVD usersEffective platform cost per user per month
250$0.80
500$0.40
1,000$0.20
2,500$0.08

Nothing about the plan changed across those rows. The denominator did. (These figures are the Atlas AVD management fee only; your Azure consumption is billed separately by Microsoft and scales with infrastructure, not with this line.)

Under any headcount-linked model, that same table is a flat line: the per-user rate stays roughly constant, so the total climbs in step with the business. That is the mechanism behind predictable AVD costs: the wider your estate, the wider the gap, and it compounds precisely when you are already absorbing the cost of growth everywhere else. Over a three-year horizon it becomes a materially different total cost of ownership. To put your own numbers against it, the AVD ROI calculator models the Azure side of the equation alongside the flat platform fee.

It is worth being precise about the size of the effect rather than overselling it. Below a few hundred users, a flat rate and a per-user rate can land in similar territory; the advantage is real but modest at small scale. Flat-rate AVD licensing earns its keep as the estate grows, which is exactly when a licensing decision made today starts to matter most.

Budgeting becomes a single fixed line

Finance teams do not dislike software spend. They dislike software spend they cannot forecast. A flat monthly platform fee is a line item you can enter once for twelve months and revisit only when you license another tenant or change plans.

Growth decisions stop requiring a licensing review

When onboarding 300 users has no licensing consequence, nobody has to model the software impact of a hiring plan, a seasonal ramp, or a new site. You size the Azure infrastructure (which Atlas AVD then helps you optimize) and move on.

Seasonality costs nothing extra

Retail, education, accounting, healthcare, and professional services all run headcount curves with sharp peaks. Under per-user billing, a seasonal surge is a billing event. Under flat-rate licensing, it is just Tuesday.

Mergers and acquisitions do not reprice the platform

Bringing an acquired company's users onto your AVD estate is an integration project, not a renegotiation.

A worked example: 350 users become 1,800

Picture a company that standardizes on Atlas AVD at 350 AVD users in one tenant on Atlas AVD. Two years later it acquires another business and folds those employees into the same AVD estate and tenant. Headcount on the platform is now 1,800 users.

Two costs move in different directions:

  • Azure infrastructure cost rises, and it should. More users need more session hosts, more storage, and more bandwidth. Microsoft bills that to your subscription directly, and Cost Intelligence and Adaptive Density work to keep it as low as the workload allows.
  • Atlas AVD platform cost stays exactly the same. Atlas AVD was $199 per month at 350 users and it is $199 per month at 1,800. The effective platform cost per user quietly fell from about $0.57 to roughly $0.11.

This is the distinction the whole model turns on: infrastructure cost tracks what you run; management-platform cost, under Atlas AVD, does not. The acquisition changed the first number because more people genuinely consume more compute. It left the second untouched because managing a larger estate is the same orchestration work the platform was already doing. On a per-user model, that same integration would have arrived with a second, avoidable bill: the software equivalent of paying twice for the deal.


What you get for a flat rate

Flat pricing is only a real advantage if the platform behind it is complete. Atlas AVD is built as a premium, enterprise-grade Azure Virtual Desktop management platform, and the capabilities below are part of the plan you buy, not a menu of add-ons layered on afterward.

  • Your own Azure tenant, always. Atlas AVD deploys into your subscription via ARM. Your session hosts, profiles, images, and data stay under your ownership and your compliance boundary.
  • No inbound connectivity required. Atlas AVD operates entirely over outbound connections. No public IPs and no inbound firewall exceptions. Core management needs no agent on session hosts; the optional Atlas AVD Endpoint Agent adds near-real-time host metrics when you want them.
  • Atlas Advisor. Continuous, prioritized recommendations on drift, misconfiguration, security gaps, and savings opportunities, in plain language, not a raw metric dump. Included on every plan, Community too.
  • Adaptive Density. Automatically tunes host pool max-session limits against real usage instead of a number someone guessed at deployment. Included on Atlas AVD.
  • Adaptive Quota. Quota-aware deployment orchestration so an Azure quota ceiling never silently fails a provisioning run. Included on Atlas AVD.
  • Atlas Vault. Encrypted credential and document storage (local admin accounts, service principals, API keys, runbooks, and SOPs) with sensitivity ratings, rotation schedules, and full access auditing. Included on Atlas AVD.
  • Timeline. A chronological record of everything that changed in your environment, so "what happened at 09:40 on Tuesday" is a lookup rather than an investigation.
  • Cost Intelligence. Ranked savings recommendations for every host pool (drain idle hosts, run fewer hosts, smaller sizes, idle timeouts), each with an estimated monthly saving, plus a Reservations and Savings Plans advisor. Included on Atlas AVD, with per-pool cost tracking and savings tracking.
  • White-label branding. MSP Capabilities adds your logo, brand name, colors, support details, and login experience, for $50 more per tenant a month on top of Atlas AVD.

Browse the complete capability set on the features page.


Considering Atlas AVD as a Nerdio alternative or Hydra alternative

If you are evaluating Atlas AVD alongside Nerdio or Hydra, the honest framing is that these are good products solving a real problem, and the choice usually comes down to fit rather than quality.

The distinction we would ask you to weigh is architectural rather than competitive:

  • Atlas AVD is built around AVD. Azure Virtual Desktop sets the direction of every release, and the rest of the platform (Atlas Reach, Ink, Vault, Spool and Flow) works alongside it in the same console rather than spreading across general Azure resource management.
  • Atlas AVD is licensed flat per tenant, so the platform cost of your 2029 AVD estate is knowable in 2026. Nerdio licenses its AVD management per user, per month, so every user who connects carries its own fee on top of Azure: a per-user tax that grows with your headcount.
  • Atlas AVD includes every AVD feature on one plan, with white-label and Atlas Command as one optional upgrade, rather than spreading features across tiers.

Where another platform fits your operating model better (deep PSA billing integration, or managing a broad mix of Azure resources beyond AVD), that is a legitimate reason to choose it, and we will say so on a call.

For a side-by-side breakdown, see Atlas AVD vs Nerdio: the Nerdio alternative without the per-user tax and Atlas AVD vs Hydra.


Who Atlas AVD is built for

Enterprises

Internal IT teams running production AVD for hundreds or thousands of users, where the platform has to satisfy security review, audit, and change-management expectations, and where a predictable software line item is easier to defend than a variable one. Start at Atlas AVD.

Managed service providers

MSPs delivering AVD as a service need margin they can predict. A flat price per tenant means your cost moves only when you add a customer, never when a customer adds people, and how you package and price your own service stays entirely your decision. White-label branding and Atlas Command come with MSP Capabilities. See MSP solutions.

Organizations with multiple Azure tenants

Post-acquisition estates, regional subsidiaries, and separated production and regulated environments all end up with more than one tenant. Atlas AVD manages several tenants of your own, at one flat price per tenant, switching between them; MSP Capabilities adds Atlas Command to see them all at once.

Companies expecting significant AVD growth

If your AVD footprint is going to be materially larger in two years than it is today, the licensing model matters more than the first invoice. Growth is exactly the scenario flat-rate licensing is designed for.


Atlas AVD pricing FAQ

Is Atlas AVD less expensive than per-user licensing?

In the model above, yes for most organizations past a few hundred users, because the flat platform fee does not scale with headcount: Atlas AVD charges for the management platform once per tenant per month, while a per-user model charges again for every person you add. At small user counts the two approaches can land in similar territory. The gap opens as you grow, which is the point; put your own user count into the AVD ROI calculator to see where it lands.

Is there a per-user license for Atlas AVD?

No. The Atlas AVD platform is licensed flat per tenant and is never billed per AVD user, however many people connect to your desktops. Four optional modules are metered by use, drawn from your plan's included pooled unit allowance, which they all share (10 units a month on Community and 50 per licensed tenant on Atlas AVD): the End User Portal at $1 per active user per month, Atlas Ink managed email signatures at $1 per active user per month, Atlas Reach at $1 a month per managed device that is not an AVD session host (an Azure VM that is not a session host is billed), and Atlas Spool at 5 units per managed printer, charged once. Atlas Resolve DNS filtering is included with Atlas Reach and uses no units of its own. The per-user ones are billed only for the people who actually use them each month, so they never turn the platform into a per-user license. The portal is subject to a monthly admission cap of 10 distinct active users on Community; Atlas AVD are unlimited.

Are there hidden costs?

No. Plan prices are published on the pricing page. There are no setup fees, no per-technician charges, and no percentage of your Azure spend; product support is free on Atlas AVD, and hands-on help is available as prepaid support hours if you want it. Two kinds of charge are billed separately and stated plainly rather than hidden. The first is metered module usage, drawn from your plan's included pooled unit allowance, which every metered module shares (10 units a month on Community and 50 per licensed tenant on Atlas AVD), with more prepaid units available to add whenever you need them and never an overage bill: the End User Portal at $1 per distinct active user per month, Atlas Ink at $1 per distinct active user per month, Atlas Reach at $1 a month per managed device that is not an AVD session host (an Azure VM that is not a session host is billed), and Atlas Spool at 5 units per managed printer, charged once in the month it is created. Atlas Resolve DNS filtering is included with Atlas Reach and uses no units of its own. The second is your Azure consumption, which Microsoft bills directly to your own subscription.

Will my bill increase as my company grows?

Not from adding AVD users. Your Atlas AVD platform price changes only when you license another tenant or deliberately change plans, for example to add MSP Capabilities for Atlas Command and white-label branding. Adding users, session hosts, or host pools does not move the platform price. The metered lines move only with actual feature use: each distinct user who signs in to the End User Portal is $1 on that month's meter, each who receives a managed Atlas Ink signature is $1, each managed Atlas Reach device that is not an AVD session host (an Azure VM that is not a session host included) is $1 for the month, and each managed Atlas Spool printer is 5 units, charged once. Atlas Resolve DNS filtering adds nothing: it is included with Atlas Reach.

Why doesn't Atlas AVD charge per AVD user?

Because the platform's workload does not scale with your user count in a way that would justify it. Managing a host pool is the same orchestration problem at 300 users as at 3,000. Pricing on headcount would charge you more for work that has not changed, and it would put our commercial interest in tension with your growth. Our incentive should be to win more customers, not to bill each one more as they expand.

Is every feature included?

Yes. Every AVD feature is on Atlas AVD, with no add-on SKUs and no per-feature upsell: Atlas Vault, Cost Intelligence, DrainGuard, Adaptive Density, Adaptive Quota and Self-Healing all included. The full Atlas Advisor is on every plan, Community included, and MSP Capabilities adds Atlas Command and white-label branding. The full matrix is on the pricing page.

How does Atlas AVD compare with other AVD management platforms?

On capability, the comparison is feature-by-feature and worth doing properly: start with Atlas AVD vs Nerdio and Atlas AVD vs Hydra. On pricing, the difference is structural: many platforms in this category price per user or against consumption, while Atlas AVD prices the platform itself. Neither approach is inherently right. They optimize for different customers, and flat-rate licensing optimizes for organizations that expect to grow.

Why does Atlas AVD offer unlimited AVD users?

Because a cap would create the wrong conversation. Capped licensing means someone has to check the contract before onboarding a department, and eventually someone leaves users on unmanaged infrastructure to stay under a threshold, which is worse for security, worse for cost, and worse for the people using those desktops. Unlimited AVD users removes the decision entirely: every AVD user in your estate belongs in the platform.


Next steps

Everything above is published pricing, not a quote you have to request. When you are ready to go deeper, this is the order most architects find natural, from a no-commitment look to a conversation:

  1. Explore the interactive demo: a live Atlas AVD environment, no form and no call, so you can see how the platform manages a real estate.
  2. Model your numbers in the ROI calculator: put your own user count and Azure spend against the flat platform fee.
  3. Compare plans side by side: the complete feature matrix, plan by plan, on the pricing page.
  4. Start free on the Community plan: one Azure tenant, core host pool management, unlimited AVD users, no credit card.
  5. Schedule a live demo: bring your hardest Azure Virtual Desktop pricing question and we will answer it on the call.

If you manage AVD for customers rather than colleagues, start with MSP solutions instead; white-label branding and Atlas Command come with MSP Capabilities.