Azure Virtual Desktop vs Citrix: architecture, performance and costs

AVD or Citrix: start with the workload

A cheaper virtual desktop is not a saving if it slows down the business application or breaks an essential printer. The right platform depends on concurrent users, data proximity, peripherals and your team's ability to operate it.

This guide compares Azure Virtual Desktop in Azure, Citrix DaaS and self-managed Citrix Virtual Apps and Desktops (CVAD). It also distinguishes AVD for Azure Local from AVD Hybrid: keeping machines in your datacenter does not make the control plane independent of the cloud. The recommendations and simulated budget are a decision framework, not a benchmark or commercial quote.

Compare three control-plane models

AVD publishes resources through host pools, application groups and workspaces, supporting personal desktops, shared pools and RemoteApp. You do not install the AVD broker.

Citrix DaaS organizes resources into catalogs and Delivery Groups. A traditional Cloud Connector design needs redundancy in each resource location; Citrix recommends at least two connectors. HDX traffic does not necessarily traverse them: its path depends on Gateway, Rendezvous and selected connectivity options.

CVAD leaves more components under your control. Include the site, logging and monitoring SQL databases, controllers and StoreFront access in the operating plan. A VDA runs on the machines delivering Citrix sessions.

• Microsoft — AVD overview ↗
• Citrix — DaaS architecture ↗
• Citrix — CVAD components ↗

What if applications must remain on premises?

AVD for Azure Local and AVD Hybrid are different offerings. AVD Hybrid registers local session hosts through Azure Arc. Its documentation excludes Windows Enterprise multi-session, autoscale, power management and Start VM on Connect. Do not copy an Azure-hosted AVD estimate into this design.

Citrix is worth evaluating when a common toolset must manage several compatible hosting environments. Supported hypervisors and features depend on release and provisioning method. Selecting the hypervisor and selecting the desktop delivery platform are separate decisions.

Citrix can also provide the delivery layer for Azure resources with appropriate Microsoft entitlements. AVD versus Citrix is not always an either/or choice: identify what Citrix adds and price that layer.

• Microsoft — AVD Hybrid limitations ↗
• Microsoft — Azure, Azure Local and Hybrid models ↗
• Compare platforms for leaving VMware →

A sizing questionnaire before requesting quotes

Do not treat 100 accounts as 100 active sessions, or 100 sessions as 100 VMs. Measure each user group. A density that works for a light application may fail with heavy browser use, Teams and design software.

• How many named and concurrent users, including peaks? What are the working hours, time zones and on-call requirements?
• Full desktops or selected apps? Shared sessions or persistent personal machines? Which applications cannot support multiple users?
• Where are SQL, files and application services? Measure session-host-to-backend latency, not just endpoint-to-desktop latency.
• Which displays, resolutions, GPUs, scanners, printers, smart cards, cameras and headsets must work?
• How large are profiles, Outlook caches and OneDrive data? What growth and morning logon load are expected?
• What recovery targets, data residency constraints and fallback access paths apply?
• Which licenses are already paid for? Who supports users, images, storage and after-hours incidents?

HDX and RDP Shortpath: measure the real experience

AVD starts through TCP reverse connect and can switch to UDP using RDP Shortpath. Public-network connectivity can use STUN or TURN relay, with TCP fallback when UDP fails. A private Shortpath listener normally uses UDP 3390 and needs a narrowly scoped network rule.

Citrix Adaptive Transport prefers EDT and can fall back to TCP. HDX encompasses more than transport: channels, redirection and the client also matter. The comparison is not simply fast HDX versus slow RDP.

Run identical tasks from the office, home and a degraded link: logon, application switching, typing, scrolling, conferencing and printing. Record the negotiated transport. Do not assume the native and browser clients behave identically.

For Teams, media and specialized devices, validate the exact client/OS/agent support matrix and available optimizations. No protocol fixes a distant database or an overloaded session host.

• Microsoft — RDP Shortpath network requirements ↗
• Citrix — Adaptive Transport and EDT ↗

FSLogix and profiles: storage is on the critical path

