Licence Mobility Through Software Assurance: Enterprise Guide

What Licence Mobility Through SA Actually Does

Licence Mobility through Software Assurance is a deployment right that allows enterprises to move SA-qualified server application licences to shared server infrastructure — including third-party hosted environments, cloud services, and co-location facilities — without purchasing additional licences. Without Licence Mobility, running a licensed Microsoft server application on hardware shared with other tenants would require a separate "hosted" licence, typically at significant additional cost. With Licence Mobility active, you can deploy your on-premises SA-covered licences in hosted environments as if they were on dedicated infrastructure you own.

This benefit is particularly valuable for enterprises using managed service providers (MSPs), co-location hosting, or hybrid cloud arrangements involving non-Azure infrastructure. For Azure-specific deployments, Azure Hybrid Benefit (AHUB) is the more direct mechanism — see our SQL Server AHUB strategy guide. Licence Mobility fills the gap for hosted environments outside Azure and for products not covered by AHUB. For the complete SA context, see the Microsoft Software Assurance guide.

Which Products Are Eligible for Licence Mobility

Not all Microsoft products qualify for Licence Mobility through SA. Eligibility is limited to specific server application products. Desktop applications (Office, Windows) are excluded — they have separate deployment rights under different SA provisions.

The Authorised Outsourcer Requirement

Licence Mobility only applies when your hosting provider is a Microsoft "Authorised Outsourcer" — a partner that has signed a specific agreement with Microsoft confirming they will honour the Licence Mobility framework and will not charge customers for Microsoft licences that the customer is providing under SA. This requirement is where most Licence Mobility activations fail.

Major public cloud providers (AWS, Google Cloud Platform) and large MSPs are typically Authorised Outsourcers. Smaller regional MSPs and co-location providers may or may not hold the agreement — you need to verify this before assuming Licence Mobility applies. If your hosting provider is not an Authorised Outsourcer, Licence Mobility cannot be applied, and you would need either to use licences included in the hosted service pricing or to negotiate an arrangement where the provider obtains the Authorised Outsourcer status.

Verification process: Ask your hosting provider directly whether they are a Microsoft Authorised Outsourcer and to confirm in writing. Microsoft publishes a list of Authorised Outsourcers, but it is not always current — direct confirmation from the provider is more reliable.

How to Activate Licence Mobility

Licence Mobility activation is a four-step process involving both your organisation and the hosting provider. Unlike Azure Hybrid Benefit (which is activated directly in the Azure portal), Licence Mobility requires formal documentation between the enterprise and the outsourcer.

Step 1: Verify SA Coverage

Confirm active SA on the specific product licences you intend to move to the hosted environment. Pull SA entitlement records from VLSC. The SA must be active — lapsed SA removes Licence Mobility eligibility. Note the specific product, edition, and licence count.

Step 2: Confirm Authorised Outsourcer Status

As described above, verify your hosting provider holds Authorised Outsourcer status. Obtain written confirmation. This step must be completed before proceeding — if the provider is not an Authorised Outsourcer, the remaining steps are not relevant.

Step 3: Complete the Licence Verification Form

The enterprise submits a "Licence Verification Form" (LVF) to the Authorised Outsourcer confirming the licences being moved, the SA coverage details, and the term of deployment. The LVF format is defined by Microsoft and must include specific fields. The outsourcer countersigns the form acknowledging receipt and confirming the deployment conditions.

This documentation requirement is where activations stall most frequently. The LVF process requires coordination between the enterprise's licence administrator, the hosting provider's account team, and sometimes Microsoft directly. Build 2–4 weeks lead time into any hosting arrangement that requires Licence Mobility activation.

Step 4: Retain Documentation for Audit

Both the enterprise and the hosting provider must retain the completed LVF and evidence of SA coverage for Microsoft audit purposes. Licence Mobility without proper documentation is not compliant — the right is earned through the documentation process, not assumed. Store records alongside your broader licence compliance documentation. For audit defence context, see our Microsoft licence compliance audit guide.

Licence Mobility vs. Azure Hybrid Benefit: Choosing the Right Tool

Enterprises with hybrid infrastructure need to understand which SA benefit applies to which deployment scenario to avoid both compliance gaps and missed savings.

Quantifying the Commercial Value

The financial value of Licence Mobility depends entirely on the alternative cost — what your hosting provider would charge for equivalent Microsoft licences in the absence of your SA-covered deployment rights.

Managed service providers typically build Microsoft licences into their service pricing through two models: SPLA (Services Provider License Agreement) pricing, where the MSP licences Microsoft products monthly and passes the cost through as a service component, or dedicated licence inclusion, where specific licences are included in the service contract price. SPLA pricing for SQL Server Enterprise runs approximately $400–$800/server/month depending on provider margin; for SQL Server Standard, approximately $100–$250/server/month.

For an enterprise with 80 SQL Server Standard instances on managed infrastructure: without Licence Mobility, SPLA-equivalent cost = $8,000–$20,000/month ($96,000–$240,000 annually). With Licence Mobility (and SA-covered licences), this cost is eliminated. Against SQL Server SA costs of approximately $80,000–$120,000 annually for 80 instances, Licence Mobility alone generates positive ROI on SA for this deployment pattern.

This is why SA ROI analysis must be deployment-specific. An enterprise with no hosted workloads receives zero value from Licence Mobility, while an enterprise with significant managed hosting receives savings that can justify significant SA spend on their own. See our SA ROI calculation framework for the complete analysis methodology, and the EA negotiation complete guide for renewal context.