Azure Virtual Desktop vs Windows 365 vs traditional desktops

Every growing business eventually asks the same question: do we buy laptops and desktops the way we always have, or do we move the desktop itself into the cloud? And if we go cloud, is that Azure Virtual Desktop or Windows 365? There's no universally right answer, only the right answer for your workforce, your applications and how predictable your usage actually is.

In short: Windows 365 gives every user a fixed-cost, dedicated Cloud PC with the simplest management overhead of the three, and suits stable, predictable headcount. Azure Virtual Desktop is more flexible and can be cheaper at scale or with variable usage, but demands real ongoing engineering to configure, scale and secure properly. Traditional desktops still make sense for specialist hardware, offline-first work, or genuinely small, static teams where cloud desktop infrastructure is more than the problem needs. Most growing businesses end up using a mix rather than picking one exclusively.

This isn't a hypothetical decision. It's one we get asked to help with regularly, usually by a business that's either replacing an ageing desktop fleet, supporting a hybrid or remote workforce for the first time, or trying to work out why last year's laptop refresh budget keeps growing. This guide compares all three approaches honestly, including where each one falls down, not just where it shines.

What are you actually choosing between?

It helps to be precise about what each option actually is, because the marketing language around all three tends to blur the lines.

Azure Virtual Desktop (AVD)

AVD is Microsoft's virtual desktop infrastructure (VDI) platform, built on Azure. You (or a partner) design and manage the host pools, the virtual machines that actually run Windows, decide how sessions are pooled or dedicated, configure autoscaling, choose VM sizes, and manage the FSLogix profile storage that keeps a user's desktop consistent between sessions. It's powerful and flexible, but it's genuine infrastructure you're responsible for configuring and maintaining, not an out-of-the-box product.

Windows 365

Windows 365 is Microsoft's Cloud PC service: a defined, fixed-configuration virtual machine assigned to a single named user, provisioned automatically once you assign a licence. There's no host pool to design, no VM sizing decision beyond picking a plan, and no scaling plan to configure, Microsoft handles the underlying infrastructure. The trade-off for that simplicity is less flexibility: you're choosing from a smaller set of pre-defined configurations rather than architecting the environment yourself.

Traditional (physical) desktops

