Software assurance grants a passive failover instance of SQL Server at no additional license cost. It is one of the most valuable benefits in the SQL estate and one of the most commonly mislicensed, in both directions. Some organizations buy licenses for secondaries that qualify for the free benefit and pay twice for resilience. Others run secondaries that breach the passive condition and carry an exposure they do not know exists. The failover benefit is generous but conditional, and the conditions are precisely where the cost and the risk live. Getting it right both removes wasted spend and closes an audit finding that surfaces in nearly every SQL Server review.
The failover benefit grants a passive secondary at no license cost, but only when two conditions hold together. The primary must be covered by active software assurance, and the secondary must remain genuinely passive. Lose either condition and the free instance becomes a licensable one, often retroactively in an audit. Most mislicensing comes from misunderstanding what passive actually means in practice.
The free failover instance is a software assurance benefit, not a baseline licensing right. Without active SA on the primary, the secondary requires its own full license. This is the trap for estates that let SA lapse to save money and inadvertently make every passive secondary a licensable instance overnight.
A passive secondary may receive transaction log shipping, mirroring, or replication to stay synchronized, and that is permitted. What is not permitted is serving any active workload: no read queries, no reporting, no backups run against it, no analytics offloaded to it. The moment the secondary does work, it is active and must be licensed.
The failover benefit is lost not through a deliberate decision but through a configuration choice made for performance or convenience that no one connected to licensing. Three patterns account for most lost benefits in real estates.
An Always On availability group configured to route read only traffic to the secondary turns that secondary active. It is a common performance optimization that quietly converts a free instance into one requiring a full license. The DBA who enabled it was solving a load problem, not making a licensing decision.
Running backups against the secondary to spare the primary is a sensible operational practice and a licensing breach. Backup activity counts as workload, so the secondary is active and licensable. Resilient design and licensing economy point in opposite directions here unless the configuration is deliberate.
The benefit covers one passive secondary per licensed primary under current terms. A second standby for additional resilience or a geographically separate copy is a separate licensable instance. Estates that built multi node clusters for safety often carry uncounted instances beyond the single free one.
The correct failover position removes spend where the benefit applies and closes exposure where it has been breached. Both matter, because the failover line is examined in nearly every SQL Server audit and is a frequent source of both refunds and findings.
Estates that bought full licenses for secondaries that qualify for the free benefit are paying twice for resilience. Identifying the genuinely passive secondaries and reclaiming or reallocating those licenses is direct recovered cost. This is common in environments built before the team understood the benefit, where every node in a cluster was licensed defensively. The reclaimed licenses can then cover growth elsewhere, deferring new purchases at renewal.
Where a secondary has drifted active through read routing, offloaded backups, or an extra node, the choice is to reconfigure it back to passive or to license it properly. We model both: the cost to license versus the operational impact of removing the workload from the secondary. Often the read traffic can move to a dedicated reporting replica that is licensed deliberately, restoring the failover benefit on the original secondary. Either way the exposure is closed on your terms rather than discovered on Microsoft's.
The two conditions that gate the free instance, the configurations that quietly forfeit it, and the dual review that recovers spend on over licensed secondaries while closing exposure on active ones. Sent on request.
We map every secondary in the SQL estate against the two conditions, reclaim licenses wasted on genuinely passive instances, and close the exposure on secondaries that have drifted active through read routing or offloaded backups. The failover line stops being an audit risk and becomes recovered spend.