A Citrix to AVD migration is one of the most common moves enterprises model when a Citrix renewal arrives with a steep increase, and the licensing is where it most often goes wrong. The mistake is treating it as a simple swap, dropping the Citrix subscription and picking up Azure Virtual Desktop, when in fact the two license different things and overlap in ways that create double payment if you are not careful. This license mapping guide sets out how Citrix entitlements map onto AVD, what you genuinely stop paying for, what you still owe Microsoft, and how to stage the move so you never fund both platforms at once. It is written for buyers who want the migration to cut cost rather than quietly shift it.
What a Citrix to AVD migration actually changes
Azure Virtual Desktop is a Microsoft capability that brokers and delivers Windows sessions running on Azure infrastructure. A Citrix to AVD migration replaces the Citrix delivery and brokering layer with AVD's native session host and management plane. What it does not do, automatically, is replace everything Citrix was doing for you. Citrix layers advanced image and provisioning tooling, the HDX protocol, granular policy control, and multi cloud brokering over the top of infrastructure. AVD provides a leaner native equivalent, and the gaps have to be filled with Azure native services, third party tooling, or an accepted change in capability. The licensing question and the capability question are inseparable: you cannot map the licenses honestly without mapping the capability they paid for.
This is why a license mapping starts with an inventory rather than a price comparison. You need to know which Citrix features each workload actually uses, because the cost of reproducing them on AVD is part of the migration, and the features no longer used are exactly the spend the move should eliminate. Mapping licenses without mapping capability is the single most common reason these migrations overrun their business case.
You cannot map the licenses honestly without mapping the capability they paid for. The inventory comes before the price comparison.
The Microsoft side of the map
Azure Virtual Desktop is not free to license. It requires an eligible Windows or Microsoft 365 entitlement that grants the desktop access right, plus the Azure compute, storage, and networking the sessions consume. The reason a Citrix to AVD migration can look inexpensive is that many enterprises already hold the eligible Microsoft license through an existing agreement they pay for regardless, so the marginal licensing cost of the desktop right approaches zero. That is a real advantage, but it is never the whole bill, and it is never automatic. The first line of any license mapping is to confirm the eligible Microsoft entitlement is genuinely in place across the users you intend to move, before any Citrix reduction is planned on the assumption that it is.
The second Microsoft line is consumption. AVD shifts cost from a Citrix subscription onto Azure compute and storage sized to real concurrency. Size that compute to genuine measured demand rather than a defensive peak, or the consumption bill quietly recreates the overspend you left Citrix to escape. The desktop right may be covered, but the infrastructure underneath it is metered, and an unmanaged AVD estate is as capable of waste as an oversized Citrix one.
The double payment trap
The most expensive mistake in a Citrix to AVD migration is paying for both platforms during the move. Because Citrix eliminated perpetual licensing in October 2022 and is subscription only, you cannot simply stop paying mid term when a workload leaves. The Citrix commitment runs to its contracted end regardless of how many sessions you have moved off it, so a migration that ignores the subscription calendar pays for emptying Citrix capacity and the AVD that replaced it at the same time. The discipline is to make the migration plan and the renewal calendar a single document, reducing the Citrix commitment only at renewal or co termination points, and only as far as the workloads that have actually moved.
We treat the Citrix subscription term as the spine of the migration plan for this reason. Each reduction in the Citrix commitment has to line up with a contractual opportunity to reduce it, and each workload move has to be timed so the overlap is controlled rather than absorbed. This is the same staging logic we apply across partial Citrix exit strategies, where the order and timing of moves determines whether the saving is real or merely deferred.
Staging the migration by workload
Few estates should move to AVD all at once, and the license mapping usually argues for stages. Standard task and knowledge workers, who use little of the advanced Citrix capability, tend to move cleanly first and deliver the earliest saving. Graphics intensive, latency sensitive, and specialist application workloads either move later with added Azure or third party tooling to replace what Citrix provided, or stay on Citrix where the protocol and management advantage still justifies the premium. Sequencing the move this way keeps each step low risk and lets the Citrix commitment fall in measured increments rather than a single uncertain leap. It is the same workload by workload separation we use in a Citrix migration risk assessment, applied to licensing rather than technical risk.
A staged map also forces the migration cost into the open. Re imaging, application packaging and testing, user acceptance, and retraining all carry one time cost, and a license mapping that counts only the steady state saving against the Citrix subscription flatters the move. We fold that one time cost into the full picture in our work on Citrix exit economics, so the business case reflects the cost of getting to AVD, not just the cost of being there.
Using the map at renewal
A complete Citrix to AVD license mapping is valuable even if you never finish the migration, because it is leverage. A renewal arrives, the increase is presented as inevitable, and a costed, staged AVD plan that your team could execute is the strongest available counter. The vendor is no longer the only option, and the movable portion of the estate is a credible departure rather than a vague threat. As of 2026, with Cloud Software Group renewal increases widely reported between 50% and 200%, a license mapping that proves part of the estate can leave is one of the more practical ways to turn a take it or leave it quote into a negotiation.
This is why the mapping and the renewal belong together. A model that proves a viable AVD destination underpins the credible exit threat that moves price, and it lets you decide to migrate, stage, or stay on facts. For the full comparison of AVD against Citrix on total cost, see our Citrix vs Azure Virtual Desktop total cost analysis, and for the wider set of exit options, the Citrix alternatives pillar links every related guide. Whether you move or not, the map keeps the numbers in your hands rather than the vendor's.
Frequently asked questions
What does a Citrix to AVD migration replace and what does it not?
A Citrix to AVD migration replaces the Citrix delivery and brokering layer with Azure Virtual Desktop's native session host and management. It does not automatically replace everything Citrix did. Advanced image and provisioning tooling, granular policy, the HDX protocol, and multi cloud brokering have to be reproduced with Azure native services, third party tools, or accepted as a change in capability. Mapping licenses without mapping capability is how migrations overrun, so both have to be inventoried before any commitment changes.
Do I still need Microsoft licenses to run AVD?
Yes. Azure Virtual Desktop requires an eligible Windows or Microsoft 365 license that grants the desktop access right, plus the Azure compute, storage, and networking the sessions consume. Many enterprises already hold the eligible Microsoft license through an existing agreement, which is why the marginal licensing cost of moving can be low, but it is never zero. Confirming the eligible entitlement is in place is the first line of any license mapping, before any Citrix reduction is planned.
How do I avoid paying for Citrix and AVD at the same time?
Stage the migration against the Citrix subscription term and reduce the Citrix commitment only as workloads actually move. Because Citrix eliminated perpetual licensing in October 2022 and is subscription only, you cannot simply stop paying mid term, so the migration plan and the renewal calendar have to be one document. Plan the Citrix reductions to land at renewal or co termination points, not before, so the overlap is controlled rather than paid for twice.
Can I migrate to AVD in stages?
Yes, and most estates should. Standard task and knowledge workers usually move cleanly first, while graphics, latency sensitive, and specialist application workloads either move later with added tooling or stay on Citrix. A staged, workload by workload migration lets you cut the Citrix commitment in steps and keeps each move low risk, which is also the structure that gives the most negotiating leverage at each renewal.
Does planning a Citrix to AVD migration help my Citrix negotiation?
It does, provided the plan is real. A costed, staged AVD migration that your team could execute is a credible alternative, and a credible alternative is the single most effective counter to a renewal increase. As of 2026, with Cloud Software Group increases widely reported between 50% and 200%, a license mapping that proves a movable portion of the estate can leave changes the renewal from a take it or leave it quote into a genuine negotiation.