Windows 365 Enterprise Pricing
Windows 365 Enterprise is a fixed per-user-per-month subscription priced by machine size. Entry configurations — 2 vCPU, 4 GB RAM, 128 GB storage — start around $31 per user per month, scaling up to roughly $123 per user per month for an 8 vCPU, 32 GB, 128 GB machine. Microsoft has trimmed pricing on some persistent-desktop and lower-tier configurations by around 20%. Each Enterprise Cloud PC user must also hold an eligible Windows and Microsoft 365 licence, so the Cloud PC line sits on top of an existing per-seat commitment within the wider advanced Microsoft estate.
The defining feature is predictability: unlike a consumption meter, the Cloud PC bill is the same every month regardless of usage. That simplicity is the product's main selling point — and also the source of its main waste, because a machine sized too large costs the same whether or not its capacity is ever used.
| Configuration | Indicative price (user/month) | Typical persona |
|---|---|---|
| 2 vCPU / 4 GB / 128 GB | ~$31 | Task / frontline worker |
| 2 vCPU / 8 GB / 128 GB | ~$41 | Knowledge worker |
| 4 vCPU / 16 GB / 128 GB | ~$66 | Power user / analyst |
| 8 vCPU / 32 GB / 128 GB | ~$123 | Developer / engineering |
Windows 365 vs Azure Virtual Desktop
The most important Cloud PC decision is not which Windows 365 size to buy — it is whether to use Windows 365 at all, or Azure Virtual Desktop (AVD) instead. Windows 365 is a fixed per-user subscription: predictable, simple to administer, always-on, and ideal for persistent single-user desktops. AVD is consumption-based — you pay for the underlying Azure compute and storage — which is far cheaper for shared, multi-session, part-time or seasonal workloads, but requires real engineering to size, scale and manage.
A call centre with 500 agents working fixed shifts is almost always cheaper on AVD multi-session than on 500 always-on Windows 365 subscriptions. A field workforce of 500 contractors who each need a persistent, individually-managed desktop is almost always simpler and cheaper on Windows 365. Most enterprises need both — and pay too much by forcing every persona onto one model.
The trade-off is the same predictable-versus-variable choice that runs through the entire estate, from Sentinel ingestion tiers to AI throughput. Fixed subscriptions win on simplicity and steady use; consumption wins on cost for variable demand.
The Real Business Case
On a pure hardware comparison, Windows 365 loses. A $31–$123 per-user-per-month subscription is $370–$1,480 a year — more than the amortised cost of a mid-range laptop spread over three years. The business case is never the hardware swap; it is everything the Cloud PC removes: device management overhead, secure remote and BYOD access, instant contractor onboarding and offboarding, and built-in disaster recovery. For a regulated or security-sensitive estate, the access-control benefit alone can justify the subscription — and it connects directly to the Entra ID Conditional Access posture that governs who reaches the Cloud PC and how.
Quantify those operational savings before approving a Cloud PC rollout. Where the device-management and security savings are real and large, Windows 365 pays for itself; where they are thin, a managed physical device is cheaper.
Persona-Matching the Cost
Within Windows 365, the cost lever is machine size. Most users do not need an 8 vCPU / 32 GB Cloud PC — task and knowledge workers run comfortably on the $31–$41 configurations, while the $123 top tier should be reserved for developers and engineering power users. Over-sizing every seat to a high tier is the single most common Windows 365 overspend, and because the subscription is fixed, the waste never shows up as a usage spike — it just sits in the monthly bill. Persona-matching a flat-tiered Cloud PC estate typically cuts 20–40% with no impact on the users who were over-provisioned.
This is the same persona discipline that governs hybrid-server cost through Azure Arc and government-tenant SKU selection in Microsoft 365 Government: licence to the actual workload, not the maximum conceivable one. Review assignments at least twice a year as roles change.
Buying Cloud PC Well
Windows 365 belongs in the Microsoft 365 and Azure conversation rather than a standalone purchase, because the Cloud PC entitlement layers on top of existing per-seat licences and the AVD alternative draws on your Azure commitment. The levers are: split the estate correctly between Windows 365 and AVD by persona, size each Cloud PC to its role, and fold the volume into the broader Microsoft commitment rather than buying at portal list. That benchmark-led approach is set out in the Microsoft Enterprise Agreement Guide and supported by the Microsoft vendor intelligence hub.
Before committing to a Cloud PC rollout, model Windows 365 against AVD for each persona and right-size the machine tiers. To pressure-test your end-user-compute strategy against current benchmarks, request a confidential briefing — the split between fixed and consumption desktops is where most Cloud PC budgets are won or lost.