Citrix vs Parallels RAS vs Azure Virtual Desktop: what to move to

Nobody arrives at this comparison casually. It is almost always prompted by a renewal quote that came back at a number nobody budgeted for, with about ninety days to decide.

In short: Citrix remains the strongest option for very large estates, difficult network conditions and graphics-heavy work, and is increasingly hard to justify below that. Parallels RAS is the better fit for on-premises and hybrid estates publishing applications, licensed by concurrent user rather than named user, with load balancing, gateway and multi-tenancy in the one product. Native Azure Virtual Desktop and Windows 365 is the better fit where the estate is already Microsoft-centric and people need desktops rather than published applications, with EtherInsights at £0.79 per licensed user per month supplying the cost, posture and day-two management layer that Citrix used to bundle.

Why the question is being asked at all

Citrix has not become a worse product. It has become a differently priced one.

Under Cloud Software Group, licensing moved from à la carte to bundled subscriptions, minimum seat commitments arrived, and renewal quotes have come back substantially higher, in some cases at roughly double, usually with about ninety days of notice. Components that an estate does not use turn up in the bundle, and the seat floor frequently sits above real headcount.

For a large organisation using most of the platform, that can still be the right buy. For a business of a few hundred seats that adopted Citrix when it was the only credible option, and now publishes a dozen applications to a workforce that is partly part-time, it means paying enterprise pricing for a fraction of the product.

Parallels RAS: the on-premises and hybrid answer

RAS publishes applications and desktops from RDSH, VDI or Azure Virtual Desktop, and brokers across VMware ESXi, Hyper-V, Nutanix and Scale as well as Azure and AWS. That breadth is the point: it meets an estate where it currently is, rather than requiring it to move first.

Two things decide most cases.

Concurrent-user licensing. RAS bills the maximum number of simultaneous connections, not the number of people with accounts. Where a workforce is shift-based, part-time, seasonal, or working from shared devices on a clinical or factory floor, peak concurrency sits well below headcount and the gap is the saving. Where everybody works full time and connects all day, it saves very little, and that is worth establishing in an hour rather than assuming for a quarter.

One product rather than editions. HALB load balancing, the secure gateway, multi-tenancy, FSLogix profile container support, MSIX app attach and App-V integration, and clients for Windows, macOS, Linux, iOS, Android and the browser are all in the single product rather than distributed across tiers.

The honest limits are real. HDX is ahead over poor networks and for graphics-heavy work. At many thousands of seats with deep ecosystem integration, replacement is a programme rather than a swap. And Citrix App Layering has no exact equivalent, so where that is genuinely in use it can decide the answer by itself.

Native AVD and Windows 365: the Microsoft-centric answer

If the applications are modern, the estate is already Microsoft-centric, and what people need is a desktop rather than finely controlled published applications, the simplest answer is usually no third-party broker at all.

Azure Virtual Desktop is metered Azure consumption, which suits variable and elastic usage. Windows 365 is a fixed per-user subscription, which suits predictable full-time users and removes the sizing exercise entirely. Our AVD vs Windows 365 vs traditional desktops guide covers choosing between those two in detail.

One vendor instead of two is a genuine advantage, and we say so as a company that sells the broker as well.

The management layer nobody prices in

Here is the part that catches estates out, and it is the strongest single argument in the whole comparison.

Citrix bundles two different things: brokering sessions, and the console that shows you what the estate is doing. Leave Citrix for native Microsoft and you keep the desktops, but you lose the single place where cost, usage, posture and day-two management were visible. Microsoft's own tooling covers pieces of it across several different portals, and the gap usually surfaces a few months later, when somebody asks what the Azure bill is being spent on per team, or which accounts are over-permissioned, and the answer takes a week to assemble.

EtherInsights is the layer we put in its place on AVD and Windows 365 estates. Cloud cost attribution and forecasting, Microsoft 365 security posture, Copilot readiness and day-two management, in one view, at £0.79 per licensed user per month.

On a 250-seat estate that is roughly £198 a month. Set against a Citrix bundle priced per named user with a seat floor, the comparison is not close, and it is worth being precise about why: you are no longer buying brokering and visibility as one product. The brokering question gets answered by AVD or Windows 365, and the visibility question gets answered separately and far more cheaply.

It is an analysis platform, not a managed service and not a remediation tool. It tells you what is true and what it is costing. It does not broker sessions, and it is not a Citrix replacement on its own.

The full comparison

How to decide, in order

Take these in sequence, because answering them out of order is what produces the wrong platform.

1. Inventory what is actually published. Applications, who uses them, from where, on what devices. This is almost always shorter than people expect, and it determines feasibility more than any other factor.
2. Measure peak concurrency against named licences. An hour's work, and it either makes the concurrent-user argument or removes it.
3. Find the dependencies that decide it. HDX-class performance, App Layering, a specific integration. One real dependency outranks every cost argument on this page.
4. Ask where the applications and data actually live. On-premises and hybrid points at RAS. Microsoft-centric and modern points at native AVD or Windows 365.
5. Decide the management layer deliberately, at the point of migration rather than six months afterwards.
6. Pilot with real users and real peripherals. Printing, scanners, smart cards, USB devices and the one undocumented legacy application are where remoting migrations fail, and they only surface with people doing actual work.

Where we land

For on-premises and hybrid estates, Parallels RAS is the stronger answer, and it has the additional advantage of letting you solve the renewal now and decide about Azure later, on its own merits, rather than turning one deadline into two projects.

For AVD and Windows 365 deployments, go native and add EtherInsights for the cost, posture and management visibility. That combination is the way forward for a Microsoft-centric estate, and at £0.79 per licensed user per month the visibility costs a fraction of what it did as part of a bundle.

For very large estates, difficult network conditions or graphics-heavy work, stay on Citrix and negotiate. We would rather tell you that than sell you a migration that makes your users' day worse.

We deliver all three, including the Parallels RAS work, the AVD and Windows 365 consultancy, and the endpoints people connect from. The recommendation does not change depending on which one you pick.