Windows 365 vs Azure Virtual Desktop: cost compared

Microsoft describes the billing difference plainly. Windows 365 Cloud PCs for human use are billed in a per-user per-month model, so your organization does not manage the variability of compute and storage costs. For Azure Virtual Desktop, the license that entitles a user is a fixed cost per user each month regardless of behavior, and the infrastructure sits on your Azure bill, billed per second at pay as you go or discounted through reservations.

The operating models differ in the same direction. A Cloud PC is one persistent Windows 11 desktop per person that you manage in Intune. Azure Virtual Desktop leaves the host pool design, images, scaling and profile storage to you, and in return gives you pooled desktops, scaling plans and control over VM size and region. Neither is cheaper in the abstract. The cost depends on how many hours the machines really run, how many users can share one VM, and how much of your admin time each model consumes.

Microsoft's published US list prices for Windows 365 Enterprise, per user and month, for the sizes most organizations choose:

For Azure Virtual Desktop, Microsoft's pricing page splits the cost in two: user access rights, which are free for employees holding an eligible Windows or Microsoft 365 license, and Azure infrastructure, meaning virtual machines, storage for images, disks and user profiles, and networking. The same page notes that AVD virtual machines are charged at Linux compute rates for Windows 11 and Windows 10, which removes the Windows license line from the VM price. Virtual machines can be pay as you go or reserved, and Microsoft quotes savings of up to 72% for one or three year reserved instances versus pay as you go. Our comparison of reservations and savings plans covers how to commit the always-on baseline.

Prices are US dollar list prices. Swiss customers see a CHF list and agreement rates, and Windows 365 pricing in your market can differ. Use the proportions here for planning and your quote for budgeting. One more difference: with a Windows 365 Enterprise Cloud PC on your own network, traffic leaves through your Azure virtual network and Azure bandwidth pricing applies, which is a cost outside the license fee. On a Microsoft-hosted network, outbound data charges follow the Business model.

Microsoft lists the eligible licenses for Azure Virtual Desktop on Windows 11 and Windows 10: Microsoft 365 E3, E5, A3, A5, F3 and Business Premium, Windows Enterprise E3 and E5, Windows Education A3 and A5, and Windows VDA per user. Windows Server session hosts need RDS Client Access Licenses with Software Assurance, or RDS user subscription licenses. These licenses grant access for internal commercial purposes only. Per-user access pricing, billed through an Azure subscription, is for external commercial use, meaning your own customers. It does not cover your employees or contractors, who need the same eligible license as employees.

Windows 365 Enterprise requires that each user holds licenses for Windows E3, Intune and Microsoft Entra ID P1 and the Windows 365 license itself. Microsoft's licensing pages for Windows 365 Flex and Reserve accept Microsoft 365 E3, E5, F3 and Business Premium as meeting these prerequisites. Windows 365 Business is the simpler edition for up to 300 users and has no licensing prerequisites to buy and deploy. Windows 365 now has five editions: Business, Enterprise, Government, Flex (formerly Frontline) and Reserve.

Sources: Microsoft Learn, Licensing Azure Virtual Desktop; Requirements for Windows 365; Windows 365 service description.

The licensing prerequisite works in your favor if you already hold Microsoft 365 E3 or E5: the entitlement is paid for. If you run Microsoft 365 E1 or Business Standard, neither service is covered by your suite, and you would add Windows Enterprise E3 or move a plan before you start. Check this before you compare prices.

Microsoft's multi-session FAQ states that running Windows Enterprise multi-session outside the Azure Virtual Desktop service in production is not allowed. A Cloud PC is therefore a single-user machine, and you pay for its full size for every user. On Azure Virtual Desktop, a pooled host spreads the same VM across users. Microsoft's pricing page gives two planning densities: 2 users per vCPU for standard Office workers, and 6 per vCPU for low-intensity call center users. It also says that for most businesses a concurrency of 0.9 is a good starting point, because not every user is signed in at the same time.

The same page flags the catch: deployments with few users may see an incremental per-user cost if VMs are not fully used, and you should validate density with real workloads rather than trust the planning figure. Multi-session is unsuitable for users who need administrative rights to the OS, or for applications that do not work on a multi-session host. For those users, personal desktops are the right design, and there the comparison with Windows 365 becomes close, as the example below shows.

All figures are USD per month and illustrative. The Windows 365 price is Microsoft's US list price. The VM rates and the non-compute allowance are Zation planning assumptions and not Microsoft prices, so replace them in the Azure pricing calculator for your region and agreement before you rely on the result.

Assumptions.

1. 100 office users, all licensed for Microsoft 365 E3, so the Windows entitlement is already paid for in both models. Windows 365 Enterprise size: 2 vCPU, 8 GB, 128 GB at USD 41.
2. Pooled AVD: 90% concurrency means 90 simultaneous sessions. At 2 users per vCPU that needs 45 vCPU, so 12 VMs with 4 vCPU and 16 GB.
3. Compute rate for a 4 vCPU, 16 GB general purpose VM at the Linux rate: assumed USD 0.192 per hour. For a 2 vCPU, 8 GB VM: assumed USD 0.096 per hour.
4. Business hours VMs: 12 hours on 22 working days, 264 hours per month, using scaling plans. Always on: 730 hours.
5. Storage, FSLogix profiles, networking and monitoring: assumed USD 15 per user and month in every AVD scenario.
6. Reserved scenario: three year reservation at an assumed 50% discount on compute. Microsoft's ceiling is 72%.
7. Excluded: admin effort, support, Windows 365 egress on your own network.

Three results stand out. Pooled AVD is roughly half the price of Windows 365 when the VMs follow business hours, and still cheaper when they run around the clock. Personal AVD VMs with scaling plans cost about the same as a Cloud PC, so the choice then is about management, not price. And personal VMs left running all day cost about twice as much as the Cloud PC, which is the usual way AVD estates overspend.

The break-even is easy to read. Windows 365 stays ahead only when admin time and costs outside this model exceed the gap. In the pooled business-hours case that gap is about USD 20 per user and month, or USD 23'901 per year at 100 users. If running AVD takes you 0.2 of a full-time role, the admin cost can swallow that gap, and the Cloud PC becomes the better buy. That is a decision about your team, not about the price list.

Before any of this, check how many of your users need a virtual desktop at all. A VDI that serves 40 people who could work on a managed laptop is the most expensive line in the table, whichever model you pick. The question order we use: who needs a desktop, which of those can share a host, what do the remaining personal desktops cost on each model, and only then which licenses to buy. Tooling matters here, because the figures above move with your actual usage; see how Azure cost optimization tooling surfaces idle session hosts and oversized VMs.