Licence Mobility and True-Up Strategy for SQL Server in Virtualised Environments

Why SQL Server Licensing in Virtual Environments Is Uniquely Difficult

SQL Server is one of Microsoft's highest-value products and one of the most frequently mismanaged in terms of licence compliance and cost optimisation. The core complexity arises from the interaction of three factors: a per-core licensing model that generates costs based on physical host topology; virtualisation environments where SQL Server instances move dynamically between hosts; and a Software Assurance (SA) programme that fundamentally changes what the organisation is permitted to do with its licences.

Without Software Assurance, a SQL Server licence is assigned to a physical server and can only be reassigned to a different server after a 90-day minimum period. In virtualised environments where VMs are migrated between hosts routinely — for load balancing, maintenance, or failover — this 90-day constraint means that every unplanned migration technically creates a licence compliance breach. Organisations operating SQL Server in VMware vSphere, Microsoft Hyper-V, or any other dynamic virtualisation environment without Software Assurance are, in almost all cases, in a state of inadvertent non-compliance that they are unaware of.

Software Assurance resolves this problem, but it does so at a cost that requires careful evaluation. And beyond mobility, SA provides a broader set of benefits — disaster recovery rights, fail-over rights, Azure Hybrid Benefit, and version upgrade rights — that change the calculus of SQL Server licensing strategy significantly.

Licence Mobility: What It Means and Why It Matters

Licence Mobility through Software Assurance is a Microsoft SA benefit that allows certain server licences — including SQL Server — to be reassigned to a different physical server within an authorised server farm at any time, without the standard 90-day constraint. It also allows licences to be used on authorised outsourcer infrastructure (third-party managed hosting) without a separate licence acquisition, subject to the mobility framework requirements.

In practical terms, Licence Mobility through SA means that a SQL Server licence can follow a workload as it moves between hosts in a VMware cluster, across nodes in a Windows Server failover cluster, or to an authorised cloud infrastructure provider — all without triggering a compliance event. This right is not available without active Software Assurance. Organisations that have let SA lapse on SQL Server licences — a common scenario when renewal costs are challenged — lose mobility rights immediately and must operate under the 90-day constraint.

The financial logic of maintaining SA on SQL Server licences in virtualised environments is clear: the cost of SA is justified by the mobility and compliance protection it provides, and by the Azure Hybrid Benefit that allows SA-covered licences to be used to licence Azure SQL VMs or Azure SQL Managed Instances at a significant reduction from standard Azure pricing. For organisations with SQL Server workloads both on-premises and in Azure, the Azure Hybrid Benefit alone can justify the SA investment.

Mobility Requirements and Documentation

Licence Mobility through SA is not automatic — it requires active administration. Microsoft requires that organisations maintain documentation of their licence mobility assignments, specifically recording which licences are assigned to which physical servers or outsourcer infrastructure at any given time. When Microsoft or an authorised auditor requests this information, the organisation must be able to produce it promptly and accurately.

In practice, many organisations that have SA-covered SQL Server licences do not maintain this documentation at the required level of granularity. They know they have SA, but they cannot produce a current, accurate mapping of licence assignments to physical hosts. This gap does not typically create an immediate compliance problem — Microsoft rarely audits licence assignment documentation directly — but it does create vulnerability in an audit context if the organisation's effective SQL Server count is questioned.

SQL Server True-Up Strategy in Enterprise Agreements

Most organisations of significant size licence SQL Server through a Microsoft Enterprise Agreement (EA). The EA is a three-year commitment that includes an annual true-up process — a formal reconciliation of actual SQL Server deployments against the committed licence counts recorded in the agreement.

True-up creates a specific strategic dynamic. At the initial EA commitment, the organisation declares its current SQL Server deployment and the licences are priced accordingly. At each annual true-up, any increase in deployment since the last measurement point must be reported and paid for at the applicable EA pricing. This structure means that organisations that grow their SQL Server footprint between true-ups are exposed to catch-up payments that can be material — particularly if SQL Server instances have proliferated in development, test, or database farm environments where deployment discipline is lower than in production.

Pre-True-Up Internal Audits

The most effective true-up strategy begins with a self-initiated internal review conducted before Microsoft's formal true-up request. This review should identify every SQL Server instance in the environment — including development and test instances, SQL Express deployments, and instances running in containers or automated deployment environments that may have been provisioned without licence accounting — and reconcile them against the current EA entitlement baseline.

The goal of the internal review is to know your position before Microsoft knows it. If the internal review reveals licence shortfalls, the organisation can make an informed decision about remediation: bringing the position into compliance before the true-up through EA order, restructuring the deployment to reduce the licence requirement, or entering the true-up conversation with a clearly articulated position. Each of these options is significantly better than responding to a Microsoft-initiated assessment with an unknown or contested position.

Common sources of SQL Server licence undercount in true-up preparation include: SQL Server instances on VMs that were not captured in the configuration management database; SQL Server Express deployments that have been upgraded to full editions without licence provisioning; developer SQL Server licences being used for production workloads under the mistaken belief that developer licences cover production use; and SQL Server running as a component of other Microsoft products (SharePoint, System Center) without awareness that the host server still requires a separate SQL Server licence if it exceeds the bundled use rights.

EA Renewal and SQL Server Negotiation

The EA renewal is the primary commercial leverage point for SQL Server cost management. Renewal proposals from Microsoft typically present SQL Server at the current list price, discounted by the EA discount tier that applies to the total contract value. The negotiating variables are the EA discount tier, the price lock-in terms for add-ons during the agreement, and the specific treatment of SQL Server licences relative to subscription versus perpetual options.

