Windows 365 gives each user a dedicated Cloud PC for a fixed monthly licence, provisioned and managed from the Microsoft Intune admin centre. The cost is predictable per head and there is no host pool to size.
Comparison guide
Windows 365 vs AVD: which users belong where?
You are being asked whether desktops should move to Cloud PCs, and both answers are Microsoft's own. This page compares the two operating models the way a 50 to 600 user estate has to decide: who needs a persistent machine, what each model bills you for, and who ends up owning the work.
From £0.79 per active user/month · 14-day free trial
Card required to start. Connect your tenant in minutes.
Both products are Microsoft's. Nothing here is a criticism of either one: the expensive mistake is normally a group of users placed on the wrong model, not a bad product. Figures on this page are Microsoft UK list prices checked on 12 August 2026 and are directional rather than a quote. Last reviewed: August 2026.
The short answer
Windows 365 is a desktop you buy. Azure Virtual Desktop is infrastructure you run.
Both deliver Windows from Azure, and Windows 365 Enterprise uses Azure Virtual Desktop for remote connectivity underneath, so this is a choice of operating model rather than a choice of technology.
Azure Virtual Desktop gives you multi-session hosts you design, scale and pay for by consumption. It is the cheaper shape at density, and the more expensive one in effort.
Most estates between 50 and 600 users end up running both: Windows 365 for the people who need a persistent machine, Azure Virtual Desktop for density and for the workloads that need Azure-native control.
Comparison
Windows 365 Enterprise, Windows 365 Flex and Azure Virtual Desktop
Three Microsoft models, one estate. Read down the column that matches the group of users you are placing, not the one that matches the budget you already have.
| Decision factor | Windows 365 Enterprise | Windows 365 Flex | Azure Virtual Desktop |
|---|---|---|---|
| What a user gets | A dedicated Cloud PC. The same machine every session, with data that persists. | One active session per licence. Dedicated mode provisions up to three Cloud PCs per licence for people who are never online together; shared mode serves a group from one Cloud PC. | A session on a pooled multi-session host, or a personal host pool virtual machine where one user keeps one machine. |
| Cost shape | Fixed per user, per month, sized by vCPU, RAM and storage. | Fixed per licence, pooled at tenant level and sized on peak concurrency rather than headcount. | Consumption. You pay Azure for compute, storage and networking on top of the access licence. |
| Where you administer it | The Microsoft Intune admin centre. Provisioning policies create Cloud PCs automatically when a licence lands on a user in the right group. | The Microsoft Intune admin centre, with licences pooled at tenant level rather than assigned to named users. | The Azure portal, CLI, PowerShell or REST for host pools and session hosts, plus Intune for the session hosts you join to it. |
| Azure you have to run | None by default. A Microsoft-hosted network needs no Azure subscription; an Azure network connection is only required when you bring your own network. | The same as Enterprise. Bring your own network only when line-of-business connectivity needs it. | An Azure subscription you size, scale, patch and pay for, including images, profile containers and capacity. |
| Where density comes from | It does not. One user, one Cloud PC, and no density gain to chase. | Non-concurrent reuse rather than shared sessions: the licence is reused by people who are not signed in at the same time. | Windows 11 and Windows 10 Enterprise multi-session, which is exclusive to Azure Virtual Desktop and is where per-user cost falls at scale. |
| Skills the team needs | Intune skills. No virtual desktop design work. | Intune skills, plus honest concurrency data for the groups you are pooling. | Virtual desktop design: host pools, images, profile containers, autoscale rules and capacity planning, kept current. |
| Where it usually wins | Knowledge workers, developers and long-term contractors who need a persistent machine, especially where headcount is stable. | Shift, seasonal, part-time and occasional users who are never all signed in at once. | High-density estates, GPU workloads, published applications rather than full desktops, and anywhere you need Azure-native control of the host. |
Sizing and cost shape here are directional. They tell you whether a move is worth modelling properly. They are not a quote, and they exclude migration effort and any Azure spend you keep afterwards.
Cost model
What each model actually bills you for
The comparison that matters is not licence against licence. It is a fixed per-user licence against a variable Azure bill you already pay, plus the hours your team spends keeping the estate right.
Windows 365 Enterprise
£35.60 per user, per month
2 vCPU / 8 GB RAM / 128 GB storage
The baseline for personal desktops, where one person keeps one machine and the cost is predictable per head.
Windows 365 Flex
£86.00 per licence, per month
4 vCPU / 16 GB RAM / 128 GB storage
The baseline for shift, seasonal and intermittent users, priced against peak concurrency rather than every named user.
Azure Virtual Desktop
Your current monthly Azure run cost
Consumption, not a fixed size
There is no list price to compare against. The honest input is the total you already pay each month for compute, storage, images and profiles.
Windows 365 baselines are Microsoft UK list prices, excluding VAT and without Windows Hybrid Benefit, checked 12 August 2026. Prices change, so confirm current pricing before committing to a plan.
Any figure produced from these baselines is a directional estimator, not a quote. It tells you whether a migration is worth modelling properly. It excludes migration effort, application remediation, and the Azure spend you keep after moving.
Three things the licence comparison hides
Azure Virtual Desktop cost moves with usage, so a quiet month reads as a saving and a busy quarter reads as an overspend. Windows 365 cost does not move, which makes it easier to budget and harder to over-consume.
Multi-session density is real, but it is bought with design and operations time: host pool sizing, images, profile containers and autoscale rules that somebody has to keep current.
Neither model is cheaper on its own. The estates that save money are the ones that stop paying for persistent capacity for users who never needed it.
Start here
Put your own numbers against it.
Three figures and a couple of minutes give you a direction before anyone writes a business case.
Decision criteria
Decide per group of users, not per estate
Shortlist tests a 50 to 600 user organisation can actually apply. Run them per group; one answer for the whole estate is normally the expensive one.
Choose Windows 365 Enterprise when
Users need the same machine every day, headcount is reasonably stable, and a predictable per-user cost is worth more than a variable one. It is also the right answer when nobody on the team wants to own host pool design.
Choose Windows 365 Flex when
People share a role rather than a desk: shifts, seasonal peaks, part-time and occasional users who are never all signed in at once. Licences are pooled at tenant level and sized on peak concurrency, so the saving comes from people not overlapping.
Choose Azure Virtual Desktop when
You need multi-session density, GPU workloads, published applications rather than full desktops, or Azure-native control of the host. Windows 11 and Windows 10 Enterprise multi-session is exclusive to Azure Virtual Desktop.
Take this to the decision
A Cloud PC decision is rarely one person's: the IT lead who runs it, the finance lead who signs it, and often the MSP who supports it. Bring three things to that conversation: the user groups and their real concurrency, the current monthly Azure run cost, and a directional comparison against the Windows 365 baselines.
How the decision runs
Segment first. Place second. Measure always.
The order matters more than the product choice. Segment users by persistence, concurrency and application need, place each group on the model that fits, then hold both models against one cost baseline so the next review is evidence rather than opinion.
Migration path
Moving from Azure Virtual Desktop to Windows 365
Microsoft publishes a Graph-based Migration API that moves Azure virtual machines into Windows 365 Enterprise Cloud PCs from VHD snapshots. It is deliberately narrow: Enterprise Cloud PCs only, operating-system disk only, and no Intune interface, so partners build their own tooling around it. In practice the work is sequencing and evidence rather than copying.
Baseline what you run today
One number matters more than the rest: the current monthly Azure Virtual Desktop run cost, split by personal and pooled use. EtherInsights reads it from the tenant rather than from a spreadsheet.
Segment the users
Persistence, concurrency and application need, group by group. This is where the saving is found or lost, long before anything is provisioned.
Pilot a whole group, not one user
Move a complete group so profiles, applications and support load behave like production. Keep the Azure Virtual Desktop capacity running until that group is stable.
Decommission, then prove it
The saving is not real until the old capacity is switched off and the reduction shows up in the bill. Report it, then repeat with the next group.
Guides and analysis behind this comparison
Microsoft sources
FAQ
Windows 365 vs Azure Virtual Desktop FAQ
Short answers for the questions that come up before a Cloud PC decision reaches finance.
What is the difference between Windows 365 and Azure Virtual Desktop?
Windows 365 gives each user a dedicated Cloud PC for a fixed per-user monthly licence, provisioned and managed from the Microsoft Intune admin centre. Azure Virtual Desktop gives you host pools you design and scale yourself, billed as Azure consumption on top of the access licence. Windows 365 Enterprise uses Azure Virtual Desktop for remote connectivity underneath, so this is a choice of operating model rather than a choice of technology.
Is Windows 365 cheaper than Azure Virtual Desktop?
Sometimes, and the honest answer depends on density. Personal desktop estates and low-density pooled estates often compare well against the Windows 365 baselines, while high-density multi-session and GPU workloads usually do not. Windows 365 costs the same every month; Azure Virtual Desktop costs what it runs. Put your own monthly run cost through the Windows 365 TCO calculator for a directional answer before building a business case.
What is Windows 365 Flex?
Windows 365 Flex is the non-concurrent Cloud PC model. Microsoft renamed Windows 365 Frontline to Windows 365 Flex in May 2026, with no change to the product, its licensing or its capabilities. Each licence allows one active session at a time: in dedicated mode a single licence can provision up to three Cloud PCs for people who are never signed in together, and in shared mode a group works from one Cloud PC. Licences are pooled at tenant level rather than assigned to named users.
Can you run Windows 365 and Azure Virtual Desktop together?
Yes, and most estates between 50 and 600 users end up doing exactly that. The two are complementary: Windows 365 for users who need a persistent machine, Azure Virtual Desktop for density, GPU workloads and published applications. The same Microsoft 365 E3, E5 or Business Premium licence satisfies the Windows, Intune and Microsoft Entra ID prerequisites for both, although Windows 365 additionally needs its own paid per-user or pooled Flex licence.
Do I need Azure skills to run Windows 365?
Not for a standard deployment. Windows 365 Enterprise is managed from the Microsoft Intune admin centre, and a Microsoft-hosted network needs no Azure subscription at all. You only need an Azure network connection, and therefore an Azure subscription, when you bring your own network for line-of-business connectivity. Azure Virtual Desktop is the opposite: host pools, images, profile containers and autoscale are yours to design and own.
How do I migrate from Azure Virtual Desktop to Windows 365?
Microsoft publishes a Graph-based Migration API that moves Azure virtual machines into Windows 365 Enterprise Cloud PCs using VHD snapshots. It is narrow by design: Enterprise Cloud PCs only, operating-system disk only, and no Intune user interface, so partners build tooling around it. The real work is sequencing rather than copying. Baseline the current cost, segment the users, pilot a whole group, then decommission the old capacity and prove the reduction.
Which is better for an organisation with 50 to 600 users?
Neither, as a single answer for the whole estate. At that size the win normally comes from splitting: people who need a persistent machine on Windows 365 Enterprise, shift and occasional users on Windows 365 Flex, and Azure Virtual Desktop kept for density, GPU workloads and published applications. The expensive outcome is paying for persistent capacity for users who never needed it.
Does Windows 365 replace Azure Virtual Desktop?
No. Microsoft develops and sells both, and positions them for different jobs: dedicated per-user desktops with a fixed monthly cost and no virtualisation expertise for Windows 365, multi-session density and full Azure portal control for Azure Virtual Desktop. Windows 365 Enterprise relies on Azure Virtual Desktop for remote connectivity, so one is built on the other rather than replacing it.
Try EtherInsights
Stop guessing which users belong where.
Reads the live tenant instead of a spreadsheet, so the baseline is real.
Compares Azure Virtual Desktop run cost against Windows 365 Enterprise and Flex, group by group.
£0.79 per active user, per month, with a 14-day trial.