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. It was previously called Windows Virtual Desktop (WVD), a name older documentation still uses for the same product. 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.

Who runs each layer of the desktopA grid of the three options against five layers. Azure Virtual Desktop: Microsoft runs the Azure hardware; you design and size the virtual machines, host pools, autoscaling, FSLogix profile storage and ongoing management. Windows 365: Microsoft runs the infrastructure and the Cloud PC; you pick a plan and assign licences. Traditional desktops: you run the device, Windows, the data and management. The cost lands as a metered cloud bill, a fixed monthly licence, or a hardware refresh cycle and a support desk.Who runs each layerThe same Windows desktop, delivered three waysAzure VirtualDesktopWindows 365TraditionaldesktopsHardwareAzure, run byMicrosoftMicrosoft handlesthe underlyinginfrastructureA physical PC orlaptop per userWhere WindowsrunsVirtual machinesyou design and sizeFixed-configurationCloud PC,provisionedautomaticallyLocally, on eachdevicePooling andscalingHost pools and anautoscale scalingplanNo host pool, noscaling planOne device per userProfile anddataFSLogix profilestorageStorage set by theplanOn the device, withfile sync or backupon topDay-to-daymanagementConfigure, scaleand secure it,ongoingPick a plan, assigna licenceIntune or a devicemanagement platformWhere the costlandsA metered cloudbillA fixed monthlylicenceA hardware refreshcycle and a supportdeskMicrosoft runs itYou, or a partner, run itNothing to run
Who runs each layer of the desktopA grid of the three options against five layers. Azure Virtual Desktop: Microsoft runs the Azure hardware; you design and size the virtual machines, host pools, autoscaling, FSLogix profile storage and ongoing management. Windows 365: Microsoft runs the infrastructure and the Cloud PC; you pick a plan and assign licences. Traditional desktops: you run the device, Windows, the data and management. The cost lands as a metered cloud bill, a fixed monthly licence, or a hardware refresh cycle and a support desk.Who runs each layerThe same Windows desktop, delivered three waysAzure Virtual DesktopHardwareAzure, run by MicrosoftWhere WindowsrunsVirtual machines youdesign and sizePooling andscalingHost pools and anautoscale scaling planProfile anddataFSLogix profile storageDay-to-daymanagementConfigure, scale andsecure it, ongoingWhere the costlandsA metered cloud billWindows 365HardwareMicrosoft handles theunderlying infrastructureWhere WindowsrunsFixed-configuration CloudPC, provisionedautomaticallyPooling andscalingNo host pool, no scalingplanProfile anddataStorage set by the planDay-to-daymanagementPick a plan, assign alicenceWhere the costlandsA fixed monthly licenceTraditional desktopsHardwareA physical PC or laptopper userWhere WindowsrunsLocally, on each devicePooling andscalingOne device per userProfile anddataOn the device, with filesync or backup on topDay-to-daymanagementIntune or a devicemanagement platformWhere the costlandsA hardware refresh cycleand a support deskMicrosoft runs itYou, or a partner, run itNothing to run
Who runs what in each model. With Azure Virtual Desktop, Microsoft runs the Azure platform and you, or a partner, design and run everything above it. Windows 365 hands the infrastructure and the Cloud PC to Microsoft and leaves you the plan and the licences. A traditional desktop is yours from the hardware up.

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.

