Many organizations still rely on Remote Desktop Services (RDS) or Citrix for virtual desktop infrastructure. However, with the rise of cloud-first strategies, Azure Virtual Desktop (AVD) has emerged as a powerful solution for scalability, integrated security, Microsoft 365 optimization, and simplified management. This guide offers a detailed, step-by-step approach to migrate from RDS or Citrix to Azure Virtual Desktop, covering assessments, landing zone design, storage strategies, automation tools, and profile/application management best practices.

1. Conduct a Thorough Environment Assessment

A robust upfront assessment reduces surprises and lays the groundwork for a successful move to Azure Virtual Desktop.

1.1 Infrastructure & Network Inventory

• Servers & Roles: Document current RDS/Citrix server roles, OS versions, and hardware specs.
• Network Topology: Map WAN/LAN connections, including latency between data centers or remote offices.
• Identity Services: Determine whether you’ll leverage a hybrid approach (on-prem AD + Azure AD Connect) or a cloud-only model.

1.2 User & Workload Profiling

• User Personas: Identify power users requiring GPU or high compute vs. standard users.
• Application Landscape: Catalog all apps, including resource-intensive (CAD/CAM, media) and line-of-business tools.
• Profile Data: Examine average profile sizes, considering large files or cached mailboxes that might affect storage performance.

1.3 Licensing & Cost Analysis

• Microsoft 365 Entitlements: Check if Windows 10/11 multi-session rights are already included.
• Third-Party Licensing: Verify specialized apps’ EULAs for multi-session or virtual usage.
• Cloud Cost Model: Project potential monthly costs for VMs, storage, and egress; consider autoscaling and reserved instances for savings.

1.4 Security & Compliance Planning

• Regulations: Identify GDPR, HIPAA, or PCI-DSS mandates and choose Azure regions accordingly.
• Security Posture: Map existing MFA, antivirus, intrusion detection to Azure Security Center or Microsoft Defender for Cloud.
• Risk & DR: Outline threats (e.g., ransomware) and plan backup/failover strategies aligned with Azure’s redundancy features.

1.5 Project Scope & Timelines

• Stakeholder Engagement: Involve IT ops, security, finance, HR.
• Resource Availability: Ensure your team or partner can handle Azure planning and deployment.
• Success Criteria: Define measurable goals (e.g., cutting login times to <30s, reducing hardware spend by 30%).

Pro Tip:
Start with a mini pilot assessment for a handful of workloads to validate app compatibility and resource assumptions before the larger migration.

2. Design an Enterprise-Ready Azure Landing Zone

Leverage Microsoft’s Azure Virtual Desktop Landing Zone Guide for best practices. A well-structured landing zone ensures you won’t need to re-architect your environment as Azure usage grows.

2.1 Core Landing Zone Components

• Subscription Strategy: Separate production, non-production, or shared services.
• Network Topology: Adopt a hub-and-spoke or virtual WAN model for efficient connectivity.
• Identity & Governance: Implement Azure AD (or hybrid AD), role-based access control (RBAC), and Azure Policy.
• Monitoring & Management: Set up Azure Monitor and Log Analytics for real-time insights. Optionally add Azure Sentinel for advanced threat detection.

2.2 Baseline vs. Enterprise-Scale

• Baseline: Simpler approach for small-to-medium environments.
• Enterprise-Scale: Multi-subscription, layered management groups, advanced governance for larger or global organizations.

Why It Matters:
A robust landing zone design ensures consistent network security, identity controls, and compliance across all Azure Virtual Desktop host pools.

3. Storage Design & Recommendations 

Optimal storage is essential for FSLogix profiles, applications, and logs, ensuring reliability and performance in AVD.

3.1 Storage Services Overview

1. Azure Files (Premium)
   • Balances performance and cost for FSLogix profile containers.
   • Supports SMB with AD integration.
   • Options for locally redundant (LRS) or geo-redundant (GRS/ZRS) replication.
2. Azure NetApp Files
   • Offers low-latency file shares for high-I/O or GPU-heavy workloads (CAD, media).
   • Capacity pools and flexible performance tiers.
3. Blob Storage
   • Ideal for large unstructured data, logs, or backups.
   • Use lifecycle management to archive older logs and control spending.

3.2 Performance & HA Tips

• Premium Tiers: Provide higher IOPS and lower latency.
• Replication Options: Choose zone-redundant or geo-redundant if multi-region DR is mandatory.
• SMB Multichannel: Enables multi-path communication for better throughput in certain AVD scenarios.

3.3 Cost & Governance Controls

• Autoscaling & Alerts: Track usage to prevent storage overflows or unexpected bills.
• Azure Policy: Enforce encryption, region limits, or minimum SKU standards.
• Capacity Planning: Calculate concurrency and average profile sizes to avoid under/over-provisioning.

Storage Best Practice:
Run a small-scale pilot measuring real-world IOPS and user load on your chosen tier (Azure Files Premium or NetApp Files) before the full rollout.

4. Executing the Migration

Once assessment, landing zone, and storage are finalized, you can begin migrating from RDS or Citrix to Azure Virtual Desktop in two phases.

4.1 Phase 1: Pilot Migration

1. Pilot Host Pool Setup
   • Deploy minimal Windows 10/11 multisession VMs (ARM/Bicep/Terraform).
   • Integrate Azure Files or NetApp shares for FSLogix profile containers.
