Introduction
Citrix renewals, aging infrastructure, and a growing Microsoft 365 and Azure footprint push many IT teams to the same question: should our desktops move to Azure Virtual Desktop (AVD)?
Citrix is also changing how it licenses on-premises components. Its license activation announcement retires file-based licensing on April 15, 2026, in favor of the License Activation Service.
Don't treat the move as a lift-and-shift. Identity, networking, applications, profiles, security, cost controls, and operating processes all need redesigning for the target platform.
This article walks through the roadmap: decide whether AVD fits, prepare the environment, migrate in waves, validate the user experience, and optimize after go-live.
Key Takeaways
- Start with a full inventory of Citrix components, apps, users, dependencies, and licenses.
- Resolve app compatibility, identity, networking, and FSLogix design before broad rollout.
- Design around user personas, not a copy of every Citrix setting.
- Keep Citrix running through the pilot and early waves, with rollback criteria defined up front.
Why Migrate from Citrix to Azure Virtual Desktop?
Strategic differences, not a feature checklist
With AVD, Microsoft runs the control plane (brokering, gateway, management). You run everything else: identity, session hosts, storage, networking, monitoring, and governance. With Citrix, you typically operate more of the delivery stack yourself, or buy Citrix DaaS to offload it.
That shift changes who patches what, how you scale, and how administrators work day to day.
Where AVD fits well
Organizations already invested in Microsoft 365 and Azure gain the most:
- Microsoft Entra ID, Conditional Access, and MFA apply to desktop sign-in
- Intune and Defender manage compliance and endpoint protection
- Windows 11 Enterprise multi-session reduces the number of VMs to patch
- Azure networking and Microsoft 365 apps sit in the same ecosystem
Licensing matters here. Microsoft states that you must provide an eligible license for each user, such as Microsoft 365 E3, E5, or Business Premium. Eligibility doesn't remove Azure consumption costs for compute, storage, and networking. AVD isn't automatically cheaper than Citrix, so build the comparison with real numbers.
When AVD needs extra validation
Test these workloads before committing:
- Legacy apps that break on multi-session Windows
- Specialized peripherals and graphics-intensive workloads
- Strict latency requirements or heavy on-premises dependencies
- Licensing constraints
For on-premises dependencies, AVD Hybrid (now generally available) keeps desktops on Arc-enabled local infrastructure while Azure manages them. That suits organizations that can't fully move out of their data centers.
How to Prepare for a Citrix-to-AVD Migration
Inventory the existing Citrix environment
Document everything before designing anything:
- Delivery controllers, StoreFront, gateways, VDAs, catalogs, and delivery groups
- Citrix policies, profile technology, and images
- Applications, printers, peripherals, and file shares
- User populations and monitoring tools
Azure Migrate can help with discovery, and it accepts CSV imports for inventory you've already collected.
Then group users into personas: task workers, knowledge workers, contractors, developers, graphics users, and regulated or privileged users. Record each group's apps, performance needs, concurrency, and access requirements. One host pool per persona keeps design clean.
Build the business case and licensing plan
Compare current Citrix spend against projected AVD costs before you present numbers to finance.
Current Citrix side: licensing, infrastructure, support, staffing, and storage.
Projected AVD side: eligible Microsoft licensing, session-host VMs, shared storage, egress, backup, monitoring, and security.
Microsoft's cost estimation guidance points to the Azure Pricing Calculator. Verify current licensing and pricing on Microsoft's pages before you lock the business case.
Design identity, networking, and storage
Identity. Session hosts can join Microsoft Entra ID, Active Directory Domain Services, or Microsoft Entra Domain Services. Decide this early, along with MFA, Conditional Access, privileged administration, device compliance, and service accounts.
Networking. Map paths from users and session hosts to on-premises apps, databases, file shares, DNS, and domain controllers. Microsoft recommends round-trip time under 150 ms from clients to the host pool region, so region selection matters. Required endpoints must stay reachable.
Storage. Microsoft recommends Azure Files or Azure NetApp Files for FSLogix containers. Size for capacity, IOPS, availability, backup, and data location. Sign-in storms drive peak IOPS far above steady state.
Establish governance and migration controls
Translate Citrix security policies into AVD controls: RBAC, clipboard and drive redirection, session policies, Conditional Access, Defender, Intune, and logging. Newly created host pools disable clipboard and drive redirection by default, and the most restrictive setting wins when host-pool and Intune/GPO settings conflict.
Also define:
- Migration waves and pilot eligibility
- Test cases and success criteria
- Support ownership and maintenance windows
- Rollback triggers and conditions for retiring Citrix
If your team wants independent validation before migrating, TechSogna's fixed-fee AVD assessment reviews architecture, security, cost controls, dependencies, and documentation. It's a read-only review, with fixed fees starting at $3,500 depending on environment size.
How to Migrate from Citrix to Azure Virtual Desktop
Build the Azure and AVD foundation
Set up the Azure foundation before any production session host exists:
- Subscriptions, resource groups, and policies
- Virtual networks, NSGs, and DNS
- Identity connections, monitoring, and backup
- Admin access controls
Microsoft's landing zone guidance aligns with the Cloud Adoption Framework and supports portal, Bicep, and Terraform deployment.
Then design host pools around personas:
- Pooled or personal desktops
- Single-session or multi-session
- VM sizing, application groups, and workspaces
- Availability needs and scaling policies
Microsoft's sizing guidance suggests up to 6 users per vCPU for light workloads, 4 for medium, and 2 for heavy. Treat those as starting estimates and adjust with pilot data.
Create clean images and migrate applications
Build new images where you can. If you remediate Citrix images instead, strip out the VDA, legacy optimization tools, and obsolete policies. Microsoft's master-image guidance says the VM must not already have the AVD Agent installed.
Test apps individually and inside real workflows:
- Authentication and licensing
- Printing, peripherals, and file access
- Multimedia and line-of-business integrations
Decide what lives in the image and what gets delivered separately through Intune, Configuration Manager, or MSIX app attach.
Transition profiles and user data
Map your Citrix profile solution to an FSLogix design. FSLogix attaches the full profile as a VHD/VHDX at sign-in. Citrix Profile Management has no turnkey path to FSLogix, so plan exclusions, folder redirections, and profile size deliberately.
Test with representative users:
- First logon and concurrent access
- Profile locking and recovery from corruption
- Teams and Microsoft 365 behavior
- Redirected folders and personalization
Decide what data belongs in OneDrive, SharePoint, or Azure file services instead of the profile.
Run a pilot and validate the user experience
Microsoft requires a proof of concept before first deployment. Run AVD alongside Citrix, and include users from every persona, location, endpoint type, and business function. Don't hand-pick only the easy ones.
Measure what users feel:
- Connection and logon time, using Insights' time-to-connect metric
- Round-trip time and input delay
- Application launch, printing, and peripherals
- Audio/video, reconnect behavior, and help-desk workflows
Log defects by severity, define go/no-go criteria, and fix image, network, policy, or profile problems before widening the rollout.
Execute phased cutover and decommission Citrix
Move users in waves, with communications, training, support coverage, and a rollback path that keeps Citrix available until each wave is accepted. Revalidate critical workflows after every wave and keep evidence of tests, approvals, incidents, and exceptions.
Decommission only after you complete:
- User migration and app validation
- Profile confirmation and dependency closure
- Licensing review and backup verification
- Business sign-off
Then document the final environment in As-Builts and runbooks.
Common Migration Challenges and Best Practices
Application compatibility and legacy dependencies
An app that ran fine on Citrix can fail on AVD. Multi-session behavior, image composition, profile handling, authentication, printing, and network location all change under AVD. Windows Enterprise multi-session reports a different product type than client Windows, and Microsoft documents installer issues that require updated vendor versions.
Work through each dependency and assign every app one outcome:
- Remediate or replace
- Repackage or layer
- Move to dedicated hosts
- Defer to a later wave
Network performance and hybrid connectivity
Region choice, routing, latency to on-premises services, bandwidth, and internet egress all shape the experience. RDP Shortpath uses UDP and falls back to TCP when UDP is blocked. In one TechSogna assessment, every observed connection used TCP because Shortpath wasn't in use, which is a common miss.
Set baselines before cutover. Microsoft's 150 ms RTT recommendation is separate from input delay; Insights guidance targets under 100 ms.
Identity, security, and compliance
Moving desktops doesn't reproduce Citrix controls automatically. Review these controls end to end:
- Identity flows, privileged access, and MFA
- Conditional Access and endpoint compliance
- Defender, RBAC, and session restrictions
- Logging and incident response
For healthcare, federal, and financial environments, plan for:
- Evidence collection and administrative access reviews
- Hardened images and recovery testing
- Data location requirements
Platform scope isn't customer compliance. Microsoft lists AVD under FedRAMP High audit scope, but that doesn't authorize your configured system. Microsoft's BAA exists for HIPAA, but you still own your compliance program.
Cost management and performance consistency
Costs follow host sizing, concurrency, storage performance, uptime, and scaling schedules. Review utilization, idle capacity, storage, network charges, and logon performance on a recurring basis. Azure Advisor flags underused VMs and recommends reservations or savings plans, which carry 1- or 3-year commitments.
User adoption and operational ownership
Bring users and service-desk staff into discovery, pilots, and training. Then name owners for:
- Image updates and app packaging
- Profile support and security changes
- Monitoring and incident response
- Cost governance and documentation
How to Optimize and Operate AVD After Migration
Monitor and improve the user experience
AVD Insights uses Azure Monitor Agent and Log Analytics. Alerts are optional and configured separately, so configure them early. Track:
- Session-host health and utilization
- Logon performance and profile issues
- Connection quality and security events
Review results against your pilot acceptance criteria. Prioritize fixes by user impact, business criticality, security risk, and effort. Monitoring itself is billed by ingestion and retention.
Control costs through scaling and right-sizing
As real usage arrives, revisit:
- Host sizing and concurrency assumptions
- Autoscale schedules and session limits
- Storage tiers and licensing
Native autoscale supports power management in Azure and Azure Government, while dynamic autoscale is Azure only.
Cut capacity carefully. Savings that damage performance, availability, recovery, or compliance aren't savings. In one TechSogna sample, cold starts of up to five minutes showed how aggressive scale-down hurts users.
Document the platform and define ongoing support
Keep living documentation for:
- As-Builts, diagrams, and baselines
- Image versions, application owners, and profile settings
- Runbooks, recovery procedures, access reviews, and change records
For teams that want to stay in control, TechSogna offers business-hours co-management (Monday to Friday, 9 am to 6 pm CT) and Nerdio Manager expertise. You keep day-to-day control while TechSogna helps with operations, automation, documentation, security, and cost optimization.
Frequently Asked Questions
How do I migrate from Citrix to Azure Virtual Desktop?
Inventory Citrix, design identity and architecture, prepare apps and profiles, pilot with every persona, then migrate in waves. Validate each wave and decommission Citrix only after sign-off.
Can I use Citrix Cloud on Azure?
Yes, Citrix publishes its own DaaS offering for Azure, but that's a Citrix-managed model, not native AVD. Verify current Citrix licensing, architecture, and coexistence options before deciding.
What are the biggest challenges when migrating from Citrix to AVD?
Application compatibility, profile migration, identity and network dependencies, licensing, security controls, user adoption, and cost management. Most post-migration issues trace to profiles, images, sizing, or network settings.
Do I need to migrate Citrix user profiles to FSLogix?
Usually the target design is FSLogix, but it depends on your current profile solution and workload. Plan permissions, storage, exclusions, profile size, testing, and recovery.
How long does a Citrix to AVD migration take?
It depends on user count, applications, dependencies, identity readiness, compliance needs, pilot scope, and wave count. No reliable fixed duration exists without an assessment.
What happens to Citrix during the transition to AVD?
Run it in parallel through assessment and pilot. Migrate users in phases, set rollback criteria, and retire Citrix only after validation and business approval.