"None of the three models is free of cost, they just put the cost in different places: a metered cloud bill, a fixed monthly licence, or a hardware refresh cycle and a support desk. The question isn't which one costs nothing, it's which one matches how your business actually works."

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, a GPU configuration outside its four GPU Cloud PC sizes, 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 a specific GPU VM series or pooled GPU hosts, 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 DesktopWindows 365Traditional desktops
Cost modelMetered Azure compute, storage and networkingFixed per-user, per-month licenceCapital/lease cost plus ongoing support
Cost predictabilityVariable, scales with usage and configurationHigh, fixed regardless of usagePredictable per refresh cycle, variable support cost
Management overheadHighest, ongoing host pool and scaling managementLowest, provision-and-manage via IntunePhysical asset and on-site support overhead
FlexibilityHighest, custom VM sizing, GPU, pooled hostsFixed plan menu, no custom configurationFull hardware choice, but per-device
Recovery from device lossFast, session isn't tied to hardwareFast, session isn't tied to hardwareSlow, user is down until device is fixed/replaced
Best suited toVariable usage, specialist or elastic workloadsStable headcount wanting simplicitySpecialist hardware, offline-first, small static teams

Common mistakes when choosing

Three mistakes come up again and again:

  • Copying another business's answer. 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.
  • Treating the decision as permanent. 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. Our AVD, Windows 365 or AVD Hybrid decision guide shows which criteria point to which option.
  • Underestimating AVD management. 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 Enterprise licenses each named user, while Windows 365 Flex lets shift workers who are never signed in together share Cloud PCs. So concurrency is where AVD can save, but only once its disks, profile storage, unreserved compute and running effort are counted against it, and in most estates we see that Windows 365 still comes out the more affordable.

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 Enterprise does offer GPU Cloud PCs (Microsoft Learn, updated 19 May 2026) in four fixed sizes, bought through a Microsoft account team rather than online and not available on Business, and they don't support nested virtualisation. If you run CAD, rendering or GPU-accelerated analysis and need a specific GPU VM series, pooled GPU hosts or the exact same GPU configuration for every user, AVD is the stronger choice, which is also Microsoft's own recommendation for identical configurations.
  • Shift patterns with Windows 365 Flex. Windows 365 Flex (formerly Frontline; Microsoft Learn, checked 5 October 2026) licenses one active session rather than one named user: in Dedicated mode a licence covers up to three Cloud PCs, each assigned to one user and used one at a time, and in Shared mode one Cloud PC is shared by a group, one user at a time, with user data deleted at sign-out. That claws back much of AVD's concurrency advantage for exactly the pattern that usually favours AVD. Check it 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, at pay-as-you-go rates unless reserved instances or a savings plan are committed, 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. Switching hosts off cuts compute only: each host's OS disk is still billed while it is switched off, and profile storage and the people time carry on.

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. In our experience Windows 365 is the more affordable choice in most estates once profiles, storage, unreserved compute and operating effort are counted; AVD wins where usage is genuinely concurrent and shift-based, or the workload needs control Windows 365 does not give.

