Windows 365 or Azure Virtual Desktop? Start with the Operating Model
A question I get all the time is: Windows 365 or Azure Virtual Desktop? The honest answer is often yes. Not because the two products are interchangeable, but because most organisations do not have one uniform user population.
On the surface, both deliver Windows desktops and applications from the cloud. The more useful distinction is the operating model. Windows 365 is a finished service that you assign and manage. Azure Virtual Desktop is a platform that you design and operate. It is the difference between assigning a licence and assembling an environment.
That distinction usually tells you which team owns the result. If the service belongs with the endpoint team and should behave like another Intune-managed PC, start with Windows 365. If it belongs with a platform team that needs to control session hosts, host pools, scaling, profiles and application delivery, start with Azure Virtual Desktop.
Start with the operating model
A useful first pass is to compare what each service asks the operating team to own:
| Decision axis | Windows 365 Enterprise | Azure Virtual Desktop |
|---|---|---|
| Operating model | SaaS: Microsoft operates the desktop service | Cloud VDI platform: you design and operate the environment |
| Optimised for | Simplicity and a consistent end-user experience | Flexibility and control |
| Desktop model | One persistent Cloud PC per user and licence | Personal or pooled desktops; full desktop or individual applications |
| Operating systems | Windows 11; existing Windows 10 deployments require lifecycle and ESU planning | Windows 11 and supported Windows Server releases; legacy Windows 10 requires lifecycle and ESU planning. Single- or multi-session depends on the OS. |
| Primary management plane | Microsoft Intune | Azure plus the tools you select for images, profiles, monitoring and endpoint management |
| Commercial model | Predictable per-user, per-month licence | Eligible user access plus consumption for Azure infrastructure |
| Best first fit | Predictable, standardised, persistent personal desktops | Variable, pooled or specialised workloads that justify platform control |
Windows 10 22H2 reached end of support on 14 October 2025. Eligible Windows 365 and AVD deployments can receive Extended Security Updates (ESU), but security-update eligibility is not the same as full product support.
The caveat is that Windows 365 is no longer one operating pattern. Windows 365 Enterprise provides persistent, dedicated personal Cloud PCs. Windows 365 Flex changes the licensing and session model within the same managed service, adding dedicated and shared modes for populations whose headcount and concurrent use are different numbers. That gives you another option between an always-available personal Cloud PC and a VDI platform, but it does not turn Windows 365 into AVD.
Choose Windows 365 when the PC should be boring
I mean that as a compliment. For many users, a cloud PC should simply be there, keep its state and follow them between devices. The endpoint team should be able to apply the same Intune policies, applications and security controls it uses elsewhere without also becoming a virtualisation team.
Windows 365 Enterprise is the natural starting point when:
- each user needs a persistent, personal desktop;
- the population and required sizes are reasonably predictable;
- per-user monthly cost is preferable to an infrastructure bill that moves with runtime, storage and network usage;
- Intune is the operational centre of gravity; and
- the organisation values a smaller infrastructure surface more than it values tuning every part of the platform.
This does not mean there are no architecture decisions. Identity, images, network placement, access to on-premises resources, application packaging and recovery still need deliberate choices. A Microsoft-hosted network is simpler; an Azure network connection places the Cloud PC network interface in your virtual network and brings your routing, DNS, firewall and egress design into the picture. SaaS removes a class of infrastructure work. It does not remove architecture.
Choose AVD when control has a job to do
Azure Virtual Desktop earns its additional moving parts when those parts solve a real requirement. It supports personal and pooled host pools, Windows multi-session and RemoteApp-style application publishing. You choose the session-host sizes and locations, image process, profile design, scaling behaviour, storage, network path and much of the surrounding operating model.
That makes AVD the stronger starting point when:
- many users can share pooled session-host capacity;
- you need Windows multi-session or control over how applications are published;
- usage is intermittent enough that scaling and deallocation materially change the economics;
- a workload needs infrastructure choices that the Windows 365 service does not expose; or
- a platform team is prepared to own images, capacity, profiles, monitoring and recovery as a service.
The last point is the one that feature matrices tend to hide. AVD's control is valuable only when somebody uses and operates it. Otherwise, flexibility becomes a collection of decisions that still need owners at 02:00 on patch night.
Where Windows 365 Flex fits
There is a sizeable group between “one machine permanently assigned to every person” and “build a pooled VDI service.” Think of shift workers, contingent staff or people who need their own environment but do not all connect at once. That is where Windows 365 Flex deserves a look.
Flex Dedicated can provision up to three dedicated Cloud PCs per licence while allowing one concurrent session. Capacity therefore follows peak concurrency, not just headcount. Where available, the concurrency buffer is there for short and infrequent peaks; it is not a substitute for capacity planning. Also check what happens after sign-out or disconnection. Dedicated Cloud PCs power off after the sign-out idle period; eligible disconnected Cloud PCs can hibernate through Session State Retention. Neither model is a substitute for a machine that must keep compiling overnight.
Flex Shared is non-persistent: local user data is removed at sign-out. When enabled, User Experience Sync retains supported profile data and settings in separate cloud storage. Shared mode also supports Windows 365 Cloud Apps for application-only delivery. That can fit task-oriented work, but it is not merely a cheaper personal Cloud PC. Treat persistence, local administration, background processing and the user profile as design requirements, not footnotes.
Why the answer can be both
A mixed deployment is not an architectural failure. Users can access Windows 365 and AVD resources through Windows App, and both can use Microsoft Entra identity. Intune manages Windows 365 and is also available for supported AVD session-host scenarios, although pooled multi-session hosts have their own support boundaries. The shared entry points make a persona-based design practical; they do not erase the operational differences behind them.
A common shape is:
- Windows 365 Enterprise for people who need a standard, persistent PC every working day;
- Windows 365 Flex Dedicated for named users who need a personal environment but connect at different times;
- AVD pooled for multi-session density, published applications or highly variable shared capacity; and
- AVD personal for specialised personal desktops where the platform controls are worth operating.
Those are starting hypotheses, not automatic assignments. A developer, a contractor and a call-centre worker are not product SKUs. Their applications, identity, working hours, persistence needs and support model still decide the answer.
“Which is cheaper?” needs a usage pattern
Predictable per-user pricing and consumption pricing are different shapes, not a universal ranking. Windows 365 gives you a known licence cost for the selected configuration. AVD combines access eligibility with Azure costs such as virtual machines, storage and network traffic. Deallocating an AVD VM stops its pay-as-you-go compute charge, but disks and some network resources continue to cost money.
Compare the same thing on both sides: equivalent compute, storage, region, network path, hours of use and software entitlements. Then include the cost of operating images, profiles, scaling, monitoring and incident response. A cheap spreadsheet row can become an expensive service if it quietly assumes that engineering time is free.
Check the required Windows Enterprise, Intune and Entra ID entitlements, application licences, and any customer-managed networking costs as well.
For Flex, measure peak concurrent sessions, not only the number of eligible users. For AVD, measure actual connection and VM runtime, then model the scaling policy you can realistically operate. For Windows 365 Enterprise, look for Cloud PCs that are consistently underused before assuming that every user needs the same size or service model.
A decision workshop that produces an answer
Instead of starting with products, split the users into populations and ask the same questions for each one:
- Persistence: does the user need the same personal desktop and local state every time?
- Concurrency: how many assigned users are connected at the same time, including predictable peaks?
- Session model: full desktop, published applications, single-session or multi-session?
- Workload: what CPU, memory, GPU, storage, peripheral and background-processing requirements exist?
- Connectivity: which on-premises and cloud resources must be reachable, and what identity model do they require?
- Ownership: which team will patch, monitor, recover and pay for the service?
- Economics: is usage steady, scheduled, intermittent or unpredictable?
Then put the populations on two rough axes: predictable versus variable, and standardised versus specialised. The ratio is usually more informative than a platform-wide vote. Predictable and standardised pulls toward Windows 365 Enterprise. Variable and shared pulls toward AVD pooled. Lower concurrency with a need for personal desktops makes Flex Dedicated interesting. Specialised requirements may justify AVD personal, even when the user count is small.
Finally, pilot the uncertain groups. Measure sign-in and application launch times, resource use, concurrent connections, network behaviour, support effort and the user workflows that matter. A pilot should retire assumptions, not just prove that a desktop can open.
So, Windows 365 or Azure Virtual Desktop? Do not turn it into a religious debate. Decide what should be consumed as a service, what genuinely needs to be operated as a platform, and which users belong in each group. The answer may still be “yes,” but now it has an operating model behind it.