Microsoft SPLA is the Services Provider License Agreement, Microsoft’s licensing program for service providers and ISVs that deliver eligible Microsoft software as hosted services to end customers.
For a Windows Server buyer, the practical value is simple: the hosting provider can supply the Microsoft licensing path for the hosted workload instead of requiring you to buy a standalone Windows Server license for that provider’s infrastructure. That does not mean every Microsoft product is automatically included, and it does not make activation the same thing as licensing compliance.
Raff Technologies provides Windows Server licensing through its Microsoft SPLA program. For the common hosted Windows Server Standard path, Raff currently lists the Windows license as $15/month per VM, separate from compute. Multi-user Remote Desktop Services, SQL Server, Microsoft 365 Apps, and other Microsoft products can require separate licensing.
This guide focuses on Microsoft SPLA licensing for hosted Windows Server and how to evaluate an SPLA hosting provider before buying. For the broader Raff-specific decision between SPLA, evaluation, and customer-owned licensing, see Windows Server Licensing on Raff.
Microsoft licensing rules can change and depend on the exact product, agreement, deployment model, and user access. Microsoft Product Terms, the current Services Provider Use Rights (SPUR), and the applicable customer/provider agreements control the final licensing position. This guide is practical infrastructure guidance, not legal advice.
What is Microsoft SPLA?
Microsoft describes SPLA as a licensing program for service providers and ISVs that want to license eligible Microsoft software to provide hosted software services and applications to end customers.
Current Microsoft licensing guidance confirms several important characteristics:
- SPLA agreements have a three-year term;
- eligible products are licensed for hosted service-provider use;
- product use is governed by the Services Provider Use Rights (SPUR);
- SPLA uses different licensing models depending on the product, including per-core and Subscriber Access License models;
- providers report applicable license usage on a monthly basis;
- Windows Server Standard and Datacenter remain available through the SPLA channel.
In practice, SPLA is relevant to cloud providers, MSPs, SaaS vendors, application hosts, accounting/ERP providers, and other businesses that deliver Microsoft-based software as a hosted service.
Why SPLA matters when buying a hosted Windows Server VM
A Windows VM quote has at least two separate layers:
- Infrastructure — vCPU, RAM, NVMe/SSD storage, networking, backups, support, and the VM itself.
- Microsoft licensing — Windows Server plus any additional Microsoft access rights or products required by the workload.
That separation matters because a low advertised VM price is not necessarily the total price of a licensed production Windows environment.
On Raff, the current Windows VM product page lists compute from $13.99/month and Windows Server Standard licensing through SPLA at $15/month per VM, for a current starting total of $28.99/month before optional items such as RDS access, additional storage, backups, or application-specific licensing.
The commercial value of SPLA is not that licensing disappears. It is that the provider can make the licensing path explicit and bill it as a monthly service component.
SPLA is provider-led licensing
The easiest way to understand SPLA is to ask one question:
Who supplies the Microsoft licensing rights for this hosted deployment?
With SPLA, the service provider supplies eligible Microsoft software as part of its hosted service under the provider’s Microsoft agreement and the applicable SPUR terms.
For the customer, that generally means:
- no upfront purchase of a perpetual Windows Server license just for the hosted VM;
- the Windows license can be billed with the hosting service;
- the provider handles its SPLA reporting obligations;
- the customer still needs to identify the actual products and access model used by the workload.
SPLA does not mean one Windows Server license automatically covers RDS, SQL Server, Office, Microsoft 365 Apps, or every Microsoft workload installed on the VM.
What an SPLA hosting provider should make clear before you buy
A trustworthy SPLA hosting offer should make the licensing boundary understandable before checkout, not after an audit or migration.
Ask the provider to clarify:
- whether the Windows Server license is included or a separate line item;
- which Windows Server edition/version is being supplied;
- whether the price changes with VM size;
- whether Remote Desktop Services requires separate SALs;
- how SQL Server is licensed if installed;
- whether Microsoft 365 Apps/Office are supported and under which customer rights;
- whether BYOL is available for eligible customer licenses;
- what information the customer must provide about users, products, and workload design;
- whether provider-supplied licenses remain with the provider if you migrate away.
Be cautious when a host treats activation as proof of licensing. A server can be technically activated without proving that the deployment has the correct Microsoft licensing rights.
How to verify an SPLA hosting offer commercially
For a buyer, you usually do not need to become a Microsoft licensing specialist. You do need enough clarity to avoid hidden costs and unsupported claims.
A good provider should be able to answer these questions in writing:
| Question | Why it matters |
|---|---|
| Is Windows Server licensing itemized? | Prevents a cheap compute price from hiding the license cost |
| Is the license provider-supplied or BYOL? | Determines who supplies the rights |
| Are RDS users licensed separately? | Multi-user RDS can materially change monthly cost |
| Is SQL Server included? | Usually no; SQL licensing is a separate decision |
| Does the provider distinguish test/evaluation from production? | Evaluation should not silently become the production licensing model |
| Can I bring eligible customer licenses? | Important for organizations with subscription/Software Assurance rights |
| What happens when I leave the provider? | Provider-supplied SPLA rights generally do not become your portable license |
A provider that can clearly explain these boundaries is usually easier to work with than one that simply says “Windows included.”
SPLA vs evaluation vs customer-owned licensing
Most hosted Windows buyers encounter three practical paths.
| Licensing path | Best fit | Production use | Who supplies the licensing path? |
|---|---|---|---|
| Windows Server evaluation | Lab, migration test, proof of concept | Not as the permanent production basis | Microsoft evaluation terms |
| SPLA through the provider | Hosted production workload | Yes, where eligible and correctly licensed | Hosting provider |
| Customer-owned licensing / BYOL | Organization already owns qualifying rights | Yes, when Microsoft terms permit the deployment | Customer |
Evaluation
Evaluation is useful for a short migration test, proof of concept, or application validation.
It should not become the permanent licensing basis of a business-critical production workload simply because the VM continues to run.
SPLA
SPLA is often the simpler path when:
- the workload is moving into production;
- you want the hosting provider to supply Windows Server licensing;
- your organization does not maintain its own Microsoft licensing estate;
- you do not have a clearly documented BYOL right for the hosted scenario;
- monthly provider billing is easier operationally.
Customer-owned licensing / BYOL
BYOL is not the same as “we already have a product key.”
Microsoft’s current guidance provides the Flexible Virtualization Benefit for eligible subscription licenses or licenses with active Software Assurance. That benefit can allow customers to deploy eligible software, including Windows Server, on an Authorized Outsourcer’s shared or dedicated infrastructure, subject to Microsoft Product Terms and the specific licensing requirements.
Microsoft also explicitly distinguishes Windows Server from traditional License Mobility through Software Assurance.
Before using BYOL, verify:
- the exact Microsoft licensing program;
- whether the licenses are subscription licenses or have active Software Assurance where required;
- whether the provider qualifies for the intended outsourcing scenario;
- core minimums and VM licensing requirements;
- user/device access requirements;
- whether the rights apply to the exact software deployed.
What does SPLA cover for Windows Server?
SPLA is a framework, not a single all-inclusive Windows bundle.
Microsoft’s current SPLA guidance includes a Per Core (OS) model for Windows Server. Microsoft also notes that certain Windows Server roles or functionality can require Subscriber Access Licenses.
That becomes important when a server moves from ordinary administration to a service used interactively by multiple employees or customers.
A normal Windows Server VM can support administrator access for server management. A real multi-user Remote Desktop Session Host deployment requires a separate RDS licensing decision.
RDS licensing is separate from the Windows Server license
A Windows Server license does not grant unlimited users the right to use the server as a shared remote desktop environment.
If the workload uses Remote Desktop Session Host for regular multi-user access, RDS licensing must be evaluated separately.
For Raff-hosted SPLA deployments, Raff currently lists RDS User SALs at $8/month per user for applicable multi-user deployments.
Customer-owned environments can use a different Microsoft access model where their agreement permits it.
See RDS CAL Licensing on Windows Server before quoting a multi-user RDP environment.
SQL Server is a separate licensing decision
Windows Server licensing covers the operating system. It does not automatically license SQL Server Standard or Enterprise.
If the application uses SQL Server, confirm the edition and production licensing model separately.
For example:
- SQL Server Express has free-use limits;
- SQL Server Developer is for development/testing rather than production;
- SQL Server Standard and Enterprise require appropriate production licensing;
- customer-owned SQL Server rights differ from Windows Server rights and may involve License Mobility or Flexible Virtualization depending on the scenario.
This is why a Windows VM quote and a complete Microsoft workload quote are not always the same number.
Microsoft 365 Apps and Office require separate review
Do not assume a Windows Server SPLA license gives users the right to run Microsoft 365 Apps or Office in a hosted session environment.
Desktop productivity software has separate licensing and activation requirements. Shared Computer Activation and user subscription requirements can apply independently of Windows Server and RDS.
Before migrating a business desktop workload, inventory every Microsoft product installed or accessed by users.
What Raff handles under its hosted Windows licensing path
For a standard Raff Windows Server deployment using Raff-supplied SPLA licensing, Raff handles the provider-side licensing path for the Windows Server product and the related provider reporting obligations.
The customer still controls and is responsible for the guest environment, including:
- which applications are installed;
- which users access the workload;
- whether RDS is used for multi-user access;
- whether SQL Server or additional Microsoft products are installed;
- guest OS configuration and patching;
- application security, credentials, and data;
- providing accurate workload/user information where additional licensing is needed.
That boundary matters commercially. Raff provides the cloud infrastructure and applicable provider-supplied licensing path; it does not turn a self-managed Windows VM into a fully managed application environment.
Current Raff Windows SPLA pricing
Raff currently publishes the following common licensing components:
| Component | Current published price | Notes |
|---|---|---|
| Windows VM compute | From $13.99/month | Infrastructure component; plan-dependent |
| Windows Server Standard via SPLA | $15/month per VM | Provider-supplied Windows Server licensing |
| RDS User SAL | $8/month per user | For applicable multi-user RDS deployments |
| SQL Server / other Microsoft products | Workload-dependent | Requires separate review |
These figures were checked against Raff’s live Windows VM pages on September 14, 2026. Because product pricing can change, use Windows VM and Raff pricing for the current checkout-level numbers.
A practical SPLA buying decision
Before deploying a production Windows workload, answer these questions.
1. Is this test or production?
Use evaluation licensing only when it genuinely fits a test/evaluation scenario. Establish the permanent production licensing path before employees or customers depend on the service.
2. Who supplies the Windows Server rights?
If Raff supplies them, SPLA is the provider-led path. If the customer supplies them, validate the customer’s Microsoft rights for the hosted deployment.
3. Will regular users connect through Remote Desktop Services?
If yes, quote and validate RDS licensing separately.
4. Is SQL Server installed?
If yes, identify the exact edition and production licensing model before migration.
5. Are Microsoft 365 Apps or Office installed?
If yes, validate the user subscriptions and shared-computer rights separately.
6. Are you moving from another hosting provider?
Do not assume the old provider’s SPLA licensing transfers with the VM image. Re-establish the licensing path at the destination.
7. Do you already own qualifying Microsoft licenses?
If yes, compare SPLA with BYOL under the current Flexible Virtualization Benefit and Microsoft Product Terms before paying twice for rights you may already have.
Common SPLA misunderstandings
“The VM is activated, so licensing is solved.”
Activation and licensing rights are different. Activation only proves the software accepted an activation mechanism; it does not establish that the deployment model has the correct legal rights.
“SPLA includes every Microsoft product on the server.”
It does not. Windows Server, RDS, SQL Server, Office, and Microsoft 365 Apps can each require separate licensing analysis.
“BYOL is always cheaper.”
Not necessarily. Existing licenses can reduce cost only when the customer has the correct rights and can document them. SPLA can be operationally simpler for small teams that do not manage Microsoft volume licensing.
“Windows Server uses ordinary License Mobility.”
Microsoft distinguishes Windows Server from traditional License Mobility. Eligible subscription licenses or licenses with active Software Assurance may instead use the Flexible Virtualization Benefit on qualifying Authorized Outsourcers, subject to Microsoft terms.
“A hosting provider saying ‘Microsoft licensed’ is enough.”
Ask what product is licensed, under which provider/customer model, whether RDS/SQL are separate, and how the cost appears on the invoice. Precise answers are more useful than a generic badge.
“Evaluation is fine as long as the server keeps running.”
Evaluation is a testing path, not a permanent production licensing strategy.
Why SPLA matters for MSPs and hosted application providers
SPLA is particularly useful when an MSP, SaaS vendor, ERP/accounting provider, or software host needs to deliver a Microsoft-based environment without asking every customer to solve the hosting license model independently.
Common examples include:
- hosted Windows business applications;
- RDS-based accounting or ERP environments;
- IIS and .NET application hosting;
- Windows-based SaaS infrastructure;
- SQL Server-backed applications;
- customer Windows environments operated by an MSP.
For these workloads, licensing clarity is a commercial trust issue. The buyer should understand the VM cost, the Microsoft licensing cost, which access licenses are additional, and what happens if the workload changes.
Should you use Raff SPLA or BYOL?
Choose Raff-supplied SPLA when you want a straightforward hosted production license, do not have qualifying customer-owned rights, or prefer the provider to supply and report the Windows Server licensing component.
Evaluate BYOL when your organization already has eligible Microsoft subscription licenses or licenses with active Software Assurance and the Flexible Virtualization Benefit applies to the intended deployment.
Use evaluation licensing only for genuine test, proof-of-concept, or migration-validation scenarios.
If you are unsure, list the Windows Server version, user count, RDS requirement, SQL Server edition, Microsoft 365/Office requirement, and any customer-owned licenses before requesting a quote. That information is enough to avoid most obvious licensing mismatches before migration.