What the monthly cost really includesLine by line: the Windows 365 per-user price includes compute, the OS disk, user profile storage, networking on the Microsoft-hosted network, and Microsoft running the infrastructure. Azure Virtual Desktop adds OS disks per host, FSLogix profile storage, pay-as-you-go compute unless reserved, networking and monitoring, and the people time to manage images, patching and scaling. Four factors decide it: named or concurrent users, usage hours, reserved instances and blast radius.What the monthly cost really includesOne Windows 365 price per user, against Azure Virtual Desktop compute plus everythingthat comes with itWindows 365One price per user, permonthAzure Virtual DesktopCompute, plus the linesbelowComputeIncluded: the Cloud PC'svCPUs and memory, by planEvery hour each host runs,at pay-as-you-go ratesunless reserved instances ora savings plan are committedOS diskIncluded: the Cloud PC'sdisk, by planA managed disk per host,still billed while the hostis switched offUser profilesIncluded: the profile liveson the Cloud PC's own diskFSLogix profile storage,such as Azure Files, and itstransactionsNetworking andmonitoringIncluded on theMicrosoft-hosted network,with no Azure subscriptionneededYour virtual network andbandwidth, plus log data ifyou use AVD InsightsRunning itMicrosoft runs theinfrastructure; you managethe Cloud PC configurationImage management, patching,host pools and scalingplans: people time, everymonthIncluded in the Windows 365 per-user priceAdded on top of AVD computeWhat decides itNamed or concurrent usersWindows 365 Business and Enterpriselicense each named user. Windows 365 Flex(formerly Frontline) licenses one activesession: up to three Cloud PCs inDedicated mode, or one Cloud PC shared bya group in Shared mode. Pooled AVD issized to peak concurrency.Usage hoursSwitching AVD hosts off cuts computeonly: disks, profile storage and peopletime carry on. A Windows 365 Business orEnterprise licence costs the same howevermany hours it is used.Reserved instancesA one- or three-year reservation or asavings plan lowers AVD compute on asteady baseline. Without one, every hosthour is billed at pay-as-you-go rates.Blast radiusA multi-session host is shared, so a badupdate, a runaway process or acompromised session can reach everyonesigned in to it. A Cloud PC is one user'smachine, so an incident stays with thatuser.In our experience Windows 365 is the more affordable choice in mostestates once profiles, storage, unreserved compute and operating effortare counted; AVD wins where usage is genuinely concurrent andshift-based, or the workload needs control Windows 365 does not give.Like for like, Windows 365 list prices per user a month at 4 October 2026, excluding VAT:Business from £24.30 (2 vCPU, 4 GB RAM) and Enterprise from £35.60 (2 vCPU, 8 GB RAM),storage included. Microsoft notes that extra costs may apply based on network usage.Sources: Microsoft UK Windows 365 pricing pages, 4 October 2026. Microsoft Learn, checked 5October 2026: Understand and estimate costs for Azure Virtual Desktop; States and billingstatus of Azure Virtual Machines; What is Windows 365 Flex?; Windows 365 networking deploymentoptions; Security recommendations for Azure Virtual Desktop.
What the monthly cost really includesLine by line: the Windows 365 per-user price includes compute, the OS disk, user profile storage, networking on the Microsoft-hosted network, and Microsoft running the infrastructure. Azure Virtual Desktop adds OS disks per host, FSLogix profile storage, pay-as-you-go compute unless reserved, networking and monitoring, and the people time to manage images, patching and scaling. Four factors decide it: named or concurrent users, usage hours, reserved instances and blast radius.What the monthly cost reallyincludesOne Windows 365 price per user, against AzureVirtual Desktop compute plus everything thatcomes with itWindows 365One price peruser, per monthAzure VirtualDesktopCompute, plus thelines belowComputeIncluded: theCloud PC's vCPUsand memory, byplanEvery hour eachhost runs, atpay-as-you-gorates unlessreservedinstances or asavings plan arecommittedOS diskIncluded: theCloud PC's disk,by planA managed diskper host, stillbilled while thehost is switchedoffUser profilesIncluded: theprofile lives onthe Cloud PC'sown diskFSLogix profilestorage, such asAzure Files, andits transactionsNetworking and monitoringIncluded on theMicrosoft-hostednetwork, with noAzuresubscriptionneededYour virtualnetwork andbandwidth, pluslog data if youuse AVD InsightsRunning itMicrosoft runstheinfrastructure;you manage theCloud PCconfigurationImage management,patching, hostpools and scalingplans: peopletime, every monthIncluded in the Windows 365 per-user priceAdded on top of AVD computeWhat decides itNamed or concurrent usersWindows 365 Business and Enterprise licenseeach named user. Windows 365 Flex (formerlyFrontline) licenses one active session: upto three Cloud PCs in Dedicated mode, or oneCloud PC shared by a group in Shared mode.Pooled AVD is sized to peak concurrency.Usage hoursSwitching AVD hosts off cuts compute only:disks, profile storage and people time carryon. A Windows 365 Business or Enterpriselicence costs the same however many hours itis used.Reserved instancesA one- or three-year reservation or asavings plan lowers AVD compute on a steadybaseline. Without one, every host hour isbilled at pay-as-you-go rates.Blast radiusA multi-session host is shared, so a badupdate, a runaway process or a compromisedsession can reach everyone signed in to it.A Cloud PC is one user's machine, so anincident stays with that user.In our experience Windows 365 is themore affordable choice in mostestates once profiles, storage,unreserved compute and operatingeffort are counted; AVD wins whereusage is genuinely concurrent andshift-based, or the workload needscontrol Windows 365 does not give.Like for like, Windows 365 list prices per usera month at 4 October 2026, excluding VAT:Business from £24.30 (2 vCPU, 4 GB RAM) andEnterprise from £35.60 (2 vCPU, 8 GB RAM),storage included. Microsoft notes that extracosts may apply based on network usage.Sources: Microsoft UK Windows 365 pricing pages, 4October 2026. Microsoft Learn, checked 5 October2026: Understand and estimate costs for AzureVirtual Desktop; States and billing status ofAzure Virtual Machines; What is Windows 365 Flex?;Windows 365 networking deployment options;Security recommendations for Azure VirtualDesktop.
A fair cost comparison counts every line, not AVD compute against a whole Windows 365 licence. The Windows 365 price per user already covers the Cloud PC's compute, disk, profile and network, and Microsoft runs it. On Azure Virtual Desktop each of those is a separate line on top of the session hosts, plus the time to run them.