The model most businesses grew up on: a physical PC or laptop per user, purchased outright or leased, with applications, data and the user profile living locally (with file sync or backup layered on top, if you're doing it properly). Management happens through tools like Intune or a traditional device management platform, and hardware failure means the user is down until that specific device is fixed or replaced.

Cost model compared

The single biggest source of confusion in this decision is that all three options spend money in structurally different places, which makes a like-for-like number nearly impossible to give honestly, and anyone who quotes you one figure without asking about your usage pattern first is guessing.

How AVD is priced

You pay for the underlying Azure compute (the VMs themselves), storage (for FSLogix profiles and any attached disks), networking, and the Windows/Microsoft 365 licensing that makes multi-session Windows legally usable. Because it's metered infrastructure, cost scales with actual usage: an autoscale scaling plan that shuts hosts down outside working hours genuinely reduces the bill, and a pool sized for real demand rather than "just in case" makes a material difference.

That's the upside. The downside is that cost also scales with configuration quality: a poorly tuned AVD environment, oversized VMs, no autoscaling, premium storage nobody needed, can quietly cost more than either of the alternatives.

How Windows 365 is priced

A flat, fixed, per-user, per-month licence cost set by Microsoft based on the Cloud PC's compute, memory and storage specification. You choose a plan up front and the cost is predictable regardless of how much or how little that user actually works that month.

There's no variable Azure consumption bill to reconcile, no surprise from a scaling plan misfire. The trade-off is that you're paying the same amount whether a Cloud PC is used eight hours a day or barely logged into, there's no automatic reward for low usage the way AVD's autoscaling offers.

How traditional desktops are priced

Capital cost (or lease payments) for the hardware itself, spread across a refresh cycle that typically runs several years, plus the ongoing cost of on-site support, hardware repairs, and the IT time spent managing a fleet of physical devices that all age and fail on their own separate schedules.

It's easy to underestimate this model's total cost because so much of it, break/fix time, replacement parts, the admin overhead of tracking asset lifecycles, doesn't appear as a single clean line item the way a cloud subscription does.

Management overhead

Cost is only half the decision. The other half is how much ongoing effort each option demands from whoever is running your IT, whether that's an internal team or a managed provider.

AVD management overhead

This is where AVD asks the most of you. Host pools need to be designed correctly from day one, session host images need to be maintained and patched, FSLogix profile storage needs monitoring, and autoscaling plans need setting up and revisiting as usage patterns change.

Done well, AVD runs efficiently and flexibly. Done once at launch and never revisited, which is depressingly common, it tends to become an expensive, static environment that nobody wants to touch. AVD rewards ongoing, competent management far more than it punishes a one-off configuration mistake.

Windows 365 management overhead

Deliberately the lightest of the three. Assign a licence, the Cloud PC provisions itself, and day-to-day management largely happens through the same Intune/Microsoft 365 tooling you'd already use to manage any other Windows endpoint.

There's no host pool, no VM sizing decisions to keep revisiting, no scaling plan. The trade-off is that when you do need something outside the standard plan menu, more storage, a different vCPU/memory ratio, GPU acceleration, Windows 365 simply doesn't offer it, and that's a real limitation for some workloads.

A less-discussed difference sits underneath both of these: blast radius when something actually fails. A real-world AVD session host typically carries somewhere around 20-30 concurrent users, not the higher figure Microsoft's own published sizing guidance might suggest is achievable, so a single host going down takes that whole group offline at once.

A Windows 365 Cloud PC is dedicated to one named user; if it has a problem, exactly one person is affected. Neither model is wrong, but it's a real operational trade-off that a pure cost comparison misses.

Traditional desktop management overhead

Physical asset management: tracking which device belongs to which user, coordinating repairs and replacements, managing local patching and software deployment across a fleet spread across however many locations your people actually work from, and handling the logistics of collecting and reissuing hardware when someone leaves or a device fails. None of this is exotic, but it scales roughly linearly with headcount and device count, in a way that cloud desktop management generally doesn't.

Where each one actually fits

When AVD makes sense

Genuinely variable or seasonal usage where autoscaling has real work to do; specialist workloads needing GPU-backed VMs, custom VM sizing, or pooled multi-session hosts for cost efficiency at scale; organisations with the in-house skill (or a specialist partner) to configure and actively manage the environment rather than deploy it once and leave it; and scenarios needing configurations Windows 365's fixed plans simply don't offer.

When Windows 365 makes sense

Stable, predictable headcount where most users need a similar, consistent desktop experience; businesses that want cloud desktop resilience (work from anywhere, fast recovery from a lost or broken device) without taking on infrastructure management; and organisations without the in-house appetite to actively tune and monitor a virtual desktop environment, where "provision and forget" is genuinely the right trade-off, not a shortcut.

When traditional desktops still make sense

Specialist or legacy hardware dependencies that don't virtualise cleanly, high-performance local workloads with heavy graphics or hardware peripheral requirements, genuinely offline-first work where connectivity can't be assumed, and small, static teams where the operational overhead of any virtual desktop platform, AVD or Windows 365, is more infrastructure than the problem actually needs. Cloud desktops solve a real problem; they're not automatically the right answer for every team size.

The full comparison

	Azure Virtual Desktop	Windows 365	Traditional desktops
Cost model	Metered Azure compute, storage and networking	Fixed per-user, per-month licence	Capital/lease cost plus ongoing support
Cost predictability	Variable, scales with usage and configuration	High, fixed regardless of usage	Predictable per refresh cycle, variable support cost
Management overhead	Highest, ongoing host pool and scaling management	Lowest, provision-and-manage via Intune	Physical asset and on-site support overhead
Flexibility	Highest, custom VM sizing, GPU, pooled hosts	Fixed plan menu, no custom configuration	Full hardware choice, but per-device
Recovery from device loss	Fast, session isn't tied to hardware	Fast, session isn't tied to hardware	Slow, user is down until device is fixed/replaced
Best suited to	Variable usage, specialist or elastic workloads	Stable headcount wanting simplicity	Specialist hardware, offline-first, small static teams

Common mistakes when choosing

The most common mistake is picking a platform based on what a vendor or a case study recommends for a business that doesn't resemble yours. A pooled AVD environment tuned for a call centre with predictable shift patterns is a poor template for a professional services firm with unpredictable, spiky usage, and vice versa.

The second most common mistake is treating the decision as permanent and irreversible: it isn't, and plenty of businesses run a mixed estate, Windows 365 for most of the workforce, AVD for the elastic or specialist minority, and a handful of traditional desktops for the roles that genuinely need dedicated hardware. The third is underestimating management overhead on the AVD side specifically: an environment configured once at launch and never revisited tends to be the most expensive of all three options, not the cheapest, because none of the levers that make AVD cost-efficient get pulled without ongoing attention.

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

Short answer: AVD wins on cost when concurrency is well below headcount, because pooled hosts and autoscale stop billing for seats nobody is using. Windows 365 wins when concurrency is close to headcount, because there is nothing left for AVD's flexibility to save and the design overhead buys you nothing.

The crossover point is not a number of users, which is the first thing worth unlearning. We have seen two businesses of near-identical headcount land on opposite answers, because one ran a nine-to-five office where almost everybody was signed in at once, and the other ran shifts where peak concurrency never exceeded 40% of staff.

The ratio that actually decides it

What actually decides it is the ratio between peak concurrent sessions and total licensed users. If 100 people share a platform but only 45 are ever signed in at the same time, AVD can size the pool to 45-ish with headroom and ramp it down overnight and at weekends. Windows 365 bills all 100 whether they are working or not. That gap is where AVD's saving lives, and it compounds every hour the pool is smaller than the headcount.

Invert it and the logic inverts too. If 95 of those 100 are signed in every weekday morning, the pool never shrinks meaningfully, autoscale has nothing to reclaim, and you have taken on host pool sizing, image management, storage design and scaling plans in exchange for a saving that did not materialise. At that point the fixed per-user price is not just simpler, it is usually cheaper once you count the management time honestly.

Three situations override the concurrency maths entirely:

• GPU workloads. Windows 365 has no GPU option. If you run CAD, rendering or GPU-accelerated analysis, AVD is the only one of the two that can do it, at any headcount.
• Shift patterns with Frontline. Windows 365 Frontline lets a pool of licences rotate across shift workers, which claws back some of AVD's concurrency advantage for exactly the pattern that usually favours AVD. Worth checking before assuming AVD wins on a shift-based estate.
• Nobody to own it. AVD's saving is conditional on somebody tuning it. An untuned AVD estate reliably costs more than Windows 365, because host pools sized for a Monday peak keep running at that size every night and weekend.

TCO analysis: AVD vs Windows 365

Short answer: A genuine TCO comparison has four lines, not one. Licensing, infrastructure consumption, storage, and the management effort to keep it correct. Comparing only the first two is what produces business cases that look right and then drift.

Licensing

Windows 365 is a single per-user, per-month figure that covers the desktop and the compute together. AVD splits it: the Windows access right usually comes bundled in a licence you already hold, Microsoft 365 E3, E5, F3, Business Premium or Windows Enterprise E3 and E5, and the compute is billed separately as Azure consumption. That bundling is why AVD licensing looks free at first glance and why AVD estates so often carry duplicate-purchased access rights.

Infrastructure

This is the line Windows 365 does not have and AVD lives or dies by. Session host VMs are billed by the hour they run, which means the real driver is not the VM size but how many hours per week the pool is actually up. A pool that runs 168 hours a week when the business works 50 is paying more than three times what it needs to, and no VM right-sizing exercise recovers that.

Storage

FSLogix profile containers on Azure Files, and the tier choice here is a genuine trap. Standard tier looks cheaper per gigabyte and bills per transaction, and an active virtual desktop workload generates tens of thousands of transactions per user per day across logon, logoff, application launches and file syncs.

Standard routinely costs more than Premium once transactions are counted, which is the opposite of what the per-gigabyte price suggests. Windows 365 has no equivalent line because the profile lives on the Cloud PC.

Management

The line most business cases omit, and the one that most often decides the answer. AVD needs somebody to own autoscale tuning, image versioning, storage tier review and capacity checks on an ongoing cycle, not once at go-live. Whether that is internal time or a managed service, price it, because a TCO model that values it at zero will always recommend AVD and will always be wrong when nobody has the time.

A model built on those four lines usually produces a different answer than the licensing comparison people start with, and it is the model we use at assessment rather than a rule of thumb.

AVD management vs Windows 365 management

Short answer: Windows 365 management is subscription management. Assign a licence, a Cloud PC appears; remove it, it goes. AVD management is infrastructure management for infrastructure you do not physically own, and none of its decisions stay correct on their own as usage changes.

The distinction that matters is not how much work each takes on day one. Both are straightforward to stand up. It is how much work each takes in month six, and whether that work has an owner.

With Windows 365: licence hygiene

With Windows 365, the ongoing job is licence hygiene and Intune policy. Are leavers' Cloud PCs reclaimed? Is anybody on a bigger size than they need? Is the Intune configuration still matching how people work? That is real work but it is bounded, and getting it wrong costs money rather than breaking things.

With AVD: the environment itself

With AVD, the ongoing job is the environment itself. Scaling plans need revisiting as working patterns shift, because a ramp-up schedule built around a 9am login wave is wrong the moment the business moves to staggered starts.

Golden images need versioning and rebuilding, because an image that accumulates applications boots slower, patches slower and takes longer to roll out every cycle. Storage tier needs reviewing against measured transaction volume. Host pool sizing needs checking against actual concurrency rather than the number it was set to at go-live.

None of that trips an alarm when it stops being correct. It shows up as a slowly rising invoice and slowly worsening logon times, which is why AVD estates so often reach a renewal review with nobody able to explain how they got there.

Feature comparison of AVD and Windows 365 management platforms

Short answer: They are managed through overlapping but different planes. Windows 365 is governed almost entirely through Intune and the Microsoft 365 admin centre. AVD adds the Azure portal, host pools, scaling plans, the Compute Gallery and storage configuration on top of that same Intune layer.

Management concern	Windows 365	Azure Virtual Desktop
Primary plane	Intune and Microsoft 365 admin centre	Azure portal, plus Intune for the guest OS
Provisioning	Assign a licence and a provisioning policy	Build host pools, session hosts and app groups
Capacity control	Change the Cloud PC size	Host pool sizing, VM SKU choice, session density
Scaling	None to configure	Scaling plans with ramp-up, peak and ramp-down
Image management	Gallery image or a custom image	Azure Compute Gallery with versioning and staged rollout
Profile storage	On the Cloud PC, nothing to design	FSLogix containers on Azure Files, tier and size chosen by you
Application delivery	Intune Win32 apps	Image, Intune Win32, or MSIX App Attach
Monitoring	Endpoint analytics	Azure Monitor, per-host metrics, Log Analytics
Identity and access	Entra ID with Conditional Access	Entra ID with Conditional Access, plus RBAC on Azure resources
Patching	Intune update rings	Update rings plus session host patching and image rebuilds

Read down the AVD column and the pattern is clear: every row where Windows 365 says "nothing to configure" is a row where AVD gives you a lever. Those levers are precisely why AVD can be cheaper and faster than a Cloud PC, and precisely why it is not automatically either.

What is the best way to manage both AVD and Windows 365?

Short answer: Standardise everything that can be shared, and keep the platforms separate only where they genuinely differ. Identity, Conditional Access, application packaging and Intune policy should be common. Host pool design and scaling stay AVD-only, because Windows 365 has no equivalent.

Mixed estates are common and they work well when they are designed as one estate with two delivery mechanisms, rather than as two projects that happen to share a tenant.

The parts that should be shared:

• Identity and Conditional Access. One set of policies covering both, so a Cloud PC and an AVD session are held to the same access standard. Two divergent policy sets is how a gap opens.
• Application packaging. Package once, deliver to both. MSIX and Intune Win32 packages work across the two, so maintaining separate application estates is avoidable effort.
• Intune configuration and update rings. The guest operating system is Windows in both cases, so device configuration, security baselines and update rings should not fork.
• Monitoring and service desk process. Users do not care which platform their desktop runs on, and neither should the first line of a support ticket.

The parts that stay separate: host pool sizing, scaling plans, FSLogix storage and image versioning are AVD concerns with no Windows 365 counterpart, and Cloud PC size assignment and licence reclamation are Windows 365 concerns with no AVD counterpart. Trying to force those into a single process creates work rather than saving it.

The allocation rule we use most often is simple. Permanent staff with predictable hours go on Windows 365, because nothing needs sizing and the cost is known in advance. Task workers, contractors, seasonal staff and anyone needing GPU or a specialist VM series go on AVD, where the pool can flex around them.

What are the challenges of managing AVD and Windows 365 separately?

Short answer: Duplicated effort and divergent policy. Two application packaging streams, two sets of Conditional Access rules, two monitoring approaches and two support runbooks, for one population of users doing one job. The cost is rarely visible as a line item and usually shows up as drift.

The specific failure modes we see most often:

Policy divergence. Conditional Access is tightened on one platform after a review and not the other. Six months later the looser platform is the way in, and nobody planned it that way.

Application drift. An application gets updated in the AVD golden image but not in the Intune package that serves Cloud PCs, or the reverse. Users on different platforms are now running different versions of the same line-of-business software, which turns a support call into an investigation.

Inconsistent onboarding. A new starter's experience depends on which platform they land on, so the process has two branches and the less-used branch quietly decays.

Split cost visibility. Windows 365 shows up as a licence line and AVD as Azure consumption, on different bills, often owned by different people. Nobody sees total desktop cost in one place, which is how a business ends up unable to answer what its desktops actually cost.

Duplicate licensing. The one that costs real money quietly. AVD access rights bundled into Microsoft 365 E3, E5 or Business Premium get purchased again as standalone licences because the two platforms were procured by different processes.

None of these are arguments against running both. They are arguments against running both as two estates.

What overlooked factors drive up AVD and Windows 365 costs?

Short answer: On AVD, the hours the pool runs rather than the VM size, the FSLogix storage tier, and image bloat. On Windows 365, licences that are never reclaimed. In both cases, duplicate-purchased access rights already bundled in Microsoft 365.

The costs people expect are VM size and licence count. The ones that actually cause the drift are less obvious:

• Running hours, not VM size. Right-sizing a VM saves a percentage. Ramping the pool down out of hours and at weekends saves a multiple. A business working 50 hours a week on a pool that runs all 168 is carrying the single largest recoverable cost in most AVD estates, and it is a configuration change rather than new infrastructure.
• FSLogix on the wrong storage tier. Standard tier bills per transaction, and virtual desktops generate enormous transaction volumes. The per-gigabyte saving is routinely wiped out and then some. This one stays invisible until somebody reads the storage bill by transaction rather than by capacity.
• Image bloat. Every application baked into a golden image makes every host boot slower, patch slower and take longer to roll out. The cost is not a line item, it is compounding time on every cycle.
• Cloud PCs assigned to nobody. The commonest Windows 365 waste by a distance. Leavers, long-term absence and role changes leave licences assigned and billing at full rate. There is no autoscale to catch it, so it needs a reclamation routine or it accumulates indefinitely.
• Duplicate access rights. AVD access is included in Microsoft 365 E3, E5, F3, Business Premium and Windows Enterprise E3 and E5. Buying it again standalone is easy when licensing and infrastructure sit with different people.
• Log Analytics retention. Diagnostic settings left at defaults on a large estate quietly ingest and retain far more than anyone needs, and it lands on the Azure bill rather than anywhere anyone associates with desktops.

Our AVD cost optimisation quick wins post works through the AVD side in the order we tackle it, and the full AVD cost optimisation checklist sits on our Azure Virtual Desktop consultancy page.

How to actually decide

Start with usage pattern, not price. If most of your workforce logs in for similar hours most days, that predictability favours Windows 365's flat cost and low overhead. If usage genuinely varies, seasonal headcount, seasonal contractors, workloads that spike and then go quiet, AVD's metered model has real room to earn its extra management overhead back.

Then layer in workload requirements: anything needing GPU acceleration, custom VM sizing, or pooled multi-session cost efficiency at real scale points toward AVD regardless of usage pattern, because Windows 365 simply doesn't offer those configurations. Finally, be honest about who's going to manage whichever platform you pick, day two matters more than day one, and an AVD environment without someone actively tuning it tends to underperform both the alternatives.

If you're weighing this up for your own business, our end-user computing service covers Azure Virtual Desktop and Windows 365 design and consultancy, working out which model (or mix of models) actually fits your usage pattern and workforce, before anything gets built.

We've also written a more focused Windows 365 vs AVD comparison if you've already ruled out traditional desktops and want to go deeper on just those two. And if managed support for whichever platform you choose is the next question, our managed IT support team covers the day-to-day running of all three models, not just the ones we've built ourselves.