The Real Math Behind AVD Management Pricing: Minimums, Tiers, and Year-One Costs
April 16, 2026
In our last post, we walked through the difference between Monthly Active User (MAU) pricing and peak concurrent user pricing, and why that single distinction can dramatically change your actual bill. If you haven’t read it yet, start there first: it sets up everything we’re about to get into. Because even once you understand MAU billing, there’s still more to unpack.
What “Per User” Actually Means in AVD Management Pricing
Monthly Active User (MAU) pricing is the dominant model in the Azure Virtual Desktop (AVD) management space right now. The definition is straightforward: any user who logs in at least once during the month counts as a full MAU.
The problem is that “logged in once” and “actively using” are very different things.
If 2,000 users are in your environment, but your peak concurrent sessions never exceed 600 (because you have shift workers, occasional users, or seasonal staff) you’re still billed for all 2,000. The 1,400 people who logged in once for five minutes count the same as your power users who are on eight hours a day.
For environments that have variable workloads like this, it’s where the model starts to cost significantly more than expected.
As an example, one widely used AVD management platform lists two pricing tiers:
- Core: $6.00/user/month
- Premium: $10.00/user/month
Both are per MAU. And both come with a $1,000/month minimum.
Monthly Minimums: The Floor That Changes Your Per-User Math
Monthly minimums are common in this pricing category and worth modeling carefully before you commit. A $1,000/month floor means that if your calculated bill comes in below that threshold, you pay the minimum regardless. This hits hardest on smaller environments, during pilots, and phased rollouts (the exact moments when you’re still validating whether the platform is right for you).
A simple illustration of how it plays out:
300 users × $6/MAU = $1,800/month calculated (minimum doesn’t apply here)
But at 140 users, your $840 bill becomes $1,000. You’re not overpaying because anyone misled you, it’s because there’s a floor in the licensing model, and it’s easy to miss until you run the actual numbers.
For teams running a proof-of-concept or gradually migrating from a legacy platform, this minimum can bloat your per-user cost during the period when you’re least certain the platform is right for you.
SKU Tiers: Which One Does Your Production Environment Actually Require?
Tiered pricing is standard in enterprise software; there’s nothing unusual about it. What you should determine during an evaluation is which tier your production environment actually requires.
Features like advanced auto-scaling, storage auto-scaling, Azure API limit boosters, advanced self-service portals, and deeper dashboards typically sit above the base SKU in this type of pricing model. If advanced auto-scaling is part of why you’re adopting a management platform in the first place (and for most teams it is) it’s important to factor into your starting point before you sign, not finding out after.
Onboarding Costs: What It Actually Takes to Go Live
Complex platforms require onboarding. Whether that shows up as a line-item professional services fee, a migration engagement with a partner, or internal engineering time allocated to the deployment, it is a real cost, and it lands in year one, before you’ve proven out the value.
Some vendors build it into a services package; others leave it to partners. But the more configurations a platform has, the more time and resources a production deployment typically requires.
It’s worth asking directly during evaluation: what does a production deployment actually look like, and what does it cost to get there?
Support: Included, Until You Actually Need It
Most platforms include a base support tier, but in practice, enterprise teams often find out what’s actually covered in that the hard way (aka during an incident).
The support model that gets you through a production outage typically isn’t the one that comes standard. Things like faster SLAs, screensharing, dedicated escalation paths, and a human who already knows your environment are often inside a premium support tier.
That means when something breaks at 2am and your users can’t get in, you’re either waiting on an email queue or you’re upgrading support on the spot because downtime costs more than the add-on. And in our opinion, that’s the worst time to pin an upgrade on a customer.
What AVD Management Actually Costs in Year One
Let’s pull it all together with conservative, yet realistic assumptions:
Assumptions:
- Core tier: $6/MAU/month
- Premium tier (production-realistic): $10/MAU/month
- $1,000/month minimum
- Onboarding/professional services: varies (estimated at $15,000 for illustration only)
| Users | Advertised Monthly (Core, MAU) | Realistic Monthly (Premium tier) | Annual Licensing | Est. Onboarding | Year 1 Total | Effective $/User/Mo |
|---|---|---|---|---|---|---|
| 200 users | $1,200 | $2,000 | $24,000 | $15,000 | $39,000 | $16.25 |
| 500 users | $3,000 | $5,000 | $60,000 | $15,000 | $75,000 | $12.50 |
| 1,000 users | $6,000 | $10,000 | $120,000 | $15,000 | $135,000 | $11.25 |
The pattern is pretty clear: smaller environments get squeezed by minimums, mid-size environments often require a tier upgrade, and the all-in year-one cost can be significantly higher than what the initial calculation suggests.
To be clear, none of this involves misleading pricing. All of these numbers are publicly available and standard enterprise practice. The issue is simply that they’re easy to evaluate in isolation and easy to underestimate in aggregate.
Questions to Ask Before You Sign an AVD Management Contract
We’re not suggesting that platforms with tiered pricing or monthly minimums are inherently a bad deal. Feature depth has real value, and if you’re using the Premium tier fully, the math works out.
But here’s what you should seriously evaluate before you sign:
- Does the licensing model align to how your environment actually runs?
- Are you paying for concurrency, or for every person who logged in once this month?
- Does the tier you need to run in production match the tier you evaluated against?
- Are onboarding or migration services a known line item, or something you’ll figure out once you’re already committed?
- What does the support model look like when something breaks?
These are the questions that determine whether your year-one estimate and your year-one invoice are in the same ballpark.
How Hydra’s AVD Management Pricing Works Differently
We built Hydra to be the most practical approach to AVD management: a platform that covers what your team actually needs day to day, without charging you for the parts you’ll never use. And our pricing model is part of the same thinking.
Pricing that reflects how AVD actually runs. Hydra is billed at $5/peak concurrent user per month, not per MAU. If 800 of your 1,000 users are shift workers or occasional logins, you don’t pay for them during the periods they’re not active. Your bill flexes with reality, and you are never permanently punished for short-term burst usage.
No monthly minimums. Hydra has no minimum you have to hit before your actual usage kicks in. Pay only for peak concurrent users, that’s it.
No tiering to unlock production functionality. The features you need to run at scale (autoscaling, image management, session control, multi-tenant support, real-time diagnostics, etc.) are included…always. There’s no Premium gate between you and a fully functioning environment.
No onboarding or migration fees. Hydra is designed to be operational within minutes, without a professional services engagement required to get there. Existing workspaces can be connected without rebuilding infrastructure or host pools.
Burst protection included on annual plans. Temporary spikes from seasonal hiring or project surges don’t permanently inflate your license tier. Annual plans include one month of burst protection at 2x concurrency at no additional cost.
Our intention is straightforward: pricing you can predict and trust before you sign, and a bill that matches that when it arrives, nothing more. Everything about Hydra is built on operational practicality, pricing included.
Start with the Hydra ROI Calculator to plug in your own numbers and see what this actually looks like for your environment. From there, our pricing page breaks down exactly what’s included at each tier. And if you want to put the two platforms side by side, our AVD management platform comparison links every feature directly to official documentation, so you’re not just taking our word for it.
Pricing sourced from publicly available pages as of March 2026. All figures subject to change.
Hydra