What decides it: the operating model

What decides it is the operating model. Named users who sign in every day suit a Cloud PC each; genuinely concurrent or shift-based use suits pooled AVD or Windows 365 Flex. Blast radius matters as well as price: a multi-session host is shared, so a bad update, a runaway process or a compromised session can reach everyone signed in to it, while a Cloud PC is one user's machine and an incident stays with that user. Microsoft's own security recommendations for Azure Virtual Desktop (Microsoft Learn, checked 5 October 2026) tie multi-session to the trust level between the users sharing a host, and recommend a personal desktop for users who need administrative privileges.

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 concernWindows 365Azure Virtual Desktop
Primary planeIntune and Microsoft 365 admin centreAzure portal, plus Intune for the guest OS
ProvisioningAssign a licence and a provisioning policyBuild host pools, session hosts and app groups
Capacity controlChange the Cloud PC sizeHost pool sizing, VM SKU choice, session density
ScalingNone to configureScaling plans with ramp-up, peak and ramp-down
Image managementGallery image or a custom imageAzure Compute Gallery with versioning and staged rollout
Profile storageOn the Cloud PC, nothing to designFSLogix containers on Azure Files, tier and size chosen by you
Application deliveryIntune Win32 appsImage, Intune Win32, or MSIX App Attach
MonitoringEndpoint analyticsAzure Monitor, per-host metrics, Log Analytics
Identity and accessEntra ID with Conditional AccessEntra ID with Conditional Access, plus RBAC on Azure resources
PatchingIntune update ringsUpdate 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 a specific GPU or 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 a specific GPU VM series, 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.

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.

This is one of a series. The rest, covering licensing, desktops, support models and certification in the same format, are listed on all our IT comparison guides.

Frequently asked

Is Azure Virtual Desktop or Windows 365 cheaper?

It depends on the operating model, not on which platform is inherently cheaper. In our experience Windows 365 is the more affordable choice in most estates once profiles, storage, unreserved compute and operating effort are counted; AVD wins where usage is genuinely concurrent and shift-based, or the workload needs control Windows 365 does not give. Compare like with like: AVD compute alone against a full Windows 365 licence leaves out OS disks, FSLogix profile storage, networking, monitoring and the people time to run the hosts, all of which the Windows 365 price already covers or makes unnecessary. For shift workers, check Windows 365 Flex (formerly Frontline) too, which licenses one active session rather than one named user. Traditional desktops move the cost elsewhere entirely, into hardware refresh cycles and on-site support, which doesn't show up on a monthly cloud bill but is very real. The caveat worth stating plainly is that AVD's cost also scales with configuration quality, not just usage: oversized VMs, no autoscaling plan and premium storage nobody needed can leave a poorly tuned environment costing more than either alternative. The saving is earned by ongoing tuning rather than granted by the platform.