FSLogix stores a profile in a VHD/VHDX container. It is not exclusive to AVD and can be used with Citrix when properly licensed. Profile Container normally includes Office data; a separate ODFC container needs a specific reason.

Citrix Profile Management is another option. Do not configure two engines to manage the same data without deliberate exclusions and design.

Measure concurrent logons, container attachment time, SMB latency and free capacity. Check share and NTFS permissions, authentication and storage Kerberos compatibility. An Entra-joined host does not automatically guarantee share access.

Plan to recover a corrupted profile and restore user data. Cloud Cache is not a backup. During migration, do not blindly reuse a profile across different Windows versions or platforms.

• Microsoft — FSLogix containers and coexistence ↗
• Microsoft — identity and profile prerequisites ↗
• Audit Kerberos and RC4 dependencies →

Image management with a usable rollback

AVD custom image templates use Azure Image Builder, while Azure Compute Gallery stores and distributes image versions. Citrix Machine Creation Services (MCS) provisions machines from an image. Citrix Provisioning is another technology with its own streaming and cache dependencies.

Build a reproducible sequence: base image, applications, patches, security configuration, tests and pilot promotion. Keep the previous version and publishing configuration.

Do not transfer image preparation steps blindly between tools: Citrix specifically says not to run Sysprep on MCS master images. Let sessions finish before replacing a host.

Reverting an image does not undo an application change to a user's profile. Rollback must include data and compatibility. Create separate image variants only for genuinely different requirements.

• Microsoft — building AVD images ↗
• Citrix — catalogs and MCS image preparation ↗

Autoscaling without sacrificing availability

AVD in Azure provides scaling plans. Citrix Autoscale combines schedule- and load-based decisions. Validate supported pool/catalog types, power-management permissions and available features for the chosen architecture.

Our approach is to prewarm capacity, keep a reserve, stop assigning new sessions to retiring hosts and decide how disconnected sessions will be handled. Forced logoff requires advance communication and business approval.

Avoid two systems controlling power for the same VMs. Test unexpected peaks and machine startup time. Deallocating an Azure VM can reduce compute cost, but disks and other services may remain billable.

On-premises power management does not automatically produce cloud-style savings: hardware, support and some licensing costs remain committed. AVD Hybrid does not provide Azure AVD's power-management functions.

• Microsoft — configure scaling plans ↗
• Citrix — Autoscale ↗

Security and availability: assign every responsibility

A managed control plane does not manage your backups, application or image. Document failures of a host, profile share, identity service, network link and region.

AVD needs recovery arrangements for customer-managed resources. CVAD also needs protection for controllers, SQL and entry points. Citrix DaaS Local Host Cache can preserve certain brokering capabilities during control-plane connectivity loss, subject to conditions; it is not a general offline guarantee.

Use phishing-resistant MFA where the authentication path supports it, tested Conditional Access, least administrative privilege and separate accounts. Restrict clipboard, drive, printing and USB redirection according to business needs. Keep management ports off the public internet.

With a standard user, test publishing permissions, redirection and expected denial cases. Alert on logon failures, temporary profiles, unregistered machines and capacity pressure. Base RPO/RTO on a recovery exercise, not just a provider SLA.

• Microsoft — AVD disaster recovery ↗
• Citrix — Local Host Cache limitations ↗
• Secure Microsoft 365 administrative workstations →

Licensing: separate access rights from infrastructure

For internal AVD access to Windows Enterprise, eligible Microsoft 365 or Windows subscriptions may already provide access rights; documented options include Microsoft 365 Business Premium and E3/E5. Compute, storage, networking and every application are not thereby free.

Windows Server requires appropriate RDS rights. External users and on-premises variants have separate terms. Check FSLogix eligibility, Microsoft 365 Apps shared activation, business software and GPU licensing too.

Citrix adds its subscription contract. Request the exact SKU, applicable user/device or concurrency metric, minimum purchase, hybrid rights, included features and renewal terms. Concurrent sessions are not necessarily the number of licenses you must buy.

For CVAD, also check License Activation Service compatibility. Citrix sets April 15, 2026 as the end of its legacy file-based licensing system. Local hosting therefore does not automatically remove cloud activation dependencies.

