Hosted Windows Desktop Cost: AVD vs Windows 365

A hosted Windows desktop is a Windows 11 or Windows Server desktop running in a cloud region and streamed to the user's device, so the endpoint only handles display and input. Microsoft sells it two ways: a flat per-user Cloud PC under Windows 365, or metered Azure infrastructure under Azure Virtual Desktop (AVD).

Which one costs less depends almost entirely on how many of your users are online at the same time, and on whether you have anyone who can operate Azure.

Key takeaways

• Azure Virtual Desktop carries no flat per-seat service fee. You pay for Azure compute, storage and network by consumption, plus a Windows licence entitlement that's either brought from Microsoft 365 or paid as per-user access pricing.
• Windows 365 is a fixed monthly seat per user. The Windows licence, the management plane and the patching are inside that price, which is why it's the easier number to defend to a finance team.
• AVD usually wins when concurrency is low and session hosts can be deallocated outside working hours. Windows 365 usually wins when every user needs a persistent personal desktop or when nobody in the business wants to run Azure.
• The line item that breaks most AVD business cases isn't compute. It's image management, profile storage, monitoring and the engineering time to keep the host pool healthy.
• A comparison that ignores labour and disaster recovery will always favour AVD. One that ignores utilisation will always favour Windows 365.

What is a hosted Windows desktop?

A hosted Windows desktop is a full Windows session that runs on cloud infrastructure rather than on a local PC. The user's device handles screen, keyboard, mouse and local printing; everything else, including the file system and applications, executes on the remote host.

The category splits into two models that are often confused because they share the same name history. Microsoft renamed Windows Virtual Desktop to Azure Virtual Desktop in 2021, so most documentation and pricing pages you'll find under the old name now describe AVD.

Under AVD, you build a host pool inside your own Azure subscription. You choose the VM sizes, the image, the storage and the network. Session hosts can be personal (one user per VM) or pooled multi-session, where several users share a single Windows 11 Enterprise multi-session or Windows Server host.

Windows 365 is the managed alternative. Microsoft provisions a Cloud PC per user, keeps it patched, and exposes it through the same Remote Desktop clients. You get far fewer knobs and far fewer ways to accidentally overspend.

A third option is a non-Microsoft provider: Citrix, VMware Horizon or Amazon WorkSpaces running in AWS. The economics are broadly similar to AVD, with a vendor licence on top, so this article keeps them as a footnote rather than a column.

What does a hosted Windows desktop cost?

There's no single price, because a hosted desktop bill is the sum of four separate things and only one of them is fixed. The fixed part is the licence entitlement; compute, storage and network all move with how you configure and run the environment.

The buckets look like this:

• Compute. Azure VMs bill by the second or minute while they're running. A host that nobody logs into still bills. This is the largest and most controllable line in an AVD deployment.
• Storage. OS disks, data disks, profile containers (usually FSLogix on Azure Files or a premium disk), snapshots, and backup vault storage. Storage bills even when the VM is deallocated, which surprises people.
• Network. Egress charges for data leaving the region, plus any firewall, VPN gateway or ExpressRoute in the path. Usually small, occasionally not.
• Licence entitlement. Either an eligible Windows per-user licence you already own, or Azure's per-user access pricing for multi-session hosts. Windows 365 bundles this into the seat instead.

Windows 365 has the same underlying components, but Microsoft bills them as one number per user per month, tiered by vCPU, RAM and storage. There is no compute meter to watch, which is the entire point of the product.

Note: AVD pricing pages quote infrastructure. They don't quote the person who maintains the golden image, so the published figures and your actual invoice will diverge unless you account for that elsewhere.

Windows 365 vs Azure Virtual Desktop: how do the pricing models compare?

Windows 365 converts an unpredictable consumption bill into a predictable per-user cost; Azure Virtual Desktop converts a predictable per-user cost into a bill you control by how you architect and schedule it. Everything else follows from that trade.

Dimension	Windows 365	Azure Virtual Desktop
Billing model	Flat per-user monthly seat	Metered Azure consumption + licence
Desktop sharing	One Cloud PC per user	Pooled multi-session supported
Scale to zero	No, the Cloud PC persists	Yes, deallocate idle hosts
Cost at low concurrency	Higher, you pay for idle seats	Lower, shared hosts absorb spiky use
Cost at 1:1 persistent use	Competitive and predictable	Often higher once operations are counted
Management overhead	Low, Microsoft runs the host	High, you own image, patching, monitoring
Licence handling	Included in the seat	Bring eligible licence or pay per-user access
Best fit	Knowledge workers, small IT teams, hybrid	Task and shift workers, large estates, existing Azure teams

