Editorial photograph of a virtual desktop deployment representing Windows 365 versus AVD
Microsoft · Windows 365 · AVD

Windows 365 versus AVD. The licensing decision framework.

Independent licensing analysis of Windows 365 Cloud PC versus Azure Virtual Desktop. SKU map, per user math, FSLogix license trap, M365 prerequisites, and the buyer side decision framework.

Read the framework Contact Us
$2B+Under Advisory
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Key Takeaways

Six things every buyer should know before signing

  • Windows 365 is per user fixed. Predictable. Easy to budget. Expensive at scale for full time users.
  • AVD is per Azure consumption. Variable. Cheaper at scale. Harder to budget without baseline modeling.
  • M365 entitlement is the gating license. Both products need a qualifying M365 SKU on every user.
  • FSLogix is bundled inside M365 E3. Customers on lower tiers pay extra at audit time.
  • Break even is 500 to 1,000 seats. Above that, multi session AVD economics start to win.
  • Reserved Instances change the math. One year and three year reservations bring AVD costs down sharply.

SKU map for Windows 365 and AVD

Windows 365 and Azure Virtual Desktop are not direct substitutes. They sit at different points in the Microsoft virtual desktop portfolio. The SKU map is the first thing every buyer must understand.

Windows 365 editions

  • Windows 365 Business: standalone, no Intune required, capped at 300 seats. Aimed at small business.
  • Windows 365 Enterprise: Intune managed, no seat cap. Requires Intune and Azure AD P1 entitlement.
  • Windows 365 Frontline: shared seat model with three users per license. Aimed at shift workers.
  • Windows 365 Boot: a sign in mode that routes the local Windows session to the Cloud PC at boot.

AVD service components

  • Windows 11 multi session OS: a Microsoft virtual desktop variant that supports multiple concurrent users per VM.
  • Azure VM compute: the underlying compute size, priced under the Azure consumption model.
  • Azure managed storage: Premium SSD or Standard HDD for the OS disk plus user profile storage.
  • FSLogix profile container: the Microsoft profile management tool, bundled inside M365 E3 and above.
  • Networking and bandwidth: ExpressRoute, VPN gateway, and egress bandwidth on the Azure rate card.

Per user math at three population sizes

The per user math is the dominant input to the Windows 365 versus AVD decision. The math changes shape across population size and usage pattern.

Three reference populations

PopulationUsage patternWindows 365 per user monthAVD per user month, optimizedBreak even
200 part time users4 hours per day$31 to $66$48 to $85W365 wins
500 full time knowledge workers8 hours per day$41 to $66$33 to $52Tie
5,000 full time knowledge workers8 hours per day, multi session$41 to $66$22 to $34AVD wins
1,200 contact center shift workers3 shifts per seat$22 (Frontline)$18 to $26Close call
800 power users with GPU10 hours per day$162 to $215$98 to $145AVD wins

The hidden cost lines

  • Egress bandwidth: AVD adds egress costs on the Azure rate card. Windows 365 does not surface this line.
  • Image management: AVD requires a custom image pipeline. Windows 365 ships a managed image.
  • Operational labor: AVD needs a dedicated platform team. Windows 365 does not.
  • Premium storage: FSLogix profiles on Premium SSD add 5 to 12 dollars per user per month.
  • RDP Shortpath licensing: embedded but requires correct subscription identity tier.

The FSLogix audit trap

FSLogix is bundled inside M365 E3, M365 E5, and the Windows VDA per user SKU. Customers running AVD on F1 frontline workers or non M365 identities must license FSLogix separately. Microsoft does not enforce this at deploy time. The audit team enforces it at audit time, with three year retroactive coverage.

The single largest AVD audit finding we see is FSLogix profile use on non qualifying user licenses across a frontline or contractor population.

Microsoft 365 prerequisites that change the math

Both Windows 365 Enterprise and AVD require a qualifying M365 entitlement on every user. The qualifying SKU table sets the floor on the buyer's true cost.

Qualifying M365 entitlements

  • M365 E3 and E5: qualify automatically. Include Windows 11 Enterprise, Intune, Azure AD P1 or P2, and FSLogix.
  • M365 F3: qualifies for Windows 365 Frontline only. Does not include FSLogix.
  • Windows 11 Enterprise E3 standalone: qualifies for Windows 365 but lacks Intune. Add separately for Enterprise tier.
  • Microsoft 365 Business Premium: qualifies for Windows 365 Business. Capped at 300 seats.
  • EA per device licensing: qualifies for AVD only, not Windows 365.

The total cost picture

User identity tierM365 costPlus AVD computePlus Windows 365 fixed
M365 E3$36 per user month$22 to $34$41 to $66
M365 E5$57 per user month$22 to $34$41 to $66
M365 F3$8 per user monthNot qualifying$22 (Frontline)
Win 11 E3 standalone$10 per user month$22 to $34$41 to $66
M365 Business Premium$22 per user monthNot qualifying$31 Business

The buyer side decision framework

The Windows 365 versus AVD decision is not symmetric. Each side has clear wins. The framework below collapses the decision into five questions.

