Choose Windows 365 when users need a persistent, personal Windows desktop at a predictable per-user monthly price, managed entirely from Microsoft Intune with no virtual machines in your own Azure subscription. Choose Azure Virtual Desktop (AVD) when you need multi-session pooled hosts, RemoteApp publishing, Windows Server session hosts, control over VM sizes and networking, or consumption-based billing that you can scale down with autoscale. The two aren't mutually exclusive: both connect through the same Windows App, so many organizations run both and place each user group on the platform that fits it.
Who this is for and what you will have
This comparison is for IT architects and endpoint administrators planning a virtual desktop rollout or reviewing an existing one. It uses only what Microsoft documents and leaves list prices out, because they change and vary by agreement. At the end you will have:
- A clear picture of how each service is licensed and billed.
- The management and networking differences that drive day-two effort.
- A decision table for common user groups.
- An evaluation plan you can run in a pilot.
The core difference: SaaS versus platform
Microsoft describes Windows 365 as a software-as-a-service offering that automatically creates Cloud PCs. You assign a license to a user in an appropriate Microsoft Entra group, a provisioning policy creates the Cloud PC, and the VM runs in a Microsoft-owned Azure subscription. You never create or patch the host infrastructure. In Windows 365 Enterprise, Business and Government each user has a 1:1 relationship with their Cloud PC.
Azure Virtual Desktop is a desktop and app virtualization service where Microsoft runs the control plane (broker, gateway, web access, diagnostics) and you run the session hosts as VMs in your own subscription. You create host pools, application groups and workspaces, choose VM sizes and images, and decide between single-session personal desktops and multi-session pooled desktops. Windows 11 and Windows 10 Enterprise multi-session are exclusive to AVD.
Windows 365 connections go through the Azure Virtual Desktop RDP broker service, and Cloud PCs need the same additional endpoints as AVD session hosts, so the connection path is closely related. The difference is who owns everything underneath.
Note that Azure Virtual Desktop classic retired on September 30, 2026 and connections to classic resources are blocked. Any AVD design today uses Azure Resource Manager host pools.
Licensing compared
Windows 365 editions
| Edition | Who it's for | License prerequisites |
|---|---|---|
| Windows 365 Business | Smaller organizations, capped at 300 users per tenant | None to buy and deploy; device management needs Intune licensing |
| Windows 365 Enterprise | Larger organizations, no per-tenant user cap | Windows E3, Intune and Microsoft Entra ID P1 per user, plus the Windows 365 license |
| Windows 365 Flex (formerly Frontline) | Users who don't need 24/7 access | Windows E3, Intune and Microsoft Entra ID P1; users must be in the provisioning policy's group |
Microsoft's requirements page notes that the Intune admin center may still show Frontline in some places while the rename to Flex rolls through. Flex has two modes:
- Dedicated mode: one license provisions up to three Cloud PCs, each assigned to one user, with one active session per license. Ten licenses means up to 30 Cloud PCs but only 10 active at once. A Cloud PC stays powered on for two hours after the user signs off, then powers off (or hibernates, if it's eligible for Session State Retention) and starts again when the user connects. A concurrency buffer lets you exceed the maximum a limited number of times per day.
- Shared mode: one license provisions one Cloud PC shared non-concurrently by a group. User data is deleted at sign-out, and you can publish Cloud Apps instead of the full desktop.
Flex doesn't yet support the resize remote action or cross-region disaster recovery.
Azure Virtual Desktop access rights
AVD has no separate per-user product for internal use. Each user needs an eligible license, which depends on the session host operating system:
| Session host OS | Internal users | External commercial users |
|---|---|---|
| Windows 11 or 10 Enterprise, single or multi-session | Microsoft 365 E3, E5, A3, A5, F3, Business Premium, Student Use Benefit; Windows Enterprise E3, E5; Windows Education A3, A5; Windows VDA per user | Per-user access pricing on an enrolled Azure subscription |
| Windows Server 2016, 2019, 2022 or 2025 | RDS CAL with Software Assurance (per user or per device), or RDS User Subscription Licenses | Not supported |
Per-user access pricing is only for external commercial purposes, such as a software vendor delivering its app to customers. It isn't a way to license contractors or guest accounts working for you; Microsoft recommends assigning those identities the same eligible license you buy for employees. If a subscription is enrolled in per-user access pricing, users who already hold eligible licenses are still charged, so keep internal users in a separate, non-enrolled subscription.
Cost model compared
| Cost element | Windows 365 | Azure Virtual Desktop |
|---|---|---|
| Compute and OS disk | Included in the per-user monthly license | Azure VM and managed disk charges in your subscription |
| Billing pattern | Fixed per user per month, independent of hours used | Consumption: you pay for what runs, so scaling down saves money |
| Networking | Microsoft-hosted network includes outbound data by Cloud PC RAM size (for example 12 GB for 2 GB RAM, 70 GB for 32 GB RAM); with your own network, egress is billed to your Azure subscription | Bandwidth billed to your subscription |
| Identity infrastructure | Entra ID, plus your domain controllers for hybrid join | Entra ID only, Entra ID plus AD DS VMs, or Entra ID plus Microsoft Entra Domain Services |
| Extra services | Few, since most components are managed | Insights log data in Azure Monitor, FSLogix profile storage, App Attach storage, custom image templates |
| Cost levers | Right-size the Cloud PC SKU; use Flex for part-time users | Autoscale, multi-session density, Azure savings plans, reserved VM instances |
For AVD, Microsoft points to the Azure Pricing Calculator's Azure Virtual Desktop module, which estimates session host consumption from user count, hours and concurrency. It doesn't include egress to Microsoft 365 services such as OneDrive or Exchange Online, so add that separately. VM instances are usually the largest AVD cost, which is why autoscale matters.
Management compared
Windows 365
- You must use the Microsoft Intune admin center; Cloud PCs are enrolled in Intune and managed like physical devices.
- Enterprise provisioning policies let you choose the network, the join type, local admin rights, and gallery or custom images.
- Enterprise adds resizing, reprovisioning to the initial state, Endpoint Analytics, security baselines, and Graph and Microsoft 365 Lighthouse access for partners.
- Business is simplified: Cloud PCs provision with a standard image on license assignment, policy management isn't supported, and Cloud PCs are managed mainly by assigning and unassigning licenses in the Microsoft 365 admin center.
Azure Virtual Desktop
- Host pools, application groups, workspaces and assignments are managed through the Azure portal, Azure CLI, Azure PowerShell and REST API.
- Microsoft recommends Intune for the session host OS. Intune manages Microsoft Entra joined and hybrid joined session hosts, including device and user configuration on Windows 11 and Windows 10 multi-session. Configuration Manager 1906 and later can manage domain-joined and hybrid joined hosts.
- You own image management, patching cadence, host pool sizing, load balancing and the scaling plan.
Autoscale has prerequisites that often trip up first deployments. The Desktop Virtualization Power On Off Contributor role must be assigned to the AVD service principal or the host pool's managed identity with the subscription as scope; assigning it at a resource group or lower prevents autoscale from working. Pooled host pools also need a custom max session limit rather than the default. Dynamic autoscaling additionally needs the Desktop Virtualization Virtual Machine Contributor role and a pooled host pool with a session host configuration.
Networking and identity
Windows 365 offers two network models. Microsoft recommends the Microsoft-hosted network for most new deployments; Microsoft manages the network and egress. Use an Azure network connection (ANC) only when you need Microsoft Entra hybrid join, direct network-level access to on-premises subnets, or customer-managed network controls. ANC deployments put the Cloud PC's network interface in your virtual network and run health checks that can block provisioning; see Windows 365 Azure network connection health check failures for the common errors. Microsoft Entra Domain Services isn't supported for Windows 365 because it doesn't support hybrid join.
AVD session hosts always live in your virtual network, so routing, DNS, firewalls and outbound connectivity are yours to design. Microsoft documents three identity options: Entra ID only, Entra ID with AD DS, and Entra ID with Microsoft Entra Domain Services. If AVD is part of a wider move to Azure, align the host pool network with your landing zone design; the enterprise Azure cloud migration playbook covers that foundation.
User experience
Both services are reached through Windows App on Windows, macOS, iOS, iPadOS, Android and the web. Users see their Cloud PCs and AVD resources in one place. AVD can also publish individual applications as RemoteApp, either alone or alongside full desktops, from the same host pool. Windows 365 Flex in Shared mode can deliver Cloud Apps instead of a full desktop.
The standalone Remote Desktop client (MSI) for Windows reached end of support for public cloud customers on March 27, 2026. Plan Windows App deployment as part of either rollout; the Windows App migration guide covers Intune deployment and finding remaining legacy clients.
Decision table
| User group | Better fit | Why |
|---|---|---|
| Full-time knowledge workers needing a personal, persistent PC | Windows 365 Enterprise | Fixed cost, no host infrastructure, managed like physical PCs |
| Small business up to 300 users with no Intune team | Windows 365 Business | No prerequisites, provisioned on license assignment |
| Part-time, shift or rotating staff with personal desktops | Windows 365 Flex Dedicated | Up to three Cloud PCs per license, one active session |
| Task workers on a shared kiosk-style desktop | Windows 365 Flex Shared, or AVD pooled | No data persistence needed |
| Call center or seasonal pool with high user density | AVD pooled multi-session | Multi-session density and autoscale |
| Users who need one or two line-of-business apps, not a desktop | AVD RemoteApp | Publish apps only |
| Apps requiring Windows Server or RDS-style hosting | AVD | Windows Server session hosts with RDS CALs |
| SaaS app delivered to your customers | AVD with per-user access pricing | The only licensing path for external commercial use |
Run an evaluation
- Segment users. Group them by hours of use, need for persistence, app set and on-premises dependencies.
- Check licensing. Confirm Windows E3 or equivalent, Intune and Entra ID P1 coverage for Windows 365 Enterprise or Flex, and confirm eligible AVD licenses or RDS CALs with Software Assurance.
- Estimate AVD consumption. Use the Azure Pricing Calculator's AVD module with realistic concurrency, then add egress, profile storage and monitoring.
- Pilot both. Provision a handful of Cloud PCs on the Microsoft-hosted network, and a small pooled host pool with a scaling plan.
- Measure. Use AVD Insights for session host utilization and connection quality, and Intune reports for Cloud PCs.
- Decide per group. Apply the decision table and assign each group to a provisioning policy or a host pool.
Common pitfalls
- Wrong edition for the requirement. Business doesn't support policy management, custom images or hybrid join. If you need any of those, buy Enterprise.
- Flex concurrency surprises. Dedicated mode allows three Cloud PCs per license but only one active session; size licenses on peak concurrent use, not on headcount.
- Autoscale does nothing. The power role was assigned at resource group scope, or the host pool still uses the default max session limit.
- Paying twice for internal users. Internal users with eligible licenses connected through a subscription enrolled in per-user access pricing are still charged.
- Expecting Entra Domain Services with Windows 365. It isn't supported; use Microsoft Entra join or hybrid join with AD DS.
- Legacy clients. Users still on the retired Remote Desktop client lose support; deploy Windows App before go-live.
Summary checklist
- Map each user group to Windows 365 Enterprise, Business, Flex or AVD.
- Confirm license prerequisites for each platform.
- Model AVD consumption, including autoscale and storage.
- Prefer the Microsoft-hosted network for Windows 365 unless hybrid join or on-premises routing requires ANC.
- Assign AVD autoscale roles at subscription scope.
- Standardize on Windows App for all users.
References
- What is Windows 365?
- Compare Windows 365 Business and Enterprise
- Windows 365 requirements
- What is Windows 365 Flex?
- Network requirements for Windows 365
- Windows 365 Azure Network Connection (Azure Architecture Center)
- What is Azure Virtual Desktop?
- Licensing Azure Virtual Desktop
- Understand and estimate costs for Azure Virtual Desktop
- Manage the operating system of session hosts
- Create and assign an autoscale scaling plan for Azure Virtual Desktop
- What's new in the Remote Desktop client for Windows