Two renewal conversations landed on our desk inside the same week this spring: a regional bank three years into a Citrix XenDesktop estate, and a 6,000-seat manufacturer that had never run VDI at all and wanted to skip straight to Azure Virtual Desktop. Both asked the procurement question in almost the same words — just tell us which one to buy — and both got the same answer, which is that the question as asked is malformed.
We've operated multi-tenant VDI across Citrix XenDesktop, RDS, AVD, and VMware vSphere side by side, at more than 10,000 concurrent users and 99.95 percent availability across that combined footprint, so this isn't a brand preference talking. Azure Virtual Desktop is ten months past its rename from Windows Virtual Desktop, Citrix has just relabeled its cloud control plane Citrix DaaS, and neither cosmetic change moved the actual decision drivers: endpoint diversity, peripheral redirection, WAN quality, and what you already own versus what you'd be buying new.
What did move enough to update our default recommendation this year is FSLogix licensing, Windows 11 Enterprise multi-session landing in the AVD gallery, and Nerdio maturing into a tool we stop fighting. What follows is the actual matrix we've been drawing on a whiteboard in scoping calls this month — not a repaint of a vendor comparison slide.
What still tips toward Citrix DaaS
Three things keep a Citrix estate defensible in 2022, and none of them are branding. First, HDX's adaptive transport still handles a bad WAN link better than AVD's RDP-based stack, full stop — a branch office on a congested MPLS circuit or a user tethered to a phone hotspot notices the difference within the first session. Second, peripheral redirection: the regional bank runs teller check scanners, signature pads, and receipt printers at every branch, and Citrix's USB and print-driver mapping handles that hardware list with far fewer support tickets than RDP redirection does. We tried moving one branch to AVD in a proof-of-concept last quarter and gave up after the second scanner driver fight. Third, Citrix Cloud brokers across resource locations that are not Azure — on-prem hypervisors, other clouds, whatever the bank's data center still runs — which matters a great deal if your VDI estate straddles a migration that will take years, not months. AVD is Azure-only, by design.
There's a fourth, quieter reason: thin client and endpoint breadth. A manufacturing floor running older locked-down thin client OS images often has a certified Citrix Workspace app and nothing else. That's not a technology limitation so much as a procurement one — someone bought those endpoints in 2016 and isn't replacing them to accommodate a broker decision.
Where AVD stopped being the compromise choice
The manufacturer's answer was AVD, and the reasoning held up under questioning. Their persona is office and light engineering workstations on a managed corporate network or a reasonable home connection — not a bad-WAN branch, not a peripheral-heavy teller line. For that persona, Windows 11 Enterprise multi-session (now shipping in the AVD gallery alongside Windows 10 multi-session images) gives real density economics: more users per session host VM than a single-session build, which drops the compute line directly.
The bigger shift is entitlement alignment. Most of this client's users already carry Microsoft 365 E3 licensing, which includes the Windows virtual desktop access rights AVD needs. There is no separate per-user AVD subscription to negotiate — the incremental cost is Azure infrastructure and management tooling, not a second desktop-virtualization line item stacked on licensing you already pay for. Session hosts join Azure AD directly, so Conditional Access and the Defender for Endpoint rollout already in flight apply without a parallel on-prem AD trust to maintain. For a shop this size standing up VDI for the first time, that's the whole pitch: fewer moving parts, not a superior remoting protocol.
The FSLogix layer nobody gets to skip
This is the part procurement conversations tend to skate past: FSLogix is not a point in either column. It's shared substrate. Whether the broker is Citrix or AVD, user profiles still need a profile container, the container still needs a storage backend sized for login-storm IOPS, and the license question — now moot, since FSLogix ships free with a Microsoft 365, Windows, or RDS CAL-with-Software-Assurance entitlement — doesn't change any of that engineering.
We learned this the expensive way on the manufacturer's pilot. The initial build pointed FSLogix VHDLocations at a standard-tier Azure Files share sized for the wrong metric, and the first Monday shift-change login storm produced call-center-worthy hold times before anyone touched a support ticket. The fix wasn't cleverness, it was throughput:
# FSLogix profile container settings, applied via GPO-backed registry keys
# HKLM\Software\FSLogix\Profiles
Set-ItemProperty -Path "HKLM:\Software\FSLogix\Profiles" -Name "Enabled" -Value 1
Set-ItemProperty -Path "HKLM:\Software\FSLogix\Profiles" -Name "VHDLocations" -Value "\\storageaccount.file.core.windows.net\profiles"
Set-ItemProperty -Path "HKLM:\Software\FSLogix\Profiles" -Name "SizeInMBs" -Value 30000
Set-ItemProperty -Path "HKLM:\Software\FSLogix\Profiles" -Name "IsDynamic" -Value 1
Set-ItemProperty -Path "HKLM:\Software\FSLogix\Profiles" -Name "VolumeType" -Value "vhdx"
Same registry keys regardless of whether the session host is brokered by Citrix or AVD. Move to Azure Files premium tier, or Azure NetApp Files if the concurrent-login math demands more throughput than premium file shares deliver comfortably, and the storm stops being newsworthy. Budget this as its own line, separately from the broker decision, because it is one.
The cost delta procurement never draws correctly
Sticker-price comparisons miss the shape of the two cost structures entirely. AVD's incremental cost is infrastructure consumption — compute, storage, networking — layered on an entitlement you likely already own. Citrix DaaS's incremental cost is that same infrastructure consumption plus a per-user or per-device subscription stacked on top, which also happens to buy a materially more finished management and autoscale plane out of the box.
Our Azure consolidation work across other engagements has averaged roughly a 35 percent reduction in infrastructure cost, and the desktop-virtualization line often follows the same arc when the entitlement math lines up — because you stop paying twice for the same seat. But that arithmetic only holds if you count the labor. AVD's lower licensing line hides an assembly cost: someone has to build the landing zone — host pools, application groups, workspaces, image pipeline, scaling plans — that Citrix Cloud mostly hands you configured. Either you pay that in internal engineering hours, or you pay a chunk of the licensing saving straight back out to a tool like Nerdio to buy the labor back. Compare these over a three-year term including headcount time, not a first-month Azure Cost Management export, or you'll present a number to the CFO that quietly reverses itself in year two.
The management maturity gap, and why we still buy Nerdio
Citrix Studio and Director are a decade-plus into maturing a single operational pane: session shadowing, historical performance trending, delivery-group autoscale, all in one console a helpdesk tier-one can be trained against in a day. AVD's native tooling in the Azure Portal is still assembled from parts — host pool blade, a separate Insights workbook backed by Log Analytics, scaling plans that in our field experience are still rough enough around the edges that we don't trust them unattended for cost control on their own. Most of our AVD clients end up running Nerdio Manager for the autoscale tuning, image versioning, and cost reporting that Citrix bundles natively.
There's a small, honest joke buried in the tooling that's worth knowing before you're in a scoping call: ten months after Microsoft renamed the product from Windows Virtual Desktop to Azure Virtual Desktop, the PowerShell module still hasn't gotten the memo.
Get-Command -Module Az.DesktopVirtualization | Select-Object Name -First 8
# Name
# ----
# New-AzWvdHostPool
# Get-AzWvdHostPool
# New-AzWvdApplicationGroup
# Get-AzWvdSessionHost
# New-AzWvdWorkspace
# Remove-AzWvdSessionHost
# Update-AzWvdHostPool
# Get-AzWvdRegistrationInfo
Every cmdlet still carries the old Wvd naming. Harmless, but it's a fair proxy for how much of the "new" platform is genuinely new versus relabeled — worth remembering when a vendor deck implies AVD is a from-scratch product rather than an evolution of what shipped in 2019.
The decision matrix we hand to procurement
Here's the sheet itself, stripped of vendor branding on either side:
| Factor | Favors AVD | Favors Citrix DaaS |
|---|---|---|
| Endpoint fleet is modern, managed Windows/Mac on decent WAN | Yes, by default | Only if other rows override |
| Branch offices on congested or unreliable WAN links | Adequate for light use | Adaptive transport still wins |
| Heavy USB/peripheral redirection (scanners, signature pads, card readers) | Workable, more support tickets | Materially more mature |
| Print-heavy vertical (finance, healthcare, manufacturing labels) | RDP redirection or Universal Print | Universal Print Driver, fewer exceptions |
| Estate spans Azure plus on-prem or another cloud | Not supported — Azure only | Native across resource locations |
| Existing Citrix ELA, trained staff, sunk automation | Migration cost usually not justified | Stay and modernize instead |
| Users already covered by Microsoft 365 E3/E5 or Windows VDA rights | No incremental per-user license | Subscription stacks on top regardless |
| In-house Azure/IaC engineering capacity to build the landing zone | Lowers total cost meaningfully | Less of this needed day one |
| Need a fully built management console without a third-party add-on | Plan on Nerdio or equivalent | Studio/Director included |
Treat this as the start of a conversation, not an RFP scoring rubric. Assign an actual number or a named owner to each row that applies to your estate — a checkmark isn't a decision, it's a placeholder for one. The bank and the manufacturer scored this same sheet and landed on opposite answers, and both were correct, because the rows that mattered were different rows.
If you're facing this
If procurement is asking you to pick a single winner between AVD and Citrix DaaS before anyone has listed the peripherals, the branch WAN circuits, or what's already sitting in your Microsoft 365 entitlement, that's the conversation to have first. We're glad to work through your specific mix against a sheet like this one — bring the endpoint inventory and the renewal date, not just the quadrant screenshot.