The mechanism underneath the table is utilisation. In a pooled AVD host pool, a single VM's cost is divided among everyone logged into it, so the effective cost per user falls as concurrency rises. That only helps if users genuinely overlap onto the same hosts. If each user needs their own machine left running all month, you've rebuilt a 1:1 model the hard way with extra steps.

Windows 365 has no equivalent lever. You buy a desk per person whether or not they sit at it.

Pro tip: Model AVD at two concurrency levels rather than one. The crossover point where AVD stops being cheaper is usually far lower than teams assume, and finding it early saves a painful migration later.

When is AVD more cost-effective than Windows 365, and vice versa?

AVD is more cost-effective when peak concurrency is a fraction of headcount and hosts can be switched off outside working hours. Windows 365 is more cost-effective when every user needs a persistent desktop, or when the operational capability to run AVD doesn't exist in-house.

Put more concretely, AVD tends to win in these conditions:

1. Contact centre or shift patterns where a third of the workforce is online at once.
2. Task workers running a browser and two line-of-business apps, well suited to multi-session hosts.
3. An existing Azure footprint with reserved capacity, governance and monitoring already in place.
4. Bursty contractors who need access for a defined project window.
5. Workloads where autoscaling or start-VM-on-connect can genuinely deallocate hosts overnight.

Windows 365 tends to win here:

1. Developers, designers and analysts who need a desktop available immediately on login.
2. Organisations with no Azure operations function and no appetite to build one.
3. A few hundred users or fewer, where the platform engineering overhead can't be amortised.
4. Regulated environments where a fixed, per-user, auditable line item is easier to approve.
5. Hybrid workers who use a hosted desktop as their only corporate Windows environment.

There's a middle ground worth knowing about. Windows 365 Frontline targets shift and part-time workers with a shared-entitlement model rather than one dedicated Cloud PC per named user. It exists precisely because the two extremes don't cover every workforce, and its terms are worth checking before you commit to either model.

How do you build a TCO comparison between AVD and Windows 365?

A defensible comparison needs a concurrency number, a runtime number and a labour number, in that order. Most failed business cases skip one of the three, and the labour number is the one people leave out.

1. Count users, then measure concurrency. Headcount is not the input. Pull login data for a representative fortnight and find the busiest hour. That peak drives your host pool sizing; the average drives nothing useful.
2. Classify the workloads. Split users into task workers, knowledge workers, developers and GPU users. Each group sizes differently and only some fit multi-session hosts.
3. Size the session hosts. Pick a users-per-vCPU ratio per group based on your own pilot, not a vendor blog. The ratio is the single most sensitive assumption in the model.
4. Model runtime hours per month. Include patch windows, after-hours access and the fact that hosts restarting still bill. Apply autoscale or start-on-connect and model both with and without it.
5. Add storage properly. OS disks, profile containers, snapshots, backups and the growth curve. Profile storage grows quietly and is rarely cleaned.
6. Add network. Egress, plus firewall or gateway costs if you're keeping line-of-sight to on-premises resources.
7. Add licensing. Eligible Windows per-user licences or Azure per-user access pricing for multi-session, and shared computer activation for Microsoft 365 Apps. Windows 365 seats already include this, so put it on the AVD side only.
8. Add labour. Image pipeline, update rings, monitoring, capacity management and incident response. For anything beyond a pilot this is a real fraction of a full-time engineer, and it's the line that decides most comparisons.
9. Apply discounts. Reserved instances or savings plans for AVD compute, and Azure Hybrid Benefit where you own eligible Windows Server licences. Model a one-year and a three-year view.
10. Run the same user set against flat Windows 365 seats. Include the fact that the Windows 365 column has near-zero platform labour. If AVD doesn't win by a clear margin after step 9, the operational risk usually isn't worth the saving.

Do this in a spreadsheet, not a slide. The moment the model becomes opaque, someone in finance will correct it for you at the worst possible time.

What pushes Azure Virtual Desktop costs higher than the estimate?

The gap between an AVD estimate and the invoice almost always comes from resources that keep billing while nobody is using them. Compute for idle hosts is the biggest, but it's not the only one.

• Session hosts left running 24/7. Without autoscale or start-VM-on-connect, you pay for nights and weekends.
• Over-sized SKUs. Teams buy headroom for a peak that arrives twice a year and pay for it monthly.
• Premium storage where standard would do. Premium SSDs for profiles that would sit comfortably on Azure Files is a common overspend.
• Snapshot and disk sprawl. Orphaned disks from rebuilt hosts keep charging until someone deletes them.
• Personal host pools used for everyone. If every user has a dedicated VM, AVD's sharing advantage disappears and Windows 365 becomes the simpler comparison.
• Log and monitoring ingestion. Central logging is essential and metered. Volume grows with the estate.
• Non-production environments. Test host pools that nobody switched off are a recurring line in every audit.

