Microsoft SPLA is the Microsoft Services Provider License Agreement, a licensing program that lets service providers and ISVs license eligible Microsoft software to deliver hosted software services and applications to end customers.
For a hosted Windows VM buyer, SPLA matters because the licensing path is part of the production architecture. Raff Technologies is a Microsoft SPLA Partner, so Raff can provide eligible hosted Microsoft software licensing through its SPLA agreement where applicable. That gives customers a provider-supplied path for Windows workloads without assuming that every existing Microsoft license can simply be moved into a third-party cloud.
This guide explains the practical difference between SPLA, evaluation licensing, and customer-owned licensing for hosted Windows VMs. It is informational, not legal advice; Microsoft Product Terms, the Services Provider Use Rights, and the customer's own agreement control the final licensing position.
Microsoft SPLA is provider-led hosted licensing
Microsoft describes SPLA as a program for service providers and software companies that want to license eligible Microsoft products to provide software services and hosted applications to end customers. Eligible products can be licensed on a monthly basis during the provider's three-year SPLA agreement term, with product-specific use rights defined by Microsoft's Services Provider Use Rights.
The important word for a buyer is provider-led.
Under SPLA, the hosting provider is using its Microsoft agreement to supply eligible Microsoft software as part of a hosted service. The customer does not need to treat the VM as if it were ordinary unlicensed infrastructure and then solve the Microsoft licensing question independently afterward.
That does not mean every Microsoft product or every use case is automatically covered. Windows Server, Remote Desktop Services, SQL Server, Microsoft 365 Apps, and other Microsoft products can have different licensing rules. SPLA is the framework; the exact product and access model still matter.
Microsoft's current program pages also distinguish SPLA from customer-owned licensing options. The provider licensing route and the customer's own license rights are separate decisions.
Hosted Windows VMs have three practical licensing paths
For most Raff Windows VM buyers, the decision starts with three practical paths.
| Licensing path | Best fit | Production use | Who supplies the license path? |
|---|---|---|---|
| Evaluation | Lab, test, proof of concept | No | Microsoft evaluation terms |
| SPLA through provider | Hosted production workload | Yes, where the product/use case is eligible | Raff as service provider |
| Customer-owned licensing | Customer already has eligible Microsoft rights | Yes, when Microsoft terms permit the deployment | Customer |
The paths are not interchangeable.
A Windows Server evaluation image is useful for testing and technical validation. It should not become the permanent licensing foundation for a business workload simply because the VM is already running.
SPLA is usually the cleanest option when the customer wants the provider to supply the hosted Windows Server licensing path. Customer-owned licensing can be appropriate when the organization already has eligible subscription licenses or licenses with active Software Assurance and the deployment meets Microsoft's outsourcing terms.
The first question should therefore be: Is this VM a temporary evaluation environment or a production service? The second is: Who is supplying the Microsoft license rights?
SPLA and BYOL use different Microsoft rights
SPLA and BYOL solve different licensing problems.
SPLA is based on the service provider's agreement with Microsoft. Raff supplies eligible hosted Microsoft software licensing to the customer under that provider model.
BYOL is based on the customer's own Microsoft license rights. The customer must confirm that the specific licenses, coverage, product, and hosting scenario permit deployment on the provider's infrastructure.
A key distinction matters for Windows Server: Windows Server is not simply moved to a hosting provider under traditional License Mobility through Software Assurance. Microsoft's current License Mobility guidance lists eligible application-server products such as SQL Server, Exchange Server, SharePoint Server, System Center servers, and Dynamics products, while stating that Windows Server operating system licenses remain subject to their own terms.
For Windows Server, Microsoft now documents the Flexible Virtualization Benefit. Customers with eligible subscription licenses or licenses with active Software Assurance can deploy covered software, including Windows Server, on an Authorized Outsourcer's shared or dedicated servers, subject to the Product Terms and licensing requirements. Microsoft generally defines an Authorized Outsourcer as a provider that is not a Listed Provider and is not using a Listed Provider as its datacenter provider.
That means “BYOL” should never be reduced to “we already own a Windows key.” The real questions are:
- Is the license a qualifying subscription or covered by active Software Assurance?
- Does the Flexible Virtualization Benefit apply?
- Is the host an eligible Authorized Outsourcer for the scenario?
- Are the Windows Server licensing minimums and assignment rules satisfied?
- Are separate Microsoft products on the VM licensed correctly?
For the current Raff-specific paths, use Windows Server Licensing on Raff: Evaluation, SPLA, and BYOL Explained.
RDS, SQL Server, and Microsoft 365 remain separate decisions
A licensed Windows Server VM does not automatically license every Microsoft workload installed on it.
Remote Desktop Services
Windows Server includes administrative remote access for server management, but a multi-user Remote Desktop Services environment introduces its own access licensing requirements. If the VM will serve multiple regular users through RDS, decide the RDS licensing model before the environment becomes operational.
See RDS CAL Licensing on Windows Server for the dedicated decision path.
SQL Server
SQL Server has its own editions and licensing rules. SQL Server licensing should be treated separately from the Windows Server operating-system license. Customer-owned SQL Server licenses can also have different mobility rights from Windows Server itself; Microsoft's License Mobility program specifically covers eligible application-server products such as SQL Server when the required conditions are met.
Microsoft 365 Apps and Office
Desktop productivity software has separate hosted-use and activation requirements. Do not assume that a retail Office license or a Windows Server license automatically permits a shared hosted Office environment.
The practical rule is simple: list every Microsoft product in the workload, then validate each product's licensing path.
The licensing decision framework starts with workload use
Use this framework before moving a Windows VM into production.
| Situation | Recommended starting path | What to verify |
|---|---|---|
| Testing Windows Server | Evaluation | Non-production use and evaluation term |
| Production Windows business app | SPLA through Raff | Eligible Windows Server licensing and application requirements |
| Existing Microsoft customer with SA/subscriptions | Review BYOL | Flexible Virtualization Benefit and Product Terms |
| Multi-user RDP | SPLA/BYOL plus RDS review | User/device access licensing |
| SQL Server workload | Windows path plus SQL licensing | SQL edition, cores, mobility or SPLA terms |
| Microsoft 365 Apps on hosted desktop | Separate M365 licensing review | Eligible subscription and activation model |
| Unclear existing licenses | Do not assume BYOL | Validate agreement and coverage before production |
Choose SPLA through Raff when:
- the workload is production;
- you want the provider to supply eligible Microsoft licensing;
- you do not have a clearly documented customer-owned license path;
- predictable monthly hosted licensing is operationally simpler.
Review customer-owned licensing when:
- your organization already has Microsoft subscription licenses or active Software Assurance;
- your licensing team can verify the relevant Product Terms;
- the Flexible Virtualization Benefit or another applicable right supports the hosted deployment;
- you want to use existing licensing investments rather than provider-supplied SPLA licensing.
Stay on evaluation only when:
- the VM is genuinely for testing, learning, or proof-of-concept work;
- production users and production data do not depend on it;
- you have a plan to convert or replace the environment before the evaluation basis becomes inappropriate.
Raff uses SPLA as a production licensing option
Raff Windows VMs support Windows Server workloads with RDP and administrator access. Raff's current Windows pages list Windows Server 2019, 2022, and 2025 and provide an evaluation path for testing before a production licensing decision is finalized.
For production workloads, Raff's SPLA relationship provides a provider-led Microsoft licensing route where applicable. The accurate statement is that Raff LLC is a Microsoft SPLA Partner and can provide eligible hosted Microsoft software licensing through its SPLA agreement. That should not be expanded into a claim that Microsoft endorses every Raff service, certifies every customer deployment, or that every Microsoft product is automatically included.
From Raff's operating side, licensing is treated as a deployment input rather than a cleanup task. A Windows workload should be reviewed together with:
- Windows Server version;
- number and type of remote users;
- SQL Server or other Microsoft applications;
- VM size and storage;
- backup and recovery requirements;
- customer-owned license rights, if any;
- whether the environment is test or production.
Current Raff Windows VM plans start at $9.99/month for infrastructure. Microsoft licensing can add separate cost depending on the selected licensing path and workload, so buyers should not treat the base VM price as the complete cost of a licensed production Windows environment.
Use Raff Windows VMs for the infrastructure options and Raff pricing for current plan pricing.
Common licensing mistakes create avoidable risk
The most common mistake is assuming that a Windows activation key proves the workload is correctly licensed. Activation and licensing rights are related but not identical questions.
Another mistake is using a non-production evaluation environment after the workload has become operationally important. If employees, customers, billing, accounting, ERP, tax, or other business processes depend on the VM, the licensing model should be explicitly production-ready.
A third mistake is treating BYOL as universal. Customer-owned Windows Server licenses require the correct rights for the hosted scenario. For current Microsoft commercial licensing, the Flexible Virtualization Benefit is the relevant concept for many Windows Server deployments on Authorized Outsourcers; traditional License Mobility should not be cited as if it automatically covers the Windows Server OS.
A fourth mistake is forgetting the applications above Windows Server. RDS, SQL Server, Microsoft 365 Apps, and third-party business software may each add licensing requirements of their own.
Finally, do not rely on old blog posts when the Product Terms have changed. Microsoft licensing evolves. Check the current SPLA documents, Product Terms, Flexible Virtualization guidance, and the relevant product terms when the licensing decision is material.
Best practices keep hosted Windows licensing explainable
- Classify the environment first. Decide whether it is evaluation, staging, or production before choosing the license path.
- Name every Microsoft product. Windows Server licensing does not automatically cover RDS, SQL Server, Microsoft 365 Apps, or other software.
- Separate SPLA from BYOL. Provider-supplied SPLA rights and customer-owned rights come from different agreements.
- Verify Windows Server BYOL under current outsourcing terms. Do not label Windows Server as ordinary License Mobility without checking the Flexible Virtualization Benefit and Product Terms.
- Document the user model. Administrative RDP and multi-user RDS are different licensing scenarios.
- Keep licensing evidence with infrastructure records. Record the selected path, customer-owned rights if applicable, and who approved the production licensing decision.
- Re-check terms when the workload changes. Adding SQL Server, more remote users, Microsoft 365 Apps, or a new hosting arrangement can change the licensing analysis.
Conclusion
Microsoft SPLA gives service providers a structured way to license eligible Microsoft software for hosted services. For a Windows VM buyer, the practical advantage is a provider-supplied production licensing path when the customer does not want to rely on its own Microsoft licensing rights.
The alternative is customer-owned licensing, but Windows Server BYOL should be evaluated under Microsoft's current outsourcing rules, including the Flexible Virtualization Benefit where applicable—not treated as generic License Mobility. RDS, SQL Server, and Microsoft 365 Apps remain separate licensing decisions.
Raff can provide eligible Microsoft software licensing through its SPLA agreement for hosted workloads. Before production, decide whether the VM is evaluation, SPLA-licensed, or supported by verified customer-owned rights, then document the applications and users that depend on it.