Contents
Key takeawaysWindows 365 vs AVDHow each is pricedWorked cost exampleLicenses each one needsWhen to pick whichWhat our rollouts showedControlling spendTalking to MicrosoftWhat to do nextFAQWindows 365 bills a fixed price per user for a dedicated Cloud PC, while Azure Virtual Desktop bills the Azure capacity you consume. Usage pattern, and whether anything switches idle hosts off, decides which costs less.
- Two billing models. Windows 365 is a fixed monthly price per user for a Cloud PC, from $41 to $132 on Enterprise list prices for the three standard sizes.
- AVD bills consumption. You pay Azure compute, storage and networking, plus the access license each user must already hold.
- Same base license. Both need an eligible Microsoft 365 or Windows license underneath, typically Microsoft 365 E3 or E5.
- Different strengths. Windows 365 wins on predictability and low operations, while AVD wins on density and flexibility.
- Usage decides. The break point is how many hours a desktop runs and how many users share a host, and headcount alone tells you little.
- Idle hosts erase savings. An AVD personal desktop left running all month can cost about twice a Cloud PC of the same size.
How do Windows 365 and Azure Virtual Desktop differ?
Windows 365 gives each user a dedicated Cloud PC at a fixed monthly price per user. Azure Virtual Desktop (AVD) runs virtual desktops on Azure infrastructure that you size, scale and pay for by consumption.
Both stream a Windows desktop from Microsoft's cloud, and Microsoft describes each on its Windows 365 page and its Azure Virtual Desktop page. Users see much the same desktop. The invoices differ, because one counts seats and the other meters every hour a host runs.
- Windows 365. A fixed price per user, one dedicated Cloud PC per license, and very little infrastructure for your team to run.
- Azure Virtual Desktop. Consumption billing on Azure virtual machines, with pooled hosts that let many users share one machine through Windows 11 Enterprise multi session.
- Both. Need an eligible Microsoft 365 or Windows license underneath, and both can be managed through Microsoft Intune and Microsoft Entra ID.
The operating model gap
Windows 365 hides the infrastructure. Microsoft runs the hosts, networking and storage, and sizes the machine to the plan you bought. AVD exposes it, so you choose the virtual machine size, build the images, design host pools and write the scaling rules.
That exposure buys control and density, and it costs management effort. An AVD rollout needs people who are comfortable in the Azure portal, with FSLogix profiles and with capacity planning. If you do not have them, you pay a partner or you pay for idle machines.
Where Windows 365 Flex fits
Windows 365 Flex is the shift worker edition Microsoft sold as Windows 365 Frontline until its 2026 rename. In dedicated mode one license covers up to three Cloud PCs, with one active at a time. In shared mode one license gives one Cloud PC that a group of users takes turns on.
Flex narrows the gap with AVD for part time and shift staff, but it is still one active user per license. It does not give you the multi session density of a pooled AVD host.
Azure and the MACC: Where the Leverage Actually Is
How is Windows 365 priced versus AVD?
Windows 365 is a flat fee per user per month, set by the Cloud PC size. AVD has no platform fee per user for internal staff, but you pay for Azure compute, storage and networking, and each user still needs the access license.
| Dimension | Windows 365 | Azure Virtual Desktop |
|---|---|---|
| Billing | Fixed per user | Azure consumption |
| Pooling | No, dedicated (Flex allows turns, one user at a time) | Yes, multi session |
| Predictability | High | Variable |
| Management | Low | Higher |
| Idle cost | Paid whether used or not | Zero compute when deallocated, disks still billed |
| Discount routes | Agreement pricing on the SKU | Reserved instances, Azure savings plan for compute |
Reading the pricing pages
- Windows 365 Business. Compare sizes on the plan and pricing page. At the time of writing, list prices are $36.00 for 2 vCPU, 8 GB RAM and 128 GB storage, $56.00 for 4 vCPU, 16 GB and 128 GB, and $108.80 for 8 vCPU, 32 GB and 256 GB, per user per month. Business is capped at 300 users per tenant.
- Windows 365 Enterprise. The same three sizes list at $41.00, $66.00 and $132.00 per user per month, with a GPU Standard plan at $537.00 sold through Microsoft sales.
- AVD. Model compute and storage on the AVD pricing details page, which lists pay as you go, reserved instance and savings plan options.
- Both. Add the underlying access license to every user in the model.
Business lists lower per seat than Enterprise for the same size. It does not support Group Policy or Intune policy management, has no Endpoint Analytics monitoring, and its Cloud PCs do not appear on the Windows 365 page in Intune. Tenants above 300 users, or those that need that control, pay the Enterprise price.
Microsoft EA renewal guide
Where Windows 365 seats and AVD consumption fit into your wider Microsoft renewal, and the terms to ask for.
Get the white paper →What does the cost comparison look like for one user?
For a user who works a normal day, an AVD personal desktop that shuts down out of hours can undercut Windows 365. The same desktop left running around the clock costs about twice as much. The example below uses the verified Windows 365 Enterprise price and assumed Azure rates.
Say you compare a 2 vCPU, 8 GB Cloud PC at $41 a month with an AVD personal desktop of the same size. For illustration, assume the Azure virtual machine costs $0.10 an hour and its disk $10 a month. Your region, VM series and discounts will change those two inputs, so price your own in the Azure calculator.
| Scenario | Hours billed | Compute | Disk | Total per user | 500 users |
|---|---|---|---|---|---|
| Windows 365 Enterprise | Fixed | Included | Included | $41.00 | $20,500 |
| AVD personal, always on | 730 | $73.00 | $10.00 | $83.00 | $41,500 |
| AVD personal, autoscaled to 11 hours on 22 workdays | 242 | $24.20 | $10.00 | $34.20 | $17,100 |
Break even hours per month = (Windows 365 price minus AVD disk cost) divided by the hourly VM rate. With these inputs that is ($41 minus $10) divided by $0.10, or 310 hours. Below 310 billed hours a month, the personal AVD desktop is cheaper. Above it, the Cloud PC is.
When you price the VM, use the Linux rate. Microsoft bills AVD session hosts running Windows 10 or 11 at Linux compute rates, because the user license already covers Windows.
Why compute is only part of the AVD bill
The autoscaled line saves $6.80 per user, about 17 percent, before you count anything else. AVD also needs profile storage, image builds, monitoring, networking and staff time, and each of those eats into the gap.
Pooled hosts change the arithmetic because the VM cost is split across users. Say one pooled host at an assumed $0.40 an hour carries 10 task workers on a single shift and runs 220 hours a month. Compute works out to $88, or $8.80 per user, which is why density matters far more than the hourly rate.
Which licensing stack does each cloud desktop need?
Both services need an eligible base license, typically Microsoft 365 E3 or E5, or a qualifying Windows Enterprise license. Without it, neither service is licensed to run.
Microsoft lists the AVD prerequisites on Microsoft Learn. Confirm your seats qualify before you size anything.
- AVD, Windows 10 and 11 desktops. Microsoft 365 E3, E5, A3, A5, F3 or Business Premium, Windows Enterprise E3 or E5, Windows Education A3 or A5, or Windows VDA per user.
- AVD, Windows Server session hosts. Remote Desktop Services CALs with Software Assurance, per user or per device, or RDS User Subscription Licenses.
- AVD for external users. Customers and partners who are not your staff need per user access pricing, enrolled on an Azure subscription and billed only for users who connect in the month. It is not available for Windows Server.
- Windows 365 Enterprise and Flex. Each user needs Windows Enterprise E3, Microsoft Intune and Microsoft Entra ID P1, which Microsoft 365 E3 and E5 include.
- Windows 365 Business. No licensing prerequisites, which is part of its appeal for small tenants.
The hidden prerequisite cost
If users lack a qualifying license, the cloud desktop project also becomes a Microsoft 365 uplift project. Budget for both. Contractors on Office 365 E1, or frontline staff on F1, do not carry the AVD access right; F3 does, as our frontline SKU guide explains.
Check the gap before the business case goes to the board. A $41 Cloud PC for 400 contractors is $16,400 a month on its own, and a base license for each of those 400 users sits on top of it.
When should you pick Windows 365 over AVD?
Pick Windows 365 when you want predictable cost and minimal operations for knowledge workers. Pick AVD when you have task workers who share sessions or need fine grained scaling, and the skills to run it.
- Windows 365. Dedicated users, simple billing, a lean IT team.
- AVD. Shared task workers, variable demand, cloud skills in house.
- Hybrid. Windows 365 for executives, AVD for call centers.
- Windows 365 Flex. Shift and part time staff whose working hours do not overlap.
Density is the deciding factor
Multi session AVD spreads many users across one host. That density is where AVD earns its keep against a fixed fee per user, and it only exists in AVD, because Windows 11 Enterprise multi session is not offered on Windows 365.
How the answer changes with company size
- Under 300 users. Windows 365 Business is often the whole answer. It needs no prerequisites, and a small team rarely has the Azure skills to tune host pools.
- Around 3,000 users. Many organizations at this size run Microsoft 365 E3 already, so Windows 365 Enterprise adds only the Cloud PC fee. AVD pays off for one or two large, predictable groups such as a contact center.
- 20,000 users and up. Segmentation is worth real effort. A few percent of density or idle time across thousands of hosts is a large sum, and AVD consumption also counts toward any Azure commitment you have signed.
What have we seen in recent cloud desktop rollouts?
The right model rarely matched the buyer's first instinct. Across roughly 20 to 28 cloud desktop rollouts that I advised on for Redress between 2024 and 2025, three patterns came up again and again.
- Predictability premium. Windows 365 ran 10 to 30 percent higher per heavy user, but it removed consumption surprises from the monthly bill.
- Density savings. AVD pooled hosts cut cost 20 to 40 percent for task workers who shared sessions.
- Idle waste. Always on AVD personal hosts erased the consumption advantage whenever they were left running.
Finance teams tend to find the third pattern late, because idle hours only appear on the Azure invoice after they are billed. The risk grows once a pilot group expands and no one owns the scaling plan, so we ask who owns autoscale before we look at price.
How do you control cloud desktop cost?
Control cost by matching the model to the usage pattern and by switching off idle compute. The fastest waste in AVD is an always on personal host.
- Autoscale AVD. Assign a scaling plan to every host pool so hosts shut off out of hours. Personal pools support deallocation or hibernation on disconnect and log off, with Start VM on Connect bringing the machine back.
- Right size Cloud PCs. Avoid oversized Windows 365 plans. Moving a user from 4 vCPU to 2 vCPU saves $25 a month at Enterprise list price.
- Segment users. Route heavy and light users to the right model.
- Commit only on the base load. Buy reserved instances or a savings plan for hosts that run every business day, and leave peak capacity on pay as you go.
- Watch outbound data. Windows 365 Enterprise Cloud PCs on your own virtual network pay Azure bandwidth rates, while Business includes an outbound allowance.
Why "AVD is always cheaper" fails for personal desktops
The common advice is that Azure Virtual Desktop is always cheaper because you only pay for what you use. We disagree. In the rollouts we advised, AVD personal desktops left running around the clock cost more than a fixed Windows 365 plan for the same user, because consumption billing punishes idle compute.
The better course is to split users by usage pattern. Send always on knowledge workers to Windows 365 for predictability, and keep AVD for pooled, schedulable task workloads where autoscale runs. Without disciplined autoscale, the flexible option becomes the expensive one.
Consumption is only cheaper when something turns it off. The model has to match the usage, whatever the brochure says.
How to check what you actually use
- Cloud PC recommendations report. In the Intune admin center, go to Reports, Cloud PC Overview, Cloud PC recommendations. It flags Cloud PCs as rightsized, undersized, oversized or underutilized, and underutilized means less than 40 hours of active connected time over 28 days.
- Cloud PC connection quality report. Use it before you downsize, so a cut does not show up as poor performance.
- Azure Virtual Desktop Insights. In Azure Monitor, it shows session host use and connection counts per host pool, which tells you real density.
- Azure Cost Management. Filter by the resource group or tag of each host pool to see compute and disk cost per user group.
- Microsoft 365 admin center. The licenses page shows who holds E3, E5, F3 or Business Premium, and who needs an uplift first.
What will Microsoft's account team say, and how should you answer?
Expect the account team to push whichever option grows the agreement fastest. These are the lines we hear most, with the replies that keep the discussion on your usage data.
- "Your E3 already covers the prerequisites, so Windows 365 is a simple add on." The prerequisites are covered, but the Cloud PC is still $41 to $132 a user each month. Show only the users who need a dedicated desktop all day.
- "AVD will help you consume your Azure commitment." Size any commitment to modeled AVD hours after autoscale. Always on hosts that burn down a commitment are still wasted spend.
- "Put everyone on 4 vCPU to be safe." Start most users at 2 vCPU and 8 GB, run the recommendations report after 28 days, and resize the undersized ones.
- "Flex covers three shift workers per license." Only one Cloud PC per license is active at a time. Confirm the shift pattern before you count three users per seat.
Contract terms to ask for
- Price hold on Windows 365 SKUs. Fix the per user price for the agreement term, so a later list increase does not reprice a desktop program you cannot easily unwind.
- Ramped quantities. Match Windows 365 seat counts to your rollout waves instead of paying for the full user count from day one.
- Resize and step down rights. Get written confirmation that you can move users to a smaller Cloud PC at anniversary without penalty.
- Commitment sized on your model. Any Azure commitment that includes AVD should follow your autoscaled forecast; see our Azure commitment negotiation guide.
For the licensing detail behind each option, including Flex and the external user rules, read our companion Windows 365 vs AVD licensing guide. For reserved capacity on AVD hosts, see reserved instances versus savings plans.
What to do next
- Segment your users. Split them into always on knowledge workers, schedulable task workers and shift staff.
- Confirm the base license. Check that every target user holds a qualifying Microsoft 365 or Windows license, and price the uplift for those who do not.
- Model each segment. Compare Windows 365 fixed cost with AVD consumption, using the break even hours for personal desktops and real density for pooled hosts.
- Design autoscale first. Write the scaling plan before you deploy a single AVD host, and name the person who owns it.
- Right size Cloud PC plans. Match plans to real performance needs and review the recommendations report every quarter.
- Pilot both models. Run each with a representative user group for at least one billing cycle.
- Decide on usage data. Lock the decision to what the pilot measured, whatever the vendor prefers, and put price holds and step down rights in the contract.
Frequently asked questions
What is the difference between Windows 365 and Azure Virtual Desktop?
Windows 365 is a packaged Cloud PC: one user, one machine, one monthly price, with Microsoft running the infrastructure. Azure Virtual Desktop is a service you assemble on your own Azure subscription, choosing VM sizes, images and host pools, and paying for the hours they run.
Is Azure Virtual Desktop cheaper than Windows 365?
Only when the hosts are shared or switched off. Pooled AVD hosts with autoscale usually beat a Cloud PC for task workers, but a personal AVD desktop that runs 24 hours a day costs more than a fixed Windows 365 plan of the same size, because every idle hour is billed.
Do Windows 365 and AVD need a Microsoft 365 license?
Yes for AVD and for Windows 365 Enterprise. AVD accepts Microsoft 365 E3, E5 or F3, among others, while Windows 365 Enterprise needs Windows Enterprise E3, Intune and Entra ID P1. Windows 365 Business is the exception, with no licensing prerequisites for tenants of up to 300 users.
When should I choose Windows 365?
Choose Windows 365 for knowledge workers who use one desktop most of the day, when you want a fixed monthly bill and have little Azure expertise in house. It also suits executives and remote staff who expect a persistent, personal machine that keeps their settings between sessions.
When should I choose Azure Virtual Desktop?
Choose AVD when large groups of task workers can share multi session hosts, when demand rises and falls through the day, or when you need to publish single apps rather than full desktops. It pays off when your team can build images, manage profiles and own the scaling plan.
What drives AVD cost the most?
The hours your session hosts run. Compute is usually the largest line on an AVD invoice, so a host that stays up overnight and at weekends costs several times what the same host costs when a scaling plan deallocates it. Disk and profile storage continue to bill even when hosts are off.
Can I use both Windows 365 and AVD?
Yes, and larger organizations often do. Both can be managed through Intune and Entra ID, so a mixed setup does not double the tooling. A common split puts executives and always on staff on Windows 365, and routes call centers and shared task workers to pooled AVD hosts.
How do I control cloud desktop spend?
Review usage monthly and act on it. Downsize Cloud PCs that the recommendations report flags as oversized, reclaim ones flagged as underutilized, confirm every AVD host pool has a scaling plan assigned, and cover only the always running base load with reserved instances or a savings plan.