Windows 365 vs AVD licensing and cost in 2026. Fixed per user seats against Azure consumption.

Windows 365 sells a fixed price per user Cloud PC, while Azure Virtual Desktop bills the Azure capacity you consume. The right choice turns on how steady your users are and how many can share hosts.

This guide is for end user computing and procurement leads choosing between Windows 365 and Azure Virtual Desktop (AVD) in 2026. Read it with our Azure Hybrid Benefit guide, and see the Microsoft Practice page if a renewal is close.

How do Windows 365 and AVD differ?

Windows 365 is a fixed monthly price per user for a dedicated Cloud PC. AVD is a desktop platform you build on Azure, where you pay for the compute, storage and networking you consume. Windows 365 gives you a predictable bill, and AVD gives you control over capacity. Which one fits depends on how each group of users works.

Once the machines are running, the two look alike to your support team. Cloud PCs and AVD session hosts both enroll in Microsoft Intune and Microsoft Entra ID and patch through the same tooling. So the decision is mostly commercial. You are choosing whether to pay for the same Windows desktop per seat or by the hour.

How does Windows 365 work?

Windows 365 streams a personal Cloud PC to each user at a fixed monthly price, set by the size you pick. Microsoft describes the service on its Windows 365 product pages. Every seat is dedicated, so the user gets the same virtual machine each session and their state persists.

You never size a host pool or schedule capacity. Microsoft runs the infrastructure, and your team manages the Cloud PC like any other Intune device. If a user needs more power, you resize the Cloud PC from the Intune admin center and the new price applies.

What separates Windows 365 Enterprise from Business?

• Enterprise. No seat cap. Each user must hold Windows Enterprise E3, Microsoft Intune and Microsoft Entra ID P1 alongside the Windows 365 license.
• Business. Capped at 300 seats and bought on its own, with no separate Windows Enterprise, Intune or Entra ID P1 license required. Microsoft currently lists three sizes: 2 vCPU, 8 GB, 128 GB at $36; 4 vCPU, 16 GB, 128 GB at $56; and 8 vCPU, 32 GB, 256 GB at $108.80 per user per month.
• Flex. The shared model for shift and part time staff, sold as a separate product and covered in the persona section below.

At today's list prices Business costs less per seat than the matching Enterprise size, $36 against $41 for 2 vCPU and 8 GB, and it needs no prerequisite licenses. For organizations under 300 users with light needs, price both before you default to Enterprise. Business gives up the Intune based management that larger IT teams rely on.

How does AVD work?

AVD runs desktops and published apps on Azure virtual machines that you size and manage. Microsoft documents it on the Azure Virtual Desktop pages. You can give each user a personal host, or pool users so many of them share a set of sized hosts.

AVD also runs Windows 11 Enterprise multi session, where several users share one virtual machine at the same time. Windows 365 never does this, because every Cloud PC is single user. Multi session packs more users onto the same compute than a fixed seat can. It is also why AVD needs real engineering to size, autoscale and keep in check.

What do Windows 365 and AVD cost in 2026?

Windows 365 Enterprise runs from $28 to $765 per user per month depending on Cloud PC size. AVD has 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 can carry negotiated discounts, so treat the public numbers as a ceiling.

What are the Windows 365 Cloud PC sizes and prices?

Windows 365 Enterprise lists 15 standard 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.

Prices scale with the machine size alone. A seat that sits idle overnight costs the same as one running all day, which is the core tradeoff against AVD. Graphics seats are priced separately, from GPU Select at $310 to GPU Max at $1,914 per user per month.

Watch the storage column when you pick sizes. Moving a 4 vCPU seat from 128 GB to 256 GB adds $9 a month per user, and users whose files sit in OneDrive rarely need the larger disk.

What drives the AVD bill?

AVD cost is Azure cost. The Azure Virtual Desktop pricing page confirms that licensed internal users access Windows desktops at no additional cost, so you pay for the virtual machines, disks and network traffic behind them.

Compute is the largest line. Reserved instances for one or three years, or an Azure savings plan, cut the virtual machine rate on steady baseline capacity, while burst demand stays on pay as you go. Our reserved instances and savings plans guide covers which commitment suits which host pool.

Storage gets less attention than compute. FSLogix profile containers and operating system disks accumulate, and oversized profiles inflate the bill month after month. Networking is usually minor but not zero; egress and cross region traffic add up once thousands of users connect.

Who pays the per user access fee?

Only external users. Per user access pricing exists for organizations that deliver apps or desktops to their own customers, such as a software company streaming its application. The rate is $5.50 per user per month for apps only and $10.00 for a full desktop with apps, billed only in months a user connects.

Contractors and vendors working for your business count as internal users under Microsoft's rules and need an eligible license. Per user access pricing also excludes Windows Server session hosts, Microsoft Office and Microsoft Defender, so budget those separately when you model an external deployment.

Which licenses do Windows 365 and AVD require?

