Windows 365 vs AVD: a real cost comparison

The Windows 365 vs Azure Virtual Desktop (AVD) choice comes up in almost every Cloud PC conversation, and the honest answer is "it depends on the workload, and often on how many hours the desktop is actually used". This guide walks a concrete cost example across three typical usage patterns so the trade-off stops being abstract.

The list prices below are 2026 published prices in USD — treat them as directional; your enterprise agreement, region, and reserved-instance commitments will move them. The point of the exercise is not the exact number but the shape of the answer.

The two pricing models

Windows 365 Enterprise is a fixed per-user, per-month subscription for a specific Cloud PC size — 2 vCPU / 8 GB / 128 GB is roughly $41/user/month, 4 vCPU / 16 GB / 256 GB is roughly $66/user/month, 8 vCPU / 32 GB / 512 GB is roughly $124/user/month. The price includes the VM, storage, gateway, and the Microsoft-managed control plane. It does not include the Windows 11 Enterprise, Intune, and Entra ID P1 licenses required to enrol and manage the Cloud PC — those are typically covered by Microsoft 365 E3 or E5.

AVD is Azure consumption: you pay for the underlying VM (D-series, D-series v5, B-series, whatever the session host uses) per hour, plus Azure Files or FSLogix storage, plus the Azure networking. The AVD control plane itself is free — Microsoft charges only for the infrastructure. Windows 11 Enterprise multi-session, the licensing model that lets many users share one VM, comes with the same Microsoft 365 licenses that entitle a user to Windows 365.

The consequence is that AVD gets cheaper the more users you can pack onto one VM, and gets more expensive the more hours per day those VMs run. Windows 365 is flat regardless of usage: idle Cloud PCs cost the same as always-on ones.

Scenario 1: the task worker

Call this a call-centre operator, a warehouse admin, a receptionist. Usage pattern: eight hours a day, five days a week, mostly Microsoft 365 and one line-of-business app. Very light on CPU and memory. Storage requirements low.

• Windows 365 at the 2 vCPU / 8 GB tier: $41/user/month. Fixed.
• AVD with 8 users sharing a D4s v5 host, ~40 hours/user/week, FSLogix profile on Premium Azure Files: roughly $12–18/user/month for compute + $4–6/user/month for storage. Call it $20/user/month.

AVD wins comfortably. The task worker is the archetype AVD was built for: predictable weekday hours, low individual load, high sharing ratio.

Scenario 2: the knowledge worker

An analyst, a project manager, a marketer. Ten hours a day but with real spikes — Teams calls with sharing, Excel with big models, a browser with 40 tabs. Storage matters (OneDrive cache, downloads). Some out-of-hours use.

• Windows 365 at 4 vCPU / 16 GB / 256 GB: $66/user/month. Fixed, includes storage.
• AVD with 4 users sharing a D8s v5 host during business hours plus a lower-density fallback in the evening: roughly $45–65/user/month for compute + $8–12/user/month for storage. Call it $60–75/user/month.

At this workload the two products are roughly at parity in raw cost — sometimes AVD wins by 10–15%, sometimes Windows 365 wins, depending on how disciplined the AVD scaling is. The management cost is where the difference actually lives: Windows 365 has none of the scaling, image, or FSLogix work that AVD demands.

Scenario 3: the developer

A software developer running Visual Studio, Docker Desktop, and a couple of local databases. Sustained CPU load, 16 GB minimum RAM, 512 GB+ storage. Ten to twelve hours a day, occasional weekends.

• Windows 365 at 8 vCPU / 32 GB / 512 GB: $124/user/month. Fixed.
• AVD with a personal host (no sharing) on a D8s v5, running 12h × 5.5d/week, Premium storage: roughly $130–170/user/month.

Here Windows 365 usually wins. Developers rarely tolerate a multi-session host — the workload is spiky, the tools are heavy, and the noisy-neighbour risk is high — so the AVD math loses its advantage. A personal session host is basically Windows 365 with worse management.

What the numbers do not show

The three scenarios above are only compute and storage. The management cost is the other axis.

Windows 365 is a fixed monthly item that Intune enrols and Autopatch keeps current, with almost no additional operational work. Once the enrolment policy is set, the fleet manages itself.

AVD is an Azure workload. It needs a scaling plan (start-VM-on-connect, auto-scale schedules), an image build pipeline (custom images or Azure Marketplace Windows 11 multi-session, with monthly patch cycles), an FSLogix profile container strategy on Azure Files with backup, host-pool monitoring, and shielded storage accounts. All of that costs real engineering time — commonly 0.5–1.0 FTE for a fleet of a few hundred users, more for larger fleets.

A rough rule: below ~50 users, the AVD management overhead almost always wipes out the compute savings, so Windows 365 wins on total cost of ownership. Between 50 and 500 users the picture varies by workload mix. Above 500 users, an AVD platform team can amortise the operational cost across enough users that the compute savings become real money.

Which one to pick

Pick Windows 365 when: the workload is a knowledge-worker desktop with individual state, the fleet is under a few hundred users, the goal is operational simplicity, or the user population is highly mobile with unpredictable hours.

Pick AVD when: the workload is a task worker running for a predictable weekday window at high density, the fleet is large enough to justify a dedicated platform team, GPU or specialised sizes are needed, or you already have a mature Azure landing zone the desktops can land in.

Many organisations end up with both — AVD for the call centre and the shared kiosk desktops, Windows 365 for developers and knowledge workers whose desktop feels personal.