Can you run Windows 365 and AVD side by side?

Yes, and plenty of organisations do. It's common to put predictable, steady-state users on Windows 365 for the flat cost and consistent performance, and use AVD for elastic scenarios: contractors, seasonal peaks, dev/test pools, or specialist workloads that need pooled multi-session hosts or a GPU VM series Windows 365 doesn't offer. The two aren't mutually exclusive, and mixing them by workload is often the right answer rather than a compromise. The trade-off is that you take on both management models at once. The Windows 365 side stays light, provisioning itself when you assign a licence and managed through the same Intune tooling as any other Windows endpoint, while the AVD side still needs host pools, session host images, FSLogix profile storage and scaling plans actively maintained. That's a reasonable price when a real workload needs configurations the fixed Windows 365 plan menu doesn't offer, and hard to justify when nothing does.

Do you still pay for a Windows 365 Cloud PC when nobody is using it?

Yes. Windows 365 is licensed per user for a fixed monthly fee, and each Cloud PC belongs to one named user, so a Cloud PC assigned to someone on long-term leave costs the same as one in daily use. Nothing is pooled, so there is nothing to scale down. That is the trade-off for the predictable price, and it is why reclaiming licences from leavers and long-term absences matters more on Windows 365 than any sizing decision does.

Do I still need on-premises servers if I move to AVD or Windows 365?

Not for the desktop itself, but line-of-business applications and file shares that depend on on-premises infrastructure don't disappear just because the desktop moved to the cloud. Some organisations run virtual desktops that still depend on an on-premises domain controller, an ERP server, or a legacy application server over a site-to-site VPN or ExpressRoute. Moving the desktop layer to the cloud is a real step forward, but it's not automatically a full migration off on-premises infrastructure unless you plan for that separately. What it does remove is the part of the estate that scales with headcount: the per-device hardware refresh cycle, the on-site support and the asset-lifecycle admin that grow roughly linearly with the number of physical machines you own. What's left behind is a fixed, countable set of servers, and treating their migration as its own project with its own timeline is more honest than assuming the desktop move quietly carried them along too.

What happens to a traditional desktop rollout during a hardware failure?

The user is typically down until the device is repaired or replaced, because their profile, applications and data live on that specific machine (or are only partially synced to the cloud). With AVD or Windows 365, a failed physical device is far less disruptive: the user's session lives in Azure, so they log in from a different device, a personal laptop, a loan machine, even a tablet, and are back at their desktop within minutes. This is one of the most underrated differences between the models and rarely shows up in a pure cost comparison. The honest counterweight is that cloud desktops move the failure rather than remove it. A real-world AVD session host typically carries somewhere around 20-30 concurrent users, so a host going down takes that whole group offline at once, while a Windows 365 Cloud PC is dedicated to one named user and fails for exactly one person. Neither is wrong, but it's the trade-off a pure hardware-failure comparison misses.

Is Windows 365 the same as a remote desktop connection to a normal PC?

No. A remote desktop connection (RDP to a physical PC, or a basic remote-access tool) still depends on that physical machine being switched on, on the network and working. Windows 365 provisions a genuine Cloud PC, a persistent virtual machine that exists independently of any physical hardware, with its own compute, storage and Windows licence, hosted in Microsoft's cloud rather than routed through an office PC. The user experience looks similar from the login screen, but the underlying architecture, resilience and management model are completely different. The management difference is the practical one: a Cloud PC provisions itself once you assign a licence and is then managed through the same Intune and Microsoft 365 tooling as any other Windows endpoint, with no office machine that has to stay switched on. The limit is that you pick from a fixed menu of plans, so anything needing GPU acceleration or a custom vCPU and memory ratio falls outside what Windows 365 offers.