SQL Server 2022 introduced a subscription licensing option alongside the traditional perpetual plus SA model. The subscription model — SQL Server as a service rather than a perpetual asset — has different financial characteristics that favour different deployment scenarios. Organisations with growing SQL Server footprints, high virtualisation rates, and strong Azure integration generally benefit from subscription. Organisations with stable, mature SQL Server estates may find perpetual plus SA more cost-effective over the long term.

The transition from perpetual to subscription also has implications for Azure usage. Subscription SQL Server licences do not provide the same Azure Hybrid Benefit terms as perpetual-plus-SA licences, a nuance that is often not fully presented in Microsoft renewal proposals. Organisations evaluating subscription vs perpetual should model the total cost of ownership including Azure workloads, not just on-premises licensing.

Reserved Instances vs Savings Plans for SQL Server in Azure

For organisations running SQL Server workloads in Azure, the choice between Reserved Instances and Savings Plans is a material cost decision. Understanding the difference between these two commitment mechanisms — and how each interacts with SQL Server licensing — is essential for optimising Azure SQL costs.

Reserved Instances

Azure Reserved Virtual Machine Instances (Reserved Instances or RIs) provide a discount in exchange for a one-year or three-year commitment to a specific virtual machine type, size, and region. The discount can be substantial — typically 30 to 50 percent off pay-as-you-go pricing for committed workloads. Reserved Instances are most effective for stable, predictable workloads where the VM type, size, and region are unlikely to change over the commitment period.

For SQL Server specifically, Reserved Instances interact with Software Assurance through the Azure Hybrid Benefit. An SA-covered SQL Server licence used with a Reserved Instance in Azure enables the organisation to avoid the SQL Server licence component of the Azure VM pricing — which is typically the largest cost component for SQL Server VMs — while paying only for the underlying compute at the Reserved Instance rate. This combination can reduce SQL Server VM costs in Azure by 40 to 66 percent compared to standard pay-as-you-go SQL Server VM pricing, making it one of the highest-return optimisations available to organisations with both on-premises SA and Azure SQL workloads.

Savings Plans

Azure Savings Plans are a more flexible commitment mechanism introduced more recently than Reserved Instances. Rather than committing to a specific VM type and size, Savings Plans commit to a specific hourly spend level in Azure compute, with savings applied automatically to the cheapest eligible resources. Savings Plans trade some of the discount depth of Reserved Instances for greater flexibility — useful for organisations whose workload mix changes over the commitment period.

The key distinction between Reserved Instances and Savings Plans for SQL Server is flexibility versus discount depth. Reserved Instances provide deeper discounts for workloads that are stable and predictable. Savings Plans provide better coverage for workloads that are dynamic or variable. Organisations should evaluate their SQL Server workload stability — both instance count and instance type — before deciding which mechanism to prioritise.

A common approach for large SQL Server Azure estates is to cover the stable, clearly predictable workload baseline with Reserved Instances (maximising discount depth) and manage variable or uncertain workloads through Savings Plans or pay-as-you-go, providing a combined cost profile that is lower than either mechanism alone while maintaining flexibility where it is genuinely needed.

The Software Assurance Decision

The central commercial question for many organisations managing SQL Server in virtualised environments is whether to maintain Software Assurance. SA carries a cost — typically 25 to 29 percent of the underlying licence value per year — and many finance or IT procurement teams view it as an optional add-on rather than a strategic requirement.

For SQL Server in virtualised environments, that view is difficult to sustain under analysis. The compliance protection that SA provides through Licence Mobility is not a luxury — it is the mechanism that makes SQL Server deployment in dynamic virtualisation environments legally sound. Without it, every VM migration is a potential compliance event. The Azure Hybrid Benefit is not available without SA — and for organisations with Azure SQL workloads, the savings available through Hybrid Benefit routinely exceed the SA cost. Fail-over and disaster recovery rights provided by SA — which allow passive standby SQL Server instances to operate without additional licence cost — are particularly valuable for organisations with high-availability SQL Server architectures.

The organisations that rationally choose not to maintain SA on SQL Server licences are those with entirely static, physical-server deployments with no virtualisation and no Azure usage. For any organisation with a modern infrastructure topology, maintaining SA on SQL Server is almost always commercially justified — and allowing SA to lapse is almost always a false saving.

Preparing for Your Next Microsoft EA Renewal

SQL Server should be a central element of any Microsoft EA renewal strategy. The renewal is the moment at which the multi-year cost trajectory is set, and the decisions made in the renewal negotiation — on discount tiers, SQL Server edition mix, subscription versus perpetual, and SA scope — will compound over the three-year term.

The most effective preparation for an EA renewal involving significant SQL Server spend includes: a current, accurate internal SQL Server inventory that can serve as the basis for a credible negotiation position; a clear analysis of on-premises versus Azure SQL workloads and the Hybrid Benefit implications; a modelled comparison of subscription versus perpetual licensing for the organisation's specific growth trajectory; and benchmark data on Microsoft's EA discount practice for comparable organisations.

Redress Compliance supports organisations through Microsoft EA renewals with deep expertise in SQL Server licensing strategy, Azure cost optimisation, and EA negotiation. Our clients consistently achieve better pricing outcomes than organisations that negotiate directly with Microsoft account teams without independent advisory support. Contact our team to discuss your next Microsoft renewal.