The Citrix disaster recovery licensing rules are where a lot of enterprises quietly overspend, because the instinct is to license a DR site as if it were a second production estate. Under current per user and per device subscription licensing, that instinct is usually wrong. As of 2026, with Citrix subscription only since perpetual licensing ended in October 2022, the licenses follow the user, not the server, so a standby site serving the same people you already license generally needs no extra entitlement. This guide explains how DR sites are counted, where the real obligations sit, how active active differs from active passive, and how to avoid paying twice for failover capacity you already own.
Why per user licensing changes the DR question
The old mental model for disaster recovery licensing came from a server based world, where every machine that could run the software needed to be licensed, so a DR site full of standby servers implied a second set of licenses. Citrix licensing no longer works that way for the core delivery products. Current packaging counts users or devices, not servers or hosts, which means the licensed unit is the person or the endpoint, and that unit does not multiply just because there is a second site capable of serving it. A user you license to access apps and desktops is licensed to access them, and when production fails over to the DR site, the same user is still the same licensed user. The location of the infrastructure serving them is not the thing being counted.
This is the single most important shift to internalise, because it inverts the default assumption. The right starting question is not how many servers sit in the DR site, but how many users that DR site will serve and whether those users are already licensed at the primary site. If the answer is that the same population is covered, the DR site is, broadly, already paid for. The counting logic here is the same that governs everything in the estate, and our guide to Citrix license types compared covers how user, device, and concurrent models each behave, which matters because the DR answer depends on which model you hold.
DR licensing is not a server question anymore. It is a user question. Count the people the DR site serves, not the machines that serve them.
Active passive: usually covered already
The most common DR design is active passive, where the DR site sits idle or runs minimal services until a failover event, at which point it takes over and serves users while the primary site is unavailable. Under per user and per device subscriptions, this design usually sits comfortably within your existing entitlement, because at no point are both sites serving the same users simultaneously. Production runs at the primary site, then production runs at the DR site, but it is the same production population served from one place at a time. The users were licensed before the failover and they remain licensed during it. The DR site is providing continuity for an already licensed group, not extending service to a new one.
The practical implication is that an active passive DR site for your existing user base typically requires no additional Citrix licenses for those users. What you do need is confidence that this is what your contract actually says, because the right to run the entitled users from a standby site is a term, and terms vary by product and have changed over time. The safe path is to have the DR rights confirmed in writing in your agreement rather than relying on the general principle. This is also where reading your full entitlement matters, and our guide to finding what you own in your entitlements helps you locate the language that governs failover use.
Active active: where the count can grow
Active active is the design that changes the licensing arithmetic. Here both sites serve users at the same time, splitting load across two locations for performance, resilience, or geographic distribution. Because both sites are live and serving simultaneously, the counted population is not necessarily the same as a single site design. If the active active arrangement increases the number of users or devices genuinely using Citrix at any one time, the entitlement has to cover that larger or differently distributed population. The licensing follows real concurrent use, so an architecture that genuinely expands simultaneous use can expand the license requirement.
The nuance is that active active does not automatically double your licenses. If the same fixed population of named users is simply being served across two sites rather than one, a named user model may still cover them, because they are the same named users wherever they connect. The exposure grows when the design serves more users, or when a concurrent model is in play and the peak concurrency rises. This is exactly why measuring concurrency correctly matters, and our guide to what happens when you exceed your counts explains the consequences of letting real use drift above your entitlement. The rule of thumb: active passive rarely adds cost, active active needs modelling against your specific counting model.
The double paying trap
The most expensive disaster recovery licensing mistake is double paying: standing up a fully licensed second environment for DR that duplicates entitlements already covering the same users. It happens for understandable reasons. A DR project is scoped by an infrastructure team thinking in terms of capacity and resilience, the procurement of licenses for the new site gets treated as a fresh requirement, and nobody reconciles the new purchase against the existing per user entitlement that already follows those users wherever they are served. The result is a second set of licenses for a population that was never unlicensed in the first place.
Avoiding this is a reconciliation exercise, not a technical one. Identify the users the DR site will serve, confirm they are the same users already licensed at the primary site, and establish from the contract that your entitlement permits serving them from the standby location. If all three hold, the DR site for that population needs no additional licenses, and any quote that adds them is selling you a duplicate. This is the same shelfware risk that appears throughout a Citrix estate, and the discipline that finds it is covered in our guide to finding and cutting unused licenses. As of 2026, with renewal pricing under heavy upward pressure, a duplicate DR entitlement is one of the cleaner overspends to remove.
DR across hybrid and cloud sites
Modern DR often spans on premises and cloud, with a failover target in Azure, AWS, or Google Cloud rather than a second physical data centre. That does not change the per user principle, but it does add the cloud delivery and hybrid rights dimension. To run Citrix workloads in a public cloud as a DR target, you need the hybrid rights that permit cloud delivery alongside your on premises entitlement, and you need to satisfy the cloud platform's own requirements. Our guide to Citrix on Azure licensing requirements covers the cloud side, and the broader entitlement structure is in our guide to Citrix hybrid rights.
The point for a buyer is that a cloud DR target is a hybrid rights question layered on top of the per user question. The same users are still the licensed unit, so failing them over to a cloud site does not multiply the Citrix user licenses, but you must hold the hybrid rights that let those users be served from the cloud, and you must account for the underlying cloud infrastructure and any Microsoft licensing the cloud delivery requires. Treating the cloud DR target as a Citrix re purchase is the same double paying trap in a new location. Treating it as an extension of where your already licensed users can be served, governed by hybrid rights, is the correct frame.
What to confirm before relying on DR coverage
Disaster recovery licensing is an area where general principles point the right way but the contract decides the outcome, so do not rely on assumption. Confirm four things. First, your counting model, because the DR answer differs between named user, device, and concurrent. Second, the DR rights language in your specific agreement, getting failover and standby use stated in writing rather than inferred. Third, your design, classifying it honestly as active passive or active active, since that distinction drives whether the count can grow. Fourth, for cloud DR, your hybrid rights and the cloud platform requirements that govern serving users from the failover site.
Get those four confirmed and the DR position becomes clear and defensible, which matters both for cost and for any future license review, since Citrix reviews and audits are increasing as customers attempt to reduce spend or exit. A DR estate that is correctly understood is a saving and a clean audit position at once; one that is assumed is either an overspend or an exposure waiting to surface. For the full picture of how DR sits within your total licensing and infrastructure cost, see our guide to Citrix TCO analysis and the wider Citrix licensing fundamentals pillar.
Frequently asked questions
What are the Citrix disaster recovery licensing rules?
Citrix disaster recovery licensing rules govern whether a standby or failover site needs its own licenses or can run under your existing entitlement. Because current Citrix licensing is per user or per device on a subscription basis rather than per server, the same users covered at your primary site are generally covered when they fail over, provided they are not being served simultaneously from both sites. As of 2026 the controlling detail is in your contract and product terms, so DR rights must be confirmed in writing rather than assumed.
Do I need separate licenses for a Citrix DR site?
Often no, because user and device subscriptions follow the user rather than the location, so a user licensed at the primary site is typically still licensed when production moves to the DR site. The exception is when both sites serve users at the same time, such as an active active design, where concurrent use can require additional entitlement. Confirm the specific DR language in your agreement before relying on this, as terms vary by product and over time.
Does Citrix licensing cover active active and active passive DR differently?
Yes. Active passive designs, where the DR site only carries load during a failover, usually sit comfortably under existing per user or per device entitlements because the same users are served from one site at a time. Active active designs, where both sites serve users simultaneously, can increase the counted population and may require more entitlement. The licensing follows real concurrent use, so the architecture decision directly affects the license position.
How do buyers avoid double paying for Citrix DR?
Double paying happens when an organisation provisions a fully licensed second environment for DR that duplicates entitlements already covering the same users. Because per user and per device subscriptions follow the user, a passive DR site for the same population usually needs no additional licenses. Map which users your DR site serves, confirm they overlap with your primary entitlement, and get the DR rights stated in your contract before buying anything extra.