What Licence Mobility Actually Means
Software licence mobility is the right to redeploy licences you already own — typically on-premises — into a cloud environment without buying them again. Handled well, it is one of the largest avoidable costs in any cloud migration: instead of paying for the software a second time in the cloud, you pay only for the underlying infrastructure. Handled badly, it is where enterprises discover at audit that the licences they assumed were portable were not, and face a compliance bill that erases the migration's business case. Because mobility rights are buried in product terms rather than the headline price, they belong on the same priority list as the clauses in our guide to reading a software contract.
Azure Hybrid Benefit vs License Mobility
Microsoft offers two distinct mechanisms that are routinely confused, and the confusion is expensive. Azure Hybrid Benefit (AHB) applies only to Azure and only to Windows Server and SQL Server, letting you apply existing licences with active Software Assurance to Azure infrastructure — Microsoft positions the savings at up to 85% when combined with reservations. License Mobility through Software Assurance is the broader, older mechanism that lets eligible application-server products move to a third-party cloud such as AWS or Google Cloud. Both require active Software Assurance or an equivalent subscription; without it, neither benefit exists, which is why dropping Software Assurance to save cost can quietly destroy your cloud deployment rights.
| Azure Hybrid Benefit | License Mobility (SA) | |
|---|---|---|
| Where it applies | Azure only | Authorised third-party clouds |
| Products | Windows Server, SQL Server | SQL Server, Exchange, SharePoint and other app servers |
| Requires Software Assurance | Yes (or subscription) | Yes |
| Windows Server eligible | Yes | No |
Eligible Products and the Windows Server Gap
The eligibility map contains a trap that catches even experienced teams. Application-server products — SQL Server, Exchange Server, SharePoint Server and similar — are eligible for License Mobility through Software Assurance and can move to an authorised third-party cloud. Windows Server is not. It cannot use License Mobility to a third-party cloud and must instead rely on Azure Hybrid Benefit (Azure only) or be provided through an authorised outsourcer arrangement. Enterprises that plan an AWS or Google Cloud migration assuming their Windows Server estate is portable discover the gap only when the licences will not move — a discovery that can reshape the whole migration architecture and is far cheaper to make at the negotiating table than in production.
The savings at stake make the eligibility detail worth the effort. Applied properly to a SQL Server estate, Azure Hybrid Benefit can remove the entire licence component of the cloud cost, and Microsoft positions the combined saving against pay-as-you-go at up to 85% once reservations are stacked on top. On a substantial SQL Server footprint that is the difference between a cloud migration that pays for itself and one whose business case never closes. The mistake enterprises make is to model the migration on infrastructure cost alone, discover the doubled licence cost only at the first true-up, and then have no contractual room to fix it.
The Listed Provider Trap
Microsoft's Listed Provider rules, tightened from October 2022, restrict how certain licences can be deployed on the largest competing clouds — AWS, Google and Alibaba among them. Licences bought after the cut-off carry different outsourcing rights from older ones, and the distinction decides whether a given workload can use bring-your-own-licence terms on a Listed Provider at all. This is a deliberately complex area that vendors are not motivated to clarify, and it intersects directly with the pricing pressure pushing buyers toward the vendor's own cloud. Establishing exactly which of your licences carry which rights, before you architect a migration, is the difference between a compliant move and an audit exposure.
Where bring-your-own-licence rights are constrained, two alternative routes are worth pricing. A dedicated-host arrangement can restore eligibility for some products by giving you physically isolated hardware, at a premium that is sometimes still cheaper than re-licensing. Failing that, consuming the software through the cloud provider's own licence-included or SPLA-style offering removes the portability question entirely, trading the capital value of your owned licences for operational simplicity. Neither is automatically right; the point is to model all three paths — mobility, dedicated host, and licence-included consumption — before committing, rather than discovering the constraint after the architecture is fixed.
Mobility rights are not free — they are paid for through Software Assurance. Drop the maintenance to save money and you can silently forfeit the right to run those licences in the cloud at all.
What to Negotiate Into the Agreement
Several mobility protections are negotiable at agreement signing or renewal. Secure written confirmation of mobility rights for each product family you intend to move, rather than relying on general product-terms references that the vendor can revise. Where Software Assurance is the gatekeeper, negotiate its cost as part of the overall commercial package rather than as an afterthought, and weigh it against the maintenance-reduction approach in our guide to negotiating maintenance reductions — because here the maintenance is buying you something concrete. For multi-cloud strategies, confirm dedicated-host and outsourcing rights explicitly, and capture them in the contract rather than in a slide. These are core terms of any cloud contract negotiation, not technical footnotes.
Reviewing Mobility Before You Move
The practical sequence is to inventory the licences you intend to migrate, map each to its mobility mechanism and eligibility, identify the Software Assurance status that underpins those rights, and resolve any Listed Provider questions before committing to a target cloud. A migration business case built on an untested mobility assumption is a business case waiting to be reopened by an audit. To review your estate's mobility rights before a cloud move, or to negotiate them into an upcoming agreement, request a confidential briefing.