Both rely on an eligible Windows or Microsoft 365 license underneath, and most enterprises already own it. The common error is buying that right a second time.

A user on Microsoft 365 E3 already holds every prerequisite Windows 365 Enterprise needs, plus the AVD access right, so AVD access adds $0 to that user's cost. Overspend here usually happens because the Cloud PC is bought by a different team from the one that owns the Microsoft 365 agreement.

Where do buyers pay twice?

The AVD licensing documentation lists the plans that grant access to Windows 10 and 11 Enterprise desktops, single or multi session:

• Microsoft 365. E3, E5, A3, A5, F3 and Business Premium.
• Windows. Windows Enterprise E3 and E5, Windows Education A3 and A5, and Windows VDA per user.

Double payment shows up in three places: a standalone Windows Enterprise or Intune line added for Cloud PC users who already hold E3 or E5, a Windows VDA purchase for AVD users on Business Premium, and per user access fees charged for contractors who should be on an internal license.

Microsoft 365 F3 grants AVD access, and Microsoft's Windows 365 FAQ lists F3 among the suites that carry every Windows 365 Enterprise and Flex prerequisite. Frontline and E3 users can therefore sit on different models inside one tenant, which is normal and often cheaper. Our E3, E5 and F3 comparison covers which users belong on which plan.

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, but only to Windows Server session hosts. That matters for organizations still on Remote Desktop Services that want to move server based desktops to Azure without buying new user licenses.

Azure Hybrid Benefit does not discount the Windows client desktop. Windows 10 and 11 Enterprise hosts deployed with the Windows_Client license type already carry no extra Windows license fee for eligible users. The benefit does apply to Windows Server session hosts, but for client desktops the compute saving comes from reserved instances and savings plans.

How do you check what you already own?

1. Microsoft 365 admin center. Under Billing, then Licenses, export assigned plans per user and flag everyone on E3, E5, F3 or Business Premium.
2. Your agreement's license statement. Check the Enterprise Agreement or CSP records for standalone Windows Enterprise, Windows VDA, Intune or Entra ID P1 lines that overlap with suites.
3. Intune admin center. The Windows 365 usage reports show which Cloud PCs are barely used and could be downsized or moved to Flex.
4. Flex license counts. Flex licenses are counted at tenant level and consumed by provisioning policies, not assigned to named users, so the license page will not tell you who uses them. Read real use from the Windows 365 reports in Intune.
5. Azure PowerShell. Run Get-AzVM on AVD session hosts and confirm the license type reads Windows_Client, so you are not paying for a Windows license you already hold.
6. Azure Cost Management. Tag each host pool and read its monthly run rate, so AVD spend has a named owner and a number.

Which is cheaper, Windows 365 or AVD?

It depends on usage. Windows 365 is usually cheaper for steady full time users, and AVD is usually cheaper where users can share hosts or where demand drops out of hours or by season. Model your own profiles and the crossover becomes clear.

When does Windows 365 win?

• Full time users. Always on desktops with a predictable monthly cost.
• Simple administration. No host pools, images or capacity plans to manage.
• Budgeting clarity. A known number per user per month that finance can forecast.
• Small IT teams. No need to staff autoscale tuning or Azure cost monitoring.

When does AVD win?

• Pooled workers. Many users sharing sized multi session hosts.
• Out of hours scale down. Hosts shut down when shifts end, so you pay less overnight and at weekends.
• Seasonal demand. Capacity that grows and shrinks with the calendar.
• External users and published apps. RemoteApp streaming to customers on per user access pricing.

A worked example across three workforce profiles

Say you run three groups of users. The Azure rates below are assumptions to show the method, not quotes. Replace them with rates for your own region, VM size and commitment from the Azure pricing calculator.

• Personal host. 4 vCPU and 16 GB at $0.20 per hour, plus $10 per month for its disk.
• Pooled host. 8 vCPU and 32 GB at $0.80 per hour, carrying 10 users at once.

For the knowledge worker, a personal AVD host costs the same as the $66 seat at about 280 hours a month ($66 minus $10 of disk, divided by $0.20). That is 12 to 13 hours per working day with weekends off. The scheduled host saves $12 per user per month, or $6,000 across 500 users, before engineering costs.

The contact center is the opposite case. Fifty agents per shift share five pooled hosts instead of 100 dedicated seats, and autoscale drops capacity close to zero overnight. The saving holds even at double our assumed host rate, though Windows 365 Flex narrows it, so get a Flex quote for this group before you build host pools.

Which model fits which type of user?

Map each group of users to a model before you price anything. The table below is the short version of that segmentation, and it usually produces a mixed answer.

Personas also change. A developer who needed a heavy dedicated seat two years ago may move to a pooled GPU host as tooling changes. Revisit the mapping at each renewal instead of treating it as permanent.

How does Windows 365 Flex change the shift worker case?

Windows 365 Flex, sold as Windows 365 Frontline until Microsoft renamed it in 2026, is built for staff who need a desktop for part of the day. In dedicated mode one license provisions up to three Cloud PCs, one per worker, with one active at a time. Shared mode serves ad hoc users from a pool instead.

