Last updated: July 2026
Microsoft's SPLA hosting changes in 2025 caught a lot of IT teams off guard, and the confusion hasn't fully cleared going into 2026. The short version: Windows Server and Remote Desktop Services workloads can no longer be licensed under SPLA on four specific "Listed Providers," but SPLA itself is very much alive everywhere else. This is the practical rundown of the SPLA hosting changes 2026 landscape: what changed, who it actually affects, and why independent European hosts running their own hardware remain a fully valid path for Windows Server hosting.
SPLA Hosting Changes 2026: What Actually Changed on October 1, 2025
Effective October 1, 2025, Microsoft updated its Services Provider License Agreement (SPLA) terms to bar service providers from licensing Windows Server, Remote Desktop Services, and related Microsoft server workloads when those workloads run on four named "Listed Providers": AWS, Azure, GCP, and Alibaba Cloud. In practice, a hosting company can no longer use its own SPLA agreement to license Windows Server or RDS instances that are physically running on those four hyperscale clouds. The restriction is specific to that licensing mechanism on those specific platforms — it is not a blanket statement that Windows Server hosting is going away or becoming harder to get.
Why the Restriction Targets "Listed Providers" Only
The change is narrowly scoped. Microsoft's own cloud, Azure, competes directly with the SPLA program in this instance, and AWS, GCP, and Alibaba are the other large-scale public clouds where third-party providers were reselling SPLA-licensed Windows Server capacity at volume. Restricting SPLA on those four platforms pushes that specific licensing model away from hyperscaler infrastructure. Everything outside that named list — independent hosting companies, colocation providers, and any operator running its own physical servers and datacenters — is unaffected by the October 2025 change. That distinction is the whole story, and it is the one most secondary coverage of the SPLA hosting changes glosses over.
SPLA Hosting Is Still Legal on Independent Infrastructure
This is worth stating plainly because it gets lost in the noise: SPLA hosting is still legal, and still a normal, supported way to run licensed Microsoft workloads, as long as the hosting provider owns and operates its own hardware rather than reselling capacity on one of the four Listed Providers. Independent hosts were never part of the restriction. If a provider runs its own racks in its own (or a partner's) datacenter — rather than reselling AWS, Azure, GCP, or Alibaba instances — the October 2025 policy simply does not apply to them.
None of this should be read as formal legal or licensing advice. Licensing agreements, SPLA reporting obligations, and edge cases vary by reseller and region, so any organization making a licensing decision around this change should confirm the specifics with its own Microsoft licensing advisor or SPLA reseller before signing a contract.
What It Means for Windows Server Hosting in Europe
For companies running Windows Server hosting in Europe, the practical impact of the 2025 SPLA changes comes down to where the workload physically sits, not whether Windows Server hosting is viable at all. Two paths remain fully open in 2026:
- Bring-your-own-license (BYOL): deploy Windows Server on infrastructure the organization already holds licenses for, on any hosting provider — including independent hosts, regardless of the Listed Provider restriction.
- Independent SPLA-licensed hosting: work with a provider that runs its own owned hardware and can license Windows Server/RDS workloads under its own SPLA agreement, since that arrangement was never touched by the October 2025 change.
What has genuinely gotten harder is licensing Windows Server through SPLA on top of AWS, Azure, GCP, or Alibaba resale capacity — that specific combination is the one now closed off. Everything else, including running Windows workloads on EU-based KVM virtual machines or dedicated hardware, continues exactly as before.
Listed Providers vs. Independent Hosts: The Practical Difference
| Factor | Listed Providers (AWS, Azure, GCP, Alibaba) | Independent host on owned hardware |
|---|---|---|
| SPLA licensing for Windows Server/RDS | Restricted since Oct 1, 2025 | Unaffected — still valid |
| BYOL Windows Server | Generally still possible under existing cloud licensing terms | Fully supported |
| Infrastructure ownership | Hyperscaler-owned | Provider owns and operates the hardware |
| Datacenter location control | Fixed regions set by the cloud | Provider-selected EU/US locations |
Practical Steps for Teams Reassessing Their Setup
Organizations reviewing their Windows Server footprint after the SPLA Listed Providers restriction should work through a short checklist before moving anything:
- Confirm which of the four Listed Providers, if any, current Windows Server or RDS workloads sit on today.
- Separate BYOL deployments (unaffected) from SPLA-metered deployments (affected only on the four named clouds).
- Evaluate independent hosts running owned hardware and their own datacenters as a migration target for SPLA-dependent workloads, including EU locations such as Frankfurt or Vienna for latency and data-residency reasons.
- Confirm the specific licensing path with a Microsoft licensing advisor or SPLA reseller before migrating.
Where X-Zone Servers Fits Into the 2026 Picture
X-Zone Servers runs its own infrastructure — full-root KVM virtualization on hardware the company operates itself, across 12 datacenter cities spanning Europe and the US. That matters directly in this context: X-Zone is not AWS, Azure, GCP, or Alibaba, so nothing about the October 2025 SPLA restriction touches deployments running on X-Zone's VPS hosting or dedicated servers. Teams running BYOL Windows Server, or working with an independent SPLA reseller for a licensed Windows Server/RDS setup, can deploy on X-Zone's infrastructure without the arrangement running into the Listed Provider clause at all.
Every VPS and dedicated plan on X-Zone includes DDoS protection at L3/4/7 and a 99.9% uptime SLA, with KVM virtualization giving full root access for whatever Windows or Linux configuration a workload needs. VPS instances deploy in under 60 seconds for teams that want to test a configuration quickly, while dedicated servers — from a Dual Xeon E5-2630 up through a Dual EPYC 9754 — deploy in about an hour for workloads that need full hardware to themselves. With 12 datacenter cities to choose from, EU-based teams can keep Windows Server workloads close to their users without ever touching a Listed Provider.
Verdict
The 2025 SPLA changes didn't end Windows Server hosting — they closed one specific licensing path on four named hyperscale clouds and left everything else, including independent hosts running their own hardware, exactly where it was. For teams that want that certainty going into 2026, X-Zone Servers offers owned-hardware KVM VPS and dedicated infrastructure across 12 European and US datacenter cities, entirely outside the scope of the Listed Provider restriction. Confirm the specific licensing arrangement with a Microsoft advisor, then build on infrastructure that isn't affected by the change in the first place.