• Microsoft — access rights and infrastructure costs ↗
• Citrix — migration and LAS compatibility ↗

Cost comparison: a transparent 100-user example

This is an illustrative simulation in Canadian dollars before tax, not published Azure or Citrix rates. Replace every assumption with calculator output or a quote. Assume 100 users, 60 concurrent sessions and six 8-vCPU/32-GiB hosts. Ten sessions per host is a pilot target, not guaranteed capacity.

At an assumed 260 billed hours per host each month and a hypothetical compute rate of $0.60/hour, the six hosts cost $936/month. At 730 hours, that becomes $2,628: a $1,692 difference before costs that continue while machines are off. This topology is not N+1; add the reserve validated by testing.

• Using L = $25/user/month purely as a sensitivity assumption produces $4,636 for DaaS and $5,000 for CVAD. This is not an estimate of Citrix's commercial price.
• Add missing Microsoft licenses, GPUs, spare capacity, support, migration, private networking and outbound traffic where needed. The local figures are not Azure prices.
• Include IT labor: for example, 12 hours/month at $100/hour adds $1,200. Measure each platform's effort rather than assuming CVAD and AVD take the same time.
• Compare like-for-like over three years, including renewals, commitments, replacement hardware and exit costs. Reserve only stable capacity; unused commitments can offset autoscale savings.

• Microsoft — cost components and billing models ↗
• Azure calculator — replace assumptions with your region and contract ↗

PowerShell: a read-only AVD inventory

Use an administrative workstation with Az.Accounts and Az.DesktopVirtualization, authenticate and explicitly select the subscription. Reader at the relevant scope permits this resource inventory; it does not change host pools. The local CSV exposes infrastructure names and needs protected storage.

This records configuration, not billed usage or proven session density. Add Azure Monitor/AVD Insights measurements; use Citrix Monitor or Director for the corresponding test protocol.

Connect-AzAccount
Set-AzContext -SubscriptionId '<subscription-id>'
$ErrorActionPreference = 'Stop'
$rg = 'rg-avd-production'
Get-AzWvdHostPool -ResourceGroupName $rg |
    Select-Object Name, Location, HostPoolType,
        LoadBalancerType, MaxSessionLimit |
    Export-Csv -Path './avd-host-pools.csv' -NoTypeInformation -Encoding utf8

• Microsoft — Get-AzWvdHostPool ↗

A reusable pilot and migration decision checklist

Example weighting to adapt: compatibility 30%, experience 25%, operations 20%, cost 15%, recovery 10%. Failure of a critical application should disqualify an option even if its weighted score is high.

• 1. Select 10–15 representative users and document critical tasks. This is an example pilot size, not a universal rule.
• 2. Capture today's baseline: median/p95 logon time, incidents, printer/scanner success, conferencing and business task duration.
• 3. Build comparable test groups with the same data locality, applications, resources and profile policy. Document differences you cannot remove.
• 4. Test morning load, host failure, storage loss, reconnect and recovery. Verify spare capacity actually starts.
• 5. Measure monthly cost per user and concurrent user, IT labor and satisfaction. Set acceptance criteria before seeing results.
• 6. Move one group at a time, temporarily retain the old access path and document rollback. Avoid simultaneous writes to the same profile.
• 7. Retire the old platform only after business acceptance, backup validation and support handover.

Which platform should you pilot first?

My recommendation: do not migrate merely to remove a license line. Require every candidate to prove that it runs business tasks, recovers from failure and can be supported by your team. The best cost belongs to a service that remains usable and sustainable.

Frequently asked questions

Does AVD always replace Citrix? No. Compare applications, peripherals, operational tools, hosting constraints and measured experience.

Does Citrix DaaS remove every management server? No. Citrix operates the control plane, while resources and architecture-specific dependencies remain your responsibility.

Is FSLogix mandatory everywhere? No. It is a profile-management choice requiring design and licensing, not a substitute for resilient storage.

Can I reuse an online Citrix or AVD quote? Only as a starting point. Concurrency, existing entitlements, contract, region and included features must align for a valid comparison.