Flex keeps the fixed price and simple administration of Windows 365 while dividing the cost across shifts. Its prerequisites match Enterprise, and F3 covers them. Microsoft also states that Flex is a separate product outside the Microsoft 365 F1 and F3 eligibility conditions, so the users on it do not have to meet the frontline worker definition.

The costly mistake is choosing one of them for everyone, whichever one it is.

What have we seen in Windows 365 and AVD decisions?

In the desktop environments we benchmarked in 2026, the choice rarely failed on technology. It failed when procurement picked one model for the whole workforce and then paid for idle capacity or lost flexibility.

The pattern runs both ways. Steady knowledge workers get over engineered onto AVD, with dedicated hosts that cost more than a Cloud PC, while seasonal staff get parked on fixed price Cloud PCs. The savings appear once you segment users by usage pattern first and assign a model per segment.

Why we do not accept that AVD is always cheaper at scale

Most guides say AVD is cheaper at scale and Windows 365 is simpler for small teams. We disagree with the first half. AVD only wins when you pool sessions, scale hosts down out of hours and staff the engineering to keep that tuning honest every month.

A poorly sized AVD deployment running dedicated hosts around the clock often costs more than the equivalent Windows 365 seats. It also carries more operational risk and hides its run rate inside a variable Azure bill with no single owner. That is the situation we are most often called in to unwind.

Is the reverse mistake as expensive?

Yes. Parking seasonal or shift staff on fixed price Cloud PCs pays for capacity that sits unused most of the day. In the worked example, 200 seasonal seats held all year cost more than ten times the in season AVD compute. Even priced for the three busy months only, the seats come to $24,600, nearly three times the AVD figure.

What will Microsoft's account team say, and how should you answer?

Expect the conversation to push toward one model and one purchase, usually tied to the wider Microsoft 365 renewal. These are the lines we hear most, with the replies that keep the decision yours.

• "Put everyone on Windows 365 and we will discount the first year." Ask for the price per Cloud PC size held for the full term, and price only the steady segment. A first year discount on seats you do not need is still overspend.
• "AVD needs a partner and a team, so its total cost is higher." Agree where it is true, then show your own sign in hours by group. Ask Microsoft to price the pooled segment against your autoscale schedule and real shift hours.
• "These users need Windows Enterprise and Intune added." Send the license export showing E3, E5 or Business Premium. The prerequisites are already inside those suites.
• "Sign an Azure consumption commitment and we will fund the migration." Size any commitment to the host hours your baseline pools will use with shutdown schedules in place, never to an always on estimate.

What should the contract say?

Get the desktop line in writing, inside the agreement, with the same care as the Microsoft 365 suites. A verbal quote on Cloud PC pricing does not survive the next renewal.

Terms to ask for

• Price hold per Cloud PC size. Fixes the rate for each configuration you plan to use for the full term, so resizing later does not reopen pricing.
• Renewal cap. Limits the uplift on Windows 365 seats at the next renewal, so the price you modeled is the price you keep.
• Ramped seat counts. Cloud PC seats grow with migration waves, so you do not pay for the full count from day one.
• Reduction at anniversary. Allows seats to drop when users move to Flex or AVD, instead of locking the peak count for three years.
• Resize without penalty. You can move users down a size once usage reports show they are oversized.
• Azure discount terms in writing. Records any negotiated Azure rate and its scope, so AVD compute carries the same protection as the seats.

How should you sequence a migration and renewal?

Treat the desktop decision as part of a renewal and run the licensing checks before you move a single workload. The order below keeps the commercial decisions ahead of the technical ones.

1. Inventory existing Microsoft 365 and Windows entitlements for the access right.
2. Segment users by daily active hours and by dedicated versus pooled need.
3. Price each segment against the public Windows 365 and AVD rates.
4. Model AVD with the autoscale schedules you would actually run.
5. Fold the desktop line into the EA or CSP renewal instead of a separate purchase.

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 rollout.

Expect a dual run period. During migration you may pay for both the old environment and the new Cloud PCs or AVD hosts, so keep that overlap short, budget it and time the cutover to your renewal date.

What should happen at each point before renewal?

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 cost you can explain, and use our CSP and EA comparison if the buying channel itself is still open.

What to do next

1. This week. Segment users by usage pattern before choosing any model.
2. Entitlements. Confirm which users already hold the access right through Microsoft 365 or Windows licenses.
3. Steady users. Assign full time knowledge workers to Windows 365 at the smallest size that fits.
4. Variable users. Assign pooled, shift or seasonal users to AVD or Windows 365 Flex.
5. AVD model. Price AVD with realistic scale down schedules and the engineering cost included.
6. Renewal. Fold Cloud PC growth and Azure terms into the next EA or CSP renewal.
7. Review. Plan for a mixed environment wherever the user base is mixed, and revisit it every renewal.

Frequently asked questions