Blog
The complete guide to Citrix to Azure Virtual Desktop migration
A five-phase Citrix to AVD migration guide: assessment, architecture, profiles, apps, and cutover, plus the Microsoft deadlines to plan for.
Table of Contents
- Why enterprise teams are moving from Citrix to Azure Virtual Desktop
- Phase 1: Audit and assess your Citrix environment
- Phase 2: Design your target architecture
- Phase 3: Build, pilot, and plan rollback
- Phase 4: Migrate at scale
- Phase 5: Tune post-migration operations
- Time-sensitive deadlines for active migrations
- Where Nerdio Manager for Enterprise fits in Citrix to Azure Virtual Desktop migration
- Frequently asked questions about Citrix to Azure Virtual Desktop migration
This guide is for the enterprise IT leaders and architects planning a Citrix to Azure Virtual Desktop migration (the people who own both the business case and the cutover). You may support users across several Citrix delivery groups, a fleet of published apps the business built over years, and a renewal deadline forcing the decision. The job now is a migration path that preserves the environment your business runs on, without a risky big-bang cutover.
Citrix to Azure Virtual Desktop migrations have no single automated migration path. The work breaks into:
- session host and image planning
- profile migration
- application delivery
- infrastructure assessment
Each has its own dependencies, risks, and automation opportunities, and the surprises tend to land during cutover in identity, printing, monitoring, and rollback.
Your migration target sits within Windows Cloud, Microsoft's umbrella term for Azure Virtual Desktop and Windows 365. Your replacement strategy depends on your workload mix. Windows 365 suits predictable per-user workloads and is managed through Microsoft Intune. Azure Virtual Desktop suits variable or multi-session pooled workloads, managed through the Azure Portal, PowerShell, and growing Microsoft Intune support. Many enterprises run both.
Here we will be focusing on the Azure Virtual Desktop path, with notes on where Windows 365 fits.
Why enterprise teams are moving from Citrix to Azure Virtual Desktop
Enterprises leave Citrix for three reasons: the licensing math changes, pricing shocks force a re-evaluation, and Azure Virtual Desktop runs inside the Microsoft stack they already pay for.
The financial case usually starts with licensing. Migrating Citrix catalogs running Windows Server OS to Windows 11 Multi-session on Azure Virtual Desktop removes the need for Remote Desktop Services Client Access Licenses, and eligible Microsoft licensing already includes Azure Virtual Desktop access rights. That changes the total cost of ownership math against Citrix's named-user model.
Pricing and acquisition changes at Citrix and VMware accelerated the timelines. CRN has reported a wave of customers seeking alternatives to Citrix and VMware, including Omnissa, after both vendors were acquired and changed their pricing models.
Phase 1: Audit and assess your Citrix environment
Before writing a single script, map every component in your existing Citrix environment to its Azure Virtual Desktop equivalent. Incomplete assessment creates rework later in the migration.
Nerdio Manager for Enterprise includes Nerdio Migrate, a set of guided workflows for moving from Citrix to Azure Virtual Desktop, with profile migration guidance and staged deployment waves. If your target will run both Azure Virtual Desktop host pools and Windows 365 Cloud PCs, the same platform carries assessment work into pilot waves and keeps application and Microsoft Intune policy work consistent across both.
Map Citrix components to Azure Virtual Desktop equivalents
Your Citrix infrastructure concepts translate directly to Azure Virtual Desktop terminology.
| Citrix component | Azure Virtual Desktop equivalent |
| Machine Catalogs | Host Pools |
| Delivery Groups | Application Groups |
| Citrix UPM | FSLogix Profile Containers |
| Published Apps | RemoteApp Groups |
| HDX Policies | Azure Virtual Desktop settings / Microsoft Intune / Group Policy Objects |
| Citrix Director | Azure Monitor / Azure Virtual Desktop Insights |
| Citrix Universal Print Server | Microsoft Universal Print |
| Citrix Gateway / NetScaler | Microsoft Entra ID + Conditional Access |
| StoreFront | Azure Virtual Desktop feed + Windows App |
| App Layering | App Attach (MSIX, Appx, App-V formats) |
Use this mapping as the starting point, then validate each dependency against the way your Citrix environment actually runs.
Audit your published applications
Export your published application list using the Citrix PowerShell SDK:
Get-BrokerApplication | Select-Object ApplicationName, CommandLineExecutable, CommandLineArguments | Export-Csv -Path "CitrixApps.csv"
Compare this export against actual usage data. Some published apps see little or no use, and auditing first keeps you from packaging apps nobody opens. For each app, decide its Azure Virtual Desktop delivery method. App Attach delivers compatible app formats dynamically without installing them on the OS image. Apps that cannot be converted fall back to SCCM or Microsoft Intune deployment directly onto the session hosts.
Audit identity and authentication (NetScaler to Entra ID)
Azure Virtual Desktop does not support third-party gateways such as Citrix NetScaler as an authentication front end. If you rely on NetScaler for SSL offload, load balancing, MFA, and session-level access policies, replacing it means redesigning authentication around Microsoft Entra ID Conditional Access. Inventory every NetScaler policy expression and map it to an Entra ID Conditional Access equivalent. Treat this as a security architecture project that runs in parallel with your application packaging and profile migration work.
Extract monitoring baselines from Citrix Director
Before decommissioning anything, extract historical utilization data from Citrix Director. Use performance and resource-utilization history, plus processor benchmark data, to size Azure VMs. Record logon durations, app launch latency, session counts by time of day, and peak concurrent users. You need these baselines to prove the Azure Virtual Desktop environment performs at least as well as Citrix once it is live.
Assess your printing architecture
Inventory every network printer, its driver, and its Citrix access policy before you cut over. Print redirection is a common source of post-migration tickets, and the architecture changes completely. Citrix Universal Print Server connects the session host to your Windows print server to manage network printers. Universal Print is cloud-native and, unlike the Citrix model, needs only outbound connections. Confirm your Microsoft 365 E3, E5, or Business Premium licenses include Universal Print entitlement (100 print jobs per user per month), then plan printer re-registration through the Azure Portal and permission reassignment via Entra ID security groups.
Map backend and network dependencies
Identify the SQL servers, file servers, and line-of-business backends that need low-latency connectivity. For anything staying on-premises, confirm ExpressRoute or a site-to-site VPN gives you the bandwidth and latency those apps need. Moving from single-user or lower-density Citrix VMs to multi-session pooled desktops on Azure changes your network traffic patterns, so size the connection for the new pattern.
Phase 2: Design your target architecture
Design decisions made in this phase (landing zone topology, profile strategy, application delivery, policy mapping, GPU sizing) lock in the cost and performance ceiling of the Azure Virtual Desktop environment, so make them before you start building.
Set up your Azure landing zone
The landing zone provides Infrastructure as Code templates for enterprise-scale deployments. Microsoft recommends separating resource groups by lifecycle: Azure Virtual Desktop service objects in one, session host compute in another, storage accounts in a third, and shared resources like custom images in their own. If you are running Citrix in parallel during the migration, Microsoft also maintains landing zone guidance for Citrix on Azure and hybrid networking between Citrix Cloud and Azure.
If you are standardizing deployment and operations for Windows Cloud, Nerdio Manager puts Windows 365, Microsoft Intune, and Azure Virtual Desktop into one management layer. Azure Virtual Desktop teams get repeatable image management, profile operations, and host pool administration; Windows 365 teams get Cloud PC operations, Microsoft Intune policy administration, and unified application management across Cloud PCs and host pools.
How do you migrate Citrix UPM profiles to FSLogix?
Citrix UPM uses file-based replication. Azure Virtual Desktop uses FSLogix, which stores profiles in VHD/VHDX containers on Azure Files, Azure NetApp Files, or other supported backends. Because the formats differ, you choose between a fresh start and a scripted conversion.
A fresh start works when AppData preservation is not mandatory. Deploy fresh FSLogix containers and use OneDrive Known Folder Move to sync documents, desktops, and pictures to the cloud before cutover. On first login, FSLogix creates a clean container and OneDrive syncs the critical data back down. This clears years of profile bloat, corrupted temp files, and orphaned application data.
A scripted conversion fits when preserving AppData is mandatory. Use the FSLogixMigration PowerShell module to convert file-based profiles to VHDX containers:
- Mount a new FSLogix file share.
- Loop through the existing UPM folders.
- Create a dynamic VHDX per user.
- Copy data and ACLs into the container.
- Unmount and finalize.
Microsoft documentation covers FSLogix profile containers on Azure Files with Active Directory Domain Services (AD DS) or Microsoft Entra Domain Services authentication. Confirm your file share authentication and container design before you migrate any profiles.
Design application delivery with App Attach
Repackage legacy apps into MSIX for App Attach, which attaches applications to user sessions at runtime without installing them on the OS image. Apps that cannot be converted to MSIX, Appx, or App-V need another delivery path, such as installing them in the base image. If your Citrix environment uses App Layering to merge layers at runtime, App Attach changes that model, so plan the swap carefully and decide which apps get repackaged and which go on the golden image.
What replaces Citrix HDX policies in Azure Virtual Desktop?
Azure Virtual Desktop spreads the equivalent controls across Azure Virtual Desktop settings, Group Policy, and expanding Microsoft Intune support, depending on the policy area. Citrix HDX policies govern clipboard redirection, audio quality, client drive mapping, bandwidth limits, and display rendering.
Audit every HDX policy and sort each one into a bucket: a direct Microsoft Intune, Group Policy, or Azure Virtual Desktop equivalent; needs an alternative approach; or no longer needed in the Azure Virtual Desktop architecture. Citrix environments accumulate hundreds of policies over the years, so treat the migration as a chance to rationalize them.
Plan GPU workload migration
If you are migrating Citrix HDX 3D Pro workloads such as CAD, BIM, 3D rendering, or medical imaging, choose GPU VMs during design, not after cutover. Azure offers NVv4-series VMs with AMD Radeon Instinct MI25 GPUs and NCasT4_v3-series VMs with NVIDIA Tesla T4 GPUs. Microsoft redistributes the NVIDIA GRID driver installers for these series, which removes the on-premises NVIDIA vGPU license server.
Phase 3: Build, pilot, and plan rollback
Build the target environment, validate it with a deliberately broad pilot group, and document the rollback path before day one. A successful pilot is the gate that decides whether scale rollout is safe.
Build a clean golden image
A clean build is usually the better path. Automate golden image creation with Azure Image Builder or HashiCorp Packer. Define the OS, applications, and settings in a JSON template, and the build spins up a temporary VM, installs software and updates, runs Sysprep, and saves the image to the Azure Compute Gallery.
For a complex legacy image you cannot rebuild, snapshot your Citrix master image, generate a SAS (Shared Access Signature) URL, and import the VHD into Azure. Before deploying session hosts, remove the Citrix VDA software and install the Azure Virtual Desktop agent.
New host pools that use a session host configuration need a managed identity. Two Microsoft enforcement deadlines for this have already passed: since October 15, 2025, existing host pools with a session host configuration cannot update that configuration without a managed identity, and since November 15, 2025, those host pools cannot create session hosts without one. Treat the managed identity as a prerequisite.
Recreate published apps as RemoteApps
Use the CSV you exported in Phase 1 to recreate application definitions in Azure Virtual Desktop with the New-AzWvdApplication cmdlet. Write a script that iterates through each row and publishes the RemoteApp to the right host pool and application group, mapping each Citrix app name, executable path, and command-line argument to the matching Azure Virtual Desktop parameter.
Select your pilot group
Pick a pilot group that stresses the migration across four dimensions: application complexity, geographic distribution, business criticality, and persona variety. Include the users who depend on your most troublesome apps, test latency from your most remote offices, choose a team that can absorb a brief disruption, and cover both knowledge workers and task workers.
A pilot this broad surfaces issues a single-team pilot would miss.
Plan your rollback path
Define the rollback procedure before day one. Keep your Citrix delivery groups running throughout the pilot. If a cutover fails, route users back to Citrix StoreFront with DNS or load balancer redirects, and validate FSLogix data consistency for anyone who created data in the Azure Virtual Desktop environment first. Document the exact sequence and test it during the pilot.
Phase 4: Migrate at scale
Once the pilot validates the environment, scale rollout is a coordination problem across waves, client deployment, printing, monitoring, and Citrix license wind-down. Sequence them so each wave finishes before the next billing cycle.
Roll out in waves
Microsoft's Cloud Adoption Framework recommends an assess, deploy, release approach. After the pilot validates the environment, expand in waves. Each wave should add a business unit or region, run through at least one full business cycle, and pass user acceptance testing before the next wave starts.
Deploy the Windows App to your endpoints
Deploy the Windows App across your endpoint estate through your standard software distribution process. Microsoft now recommends the Windows App for Windows 365, Azure Virtual Desktop, and Microsoft Dev Box, and the older clients are retiring: the Remote Desktop Store app ended support on May 27, 2025 and is no longer downloadable, and the Remote Desktop client MSI reached end of support on March 27, 2026. For Microsoft Teams, your environment needs Teams version 25153.x.x.x with at least Remote Desktop client 1.2.6278 or Windows App 2.0.550.0, since Classic Teams VDI ended availability on July 1, 2025.
Cut over printing to Universal Print
Microsoft Universal Print is a cloud-based option that can reduce or remove traditional print servers, depending on your printers and licensing. Re-register printers through the Azure Portal, reassign permissions via Entra ID security groups, and confirm that printer preferences persist across sessions. Unlike Citrix's bidirectional network model, Universal Print needs only outbound connections.
Cut over monitoring to Azure Virtual Desktop Insights
Replace Citrix Director with Azure Virtual Desktop Insights. Configure data collection rules and Log Analytics workspaces before you decommission Director. Your helpdesk learned Director's session shadowing and logon-duration diagnostics, so plan retraining on the new tooling as a parallel workstream.
Wind down your Citrix licenses
Coordinate your Azure Virtual Desktop go-live with your Citrix contract expiration. Parallel environments cost money, so minimize the overlap. Check your Citrix renewal notice periods and plan each wave to finish before the next billing cycle.
Phase 5: Tune post-migration operations
Migration does not end at cutover. The first 90 days decide whether the Azure Virtual Desktop environment hits the business case you built.
Control your post-migration Azure costs
Azure Virtual Desktop is consumption-based. You pay for the compute, storage, and networking your session hosts use. Four levers control most of the cost:
- Multi-session pooled desktops drive per-user cost below personal desktops.
- Auto-scaling powers down and deallocates idle VMs so you stop paying for compute you are not using.
- Right-sizing matches host pools to real demand.
- Storage tier switching drops stopped-and-deallocated VMs to cheaper disk.
Teams typically combine these with workload consolidation and Azure Virtual Desktop-optimized rebuilds. Moving from Windows Server OS to Windows 11 Multi-session also removes the Remote Desktop Services Client Access License (RDS CAL) requirement, which further reduces the post-migration costs.
Validate disaster recovery and resilience
Citrix environments are usually built across multiple sites with distributed delivery controllers. Azure Virtual Desktop needs explicitly designed multi-region resilience.
Microsoft's Cloud Adoption Framework guidance for business continuity and disaster recovery (BCDR) lists three prerequisites for a secondary region:
- network infrastructure in that region
- highly available hybrid connectivity in both regions
- authentication infrastructure available in the DR region
If your Citrix setup had multi-site failover, design comparable resilience around your recovery point objective (RPO), recovery time objective (RTO), high-availability, and BCDR requirements.
Time-sensitive deadlines for active migrations
Several Microsoft deadlines have already passed, and one major retirement is coming. Treat the passed dates as active requirements, not history.
| Deadline | Date | Status |
| Managed identity required for session host config updates | October 15, 2025 | Passed. Enforcement active. |
| Managed identity required for creating session hosts in existing host pools with a session host configuration | November 15, 2025 | Passed. Enforcement active. |
| Remote Desktop Store app end of support | May 27, 2025 | Passed. No longer downloadable. |
| Classic Teams VDI end of availability | July 1, 2025 | Passed. |
| Remote Desktop client MSI end of support | March 27, 2026 | Passed. End of support. |
| Azure Virtual Desktop Classic retirement | September 30, 2026 | Upcoming. |
The September 2026 Azure Virtual Desktop Classic retirement matters most. Any migration target must use current Azure Virtual Desktop instead of Azure Virtual Desktop Classic. If your plan assumed Classic as an interim step, adjust the architecture now.
Where Nerdio Manager for Enterprise fits in Citrix to Azure Virtual Desktop migration
The PowerShell methods and manual procedures in this guide work, but they create repeatable administrative work every time an image changes, a profile needs cleanup, or an app needs to ship. Nerdio Manager consolidates that work, so your team runs Windows 365, Microsoft Intune, and Azure Virtual Desktop from one console instead of splitting it across portals and scripts. The value holds during the migration and in the steady state after it.
Automate image management
Updating and redistributing images by hand every time the base image changes adds work and invites misconfiguration. In Dr. Tritsch's independent testing, updating a custom image dropped from 5:09s and 146 clicks in native Azure Virtual Desktop management to 0:37s and 13 clicks in Nerdio Manager: an 88% time reduction and 91% fewer clicks.
Fewer clicks means fewer manual steps, which means fewer chances to misconfigure a host pool.
Simplify FSLogix profile management
Profile maintenance turns into recurring work after cutover. Nerdio Manager turns on FSLogix profiles, Cloud Cache for high availability, and automatic profile shrinking, and handles profile cleanup from the same console. Storage still needs a correct design up front, but the day-to-day upkeep stops being manual.
Cut compute costs with auto-scaling
Auto-scaling is the most direct cost lever after migration: power hosts down, deallocate them, and stop paying for idle compute. Nerdio Manager's patented auto-scaling does this automatically, switches OS disks between premium and standard tiers during idle periods, and pre-stages hosts before shifts begin. Sage saved 62% to 65% VM costs and $1.5 million in annual savings after leaving Citrix, and Equitable Bank reported 74% compute savings per month.
Unify application management across host pools and Cloud PCs
App delivery tends to fragment across host pools, Cloud PCs, and endpoint tooling after a migration. Nerdio Manager's application management connects to your existing Microsoft Intune, SCCM, and WinGet repositories and uses one workflow for both Azure Virtual Desktop host pools and Windows 365 Cloud PCs. On the Windows 365 side, that workflow can deploy apps in about 30 seconds, rather than the multi-hour wait native Intune delivery can involve.
Manage mixed Windows 365 and Azure Virtual Desktop operations
After cutover, the work shifts into Intune policy, Cloud PC health, host pool health, and utilization. Nerdio Manager connects Microsoft Intune data into the same console and lets admins create, back up, and restore Intune policies. For Windows 365 specifically, it adds right-sizing recommendations for Cloud PCs, license reclamation alerts for underused licenses, and Flex (formerly Frontline) conversion recommendations when users do not overlap. Day-to-day support, monitoring, and remote actions run side by side for all three environments.
Run guided migration workflows
Nerdio Migrate brings the migration workflows into the same console your team keeps using after go-live, which trims the manual sequencing you own. Carvana's Nerdio migration cut IT costs 40% to 50% in a 14-day deployment. Cubesys left Citrix and stood up a 4,000-user Azure Virtual Desktop environment in two weeks. For a step-by-step pre-migration list, see the migration checklist, and for the full architectural walkthrough using Nerdio, see the Citrix migration guide.
Ready to get started? Request a demo of Nerdio Manager for Enterprise, or start a free trial.
Frequently asked questions about Citrix to Azure Virtual Desktop migration
Resources
Learn more about Nerdio Manager
