The question arrives in almost every Windows Server order: "We already pay for Windows Server and SQL Server. Can we use those licences on your servers instead of renting yours?" The answer used to be a flat no for Windows Server and a conditional yes for SQL Server. Since October 2022 it is a conditional yes for both, and the conditions are about your licence, your Software Assurance and the identity of the provider, not about the server. This guide lays out the three routes Microsoft offers for Windows Server and SQL Server on a hosting provider's shared hardware, who qualifies for each, and when renting a licence under the provider's SPLA agreement is simply the cheaper option. The rules are read from Microsoft's published licensing documents on 3 November 2026; they change, so confirm the current terms with your Microsoft reseller before you order.
The decision table
Start with what you hold and whether it carries active Software Assurance (SA) or is a subscription licence. Then read across to what Microsoft allows on a hosting provider's shared servers, meaning servers that also run other customers' virtual machines, which describes every VPS, dedicated VPS and managed cloud server.
| What you own | Software Assurance | On a shared host (not a Listed Provider) | On Azure, AWS, Google or Alibaba | Route |
|---|---|---|---|---|
| Windows Server Standard or Datacenter | Active SA or subscription | Allowed | Not allowed (except Azure Hybrid Benefit on Azure) | Flexible Virtualization Benefit |
| Windows Server Standard or Datacenter | None (OEM, retail, expired SA) | Not allowed | Not allowed | Rent under the provider's SPLA |
| SQL Server Standard or Enterprise | Active SA or subscription | Allowed | Allowed only via License Mobility to an Authorized Mobility Partner, or Azure Hybrid Benefit | Flexible Virtualization Benefit or License Mobility through SA |
| SQL Server Standard or Enterprise | None | Not allowed | Not allowed | Rent under the provider's SPLA |
| SQL Server Web | Cannot be owned | Rent only | Rent only | SPLA |
| Windows 10 or 11 Pro | Not applicable | Your own key on a VM, provider cannot rent it | Varies by provider | Bring your own key |
| RDS CALs, SQL CALs | Active SA | Allowed with the server licence they attach to | Varies | Flexible Virtualization Benefit, or rent RDS SALs |
The single most common disappointment is the OEM Windows Server licence that came with a physical server. It is tied to that hardware, has no Software Assurance, and cannot move to any provider. The second is a SQL Server licence bought through a volume agreement years ago and never renewed under SA: it is a perpetual licence, but it is a perpetual licence for your own premises only.
Route one: the provider rents you the licence under SPLA
The Services Provider License Agreement is Microsoft's programme for companies that host Microsoft software for third parties. The provider reports what ran each month and pays Microsoft per core (Windows Server, SQL Server) or per user (Remote Desktop Services, SQL Server by user). The customer never owns a licence, never holds a product key and reports nothing. The licence starts when the server starts and ends when it is cancelled.
At MassiveGRID this is the "Licence +$6.31/vCPU" option on a Windows VPS and the Windows Server Standard and SQL Server Web options on the SQL Server host: Windows Server Standard at $6.00 per vCore and SQL Server Web at $8.50 per vCore a month on top of the Linux rate, and RDS user licences at $8.90 per user a month on any Windows server. SQL Server Standard is on the Virtual Private Cloud order form at $120.00 per vCore and is quoted on the managed server. Everything is billed on the same invoice as the server and converted in place if you started on the 180-day evaluation.
SPLA is the right route when you have no Software Assurance, when the server will live for less than two or three years, when you want the licence to scale with the server, or when you need an edition you cannot own (Web). It is also the only route that lets you resell: if you host a SaaS product for your own customers, the SPLA licence covers their use, which your volume licence does not. The SPLA hosting page explains the programme from the provider's side.
Route two: the Flexible Virtualization Benefit
From 1 October 2022 Microsoft changed its outsourcing terms. Customers with licences that carry active Software Assurance, or subscription licences, may run that software on the shared servers of any outsourcer, with one exclusion: the Listed Providers. Microsoft's Listed Providers are Microsoft itself (Azure), Alibaba, Amazon Web Services and Google. On those four, bring-your-own is limited to the routes they negotiate (Azure Hybrid Benefit, License Mobility for SQL Server). On every other provider, including MassiveGRID, the Flexible Virtualization Benefit applies.
What it changed in practice:
- Windows Server became portable. Before 2022 Windows Server had no License Mobility at all, so your own Windows Server licence could only run on hardware dedicated to you. Now, with SA, it can run on a shared host.
- Licensing by virtual machine. Under the benefit, Windows Server Standard and Datacenter with SA can be licensed per virtual machine (a minimum of 8 core licences per VM, Microsoft's figure) rather than for every physical core in the host, which is what made shared hosting impossible before.
- SQL Server too. SQL Server Standard and Enterprise with SA may run on the same basis, per VM, with the usual minimum of 4 core licences per virtual machine.
- CALs follow. Where the server is reached by named users or devices, the Windows Server CALs and RDS CALs you hold with SA cover them on the hosted server.
What stays with you: the licence, the SA renewal, the product key and the obligation to prove compliance in an audit. The provider does not hold or report your licence; on our side the server is simply ordered on the "180-day evaluation" option and you activate it with your own key or KMS. Tell us before ordering that you intend to bring a licence, and we will confirm in writing that the server is not on a Listed Provider and note it on the account, which is the document an auditor asks for.
The constraint buyers miss is SA continuity. The benefit depends on Software Assurance being active on the day the software runs. Let SA lapse and the deployment becomes non-compliant that day, with the fallback being to buy the licence again or move to SPLA. Budget the SA renewal as part of the server's running cost, not as an optional extra.
Route three: License Mobility through Software Assurance
License Mobility through SA predates the Flexible Virtualization Benefit and still exists alongside it. It covers application servers (SQL Server, Exchange, SharePoint, Dynamics and others) but never Windows Server, and it requires the provider to be an Authorized Mobility Partner. The customer completes Microsoft's License Mobility verification form, the provider signs it, and Microsoft records the deployment. It is the route that matters on the Listed Providers, where the Flexible Virtualization Benefit does not reach, and it is why "bring your own SQL Server licence to AWS" works while "bring your own Windows Server to AWS" does not.
On a provider that is not a Listed Provider, the Flexible Virtualization Benefit is broader and simpler, because it covers Windows Server and needs no verification form. Some procurement teams still prefer the License Mobility paperwork for SQL Server because it produces a Microsoft-acknowledged record. If your compliance process asks for that record, ask us whether to use that route before the order rather than after.
The economics: rent or bring?
Renting under SPLA is a monthly cost with no commitment. Owning is a capital cost plus Software Assurance at roughly a quarter of the licence price per year (Microsoft's published SA rate for most server products; your reseller's quote is the figure that counts). The comparison depends on how long the server lives and how many cores it has.
| Scenario | Renting under SPLA at MassiveGRID | Bringing your own | Usually cheaper |
|---|---|---|---|
| Windows Server, 2 vCores, 18 months | $12.00 a month on the managed server ($6.00 per vCore), about $216 over the period | A 16-core minimum Windows Server Standard licence plus SA, far more than the server will ever cost | Rent |
| Windows Server, 8 vCores, 5 years, SA already paid for other reasons | $48.00 a month, $2,880 over five years | Nothing extra if the licence and SA exist and are unused | Bring |
| SQL Server Web, any size | $8.50 per vCore a month | Not possible | Rent |
| SQL Server Standard, 8 vCores, 4 years | $120.00 per vCore on the VPC order form, $960 a month | 8 core licences bought once plus 4 years of SA; usually less than 48 months of SPLA | Bring, if SA is affordable |
| Hosting your own customers (SaaS, resold desktops) | Covered | Not permitted on volume licences | Rent |
The pattern is consistent: SPLA wins on small servers, short lives and anything resold; owned licences win on large SQL Server Standard or Enterprise deployments that will run for years and already sit under an SA agreement. Windows Server itself is cheap enough under SPLA that bringing it rarely saves money unless the licence is already paid for.
The audit angle
Microsoft audits volume-licensing customers, not SPLA customers: under SPLA the provider carries the compliance and the reporting. The moment you bring a licence, you carry it. Three habits keep that manageable. Keep a one-page register per hosted server: licence, agreement number, SA expiry, core count, the provider's written confirmation that it is not a Listed Provider, and the date you activated. Never mix a rented SPLA server licence with your own CALs, or your own server licence with rented SALs, without a reseller confirming the combination; mixed models on one server are the most common audit finding. And re-check the Product Terms when SA renews, because the Flexible Virtualization Benefit is a term in those documents, not a feature of the server.
If any of this is more administration than the saving is worth, the rented licence is the honest answer. Order the server with the licence included, see the line in the configurator, and let the reporting be our problem.
Frequently Asked Questions
Can I use my own Windows Server licence on a MassiveGRID server?
Yes, if the licence carries active Software Assurance or is a subscription licence, under Microsoft's Flexible Virtualization Benefit, because MassiveGRID is not one of Microsoft's Listed Providers. OEM and retail licences without Software Assurance cannot move to any shared host. Order the server on the 180-day evaluation and activate it with your own key. Confirm the current terms with your Microsoft reseller.
Can I bring a SQL Server licence?
SQL Server Standard or Enterprise with active Software Assurance can run on our servers under the Flexible Virtualization Benefit, or through License Mobility through Software Assurance if your compliance process wants Microsoft's verification record. SQL Server Web edition cannot be owned, so it is only available rented through our SPLA agreement.
Who are Microsoft's Listed Providers?
Microsoft (Azure), Alibaba, Amazon Web Services and Google. The Flexible Virtualization Benefit excludes them, so bring-your-own licensing there depends on their own programmes such as Azure Hybrid Benefit or License Mobility for SQL Server. Every other hosting provider, including MassiveGRID, is covered by the benefit.
What happens if my Software Assurance expires while the server is running?
The right to run the licence on a shared host ends with the Software Assurance. You would need to renew SA, buy the licence again with SA, or switch the server to a rented SPLA licence, which we can do in place without reinstalling.
Is it cheaper to rent the licence or bring my own?
Renting is usually cheaper for small servers, servers that live less than two or three years, and anything you resell to your own customers. Bringing your own is usually cheaper for SQL Server Standard or Enterprise on 8 or more cores over several years when the licences and SA already exist. Windows Server under SPLA costs $6.00 per vCore a month on the managed server, which an owned licence rarely beats unless it is already paid for.
Rent the licence or bring yours, on the same server
Every MassiveGRID Windows server starts on Microsoft's 180-day evaluation for your own key, or adds Windows Server Standard, SQL Server Web and RDS user licences under our SPLA agreement, shown as separate lines before you order. Tell us you are bringing a licence and we confirm the Listed Provider position in writing.
See SPLA and licensing options