License mobility is the software assurance benefit that lets a SQL Server license you already own follow the workload to new hardware, to a shared cloud, or to a service provider, rather than forcing a fresh purchase each time the workload moves. It is the lever that makes a cloud migration affordable, because the alternative is buying SQL again at cloud list price on top of the licenses already sitting on the balance sheet. Yet mobility is one of the most underused benefits in the SQL estate. Estates migrate to the cloud and pay for SQL twice because no one applied the licenses they held, while others move licenses in ways that breach the 90 day rule or the service provider conditions and create exposure where they were trying to save. Mobility is generous, but it is conditional, and the conditions decide whether it saves money or manufactures a finding.
License mobility through software assurance unlocks three distinct moves, each governed by its own conditions. Knowing which applies to a given migration is the difference between reusing an asset you own and buying it a second time.
Mobility within your own environment lets a license move from one server to another more often than the baseline rules allow. This is what makes hardware refreshes and live migration across a cluster work without reassigning slowly, provided the move respects the reassignment cadence the benefit sets.
Mobility to authorized cloud environments lets you bring your own SQL licenses to a public cloud rather than paying the platform's bundled SQL rate. On Azure this is the hybrid benefit. The licenses you already own offset the cloud SQL cost, often by a large margin, which is precisely the saving most migrations leave on the table.
Mobility to a third party hoster lets you run your licensed SQL on infrastructure managed by an authorized service provider. The conditions here are the strictest, because the workload now sits on hardware you do not control, and the provider has to be on the authorized list for the move to qualify.
Mobility is not unconditional. Three conditions decide whether a move is valid, and breaching any of them turns a legitimate reuse into an exposure that surfaces in an audit as a license that was moved when it had no right to.
Mobility is a software assurance benefit and ends when SA lapses. A license that moved to the cloud under mobility and then lost its SA at renewal has lost the right that put it there. This is the trap for estates that drop SA to cut cost without realizing the cloud workloads depended on it.
License mobility to a cloud or service provider does not carry the usual restriction on how often a license can be reassigned, but movement within your own server farm still respects a reassignment cadence. Confusing the two leads estates to move licenses between owned servers faster than the baseline allows and to assume mobility covered it when it did not.
The cloud or provider has to be on the authorized list for mobility to apply. Moving licensed SQL to a hoster that is not authorized, or to a cloud configuration the benefit does not cover, breaks the move. The destination matters as much as the license, and the list is not the same as the set of providers willing to host you.
The correct mobility position is a deliberate inventory of the licenses you already hold, matched against the workloads that are moving, so that owned licenses cover the migration before any new purchase is contemplated. The recovery is usually substantial, because cloud migrations are where mobility is most often forgotten.
Before a cloud migration buys a single SQL license at platform rates, we inventory the core based licenses already owned with active software assurance and apply them through mobility to the workloads moving. The hybrid benefit on Azure frequently offsets the majority of the SQL cost of a migration, turning a large new spend into a near zero one for the database layer. The licenses were already paid for. Mobility simply lets them do the job they were bought to do in a new location.
The mirror risk is the move that happened without the conditions being met: SA that lapsed after migration, reassignment faster than the cadence allows, or a destination that was never authorized. We validate each mobility based move against the three conditions and correct the ones that breach, either by restoring the missing SA, slowing the reassignment, or relicensing the workload deliberately. The point is to confirm every license that moved had the right to, so the migration that saved money does not quietly become the finding that costs it.
The three destinations your licenses can reach, the conditions that disqualify a move, and the inventory that covers a cloud migration with licenses you already own before you buy again. Sent on request.
We inventory the SQL licenses already on your balance sheet, apply them through mobility to cover hardware refreshes and cloud migrations, and validate every move against the conditions that keep it legitimate. The database layer of a migration stops being a new purchase and becomes a reuse of assets you already paid for.