Blog
Cloud desktop strategy for the EUC director: what to prioritize when you're modernizing the desktop stack
Cloud desktop strategy helps EUC directors sequence platform choice, migration, and governance as ESU and renewal costs rise.
Table of Contents
- Pressures that define your decision window
- Platform selection: Azure Virtual Desktop, Windows 365, or both
- What migration actually requires
- Cost architecture: the five components you need in your business case
- Governance as a design input during planning
- How Nerdio Manager fits across both paths
- Building the operational readiness that makes it stick
- Frequently asked questions about cloud desktop strategy
Your Citrix renewal landed on the same quarter as Windows 10 end-of-life escalation costs, and the CIO wants a modernization plan that doesn't require hiring 15 more people.
This guide is for EUC directors building a modernization plan when Citrix renewal pressure and Windows 10 Extended Security Updates (ESU) costs hit at the same time.
In 2026 the cloud desktop question has become an execution decision rather than a debate about whether to move. Citrix renewal economics, cumulative ESU fees, and a market trending toward DaaS converge into a narrow window, so the real work is deciding the sequence, the pace, and what to protect along the way. If you're weighing migration paths, this Citrix migration guide provides related planning context.
Pressures that define your decision window
Those pressures are not abstract. Each one creates a defined window to act, and together they set the timeline you are working against.
Windows 10 ESU costs are cumulative
Windows 10 ESU reached end of support on October 14, 2025. The ESU program creates escalating per-device costs of $61 in Year 1, $122 in Year 2, and $244 in Year 3. Those fees are cumulative. An organization entering Year 2 pays Year 1 retroactively.
Based on that pricing, a 5,000-device fleet would face $2.135 million in cumulative three-year ESU costs. These ESU costs are a material input to the business case you take to the board.
Legacy VDI contract disruptions are accelerating
Citrix's perpetual-to-subscription licensing transition and post-Broadcom acquisition pricing changes at Omnissa Horizon (formerly VMware Horizon) create a defined decision point at every contract renewal. Findex found Azure Virtual Desktop with Nerdio to be a better fit for its needs and cost profile than Citrix. For teams assessing options, Nerdio's Citrix alternatives page and Horizon alternatives page map the comparison more directly.
Gartner Magic Quadrant for DaaS is now baseline infrastructure
Gartner's 2025 Magic Quadrant for Desktop-as-a-Service reports worldwide DaaS spending at $4.3 billion, projected to reach $6.0 billion by 2029. Starting in June 2026, Gartner will stop reporting DaaS as a standalone segment in its quarterly services forecast and will roll that spending into traditional infrastructure-as-a-service (IaaS).
The signal is clear: DaaS has moved past emerging-technology status. In cloud computing model terms, Windows 365 is delivered as DaaS, a fully managed desktop service, while Azure Virtual Desktop is closer to PaaS (Platform-as-a-Service), since it runs as Azure VMs with an agent that allows users to connect. Reports based on Gartner's Magic Quadrant state that net-new desktop virtualization deployments are trending toward cloud-delivered models rather than on-premises VDI.
Altogether, these three pressures mean you need to decide how fast to modernize and in what order.
Platform selection: Azure Virtual Desktop, Windows 365, or both
The Microsoft cloud desktop path should fit your workforce. Microsoft positions Windows 365 and Azure Virtual Desktop as complementary products under the Windows Cloud umbrella, the term for Microsoft's combined cloud desktop portfolio. Many enterprises run both.
When Azure Virtual Desktop fits
Azure Virtual Desktop is consumption-based. You pay for Azure infrastructure, compute, storage, and networking, and bring eligible Microsoft 365 or Windows Enterprise licenses you already own. It delivers multi-session pooled desktops where multiple users share a single VM. This can reduce compute costs compared to one-user-per-VM approaches. Your team manages compute, networking, and storage primarily through the Azure Portal and PowerShell, with related Microsoft Intune controls where applicable.
Azure Virtual Desktop fits when workloads are variable, when GPU-backed VMs are required, when full control over Azure region selection for data residency matters, or when you're running Windows Server applications through RemoteApp.
When Windows 365 fits
Windows 365 delivers a dedicated Cloud PC per user at a fixed monthly price. Per Microsoft documentation, DR guidance says Microsoft manages infrastructure, capacity, and disaster recovery. Every Cloud PC automatically enrolls in Microsoft Intune during provisioning. Costs are predictable by design.
Windows 365 Enterprise fits knowledge workers, BYOD scenarios, and steady-state workloads where predictable budgeting matters more than consumption optimization. Windows 365 Flex (formerly Frontline) addresses shift workers and part-time staff. Its licensing model supports up to three users per license when their schedules never overlap.
Why many enterprises run both
A hybrid model fits many organizations in 2026, with Windows 365 and Azure Virtual Desktop matched to different workload types under a single Windows Cloud strategy.
Running both paths creates the management challenge where Windows 365 is managed primarily through Intune, while Azure Virtual Desktop is managed primarily through Azure Portal and PowerShell, with related Intune controls where applicable. That complexity affects platform choice, migration sequencing, governance, and steady-state operations.
Delivery models usually need to match user personas and operational realities. Once that fit is clear, migration sequencing becomes the next constraint that determines whether the strategy is executable. If you're comparing the two paths more directly, Nerdio's Windows 365 vs. AVD resource can support that evaluation.
What migration actually requires
The Cloud Adoption Framework and related migration guidance present moves from Citrix, Omnissa Horizon, and other VDI platforms to Azure Virtual Desktop as new deployments with phased migration rather than a direct, one-step migration path. VDI, or Virtual Desktop Infrastructure, is the legacy on-premises model. Desktop images are either migrated or rebuilt. User profiles are either migrated or recreated. Migration sequencing is a program management question.
Persona-driven wave planning
The assessment phase gathers key inputs for each user persona. Those inputs inform planning and sizing. Getting this segmentation right determines your host pool architecture, VM sizing, and wave sequencing.
Teams typically identify legacy application dependencies that require dedicated desktops during assessment and place them into later migration waves. Current waves typically proceed based on the personas and dependencies already cleared.
Realistic timeline expectations and bottleneck planning
The Forrester TEI study, commissioned by Microsoft, reports deployment timelines of 3 to 18 months across interviewed organizations. Organizations have taken a range of approaches to Citrix-to-AVD migrations. Their approach depends on size, complexity, and requirements. Profile management and application packaging are common bottlenecks in the migration timeline.
Parallel operation during cutover
Running legacy VDI alongside new cloud desktops during migration is often the approach. Teams typically keep legacy production live while pilots run. They compare user experience and operational outcomes before each wave commits. We recommend a phased migration approach with pilot groups, user waves, and decommissioning the old environment after cutover.
Success depends on wave design, profile and app planning, and disciplined coexistence while the old and new environments run in parallel. That makes cost modeling the next priority, because a weak business case can stall even a well-sequenced migration. For teams under renewal pressure, a Citrix-to-AVD migration checklist can help structure the wave plan.
Cost architecture: the five components you need in your business case
Azure Virtual Desktop costs generally derive from core infrastructure components like session host VMs and compute, with licensing also affecting total cost. A durable business case should frame costs across five components covering:
- session host VM compute
- storage (profile containers and OS disks)
- networking (egress, ExpressRoute, or VPN connectivity)
- Microsoft OS and access licensing
- third-party management, security, and user experience tooling
The full scope often extends well past the headline infrastructure line items.
Compute optimization is one part of the picture
Combined auto-scaling, right-sizing, and reserved instance strategies can reduce Azure compute costs materially, with savings varying by workload. Reserved instances save up to 72% compared to pay-as-you-go pricing on a 3-year term.
But reserved instances require upfront commitment and are appropriate for stable, predictable workloads like always-on personal host pools. For dynamically scaled multi-session pooled host pools, auto-scaling significantly narrows the reserved instance savings delta because those VMs are already stopped and deallocated during off-peak hours.
Windows 365 costs are predictable by design. The optimization levers are different: right-sizing Cloud PC SKUs to actual usage, reclaiming unused licenses, and converting eligible users to Flex licensing. Related planning resources on hidden cloud desktop costs and our AVD cost management guide can help pressure-test the model.
Hidden costs that erode your business case
Storage tier selection, Standard HDD vs. Premium SSD, creates material cost differences at scale. Profile container backends, Azure Files, Azure NetApp Files, add ongoing storage costs. Azure support plan costs are usually part of the model for business-critical desktop environments. Orphaned device records in Microsoft Intune persist after Azure Virtual Desktop VMs are deleted. They create audit and compliance overhead at scale.
TechTarget's Enterprise Strategy Group found that 56% of companies reported spending $21 or more per user per month on endpoint management, user experience, and security tools. Your business case needs to capture the full cost picture across compute and the rest of the stack.
A credible business case has to survive scrutiny beyond headline VM savings. If the model does not account for the full stack of desktop costs, governance quickly becomes a corrective exercise instead of a design input.
Governance as a design input during planning
The Cloud Adoption Framework treats security team review and approval of landing zone configurations as a readiness gate before deployment. When the security team is not a formal stakeholder from assessment through deployment, the cloud desktop strategy carries a program risk that no tooling can fix.
For regulated industries, CIS Benchmarks provide industry-standard configuration guidelines for system hardening, with CIS Hardened Images available as a secure-by-default starting point.
Data residency also requires deliberate planning. Azure Virtual Desktop session hosts from different regions are generally best kept in separate host pools, since pooled host pools load-balance users across available session hosts rather than assigning them to a specific session host or region. Windows 365 requirements state that Windows 365 Flex in Shared mode requires selection of a single Azure region, which is a material constraint for geographically distributed enterprises.
For deeper endpoint governance context, our Microsoft Intune overview and CIS security baselines resources are relevant next reads.
How Nerdio Manager fits across both paths
Running cloud desktops at enterprise scale creates management complexity on both the Azure Virtual Desktop and Windows 365 paths. Nerdio Manager for Enterprise deploys into your Azure tenant as a management and automation layer for Windows 365, Microsoft Intune, and Azure Virtual Desktop from a single console.
On the Azure Virtual Desktop path
Patented auto-scaling dynamically scales compute based on real-time demand and powers down idle resources and deallocates them to stop compute billing. Enterprise customers have saved up to 55% on Azure compute (per the previously mentioned TechTarget report). Desktop orchestration replaces manual PowerShell scripting for golden image creation, updates, and distribution. Nerdio centralizes Windows 365, Microsoft Intune, Azure Virtual Desktop, and Azure administration. Independent benchmark testing by Dr. Benny Tritsch shows common deployment and management tasks require up to 91% fewer clicks than the native Azure Portal, reducing manual steps and the opportunity for configuration errors.
Sage, a payroll and accounting software company that migrated from Citrix, achieved 62 to 65% savings on VM direct costs, $1.5 million in annual savings, and grew from 200 to 1,000 customers without adding headcount.
On the Windows 365 path
Managing Windows 365 means managing Intune, and Nerdio Manager extends Intune's native capabilities with a single console for Cloud PC administration, reporting, and policy control. Unified application management deploys applications to Cloud PCs in approximately 30 seconds compared to native Intune delivery that can take up to 3 hours. Nerdio Advisor surfaces right-sizing recommendations for Cloud PC SKUs, flags underutilized licenses for reclamation, and identifies users eligible for Flex license conversion. Nerdio Manager can also create, back up, and restore Intune policies, a capability native Intune does not offer.
For organizations standardizing Cloud PCs for steady-state workers, those day-to-day tasks change daily administration: app delivery, right-sizing and license reclamation recommendations, and backup and restore for Intune policies. If Windows 365 is the center of your plan, our articles on Nerdio for Windows 365 and W365 management tools could be helpful reads.
Proof that the unified model matters
The City of Corona, a municipal government running both Windows 365 and Azure Virtual Desktop, uses Nerdio Manager for unified management across both platforms. Systems Administrator Brad Ransbury described the difference: "Before Nerdio, we had to jump through multiple clicks in Azure or even rely on PowerShell scripting. Now, it's just a few clicks in an intuitive GUI, and we're done."
On Azure Virtual Desktop, Auto-Heal detects and repairs broken session hosts automatically without manual intervention. Agentless monitoring uses configurable polling intervals down to one minute, with a default of every five minutes, to show session host status and related environment data without installing proprietary agents on session hosts.
Building the operational readiness that makes it stick
Teams often invest in migration architecture and under-invest in steady-state operational design. Cloud desktop environments that launch successfully can degrade over time from unowned processes, undisciplined image management, and cost overruns from unmonitored scaling.
Assign named owners before migration begins
The Cloud Adoption Framework recommends identifying key stakeholders such as a sponsor, project lead, and subject-matter leads across architecture, security, operations, and business alignment, with clear responsibilities defined early in the adoption process. Gaps in this list represent program risks, not optional roles.
Retrain your service desk before migration generates tickets
Ticket categories shift after migration. Hardware failure recovery and slow log-on complaints diminish. Profile issues, connectivity errors, Conditional Access failures, and image-related application breaks appear. Level 1 and Level 2 staff need retraining on cloud-specific troubleshooting categories before broad rollout creates volume in categories they haven't seen before.
Establish DEX ownership and measurement baselines early
Forrester DEX research highlights fragmented DEX ownership and operating-model challenges. End-user productivity is the single largest benefit category in the previously mentioned Forrester TEI model, projected at $3.1 million to $6.2 million of the total $6.6 million to $10.8 million three-year benefit.
Without DEX ownership and measurement baselines established before migration, this benefit cannot be captured or reported to the CIO. Your ESU cost avoidance numbers can get the project funded. Your DEX metrics determine whether leadership considers it a success.
Operational readiness is what keeps the environment from slipping after cutover. Named ownership, service desk preparation, and DEX baselines turn a successful migration into a stable operating model.
If your Citrix renewal is colliding with Windows 10 ESU costs and your CIO expects a modernization plan without adding headcount, you need to sequence platform choice, migration, governance, and operations so the transition holds. 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 cloud desktop strategy
Resources
Learn more about Nerdio Manager
