Citrix to Azure Virtual Desktop Hybrid: A Practical Migration Route to Lower-Cost VDI

How to reuse an established Citrix image, onboard on-premises session hosts through Azure Arc and move users to Microsoft’s control plane without first relocating the workload to Azure.

Why Azure Virtual Desktop Hybrid changes the migration conversation

For years, organisations that wanted to leave Citrix faced an awkward choice: retain the existing on-premises platform or move session-host compute into Azure as part of the same programme. Azure Virtual Desktop Hybrid introduces a third route. The Azure Virtual Desktop control plane remains in Azure, while Windows session hosts continue to run on supported on-premises virtualisation or physical infrastructure and are connected to Azure through Azure Arc.
That separation is important. It allows a business to replace the Citrix brokering and access layer without forcing an immediate datacentre exit, application relocation or wholesale image rebuild.

As of 1 September 2026, Microsoft Azure Virtual Desktop Hybrid is generally available. The release moves the service beyond preview and establishes it as a supported production option for organisations that want Azure Virtual Desktop management while retaining session-host compute in their datacentre or at the edge. Microsoft’s announcement also positions Nutanix as the initial validated infrastructure platform for the GA release with more Hypervisors (VMware

The commercial proposition is equally significant. Azure Virtual Desktop Hybrid is priced at US$10 per user per month for the service licence, subject to the organisation also holding the appropriate operating-system or Remote Desktop Services user entitlement. That price can sit below entry-level Citrix licensing, creating a practical route to remove Citrix subscription cost as soon as migrated users are de-assigned and the relevant contract permits the licences to be reduced or terminated.

The target architecture

The GA architecture keeps the Azure Virtual Desktop brokering and management service in Azure while Windows desktops and applications run on Nutanix-hosted session hosts in the customer environment. Each host is onboarded as an Azure Arc-enabled server. The Azure Virtual Desktop Arc extension installs the AVD software and registers the machine with an Azure-hosted host pool. Microsoft Entra ID provides identity services, FSLogix can provide profile portability, and users connect through Windows App using the same client experience as an Azure-hosted AVD deployment.

Responsibility split

• Microsoft manages the Azure Virtual Desktop control plane in Azure.
• The customer manages the on-premises hypervisor, session hosts, operating system, networking and storage.
• Azure Arc provides the management bridge between the on-premises machines and Azure.
• The Azure Virtual Desktop Arc extension installs the AVD components and registers each host.
• Identity can use Active Directory Domain Services, hybrid join or supported Microsoft Entra ID scenarios, subject to operating-system requirements.

Migration approach: reuse the Citrix image safely

Reusing the existing Citrix master image can accelerate migration because the application set, hardening, dependencies and operational tooling are already understood. It should not, however, mean converting the live production image in place. Create a clone or new image branch, preserve the Citrix source for rollback and treat the AVD version as a separately governed artefact.

Step 1: assess and baseline the current Citrix workload

Inventory the operating system, application layers, Citrix Virtual Delivery Agent version, optimisation policies, profile solution, security agents, printing components, logon scripts, machine-creation method and network dependencies. Record logon duration, application launch time, CPU, memory, storage latency and concurrent-user density so the AVD pilot can be compared with a known baseline.

Step 2: clone and clean the Citrix image

1. Clone the approved Citrix master image or create a new image version; do not modify the only production copy.
2. Place the clone in maintenance mode and remove it from Citrix provisioning or machine catalogues.
3. Uninstall the Citrix Virtual Delivery Agent and every installed Citrix component that is not required by an application, including profile, WEM, HDX, browser, Teams optimisation and support components where present.
4. Remove Citrix-specific startup tasks, services, scheduled tasks, machine policies, firewall rules and monitoring agents after confirming they are no longer needed.
5. Reboot, verify that no Citrix VDA services or filter drivers remain, and check the application event log and device configuration.
6. Retain application prerequisites and security controls unless testing shows they conflict with AVD.

Step 3: prepare Azure and network prerequisites

Register the required Microsoft resource providers, assign least-privilege roles, create the Azure Virtual Desktop host pool, application group and workspace, and configure the host pool as a validation environment where the preview requirement still applies. Confirm that session hosts can resolve and reach all required Azure Virtual Desktop and Azure Arc endpoints through the firewall or proxy. Validate time synchronisation, certificates, DNS, identity join and Remote Desktop licensing requirements before onboarding hosts.

Step 4: Arc-enable the session-host image

Install the Azure Connected Machine agent on the cloned machine and connect it to the correct Azure subscription, resource group and region using the organisation’s approved onboarding method. Confirm that the machine appears as an Azure Arc-enabled server, that its agent status is healthy and that policy, proxy and extension operations work as expected.

Step 5: install the AVD components and register the host

For Azure Virtual Desktop Hybrid, deploy the Azure Virtual Desktop Arc extension to the Arc-enabled session host from Azure. Supply the target host pool and registration settings through the extension workflow. The extension installs the Azure Virtual Desktop Agent, Agent Bootloader, side-by-side stack and supporting components, then registers the machine with the selected host pool. This is the supported Hybrid onboarding path and should be used instead of manually installing the Agent and Bootloader unless Microsoft support guidance explicitly requires remediation.

After registration, confirm in the Azure portal that the host reports Available and that the AVD Agent and Bootloader services are healthy. Check the Azure Arc extension status, Windows event logs and AVD agent logs before assigning users. Do not seal or replicate an image while it contains a live host-pool registration. For a reusable image, remove existing AVD agent components and registration state, capture the clean image, and allow the Arc extension to create a fresh identity when each new session host is deployed.

Step 6: configure profiles, applications and user experience

Implement FSLogix profile containers or validate the existing profile strategy, ensuring users cannot mount the same writable profile simultaneously in Citrix and AVD. Reapply only the policies that are required for the AVD baseline, validate Microsoft Teams media optimisation, printing, application licensing, browser redirection, security controls and monitoring, and remove Citrix-specific optimisations that no longer apply.

Step 7: pilot, compare and remediate

• Select representative users across personas, locations, peripherals and critical applications.
• Compare sign-in time, application performance, session resilience, media quality and user density against the Citrix baseline.
• Test host drain mode, recovery, image rollback, profile recovery and loss of an Arc or network connection.
• Review Azure Arc and AVD extension logs, Windows event logs and monitoring data before approving production waves.

Step 8: migrate in waves and release Citrix cost

Move users by persona or application group, not simply by department. Give each wave a defined support period and rollback path. Once a cohort has met acceptance criteria, remove its Citrix assignments, reclaim concurrent or named-user entitlements where the agreement permits, and align subscription reductions with renewal or true-up dates. The saving is realised when licences and associated services are genuinely removed, not merely when users stop launching Citrix.

Step 9: decommission the Citrix control plane

1. Confirm that no production users, applications or automated processes depend on Citrix.
2. Export configuration and retain operational records for the agreed retention period.
3. Remove machine catalogues, delivery groups, StoreFront, Delivery Controllers, Cloud Connectors, Gateway or ADC services and supporting databases in a controlled sequence.
4. Remove DNS entries, certificates, firewall rules, service accounts and monitoring integrations that are no longer required.
5. Terminate or reduce Citrix subscriptions, support and hosting contracts in accordance with commercial notice periods.
6. Update the service catalogue, support model, disaster-recovery plan and configuration-management records.

Technical controls and common failure points

The migration is straightforward only when the image and dependencies are treated carefully. The most common risks are residual Citrix filter drivers or policies, blocked Azure Arc or AVD endpoints, stale host-pool registration captured in an image, unsupported operating-system or identity combinations, profile-container contention, incorrect Remote Desktop licensing for Windows Server and insufficient operational monitoring.
Consider:

• Use a cloned image and preserve the working Citrix image until migration acceptance is complete.
• Validate supported operating systems, identity join and licensing before building the host pool.
• Allow the documented Azure Virtual Desktop and Azure Arc network endpoints through firewalls and proxies.
• Use the AVD Arc extension for Hybrid onboarding and monitor extension health and logs.
• Prevent simultaneous writable profile access from Citrix and AVD.
• Test application licensing, printing, peripherals, media optimisation and security tooling.
• Define rollback at image, host and user-wave level.
• Use the GA service terms, supported Nutanix platform guidance and current Microsoft support boundaries as production design inputs.

Implementation note: capture screenshots during the migration of the Citrix Programs and Features inventory, the healthy Azure Arc server record, the successful AVD Arc extension deployment, the host-pool session-host status and the pilot user’s Windows App resource feed. These images provide an auditable build record and make the runbook easier for operations teams to repeat.

Final thoughts

Azure Virtual Desktop Hybrid provides a pragmatic bridge between an established on-premises VDI estate and Microsoft’s cloud-managed desktop service. Its real value is not that it makes migration effortless, but that it separates the broker transition from the infrastructure transition. Organisations can modernise the access and management plane first, then decide when—or whether to move the underlying compute.

Reusing a proven Citrix image can shorten the route to value, provided it is cloned, stripped of Citrix VDA components, validated and onboarded through Azure Arc and the AVD Arc extension. The technical work must be paired with profile, networking, identity, licensing, support and rollback design.

For organisations with suitable workloads and commercial terms, this model can create an earlier exit from Citrix licensing while preserving existing datacentre investments. The strongest programmes make that saving measurable, cohort by cohort, and do not declare success until the Citrix entitlement and supporting infrastructure have genuinely been retired.

The opportunity is not simply to replace one broker with another. It is to reduce platform duplication, retain control of the hosting location and modernise the service at a pace the business can absorb.