The free secondary that software assurance grants depends on a single word, and that word is doing more work than most estates realize. Passive is not a license type you buy or a checkbox you set. It is a behavioral condition the instance must satisfy every day it runs, and it is broken by ordinary operational decisions that no one connects to the contract. A secondary that was passive when it was deployed drifts active the moment a DBA enables a read replica, points a backup job at it, or runs a consistency check against it. The benefit does not warn you when it lapses. It simply stops applying, and the exposure accrues silently until an auditor counts the instance and asks why it was never licensed.
The product terms allow a passive secondary to do exactly one thing: stay synchronized with the primary so it can take over if the primary fails. Everything beyond synchronization is workload, and workload makes the instance active. The line is narrow and precise, and reading it carelessly is how estates accumulate uncounted licensable instances.
A passive secondary may receive everything it needs to remain a current, ready replacement. It may also run the work required to become the primary during an actual failover event. None of this forfeits the benefit.
The instant the secondary serves a user, a query, a report, or a maintenance task that benefits the business rather than the failover itself, it is active. Active instances require their own full license whether or not anyone intended them to do work.
No estate decides to break the passive condition. It happens through three ordinary operational moves, each made for a sound technical reason and none reviewed for its licensing effect. These are the patterns we find in nearly every SQL Server review, and each one converts a free instance into a licensable one.
The most common breach. A team enables read only routing on an Always On availability group to lighten the primary, and the standby now answers production read traffic. It is an excellent performance decision and a clean conversion of a free instance into one that costs a full core based license. The DBA was tuning latency, not amending the contract.
Running full or log backups against the secondary to protect primary performance is textbook operational hygiene and a clear forfeit of the benefit. Backup activity is workload. The secondary that was free for failover becomes a licensable instance the day the backup schedule moves to it.
Consistency checks, index maintenance, and certain monitoring agents that execute queries against the secondary all constitute work. These run on a schedule, often configured years ago, and they are invisible until someone reviews what the standby is actually doing on a given night.
Holding the passive condition is not difficult, but it requires that the people configuring the database understand the licensing line and that the configuration is reviewed on a cadence rather than set once and forgotten. Two practices keep the benefit intact.
When the business needs to offload reads, the answer is a dedicated, deliberately licensed reporting replica rather than borrowing the failover standby. This keeps the standby genuinely passive and therefore free, while the reporting replica carries its own license as a known, budgeted cost. The result is two correctly classified instances instead of one free instance silently turned licensable. The cost is explicit and far lower than an audit settlement on the same workload.
The only reliable test of passive is what the instance does, not what the architecture diagram says it does. A periodic review of read routing settings, backup job targets, scheduled maintenance, and monitoring queries confirms each standby still qualifies. We run this review against the live configuration, because the diagram and the deployment have usually diverged. Catching drift early keeps the benefit alive and removes the finding before it becomes a number in a compliance report.
What synchronization is permitted, the three operational patterns that quietly forfeit the benefit, and the review that confirms each standby still qualifies before an auditor counts it. Sent on request.
We review the live configuration of every SQL Server secondary against what passive actually permits, separate the genuine standbys from the instances that have drifted active, and reclassify the reporting work onto deliberately licensed replicas. The free benefit stays free and the audit line closes on your terms.