SQL Server Always On Availability Groups (AG) require Enterprise Edition the moment you deploy more than one replica, more than one database per AG, or any readable secondary. Standard Edition supports only Basic Availability Groups — one database per AG, one primary, one passive secondary, no read access on the secondary. The passive-replica licensing entitlement under Software Assurance lets you avoid licensing the standby replica, but only if it is fully passive: no queries, no backups, no reporting. The most common audit finding is a "passive" replica that has been used for read traffic or backup offload — the moment that happens, the replica requires its own licence. Always On licensing is therefore a triple-test of edition, replica topology, and SA passive-status compliance.
What Always On actually licenses
Always On Availability Groups (AG) is the high-availability technology that replicates one or more databases across multiple SQL Server instances, with automatic or manual failover and optional readable secondaries. The technology shipped first in SQL Server 2012 Enterprise and a constrained version (Basic Availability Groups) landed in SQL Server 2016 Standard. The licensing implications of each variant differ materially.
The starting point for Always On licensing is the edition trigger. SQL Server Standard Edition supports Basic AG — one database per AG, one primary, one synchronous secondary, no readable secondary, no log shipping replacement. SQL Server Enterprise Edition supports full AG — up to 9 secondary replicas (one synchronous, eight asynchronous in SQL Server 2019 and later), readable secondaries with optional read-only routing, multi-database AGs, distributed AGs, and the contained AGs feature that ships from SQL Server 2022 onward. If the deployment uses any feature beyond the Basic AG envelope, every replica must be licensed for Enterprise.
The passive-replica entitlement under Software Assurance
The single largest cost lever in Always On licensing is the passive-replica entitlement granted by active Software Assurance. The entitlement permits one fully passive secondary replica per Enterprise primary — or one per Standard primary in a Basic AG — to run without its own SQL Server licence, provided the replica meets the strict passive-status test. The Product Terms language defines passive as: no end-user queries, no backups served from the replica, no reporting, no consistency checks, no log reader services, no SSIS or SSAS workloads.
The passive-replica entitlement compounds significantly across an enterprise estate. A 16-core Enterprise primary at $15,123/core lists at $241,968 perpetual ($60,490 annualised over four years). The passive secondary at zero incremental licence cost halves the effective HA cost across the AG. For a 50-AG estate the entitlement is worth $1.2M–$3M annualised against the alternative of licensing both replicas.
If any "passive" replica in your estate runs a scheduled backup, serves a single read query, or hosts a reporting workload, the replica fails the passive-status test and requires its own SQL Server licence retroactive to the violation date. The remediation cost in the next compliance review is the full perpetual licence plus any SA arrears.
Readable secondaries: the immediate licence consumer
Readable secondaries are an Enterprise-only feature and explicitly fail the passive-status test the moment they serve a single read query. A readable secondary requires its own SQL Server Enterprise core licence with active SA. For deployments that use readable secondaries for read scale-out (typically reporting and dashboarding traffic), the licensing cost compounds against each readable replica.
The procurement question to ask before deploying a readable secondary: is the read scale-out worth the licence cost? In many cases the answer is no — the read traffic could be served from a separate reporting database on Standard, populated by SSIS or log shipping, at a fraction of the Enterprise-replica cost. Always On readable secondaries are a premium feature priced like one.
Basic AG on Standard: the cost-saver and its limits
Basic Availability Groups on SQL Server Standard Edition are the cost-effective HA path for workloads that need two-node failover but do not need read access on the secondary or more than one database per AG. The licensing cost: Standard primary at ~$3,945/core with SA, Standard passive secondary at zero incremental licence cost under the SA passive entitlement. For a 16-core Standard primary the annualised cost is roughly $16,800 over four years against the equivalent 16-core Enterprise AG at $60,490 — a 72% reduction for workloads that fit inside the Basic AG envelope.
The Basic AG limits matter: only one database per AG (so a database that needs to fail over with other databases together cannot use Basic AG); no readable secondary (so reporting workloads cannot offload); no multi-replica topologies (so geo-redundant deployments need full AG and Enterprise); no contained AG support. Audit pattern: enumerate every AG in the estate, classify each as fitting inside the Basic envelope or requiring full AG, and re-platform every fit-for-Basic workload to Standard Edition. We routinely find 35–55% of AGs in mid-size SQL Server estates fit the Basic envelope but run on Enterprise because the original deployer did not know the option existed.
The 90-day failover licensing rule
SQL Server Software Assurance grants a Failover Rights entitlement that permits temporary failover to an unlicensed standby server for up to 90 days every 90 days. The entitlement covers planned and unplanned failover scenarios. The constraint: the standby server must be used only for the duration of the failover; permanent or extended use beyond 90 days requires a licence on the standby. This entitlement is the licensing case for true disaster-recovery (DR) replicas that sit idle until a failover event.
The audit pattern most often missed: the standby replica must be physically separate from any other licensed workload. A standby replica running on a shared host that also runs other licensed SQL workloads does not qualify for the failover entitlement — the shared host triggers normal licensing for every SQL workload running on it.
Always On in Azure and hybrid topologies
Always On AG in Azure SQL Managed Instance and Azure SQL Database is included in the service entitlement — the high-availability layer is part of what the customer is paying for. For SQL Server on Azure VM the Always On licensing rules above apply identically, with the addition that the Azure Hybrid Benefit (AHB) entitlement can be applied to every SA-licensed core moved into the VM-based AG topology. The savings against PAYG SQL Server on Azure VM run 38–55% on the Enterprise edition cores. Pair the Always On rebuild with the broader SQL Server cost reduction levers and the AHB application audit.
EA negotiation levers for Always On estates
- Basic AG re-platform. For every AG fitting the Basic envelope, the migration from Enterprise to Standard delivers a 72% reduction in annualised licence cost. Capture before renewal.
- Readable secondary triage. Document every readable secondary, its use case, and its read-volume against the alternative of a Standard reporting database. Microsoft does not surface the alternative; the buyer must.
- Passive-status audit. Pre-audit every "passive" replica against the SA passive-status test before Microsoft does. Remediate any failing replica by licensing it explicitly or by stopping the non-passive workload.
- Distributed AG topology. For multi-region HA deployments, distributed AGs are an Enterprise feature and licence per replica. The leverage at renewal: negotiate distributed-AG-specific concessions when the topology was driven by Microsoft’s own DR architecture guidance.
- Azure migration AHB. For Always On replicas migrating to Azure SQL Managed Instance, apply AHB to every SA-licensed core and capture the BYOL discount.
Anonymised case study: $640K Always On rebuild
A 4,800-employee healthcare provider ran 38 SQL Server Always On AGs across the on-premises estate: 32 on Enterprise (16 cores per primary, average two replicas) and six on Standard (Basic AG). Audit findings: of 32 Enterprise AGs, 19 used no Enterprise-only AG feature beyond multi-replica synchronous (which a multi-replica Basic AG-like topology could have been re-architected to avoid); seven of the 32 had readable secondaries running ~80 read queries per day, each of which could have been re-platformed to a Standard reporting replica fed by log shipping; three replicas labelled "passive" in the SAM tool were running scheduled backups (failing the passive-status test). We rebuilt: 19 AGs re-platformed to Standard with Basic AG topology ($1.13M annualised Enterprise saving), seven readable secondaries re-platformed to Standard reporting replicas ($420K annualised saving), three failing passive replicas licensed explicitly with SA ($55K annualised). Total net annualised saving after the three licensing additions: $640K. The audit-defence document was provided to Microsoft at the renewal and the EA closed with no claim against the historical passive-status violations.
Always On Availability Groups deliver high availability that is more sophisticated than most enterprises need. Pair the AG rebuild with the broader SQL Server cost-reduction discipline and a clear position on the 2026 EA tier-collapse landscape, and Always On stops being the silent driver of Enterprise-edition cost. For the broader audit-defence posture see our SQL Server Developer + Express analysis.