Peak Concurrent Pricing for AVD and Windows 365: How Licensing Models Change Your Costs

March 17, 2026

Organizations adopting Azure Virtual Desktop and Windows 365 often focus on VM sizing, storage tiers, and autoscaling to control costs. But there’s another cost driver hiding in plain sight: how the management platform licenses users.

Some management tools charge based on every user who logs in during the month, even if those users rarely connect. In environments with contractors, shift workers, or occasional access users, that licensing model can dramatically inflate costs.

The difference between peak concurrency-based pricing and monthly active user pricing can determine whether organizations pay for actual usage or potential usage.

As environments scale, the licensing model behind the management platform can become a significant portion of the total of ownership for Azure Virtual Desktop and Windows 365 environments.

What’s the Difference Between Peak Concurrent Users and Monthly Active Users?

Peak concurrent users refer to the highest number of users logged in at the same time during the billing period.

Monthly active users (MAU) count every unique user who logs in at any point during the month, even if they only connect once.

For example, if 10,000 users log in during the month, only 6,000 are ever connected at once, MAU-based pricing charges for 10,000 users, while peak concurrent pricing charges for 6,000.

Why Does This Pricing Gap Exist?

Most Windows in the Cloud environments support far more identities than simultaneous sessions. This happens because many organizations have workforces with varying access patterns based on Login VSI customer deployment data, like:

• Shift-based workers
• Contractors
• Seasonal employees
• Training labs
• Disaster recovery environments
• Education labs

This results in the identity pool being much larger than the number of users actually connected at once. Infrastructure costs already scale with concurrency, but some management tools license based on identity counts instead of usage. That mismatch is where costs start to drift.

What Happens When Environments Grow?

IT teams usually expect infrastructure to drive costs:

• Session hosts (compute)
• Storage
• Networking
• File Shares for profiles

But as deployments scale, management platform licensing becomes increasingly important to the overall total cost of ownership for the environment.  When pricing is tied to monthly active users (MAU), organizations pay for every individual who logs in during the month, even if most never connect at the same time.

In large environments with shift workers, contractors, or occasional access, this can mean paying thousands for additional users each month who are rarely active concurrently; driving management platform costs far higher than actual usage requires.

Real-World Scenario: Large Shift Workforce

Imagine an organization running Azure Virtual Desktop for a distributed workforce.

In this environment, the cloud infrastructure only needs to support 5,000 simultaneous users. But if licensing is based on MAU, the organization pays for all 20,000 users who log in during the month. Let’s break it down further:

Cost Comparison: CCU vs MAU Licensing

Let’s assume both models cost $5 per user per month.

Concurrency-Based Licensing

Peak concurrent users: 5,000

Monthly cost:

5,000 × $5 = $25,000/month

Annual cost:

$25,000 × 12 = $300,000/year

Monthly Active User Licensing

Monthly active users: 20,000

Monthly cost:

20,000 × $5 = $100,000/month

Annual cost:

$100,000 × 12 = $1,200,000/year

Annual difference:

$900,000 – that’s not exactly pocket change.  That’s the cost of paying for identities instead of usage.

In large environments, differences in licensing models like this can significantly influence the Total Cost of Ownership in managing Windows in the Cloud environments. For this example, the organization is paying four times more for licensing despite never running more than 5,000 sessions.

Questions to Ask About Management Platform Pricing

Before selecting a platform for Azure Virtual Desktop or Windows 365, IT leaders should ask:

• Does pricing scale with identity count or concurrent usage?
• How does the platform measure peak concurrency?
• Does the platform licensing support short-term usage bursts without additional cost?
• How predictable are licensing costs as environments grow?
• Does the licensing model match how infrastructure scales?

These answers determine whether costs stay predictable or drift as user populations grow.

Hydra Licensing: Consumption-Based Platform Management

Hydra is designed as an operational control layer for Azure Virtual Desktop and Windows 365 Cloud PC environments where scalability and predictability matter. Instead of tying licensing to every user identity that connects during the month, Hydra aligns licensing with peak concurrent usage. This approach allows organizations to:

• Scale environments without licensing surprises
• Support large populations of occasional users
• Align management costs with infrastructure usage
• Maintain predictable operating costs as deployments grow

When AVD and Windows 365 environments scale into tens of thousands of users, one of the most important decisions for an organization regarding total cost of ownership is the difference between identity-based pricing and concurrency-based pricing.

Hydra was designed with that principle in mind: operational control, scalable automation, and licensing that reflects how and when cloud desktops are actually used.

Take control of your cloud desktop licensing costs. Start a Hydra trial today!