Blog
Cloud desktop migration business case: how to build it for CIO approval
Build a cloud desktop migration business case your CIO will approve. TCO data, financial models, objection handlers, and customer proof points.
Overview
Your CIO just asked for a cloud desktop migration recommendation by the end of the quarter. That means a document that satisfies the CFO's cost scrutiny, clears the CISO's security review, and gives every executive enough confidence to sign off on a multi-year commitment.
Many business cases that get shelved share the same mistake: they lead with savings projections. CIOs have seen optimistic savings numbers before, and those numbers have been wrong. The business cases that get funded lead with the cost of staying on the current platform, then use savings data as supporting evidence inside a financial model.
Your primary platform options fall under what Microsoft calls Windows Cloud, which encompasses both Windows 365 and Azure Virtual Desktop (AVD). Microsoft Intune fits as the endpoint management layer across either platform. Here is how to build the business case that gets the project funded.
Start with what your legacy platform costs over the next 3 years
Before building a single slide, quantify the cost of doing nothing.
Why the cost of staying leads the deck
Some software licenses doubled in cost. Perpetual licenses went subscription-only. Gartner estimated 2x to 3x cost increases (2024) for some customers after major vendor acquisitions. These shifts have put Citrix alternatives on the table for organizations facing renewal decisions.
A business case that opens with "we will save X%" invites immediate skepticism. Lead with strategic alignment, the cost of staying, and risk reduction. The savings data belongs in the financial model section, not the executive summary. This sequencing is the difference between a business case that gets debated and one that gets funded.
Build the cost-of-staying calculation
Your cost-of-staying calculation should cover the 3 to 5-year outlook. Include license renewal costs at new rates, hardware refresh CapEx, premium maintenance on aging hardware, and hypervisor licensing cost trajectory. This number is often larger than the migration cost itself, and it is the first slide your CFO should see.
Model the cloud desktop total cost of ownership (TCO)
With the cost of staying documented, model the future state. The published platform pricing and independent projections below are the third-party data you plug into your model. The section after that covers what organizations comparable to yours spent and saved.
Every projection in this section assumes the environment is properly managed and optimized after go-live. Modeled outcomes and real-world outcomes diverge when cost governance is treated as someone else's problem. Your financial model needs a line item for ongoing operations management, and the Ongoing Cost Governance section below covers what that looks like.
Azure Virtual Desktop
Platform license cost is $0 for organizations already holding Microsoft 365 E3, E5, E7, F3, Business Premium, A3/A5, or Windows 10/11 Enterprise E3/E5 per user. You pay for Azure infrastructure (compute, storage, networking) on top of whatever license you already hold.
Reserved instances can cut compute costs by up to 72% versus 24/7 pay-as-you-go pricing, though they require upfront commitment and work best for stable, predictable workloads rather than variable environments.
A 2021 Forrester TEI study for a composite organization of approximately 1,700 users migrating from on-premises Remote Desktop Services (RDS) found a 3-year return on investment (ROI) of 210%. Net present value (NPV) came to $1.89 million. The study's three-year model reflected an average per-user cost of approximately $20 per month for compute, storage, and networking.
Know the TCO
This step-by-step wizard tool gives you the total cost of ownership for AVD in your organization.
Windows 365
Fixed monthly pricing, all-inclusive. A standard knowledge-worker configuration (2 vCPU, 8 GB RAM, 128 GB storage) runs $41 per user per month with no separate Azure infrastructure charges.
A Forrester TEI for Windows 365 found a 3-year ROI of 40% and NPV of $1.53 million for a composite organization. Contractor device provisioning time dropped by about 80%.
Using both platforms together
A combined TEI study (2025) projected a 3-year ROI range of 94% to 217% and NPV of $3.2 million to $7.4 million for organizations running both platforms. For conservative business case modeling, use the lower bound of 94% ROI and $3.2 million NPV.
| Factor | Windows 365 | Azure Virtual Desktop |
|---|---|---|
| Pricing model | Fixed per user per month | Consumption-based |
| Azure presence required | No | Yes |
| Primary management surface | Intune (endpoint policies, apps, compliance) | Azure Portal and PowerShell (infrastructure, scaling, cost) |
| Compliance customization | Less flexible | More flexible |
| Best fit | Non-technical users; organizations new to Azure; predictable cost priority | Engineers and power users; existing Azure presence; variable workloads; compliance customization required |
Many enterprise customers run both platforms together. Each serves different user populations. Windows 365's predictable per-user pricing simplifies the finance conversation. Azure Virtual Desktop offers greater compliance control and cost optimization potential for workloads that benefit from consumption-based scaling. The combined TEI study (2025) validates this approach with projected 3-year ROI of 94% to 217%.
Some legacy desktop platforms do not publish per-seat pricing, and no vendor has published a neutral TCO comparison. Your cost-of-staying calculation will need your actual contract rates.
Take Windows to the Cloud with Microsoft and Nerdio
Join us for a webinar to discover how to take Windows to the cloud. Get insights from industry leaders on navigating the modern workspace and driving secure, cloud-powered operations.
Build the cloud desktop migration financial model
Your CFO will scrutinize three numbers. What does the migration cost? What does the environment cost to run after go-live? What is the staffing impact? The AVD total cost of ownership section above gives you the published benchmarks. This section provides the customer-comparable evidence behind each number.
Migration investment
Microsoft's Cloud Adoption Framework confirms there is no direct migration path from other virtual desktop infrastructure (VDI) platforms to Azure Virtual Desktop. You are building a new environment from scratch. Budget two tracks in parallel: the AVD migration workstream and the legacy platform retirement.
Real-world timelines from named organizations:
- Felleskjøpet Agri SA (4,200 employees, Citrix to Azure Virtual Desktop) reached production in 3 to 4 months, managed by 1 administrator. Reported approximately 9 million NOK (roughly $830,000 USD) in licensing savings over 3 years.
- Damart (migrated to Azure Virtual Desktop) reached production in under 1 month. Reported approximately 50% savings on both licensing and labor costs.
Use these timelines to calibrate your project plan, but scope based on your own environment complexity, application portfolio, and compliance requirements.
Ongoing cost governance
Your ongoing Azure spend depends on whether you treat cost governance as a defined workstream or leave it to manual oversight. This is the line item in the financial model that determines whether the TCO projections above hold up 12 months after go-live.
An ESG economic validation (September 2024) from TechTarget's Enterprise Strategy Group studied organizations that automated AVD cost governance using Nerdio Manager for Enterprise. The study found an average 55% Azure Virtual Desktop cost reduction versus AVD managed natively, a 50% reduction in IT admin hours, and a 36% reduction in support costs.
Named customer results reinforce the pattern. Sage migrated from Citrix to Azure Virtual Desktop and achieved 62 to 65% VM cost reduction, approximately $1.5 million in annual savings. Setfords reported 40 to 50% Azure cost reduction after migrating, described as hundreds of thousands of pounds annually.
The specific percentage depends on your starting environment, workload mix, and which cost categories you measure. For your financial model, use the ESG study's 55% figure as the midpoint estimate and model a range with your actual Azure consumption data. Budget cost governance tooling ($6 to $10 per user per month for Nerdio Manager) as a line item in ongoing operations.
Post-migration staffing
Include staffing impact in the financial model. The Forrester TEI study for Azure Virtual Desktop found IT support staffing dropped from 4 FTEs to 2 FTEs for deployment and maintenance. A multinational financial services firm using Nerdio Manager reported freeing 77 hours per month per engineer. Image preparation time collapsed from 2 weeks per month to 2 to 4 hours.
Pre-answer the seven CIO objections
With the financial model built, anticipate what happens when you present it. Every one of these objections will surface in the approval meeting or the hallway conversation before it. Build the counter-arguments into the document so your CIO reads the answer before forming the question.
"The TCO math does not hold up. Cloud desktops will cost more."
You have probably heard a version of this from someone who ran a cloud proof-of-concept without auto-scaling and watched the Azure bill climb. The concern has legitimate grounding. A 2025 Crayon report found 94% of global IT leaders struggle with cloud cost optimization, and AVD's cost advantage depends on multi-session pooling and active auto-scaling governance. Without both, the math can genuinely favor staying.
The response is to treat auto-scaling governance, scheduled shutdown rules, and FinOps policy enforcement as non-negotiable migration deliverables. Budget them as line items in the financial model. The ESG data from your Ongoing Cost Governance section (55% average cost reduction with a management layer) gives you the evidence to back this up.
"We will lose the mature management capabilities we have in our current platform."
If your team has spent years building automation, monitoring, and application packaging on top of Citrix or Omnissa Horizon (formerly VMware Horizon), this is not an idle concern. Native Azure Virtual Desktop management requires toggling between multiple portals, and organizations should evaluate their management tooling and day-two operations carefully before committing.
The response is to budget a management and automation layer as a line item. Nerdio Manager deploys directly into your Azure environment and provides a unified console for Windows 365, Intune, and Azure Virtual Desktop. It replaces the multi-portal overhead that makes native management costly at scale.
"Migration will disrupt business operations."
Poor planning, security gaps, and interoperability issues are among the most common migration challenges. The risk is real, and your CIO knows it.
Include a parallel-operation budget line in the business case. Run the legacy environment and Azure Virtual Desktop side by side during transition. Define production readiness as the ability to sustain changes under production load. The Citrix-to-AVD migration checklist provides a scope framework you can reference.
"We are trading one vendor lock-in for another."
Recent licensing and packaging changes showed that legacy platform lock-in carries its own pricing discontinuity risk. One report cited an approximately 1,050% proposed price increase in a lawsuit allegation.
For organizations already at Microsoft 365 E3, E5, or E7, Azure Virtual Desktop access rights are included. The incremental lock-in cost is lower than maintaining separate legacy desktop licenses on top of the existing Microsoft stack.
"Our security and compliance posture will regress."
Commission a formal security gap analysis comparing current controls against AVD equivalents before finalizing the business case. Azure Virtual Desktop hardened default security in 2025 by disabling several redirection types by default for newly created host pools.
Evaluate Azure Virtual Desktop's native integration with Entra ID Conditional Access and Microsoft Defender for Endpoint against your current control set. Include the gap analysis results in the compliance section of your document. This is the evidence your CISO needs, and it belongs in the business case alongside the financial model.
"Our IT team does not have the Azure skills."
AZ-140 and AZ-104 certification training are relevant for teams operating Azure Virtual Desktop. Frame the staffing section of your business case around skills development, with training timelines and certification milestones. Third-party management platforms like Nerdio Manager reduce the minimum viable Azure skills threshold for day-to-day operations.
"User experience will degrade, especially for power users."
Use Azure Migrate performance-based assessments to right-size VMs based on actual CPU, RAM, and disk utilization data. Classify workloads into three categories before migration. Multi-session pooled desktops suit most knowledge workers. Dedicated GPU-enabled desktops serve power users. Some workloads are not appropriate for Azure Virtual Desktop yet and should remain on-premises until a later phase.
Add the compliance dimension (regulated industries)
The objection responses above address migration risk at the portfolio level. For regulated industries, the compliance section of your business case adds a second dimension: migration as a compliance enabler. Azure's compliance certification portfolio is broad, and continuous compliance monitoring supports ongoing posture management beyond point-in-time assessments.
Three compliance migration rules for your business case:
- Do not lift-and-shift compliance settings. Use migration as an opportunity to configure properly.
- Document all settings and security controls during implementation for auditors.
- Treat the compliance reset as a distinct workstream with its own timeline and budget.
Nerdio Manager supports this with role-based access control, audit logging, and policy automation. It does not certify or guarantee compliance outcomes. It provides the governance layer that makes audit-ready configurations repeatable.
Assemble the business case: the 11 sections that get approved
You now have the financial model, the objection responses, and the compliance framing. Organize them into a document that earns the CIO's signature and withstands scrutiny from finance and security.
The three unstated criteria
Many business cases cover cost projections, a migration timeline, and a vendor recommendation. The ones that get shelved usually fail on three criteria CIOs evaluate but rarely state out loud.
Financial governance after go-live. The CIO needs confidence that Azure consumption will stay controlled throughout the environment's lifecycle. If your business case ends at "projected savings," it has a hole. Dedicate a section to auto-scaling and reserved instance policies, with a clear cost attribution model.
Hybrid realism. "Cloud-only" desktop strategies are not always achievable. Your business case should account for workloads that stay on-premises and explain why.
Multi-stakeholder alignment. Finance sees NPV. Business leaders see timelines. IT sees infrastructure readiness. Each audience gets the view they need from the same document. If your business case reads well for IT but leaves finance guessing, it will stall.
The three obvious criteria still matter. Every business case needs strategic alignment with a cloud-first mandate, quantified cost of inaction over 3 to 5 years, and a phased plan with rollback capability. The difference is that many CIOs assume you will cover those. The three above are where business cases quietly die.
The 11 sections of the cloud desktop migration business case
Based on enterprise cloud migration frameworks, these are the 11 sections that separate approved business cases from shelved ones:
- Executive summary: Recommendation, market signal, organizational catalyst, 3-year NPV, decision requested. One page.
- Current state assessment: Your legacy platform inventory and the cost-of-staying calculation from Section 1 of this article.
- Proposed solution: Map Windows 365 versus Azure Virtual Desktop versus hybrid to your Azure maturity, compliance requirements, and user population.
- TCO analysis (3 to 5 year): Current state costs versus future state costs, using the data from Section 2. Present NPV alongside the savings percentage.
- Risk assessment: Named risk register with likelihood and impact ratings, covering both migration risks and the risks of staying.
- Compliance and security: Regulatory framework mapping as a distinct workstream, per Section 5.
- Migration plan: Phased approach with pilot, wave migrations, compliance reset, and optimization.
- Staffing and organizational impact: Skills gap analysis, training budget, and development milestones.
- Platform selection rationale: Windows 365 versus Azure Virtual Desktop decision table mapped to organizational characteristics.
- Financial governance plan: Cloud cost management as a parallel workstream with auto-scaling policies, reserved instance strategy, and cost attribution models. Use Nerdio's free AVD modeler tool to model scenarios.
- Decision request: Budget (CapEx plus OpEx), headcount and training authorization, timeline commitment, and explicit next steps.
The document should read as a complete investment case. If any section requires a follow-up meeting to explain, it is not ready for submission.
Make the case for action
The business case that gets funded is the one that makes inaction look more expensive than action.
If you have followed the structure above, your document does three things the savings-led approach does not. It shows your CFO what the current platform will cost over the next 3 to 5 years at new pricing. That number is usually surprising. It shows your CIO that Azure cost governance is a budgeted workstream with named tooling and customer evidence behind it. And it shows your CISO that the migration includes a formal security gap analysis and a compliance reset workstream built from scratch.
If you are building a cloud desktop migration business case now, get a demo to see how Nerdio Manager fits into your financial model, or try it free to test it against your own Azure environment. For a deeper look at Azure desktop pricing, see the AVD TCO guide.
Frequently asked questions about cloud desktop migration business cases
Resources
Learn more about cloud desktop migration