Microsoft cloud
W365
Windows 365
Windows 365 is Microsoft's Cloud PC service, the product family that provisions and hosts the individual Cloud PC desktops users connect to. It is positioned as the simpler alternative to self-managed Azure Virtual Desktop, for organisations that want a persistent, personal Windows desktop without owning the underlying infrastructure decisions.
Why W365 matters in a Microsoft estate
W365 matters because Microsoft 365, Azure, Windows 365, Teams, and related services are usually managed as one estate. The term connects to planning, cost, configuration, security, and day-two operational decisions across that estate.
How W365 shows up in practice
It is licensed in two main editions matched to different usage patterns. Windows 365 Enterprise is for users who need a dedicated, always-available, one-to-one desktop, licensed per user at a fixed monthly rate sized by vCPU, RAM, and storage. Windows 365 Flex, formerly branded Windows 365 Frontline, is for shift-based, part-time, or rotating cohorts, where provisioning against peak concurrent usage rather than total headcount produces a materially better fit and lower cost. The commercial proposition against Azure Virtual Desktop is predictability. A Windows 365 seat has a flat, published monthly price with no separate compute, storage, or networking line items to forecast, and no session-host sizing, scaling automation, or patching burden for the underlying infrastructure, since that is Microsoft's responsibility rather than the customer's.
That simplicity is also the boundary of the model. Because a Cloud PC is dedicated to one user, Windows 365 does not offer the shared, multi-session economics that make Azure Virtual Desktop cost-effective for high-density pooled cohorts. Estates with a genuine mix of dedicated knowledge-worker and shared or specialist usage typically end up running both services side by side, rather than choosing one exclusively.
Migration into Windows 365 from an existing Azure Virtual Desktop estate is supported through Microsoft's migration API, a REST interface built on Microsoft Graph that provisions a Cloud PC from a snapshot of a prepared virtual hard disk. It currently targets persistent, single-session, Entra-joined or hybrid-joined machines, though, rather than pooled multi-session host pools, which need a fresh Windows 365 or Flex build rather than a direct migration. Deciding whether a given cohort belongs on Windows 365 or Azure Virtual Desktop comes down to persistence needs, concurrency pattern, and administrative appetite, rather than price alone. This is why a directional cost comparison against the current AVD or on-premises baseline is the usual first step before committing to a migration plan.