2. Application Testing
   • Move a small set of apps (Office 365, key LOB applications) and measure performance.
   • Collect user feedback on latency, login times, and app responsiveness.
   • Optional: Test MSIX App Attach with one or two pilot apps.
3. Profile Migration
   • Shift user profiles to Azure Files Premium or NetApp, verifying data consistency and acceptable login times.
4. Parallel Environments
   • Keep RDS/Citrix running so pilot users can revert if unexpected issues arise.

4.2 Phase 2: Full Rollout

1. Scaling Host Pools & Automation
   • Expand from pilot to entire departments or additional regions.
   • Use Azure DevOps pipelines, Terraform, or Nerdio to standardize deployments.
2. Complete Profile & App Migration
   • Migrate remaining user profiles.
   • Convert additional apps to MSIX if beneficial.
   • Gradually decommission old infrastructure.
3. Network Optimization
   • Deploy region-specific host pools for global users.
   • Implement load balancing and DNS routing for efficient distribution.
4. Security & Governance
   • Enforce Azure Policy (e.g., encryption-at-rest, region usage).
   • Require Conditional Access with MFA for remote sessions.

Rollout Best Practice:
Provide user training and a strong helpdesk channel to address any transition pains.

5. Ongoing Management & Optimization

5.1 Monitoring & Alerting

• Azure Monitor & Log Analytics: Track CPU, memory, disk I/O, network metrics.
• Azure Sentinel: Add if you require advanced security analytics and threat automation.

5.2 Autoscaling & Scheduling

• Host Pool Autoscaling: Shut down idle VMs after hours; scale up for peak times.
• Cost Management: Use Azure Advisor to identify potential savings via VM size recommendations or reserved instances.

5.3 Governance & Lifecycle

• Azure Policy & RBAC: Maintain compliance for encryption, resource locations, and admin privileges.
• App & OS Updates: Deploy new OS images or MSIX app versions without re-imaging entire VMs.
• User Feedback Loop: Continuously gather suggestions for performance tuning or new features.

Addressing Common Pitfalls

1. Network Egress Costs
   • Solution: Monitor bandwidth usage, especially if hosting in multiple regions.
2. Neglecting Multi-Session Licensing
   • Solution: Verify EULAs for each app to ensure compliance in multi-session VMs.
3. Insufficient Storage Tests
   • Solution: Pilot real user loads on Azure Files/NetApp to confirm throughput and IOPS.
4. Inadequate End-User Training
   • Solution: Publish quick start guides, hold training sessions, and staff a prepared helpdesk.
5. Weak Governance
   • Solution: Embrace a layered approach with Azure Policy, RBAC, and cost alerting to sustain enterprise standards.

FAQ: Migrate from RDS or Citrix to Azure Virtual Desktop

1. How Long Does the Migration Take?
   • Smaller deployments can be done in a few weeks; larger, global projects may require months of phased rollouts.
2. Do I Still Need RDS CALs?
   • If you’re using Microsoft 365 entitlements for Windows 10/11 multi-session, you may reduce or eliminate traditional RDS CAL requirements.
3. What if I Have GPU-Intensive Workloads?
   • Use NV-series or other GPU-enabled VM sizes for tasks like CAD, 3D modeling, or media editing.
4. How Does MSIX App Attach Help?
   • It streamlines app deployment by dynamically attaching or detaching apps without updating the base image.
5. Which Automation Tools Are Best?
   • Azure-native (ARM/Bicep, Azure DevOps), third-party tools like Terraform, or specialized solutions like Nerdio all integrate well with AVD.

Real-World Results of Azure Virtual Desktop Migration

• Reduced Maintenance & Hardware Costs
  • Retire on-prem servers and cut data center overhead.
• Global Scalability
  • Provide consistent Windows experiences worldwide with region-specific host pools.
• Efficient App Deployment
  • Packaged apps using MSIX can be shared across multiple host pools instantly.
• Enhanced Security & Compliance
  • Centralize user identity with Azure AD and enforce advanced policies like MFA.

Key Takeaways: Migrate from RDS or Citrix to Azure Virtual Desktop

1. Comprehensive Assessment – Pinpoint infrastructure, user personas, and licensing for a seamless transition.
2. Well-Designed Landing Zone – Follow proven Azure patterns for identity, networking, and governance.
3. Optimized Storage Plan – Evaluate Azure Files Premium vs. NetApp Files, plus replication tiers and capacity.
4. Phased Migration & Automation – Pilot first, then scale systematically using IaC tools for consistency.
5. Continuous Improvement – Leverage Azure Monitor, cost analytics, and user feedback to keep refining your AVD environment.

Ready to Migrate from RDS or Citrix to Azure Virtual Desktop?

By combining thorough assessments, a robust landing zone, and a well-defined storage strategy before rollout, you’ll pave the way for a high-performance virtual desktop environment. Whether you’re aiming to cut hardware costs, improve user experience, or boost security and compliance, Azure Virtual Desktop can deliver real, measurable gains.

How We Can Help

• In-Depth Assessments – Map out your infrastructure, licenses, and user needs to ensure a smooth AVD deployment.
• Landing Zone & Governance – Implement baseline or enterprise-scale topologies with Azure Policy and RBAC.
• Profile & Application Migration – Use FSLogix and MSIX App Attach for seamless user data and app delivery.
• Ongoing Support & Optimization – Get continuous performance tuning, cost management, and security reviews.

Contact us today to discover how a well-structured migration to Azure Virtual Desktop can modernize your remote work strategy—enhancing scalability, security, and overall user satisfaction.