Warning: A deallocated VM still bills for its disks and any reserved public IP. "Off" in the Azure portal is not the same as "not costing anything".

Do you need Microsoft 365 or Office 365 to run a hosted Windows desktop?

Strictly, no, but in practice nearly every deployment is built on one. AVD needs a valid Windows licence entitlement for each user, which you either bring from an eligible Microsoft 365 or Windows per-user subscription, or satisfy by paying Azure's per-user access pricing for multi-session hosts.

Windows 365 is simpler: the Windows licence sits inside the per-user seat, so you don't have to reason about entitlement for the desktop itself. You still need whatever licences your applications require.

Where it gets fiddly is Microsoft 365 Apps inside a multi-session host. It runs under shared computer activation, and not every plan that includes desktop Office supports that mode on a shared VM. Windows 365 Business and Enterprise editions also differ in seat caps, management features and which existing subscriptions count toward eligibility.

Note: Licensing eligibility for hosted desktops has changed more than once and varies by agreement type. Verify against Microsoft's current licensing documentation before you build a business case on it, rather than trusting any article including this one.

If you're on Microsoft 365 Business Premium and want a Cloud PC, the Business edition of Windows 365 is the usual starting point, though it caps out at 300 users. Past that, you're in Enterprise edition territory and the licence prerequisites tighten.

Limitations

This article explains how the pricing models are constructed. It deliberately does not quote figures, because Azure regional rates, Windows 365 seat tiers and licence terms all change, and a stale number in a business case is worse than no number.

It's also not a substitute for a model built on your own data. If you don't know your peak concurrency, nothing here will give you a reliable answer, and any vendor who claims otherwise is guessing.

Some workloads don't fit either model well:

• GPU-heavy CAD, video editing and 3D rendering can run on AVD with GPU SKUs, but the cost profile changes completely and the comparison needs redoing from scratch.
• Latency-critical applications where round-trip time to a cloud region degrades the work.
• Single users or very small teams. A managed laptop with a VPN is almost always cheaper than running a one-host AVD environment, once you count the setup and monitoring.
• Organisations that need offline working. A streamed desktop is not available on a plane.

If your organisation already runs Citrix or VMware Horizon and has a licensing estate behind it, the honest answer is that switching to AVD purely for cost rarely pays back within the depreciation window of the existing stack.

Frequently asked questions

Is Windows Virtual Desktop the same as Azure Virtual Desktop?

Yes. Microsoft renamed Windows Virtual Desktop to Azure Virtual Desktop in 2021, and the underlying service is the same. Documentation, pricing calculators and community posts still use the old name, which is why searches for both return the same results. Anything you read about "Windows Virtual Desktop pricing" is describing what's now sold as Azure Virtual Desktop.

Can I host a Windows desktop in the cloud for just one user?

You can, and both models support it. AVD would be a single personal host pool, which leaves you maintaining an image, a network and monitoring for one person. Windows 365 Business would be one Cloud PC seat, managed by Microsoft, and is nearly always the better choice below roughly ten users. Neither is cheaper than a laptop for a single user.

Is a hosted Windows desktop cheaper than buying laptops?

Not on hardware cost alone, and usually not on a three-year total either for straightforward office work. The cost case for hosted desktops comes from elsewhere: rapid onboarding and offboarding, contractors and shift staff, device loss and theft, and keeping data off endpoints. If none of those apply, replacement laptops remain the cheaper option.

Do hosted Windows desktops need a VPN?

Not for the connection itself. AVD and Windows 365 use a reverse-connect model over TLS 443, so the client reaches Microsoft's service without an inbound firewall rule. You may still need a VPN or ExpressRoute path if the desktop has to reach on-premises file shares, line-of-business servers or a legacy database, and that adds cost and complexity.

What's the cheapest way to host a Windows desktop in the cloud?

The cheapest configuration is usually a multi-session AVD host pool with autoscaling, reserved capacity, and hosts deallocated outside business hours. That's also the configuration that requires the most operational discipline, and the savings disappear the moment a host is left running. Don't treat "cheapest" and "lowest total cost" as the same thing without adding the labour column.

Where to go next

Pull your peak concurrency data for a two-week window before you model anything, because every number downstream depends on it. Then build the comparison in a spreadsheet with a labour line you're willing to defend out loud.

If the two models land within a few percent of each other, run a small Windows 365 pilot and an AVD pilot side by side for a month. The operational reality will settle the argument faster than another spreadsheet will.