Five questions to ask before signing

  1. How predictable is the usage pattern? Stable hours favor Windows 365. Variable hours favor AVD.
  2. How large is the population? Under 500 seats favors Windows 365. Above 1,000 seats favors AVD.
  3. Is there an existing Azure commit? An active MACC or EA Azure commit makes AVD cheaper per dollar.
  4. Does the user need GPU? AVD has the GPU SKU edge on cost and SKU breadth.
  5. Is there platform engineering capacity? AVD needs a dedicated platform team. Windows 365 does not.

Windows 365 wins on simplicity. AVD wins on price at scale. The break even is 500 to 1,000 seats. Below that, the operational cost of AVD eats the per user discount.

Seven SKU traps to avoid

  1. F3 plus AVD. Frontline does not qualify for AVD. The seat must be moved to E3 or W365 Frontline.
  2. FSLogix on non qualifying SKU. Three year retroactive audit exposure.
  3. Premium SSD overprovision. Default profile containers can sit on Standard SSD for half the cost.
  4. Reserved Instance under buy. One year RI on AVD compute cuts 30 to 45 percent. Three year cuts 50 to 65 percent.
  5. Egress sticker shock. Project egress in the AVD budget. Use ExpressRoute for high egress workloads.
  6. Cloud PC oversize. Mid size SKUs are oversold. Right size at the actual user usage pattern.
  7. Idle Cloud PC ghost cost. Cloud PCs run at fixed cost even when the user is on vacation.

What to do next

  1. Inventory every user and bucket by usage pattern, hours, and GPU need.
  2. Model Windows 365 and AVD side by side at the population level.
  3. Audit M365 entitlement on every user against the qualifying SKU table.
  4. Map FSLogix use against the qualifying identity tier and remediate any mismatch.
  5. Benchmark Azure consumption pricing against our Microsoft deal database.
  6. Run the Microsoft 365 license optimizer on the full estate.
  7. Engage independent buyer side advisory before signing the EA or the AVD landing zone.

Frequently asked questions

How is Windows 365 licensed?

Windows 365 is licensed per user per month on a fixed Cloud PC SKU. Sizes run from 1 vCPU 2 GB 64 GB up to 8 vCPU 32 GB 512 GB. The license includes the Cloud PC, the storage, and the Windows 11 desktop OS. The customer needs an underlying M365 entitlement for the Windows 11 license to qualify.

How is Azure Virtual Desktop licensed?

AVD splits into two parts. The Windows 11 multi session OS license rides on top of a qualifying M365 entitlement. The Azure compute, storage, and networking run on consumption pricing under the Azure subscription. AVD has no per user monthly SKU. The cost is the underlying Azure spend.

Which is cheaper, Windows 365 or AVD?

Windows 365 is cheaper for small populations or part time users on fixed sizes. AVD is cheaper for full time knowledge workers at scale because of multi session economics. The break even is typically 500 to 1,000 seats.

Does Windows 365 require Microsoft 365 E3 or higher?

Yes for the Windows 11 license to qualify. Windows 365 Business is a standalone product but is capped at 300 users. Windows 365 Enterprise requires Intune and Azure AD P1 entitlements, both of which sit inside M365 E3 and above.

Where does the FSLogix license trap hit?

FSLogix profiles ship with M365 E3 and above. Customers running AVD on F1 or non M365 user licenses must add the FSLogix entitlement. Microsoft does not enforce this at deploy time. The audit team enforces it at audit time.

How does Redress engage on a Windows 365 versus AVD decision?

We run the buyer side analysis end to end. We model both SKUs at the actual user pattern, benchmark Azure consumption against deal database pricing, and challenge the Microsoft preferred SKU position. We are not a Microsoft partner.

Microsoft will quote you one number. The buyer side must dismantle it into M365 entitlement, compute, storage, FSLogix, and egress. The leverage is in the lines.

Morten Andersen
Co Founder, Redress Compliance
Right size your virtual desktop estate before your next M365 renewal.
Open the optimizer →
White Paper · Microsoft

Download the Microsoft EA Renewal Playbook.

A buyer side reference on Microsoft EA renewal. Discount benchmarks, true up tactics, M365 right sizing, and the Azure commit conversation.

Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Microsoft contracts. No vendor influence. No sales kickback.

Microsoft EA Renewal Playbook

Open the white paper in your browser. Corporate email only.

Open the Paper →
More Reading

More from this practice.

All Microsoft articles →
Microsoft Advisory Services
Microsoft · Article
Microsoft Advisory Services
Independent buyer side advisory on every Microsoft engagement.
10 min read
Microsoft 365 License Optimizer
Microsoft · Article
Microsoft 365 License Optimizer
Right size E3, E5, and F3 against your actual usage pattern.
12 min read
Microsoft Knowledge Hub
Microsoft · Article
Microsoft Knowledge Hub
Every Microsoft licensing topic in one place.
11 min read
How to Evaluate a Microsoft Renewal
Microsoft · Article
How to Evaluate a Microsoft Renewal
The full buyer side renewal evaluation playbook.
13 min read
Editorial photograph of enterprise contract negotiation strategy

Sizing a Windows 365 or AVD rollout? Get a buyer side opinion before signing.

Independent. Buyer side. We have run 500 Microsoft engagements. We know where the FSLogix and identity traps sit.

Microsoft licensing intelligence, in your inbox

Buyer side Microsoft insight. No vendor influence. Read in five minutes.