Windows 365 sells a fixed price per user Cloud PC while Azure Virtual Desktop bills the Azure capacity you consume, so the right choice turns on how steady and how poolable your users really are.
Key takeaways
- Windows 365 Enterprise runs from $28 to $765 per user per month by Cloud PC size.
- AVD has no fixed seat price. You pay for Azure compute, storage, and networking.
- Microsoft 365 E3 and E5 already grant the AVD access right at no extra cost.
- Steady full time users favor Windows 365. Variable or pooled users favor AVD.
- Windows 365 Flex adds a shared model at a 3:1 provisioning ratio.
- A mixed estate, priced per segment, is usually the lowest total cost.
This guide is for end user computing and procurement leaders comparing Windows 365 and AVD in 2026. Pair it with the Azure Hybrid Benefit guide and the Microsoft Practice page so licensing and cloud cost work together.
How do the two desktop models differ?
The split is fixed cost against variable cost. Windows 365 sells certainty, AVD sells flexibility, and the better fit depends on the user, not the brand.
What we saw across desktop estates in 2026 is that the model choice rarely fails on technology. It fails when procurement picks one model for the whole workforce and then pays for idle capacity or lost flexibility.
Both platforms share the same management plane. You enroll Cloud PCs and AVD hosts in Microsoft Intune and Microsoft Entra ID, apply the same policies, and patch through the same tooling. The difference is commercial, not operational, once the machines run.
For a buyer, that parity is the point. You are not choosing two technologies to support. You are choosing how to pay for the same Windows desktop, fixed per seat or metered by the hour.
How does Windows 365 work?
Windows 365 streams a personal Cloud PC at a fixed monthly price per user. Microsoft describes the service on its Windows 365 product pages, and the size you pick sets the rate.
Each seat is dedicated. The user gets the same virtual machine every session, so state persists and administration stays simple. You never size a host pool or schedule capacity.
There are two editions. Windows 365 Enterprise scales without a seat cap and needs the full prerequisite stack. Windows 365 Business caps at 300 seats, bundles a Windows Pro license, and drops the Intune and Entra ID P1 requirement for smaller estates.
How does AVD work?
AVD runs desktops on Azure infrastructure you size and manage. Microsoft documents it on the Azure Virtual Desktop pages, and you pay for the compute and storage you consume.
Sessions can be pooled, so many users share sized hosts. That is where AVD earns its keep, and also where it demands real engineering to size, autoscale, and control cost.
AVD also offers multi session Windows 11 Enterprise, where several users share one virtual machine. Windows 365 never does this; every Cloud PC is single user. Multi session is the lever that lets AVD pack density a fixed seat cannot match.
What do Windows 365 and AVD cost in 2026?
Windows 365 posts a public price list per Cloud PC size. AVD carries no seat price at all, so its cost is whatever Azure capacity you choose to run.
Every rate on this page is list. Under an Enterprise Agreement or a CSP contract, both Windows 365 seats and Azure consumption carry negotiated discounts, so treat the public numbers as a ceiling, not the price you should pay.
What are the Windows 365 Cloud PC sizes and prices?
Windows 365 Enterprise lists fifteen configurations, from a light 2 vCPU seat to a 32 vCPU workstation. The published 2026 rates below come from the Windows 365 Enterprise pricing page.
| Cloud PC size | vCPU / RAM / storage | Per user per month | Typical fit |
|---|---|---|---|
| Entry | 2 / 4 GB / 128 GB | $31 | Light task worker |
| Standard | 2 / 8 GB / 128 GB | $41 | Standard office user |
| Knowledge | 4 / 16 GB / 128 GB | $66 | Knowledge worker |
| Power | 4 / 16 GB / 256 GB | $75 | Power user |
| Developer | 8 / 32 GB / 128 GB | $123 | Developer |
| Engineering | 8 / 32 GB / 512 GB | $158 | Engineering seat |
| Workstation | 16 / 64 GB / 512 GB | $277 | Heavy workstation |
Prices scale with the machine, not with usage. A seat that sits idle overnight costs the same as one running all day, which is the core tradeoff against AVD.
Windows 365 Business uses a shorter price list at similar rates but without the enterprise management stack. For estates under 300 users with light needs, Business can undercut the Enterprise prerequisite cost, so price both before defaulting to Enterprise.
What drives the AVD bill?
AVD cost is Azure cost. The Azure Virtual Desktop pricing page shows the desktop right is free for licensed internal users, so you pay only for the virtual machines and disks.
| Cost component | What you pay | Main lever |
|---|---|---|
| Session host compute | Azure VM per hour | Autoscale, reserve, schedule |
| Storage (OS and FSLogix) | Managed disk and file share | Right size profiles |
| Networking and egress | Bandwidth consumed | Region and peering choices |
| External user access | $5.50 apps or $10.00 desktop per user per month | License internal users instead |
For internal employees the access right is already licensed, so the meter is pure infrastructure. External or third party users instead pay a per user access fee, billed only in months they actually connect.
Reserved instances for one or three years, plus Azure savings plans, are the largest lever on AVD compute. Committing to steady baseline capacity cuts the virtual machine rate substantially, while burst demand stays on pay as you go.
Storage is the quiet line item. FSLogix profile containers and operating system disks accumulate, and oversized profiles inflate the bill. Right sizing profile storage and choosing the correct disk tier keeps the meter honest.
Networking is usually minor but not zero. Egress and cross region traffic add up in large estates. Keep hosts and profile storage in the same region as your users to avoid needless bandwidth charges.
Reference points we check against the advisory engagement file before any Windows 365 or AVD commitment. Figures are public 2026 list rates.
What licensing prerequisites apply to both?
Both models lean on eligible Windows and Microsoft 365 licensing for the desktop access right. The trap is buying that right twice.
The prerequisite stack is where estates overspend without noticing. A user already on Microsoft 365 E3 holds the Windows Enterprise, Intune, and Entra ID rights that Windows 365 Enterprise needs, and the AVD access right as well.
Where do buyers double pay?
Windows 365 Enterprise requires Windows Enterprise, Microsoft Intune, and Microsoft Entra ID P1. Those components ship inside Microsoft 365 Business Premium, E3, and E5, so most estates already hold them before adding a Cloud PC.
AVD access is granted by the same Microsoft 365 plans, per the AVD licensing documentation. Check the entitlement you already hold before buying anything new.
Watch the edges. Microsoft 365 F3 grants AVD access but not the full Windows 365 Enterprise prerequisite set. Frontline and E3 users can therefore sit on different models inside one tenant, which is normal and often cheaper.
How do RDS CALs and Azure Hybrid Benefit fit?
An RDS Client Access License with Software Assurance, or an RDS User Subscription License, also grants AVD access. That matters for estates still on Remote Desktop Services who want to move without new user licenses.
Azure Hybrid Benefit does not discount the Windows client desktop. Reserved instances and Azure savings plans do cut the AVD compute bill, often sharply. Both are renewal levers, not defaults.
One caveat matters. Per user access pricing covers only client operating systems, not Windows Server session hosts, and it excludes Office and Microsoft Defender. Budget those separately when you model an external or third party AVD deployment.
How does cost compare across three workforce profiles?
The cost question is really a usage question. Model three profiles and the crossover between a fixed seat and a metered host becomes obvious.
Take the knowledge worker on a $66 flat Cloud PC. To beat that with AVD you need genuine pooling and aggressive off hours shutdown; a dedicated always on AVD host at similar specification rarely lands lower.
The contact center is the opposite. Fifty agents across two shifts share far fewer pooled hosts than fifty dedicated seats, and autoscale drops capacity to near zero overnight. That density is where AVD earns a real saving.
When does Windows 365 win?
- Full time users: always on, predictable monthly cost.
- Simple administration: no capacity planning to manage.
- Budgeting clarity: a known number per user per month.
When does AVD win?
- Pooled workers: many users sharing sized capacity.
- Out of hours scale down: pay less when nobody works.
- Seasonal demand: flex up and down with the calendar.
| Workforce profile | Usage pattern | Better model | Why |
|---|---|---|---|
| Knowledge worker, daily | Steady, dedicated | Windows 365 4 / 16 at $66 | The meter never idles enough to beat a flat seat |
| Contact center, two shifts | Pooled, high density | AVD pooled hosts | Share hosts and autoscale down between shifts |
| Seasonal or part time | Bursty, occasional | AVD or Windows 365 Flex | Pay only for hours actually connected |
Windows 365 versus AVD at a glance
| Dimension | Windows 365 | AVD |
|---|---|---|
| Pricing model | Fixed per user | Azure consumption |
| Best user type | Steady full time | Variable or pooled |
| Admin effort | Low | Higher, you size it |
| Cost control lever | Right size the plan | Scale and schedule capacity |
Which model fits which persona?
Map each persona to a model before you price anything. The matrix below is the fast version of that segmentation.
Personas are not fixed forever. A developer who once needed a heavy dedicated seat may move to a pooled GPU host as tooling changes. Revisit the mapping at each renewal rather than treating it as permanent.
| Persona | Usage | Recommended model | Note |
|---|---|---|---|
| Executive or knowledge worker | Daily, dedicated | Windows 365 Enterprise | Predictable, low admin |
| Developer or engineer | Heavy, dedicated | Windows 365 8 / 32 or AVD GPU | Depends on the tooling |
| Shift or frontline | Shared, part day | Windows 365 Flex | 3:1 provisioning ratio |
| Contact center | Pooled, high density | AVD pooled | Autoscale between shifts |
| External or third party | Occasional | AVD per user access | $5.50 apps or $10.00 desktop |
The costly mistake is not choosing AVD or Windows 365. It is choosing one of them for everyone.
Where does the standard advice on desktop virtualization fall short?
Most guides frame this as AVD is cheaper at scale and Windows 365 is simpler for small teams. That framing misses where the money actually leaks.
Where the common advice on AVD savings breaks down
We disagree with the blanket claim that AVD is always cheaper at scale. AVD only wins when you genuinely pool sessions, autoscale hosts down out of hours, and staff the engineering to keep that tuning honest month after month; a poorly sized AVD estate running dedicated hosts around the clock frequently costs more than the equivalent Windows 365 seats, carries higher operational risk, and buries its true run rate inside a variable Azure bill that no single owner is watching, which is precisely the pattern we are called in to unwind.
The reverse myth is just as costly. Parking seasonal or shift staff on fixed price Cloud PCs pays for capacity that sits dark for most of the day.
The honest comparison prices the engineering too. AVD needs image management, autoscale tuning, and a named owner watching the Azure bill. Fold that operating cost into the model, or the paper saving evaporates within a quarter.
How should you sequence a migration and renewal?
Treat the desktop decision as a renewal event, not a project. Sequence the licensing checks before you move a single workload.
What order should the work run in?
- Inventory existing Microsoft 365 and Windows entitlements for the access right.
- Segment users by daily active hours and by dedicated versus pooled need.
- Price each segment against the public Windows 365 and AVD rates.
- Model AVD with real autoscale schedules, not flat running hosts.
- Fold the desktop line into the EA or CSP renewal, not a separate buy.
At an Enterprise Agreement or CSP renewal, the desktop line is a lever. Bundle Cloud PC growth into the wider Microsoft negotiation rather than buying it in isolation at list price.
Run a pilot before a full cutover. Test image management, profile storage, and a realistic autoscale schedule on a small pool, then extrapolate the run rate before you commit the wider estate.
Expect a dual run period. During migration you may pay for both the old estate and the new Cloud PCs or AVD hosts. Keep that overlap short and budgeted, and time the cutover to your renewal date.
Reserved capacity, Flex sharing, and right sized seats are all concessions you can trade. Bring the segmentation model to the table so every seat maps to a defensible cost.
Ask for the desktop line in writing, not as a verbal quote. Cloud PC and Azure discounts should sit in the agreement with clear renewal caps, so the price you modeled is the price you keep.
What to do next
- Segment users by usage pattern before choosing a model.
- Assign steady full time users to Windows 365.
- Assign pooled or variable users to AVD.
- Confirm existing Microsoft 365 entitlements for the access right.
- Model AVD with realistic scale down schedules, not flat running.
- Fold Cloud PC growth into the next EA or CSP renewal.
- Plan a mixed estate where the user base is mixed.
Frequently asked questions
What is the difference between Windows 365 and AVD?
Windows 365 is a fixed price per user Cloud PC with predictable monthly cost. Azure Virtual Desktop, or AVD, is a consumption based desktop platform you size and run yourself on Azure. One trades flexibility for simplicity, the other does the reverse.
How is Windows 365 licensed?
Windows 365 licenses per user on a fixed monthly subscription tied to a chosen Cloud PC size. It also requires eligible Windows and Microsoft 365 licensing as a prerequisite, so confirm those before pricing the Cloud PC itself.
How is AVD licensed and priced?
AVD charges for the underlying Azure compute, storage, and networking you consume, plus an access right that many Microsoft 365 and Windows licenses already grant. The desktop entitlement is often included, so the real cost is the Azure infrastructure.
Which is cheaper, Windows 365 or AVD?
It depends on usage. Windows 365 wins for steady full time users who want predictable cost. AVD wins where you can pool resources, scale down out of hours, or run part time and seasonal users efficiently.
Can you run Windows 365 and AVD together?
Yes, and many enterprises do. Windows 365 suits knowledge workers who need an always on Cloud PC, while AVD suits pooled, variable, or specialized workloads. A mixed estate is common and often the lowest total cost.
What licensing prerequisites apply?
Both rely on eligible Windows and Microsoft 365 licensing for the desktop access right. Check that your existing Microsoft 365 plans already include the entitlement before adding new licenses, because double buying is a frequent and avoidable error.
Do Microsoft 365 E3 and E5 already include AVD access?
Yes. Microsoft 365 E3 and E5 both include the Azure Virtual Desktop access right at no extra charge. So do Business Premium, F3, and Windows Enterprise E3 and E5. Confirm the plan your users already hold before buying any separate AVD entitlement.
What does the AVD per user access license cost for external users?
External users pay a per user access fee, not an internal license. The 2026 rates are $5.50 per user per month for apps only and $10.00 for a full desktop with apps. You are billed only in months a user actually connects.
What is Windows 365 Flex and when does it help?
Windows 365 Flex, formerly Frontline, is a shared Cloud PC model for part time and shift staff. One license provisions up to three Cloud PCs at a 3:1 ratio, with one user active at a time. It suits workers who need a desktop for part of the day.
Can Azure reserved instances or Hybrid Benefit cut AVD cost?
Not through Azure Hybrid Benefit, which does not discount the Windows client desktop. Reserved instances and Azure savings plans do cut AVD compute cost, often materially, when host pools run predictable hours. They are renewal levers worth modeling before you commit.
