Blog
Desktop virtualization in 2026: VDI, DaaS, RDS, and how to choose the right model
Compare VDI, DaaS, RDS, and Windows Cloud to choose the right model for your organization.
Table of Contents
- Three trigger events forcing this decision now
- Four models and what each one trades away
- Matching models to your workforce segments
- How cost structures differ across models
- What a well-scoped migration looks like
- Five filters to apply before you commit
- How Nerdio Manager works across both Windows Cloud paths
- What your desktop virtualization choice actually determines
- Frequently asked questions about desktop virtualization
Your Windows 10 end of life planning is colliding with a Citrix renewal that landed at 30% above last year's price. Finance wants a cloud desktop budget projection by next quarter. You're deciding which model to bet on.
This guide is for IT directors and EUC leaders evaluating desktop virtualization models across VDI, DaaS, RDS, and Microsoft's Windows Cloud, which encompasses Azure Virtual Desktop and Windows 365.
Many enterprise environments will end up running more than one model. Task workers land on pooled multi-session, knowledge workers on fixed Cloud PCs, and power users on dedicated VMs. The management layer you choose early shapes your operational burden for the next three to five years. Getting those segment-by-segment choices right is what the rest of this read works through.
Three trigger events forcing this decision now
Desktop virtualization evaluations in 2026 are rarely voluntary. Three market events are compressing timelines:
- Windows 10 end of life is pushing this decision forward. Many enterprises (~25%) were still running legacy Windows near the cutoff. Devices incompatible with Windows 11 can be candidates for virtual desktops, which can extend access without requiring the endpoint to run the newer OS natively.
- Legacy VDI renewal pressure is accelerating departures from Citrix and Omnissa Horizon (formerly VMware Horizon). An IDC report discusses organizations being pressured to move away from legacy virtualization platforms.
- Hardware refresh economics have shifted. IDC further reports that the PC market will decline 11.3% in units in 2026, with recovery pushed to 2028. Forrester frames virtual desktops as an alternative to high-cost laptop procurement. Lower-cost endpoints such as thin clients or reused devices can reduce capital spend in some DaaS deployments.
Any one of these events justifies an evaluation. All three hitting simultaneously helps explain why Gartner projects DaaS spending will grow from $4.3 billion in 2025 to $6.0 billion by 2029.
Four models and what each one trades away
Every desktop virtualization model involves a trade-off between control, cost, and operational burden. The differences come down to who owns the infrastructure, which OS runs on the session host, and how users share resources.
On-premises VDI
On-premises VDI gives your team full control over compute, storage, and networking. You own the hypervisor and manage every layer. That control comes with the highest management overhead and upfront capital expenditure.
Remote Desktop Services (RDS)
Remote Desktop Services (RDS) shares a single Windows Server instance across multiple user sessions. This model is often positioned with lower per-user costs than VDI or cloud desktop alternatives. The trade-off is that RDS runs on a server OS rather than a client OS. That creates application compatibility constraints for desktop-based software. Microsoft 365 Apps support on Windows Server 2016 and 2019 ended on October 14, 2025.
Azure Virtual Desktop
Azure Virtual Desktop is a Platform as a Service (PaaS) offering. It runs Azure VMs with the AVD agent installed so users can connect, deployed within your own Azure subscription. You manage session host VMs, storage, networking, and images. Microsoft manages the control plane. The trade-off is consumption-based flexibility and deep customization in exchange for Azure platform expertise and ongoing operational work on host pools, images, and scaling rules.
Windows 365
Windows 365 is the fully managed DaaS path. Cloud PCs are hosted in Microsoft's cloud, and Microsoft manages the underlying VM and much of the infrastructure for customers. The trade-off is predictable per-user pricing and a smaller infrastructure surface in exchange for a more standardized configuration model than AVD.
Microsoft positions Azure Virtual Desktop and Windows 365 as architecturally complementary rather than competing options, and many enterprises deploy both for different workforce segments.
In practice, enterprise end-user computing environments are often mixed and use-case dependent.
Matching models to your workforce segments
Microsoft provides guidance on session host sizing and host pool load balancing for Azure Virtual Desktop. The right model depends on user workloads and workforce segmentation. Teams that expect to run both Windows Cloud paths often also plan for a unified management layer such as Nerdio Manager early, because the operating model can matter as much as the desktop model.
Task workers
Task workers (call centers, data entry, kiosk, frontline shift staff) are often the best fit for multi-session pooled, non-persistent configurations. Windows 365 Frontline in shared mode fits shift-based patterns where users do not overlap. Azure Virtual Desktop pooled multi-session with Windows 11 Enterprise multi-session is the alternative for organizations wanting consumption-based billing instead of fixed licensing.
Knowledge workers
Knowledge workers (Microsoft 365 users, analysts, accountants) align with Windows 365 Enterprise for predictable budgeting or Azure Virtual Desktop multi-session for cost optimization through auto-scaling. Microsoft's performance guidance indicates that moving to a larger Cloud PC configuration can improve office-worker performance, but organizations should test with their own line-of-business applications before finalizing sizing.
Power users
Power users such as those using CAD, 3D modeling, or engineering simulation often need GPU-accelerated VMs, and in some cases dedicated GPU VMs are recommended. Azure Virtual Desktop with GPU-capable Azure VM SKUs and Windows 365 GPU-enhanced Cloud PCs are two main Microsoft options for GPU-accelerated virtual desktop workloads. Persistent and non-persistent desktops, or both, can fit this persona depending on workload. GPU SKU availability varies by Azure region, so verify before committing.
Developers
Developers are an important Microsoft persona. Microsoft offers both Windows 365 and Azure Virtual Desktop for virtualized desktop scenarios. The choice depends on the level of customization and infrastructure control needed. Azure Virtual Desktop supports assigning more than one personal desktop to a user for different roles or environments.
Many teams map their workforce into these segments, assign a model per segment, and plan for a multi-model desktop virtualization strategy by design.
How cost structures differ across models
Cost comparisons across desktop virtualization models fail when they treat "cost" as a single number. Every model includes compute and infrastructure costs, Microsoft licensing, and management or third-party tooling. Each model distributes those costs differently.
Compute and infrastructure is the most visible cost:
- Windows 365 pricing is fixed per user per month, with official list pricing examples including $31 for a 2 vCPU/4 GB RAM/128 GB Storage configuration and $123 for an 8 vCPU/32 GB RAM/128 GB Storage configuration.
- Azure Virtual Desktop costs are consumption-based, with estimates ranging from about $9-$11 per user per month for pooled multi-session compute to $170+ for dedicated power-user VMs.
- On-premises VDI carries capital expenditure for servers, storage, networking, power, and cooling.
Microsoft licensing applies to every model:
- AVD access rights are included with Microsoft 365 E3, E5, A3, A5, F3, and Business Premium subscriptions, as well as Windows Enterprise E3 and E5. Most enterprise organizations will already hold a qualifying license.
- Windows 365 Enterprise requires four components: Windows E3, Microsoft Intune, Microsoft Entra ID P1, and a Windows 365 Cloud PC license. Microsoft 365 E3 and E5 typically bundle the first three; organizations should verify component coverage before provisioning.
- RDS requires separate RDS Client Access Licenses, and upgrading session hosts to Windows Server 2025 may require corresponding CAL coverage depending on your licensing terms, such as Software Assurance rights.
Management and third-party tooling is the layer many teams underestimate:
- Azure Virtual Desktop has no separate service fee, but the operational cost of managing session hosts, images, scaling rules, and profiles through the Azure Portal, PowerShell, and Microsoft Intune adds up in labor hours.
- Windows 365 eliminates infrastructure management but requires Microsoft Intune administration for endpoint policies, application deployments, and compliance baselines. The management overhead shifts to different work. For teams evaluating the tooling layer directly, our pages on overlooked AVD and W365 costs and Nerdio value beyond cost can help structure that comparison.
The 2025 Forrester TEI study, commissioned by Microsoft, modeled organizations deploying both Windows 365 and Azure Virtual Desktop. The study projected ROI of 94-217% over three years using a three-year cost model under negotiated pricing.
Those projected savings assume a completed migration, which raises the next question. How long does the transition actually take?
What a well-scoped migration looks like
Migration from legacy VDI to Microsoft cloud desktops is a parallel build and phased cutover. Microsoft recommends planning migrations in phases. With proper tooling for migration workflows, timelines can compress materially: Carvana's migration story shows a 14-day deployment, and Felleskjøpet Agri SA reported nearly 4M NOK in annual savings, roughly a mid-six-figure USD equivalent, after leaving legacy VDI behind.
Microsoft's migration guidance breaks the work into session hosts and images, user profiles, applications, and infrastructure assessment, which helps structure that timeline.
Five workstreams run in parallel during any migration, and skipping any one of them can stall migrations:
- Profile moves that migrate user data to FSLogix or local profiles
- Application packaging and compatibility validation against the target session host OS
- Desktop image rebuilds for the new environment
- Support team retraining on the new management surfaces and workflows
- Compliance revalidation to confirm the new environment meets framework requirements
Teams should plan Citrix or Omnissa Horizon contract renewal timing around the parallel-run window. Dual-licensing costs during co-existence are a real budget line, and extending it by six months because the migration wasn't scoped correctly is a preventable cost overrun.
Before scoping that migration, five organizational filters determine whether your preferred model is even viable.
Five filters to apply before you commit
Before evaluating specific platforms, organizations should run through these disqualifying filters. Each one can override cost and operational preferences.
Data residency
Data residency requirements come first. If regulations prohibit data from leaving specific geographies, verify that your chosen model supports those regions. Microsoft guidance for Azure Virtual Desktop emphasizes choosing Azure regions based on user proximity, compliance, service availability, and data residency needs. Windows 365 Cloud PCs reside in Microsoft-managed Azure subscriptions, so verify Microsoft 365 data residency terms independently.
Application compatibility
Application compatibility is the next gating factor. RDS runs on Windows Server, which creates compatibility gaps for applications designed for a client OS. Azure Virtual Desktop's Windows 11 Enterprise multi-session solves this by delivering a client OS in a shared-session model, a capability previously unavailable. Teams should validate the application portfolio against the target session host OS before architecture decisions lock in.
Compliance and audit evidence
Compliance and audit evidence depend on configuration choices. Compliance with frameworks like PCI DSS and HIPAA depends on how the environment is configured. Azure Virtual Desktop has documented Zero Trust guidance that maps to the five CISA pillars: identity, devices, networks, applications and workloads, and data. Windows 365 Cloud PCs do not support BitLocker, so organizations whose security policy mandates full-disk encryption should verify how their Cloud PC compliance settings are configured.
Teams multimedia requirements
Teams multimedia requirements also need review. Teams audio and video in multi-user Windows Server session configurations (RDS) presents technical constraints that require validation against current Microsoft guidance for your specific deployment scenario.
Security team involvement
Security team involvement is the final filter, and it's a practical one. IDC Spotlight flags that "it is rare for enterprises to involve their security teams in the DaaS discussion." If your security team hasn't reviewed the desktop virtualization shortlist, the evaluation is incomplete regardless of which model scores highest on cost and operations.
Once these filters narrow the field, the operational question shifts to how you manage whichever models survive.
How Nerdio Manager works across both Windows Cloud paths
Many enterprises deploy Windows 365 and Azure Virtual Desktop together for different workforce personas. Managing both natively means working across multiple toolsets like Azure Portal, PowerShell, and Microsoft Intune. That adds administrative friction the migration was supposed to reduce.
Nerdio Manager for Enterprise provides a unified console for both products under the Windows Cloud umbrella, with the same policies, automations, reporting, and monitoring across desktop types.
Azure Virtual Desktop cost and efficiency proof points
Across Azure Virtual Desktop, Nerdio Manager's patented auto-scaling dynamically scales compute based on real-time demand, powers down idle resources, and switches OS disks between premium and standard tiers when VMs are stopped and deallocated. TechTarget's Enterprise Strategy Group found that customers saw up to 55% AVD cost reduction using Nerdio Manager versus Azure Virtual Desktop alone. After migrating from Citrix, Sage achieved 62% to 65% savings on VM direct costs and $1.5M in annual savings. A benchmark test by Dr. Benny Tritsch measured an 88% reduction in time and 91% fewer clicks for image updates compared to native Azure Virtual Desktop management. Fewer clicks means fewer manual steps in image update workflows.
Windows 365 management and operational value
Across Windows 365, the proof is operational and management-based rather than infrastructure-based. Nerdio's unified application management deploys applications to Windows 365 endpoints in roughly 30 seconds, compared with native Intune delivery that can take up to 3 hours. Nerdio Advisor provides right-sizing recommendations for Cloud PCs, flags oversized and undersized configurations, identifies unused licenses, and can surface potential Frontline license conversion opportunities. Nerdio Manager also creates, backs up, and restores Intune policies. Native Intune cannot back up or restore deleted policies. The City of Corona centralized management of Windows 365, Microsoft Intune, and Azure Virtual Desktop through Nerdio Manager, using a centralized, automated approach to improve security and IT operations across all three surfaces.
Architecture and reliability
Nerdio Manager deploys directly into your Azure environment with no proprietary agents on session hosts. Monitoring is agentless, so there's no agent footprint to manage as your environment grows.
The polling interval is configurable down to one minute, with a default of every five minutes. Auto-Heal detects and repairs broken Azure Virtual Desktop session hosts automatically, reducing downtime by up to 36%.
With the tooling layer addressed, the strategic question returns to what you're actually committing to.
What your desktop virtualization choice actually determines
The model you select determines how much operational responsibility your team carries for the next three to five years. Windows 365 shifts infrastructure management to Microsoft but requires Intune administration at scale. Azure Virtual Desktop gives you full control over compute, storage, and networking but demands Azure platform expertise. On-premises VDI and RDS keep everything in your data center but carry the highest management overhead and capital requirements.
The Citrix renewal on your desk, the Windows 10 devices in your fleet, and the budget projection finance requested are three expressions of the same question. How much desktop infrastructure do you want to run yourself? Your answer will be different for task workers, knowledge workers, and power users, and your architecture should reflect that segmentation.
Get a demo to see how Nerdio Manager works across your Windows 365 and Azure Virtual Desktop environment, or try it free in your own Azure tenant.
Frequently asked questions about desktop virtualization
Resources
Learn more about Nerdio Manager
