Windows Server Licensing in SPLA

If SQL Server is the engine of the hosting world, Windows Server is the chassis. It is the foundation of almost every Microsoft-based offering. While it may seem straightforward compared to databases, Windows Server licensing in the Services Provider License Agreement (SPLA) has its own set of distinct rules regarding physical cores, virtualization density, and the new "Bring Your Own License" options.

Below is your guide to navigating the Core model, avoiding the "passive" trap, and leveraging the Flexible Virtualization Benefit.

In the world of SPLA, Windows Server is licensed exclusively by Physical Core. Unlike internal Volume Licensing (where you might license by VM), in SPLA you generally license the physical hardware to allow for the creation of virtual machines (VMs).

The "Rule of 8": Minimum Requirements

You cannot simply count the cores you use. You must adhere to strict hardware minimums:

• Per Processor: You must license a minimum of 8 cores per physical processor.
• Per Server: Even if your server only has one small processor, you must purchase enough licenses to cover that processor (minimum 8).
• Packaging: Licenses are sold in 2-core packs. To cover a processor with 8 cores, you need four 2-core packs.

The decision between Windows Server Standard and Datacenter editions in SPLA is purely a mathematical calculation of virtualization density.

Windows Server Datacenter (High Density)

• How it works: You license all physical cores on the host server.
• The Benefit: Once the physical hardware is fully licensed, you can run an unlimited number of Windows Server virtual instances (VMs) or Hyper-V Containers on that host.
• Best for: Highly virtualized environments or "Dedicated Host" offerings where the customer wants to spin up VMs at will.

Windows Server Standard (Low Density)

• How it works: You license all physical cores on the host server.
• The Limitation: This grants you the right to run only 1 Operating System Environment (OSE) (plus the physical host OSE if used solely for virtualization management).
• Stacking: If you want to run 2 VMs, you must license all physical cores on the server a second time.

Best for: Physical servers with no virtualization, or environments with very low VM density.

Auditors often catch service providers on specific Windows Server misunderstandings. Here are the top mistakes to avoid:

1. The "Passive" Node Trap 

This is the most common error. In SQL Server, passive failover nodes are often free. This is NOT true for Windows Server. In SPLA, you must license the OS on every server it runs on. If you have a passive cluster node sitting idle waiting for a failover, it is running Windows Server, and you must report active SPLA licenses for it every month.

2. VDI (Virtual Desktop Infrastructure) 

Service Providers often try to host Windows 10 or 11 on shared hardware for customers.

• The Rule: You cannot use Windows Desktop OS (Windows 10/11) in SPLA.
• The Workaround: You must use Windows Server with the "Desktop Experience" enabled, and users must access it via Remote Desktop Services (RDS). This requires reporting RDS SALs (Subscriber Access Licenses) for each user,.

3. Ignoring Physical Cores for Single VMs 

A common mistake is assigning a license only to the VM itself. In standard SPLA, you must license the physical hardware layer (the host), regardless of whether the VM uses 1 core or 20.

Introduced in late 2022, the Flexible Virtualization Benefit radically changed how customers can bring their own Windows Server licenses to your datacenter.

The Scenario: Your customer, CorpInc, has a large Enterprise Agreement (EA) with Microsoft. They have purchased Windows Server Datacenter Core subscriptions or licenses with Software Assurance (SA). They want to move their workloads to your datacenter but do not want to pay for SPLA Windows Server licenses on top of what they already own.

The Rules for You (The Authorized Outsourcer)

1. Eligibility: You must be an Authorized Outsourcer. This means you are not a "Listed Provider" (Amazon, Google, Microsoft, Alibaba).
2. Shared Hardware: Unlike the old "License Mobility" rules which forbade Windows Server on shared hardware, FVB allows CorpInc to run their Windows Server VMs on your shared multi-tenant servers.
3. Reporting: You do not report these Windows Server instances on your SPLA. The customer covers them with their own licenses.

The Rules for the Customer (CorpInc)

Unlike standard SPLA (which licenses the physical host), under FVB, the customer licenses by Virtual Machine.

• Minimums: They must assign a minimum of 8 Core Licenses per VM.
• Customer Minimum: They must assign a minimum of 16 Core Licenses per customer total.
• CALs Required: The customer must also have Windows Server CALs with active SA/Subscription for every user accessing these VMs.

Octopus Cloud makes Windows Server hosting simpler and smarter. Whether you’re balancing core counts, virtualization limits, or customer-owned licenses under the Flexible Virtualization Benefit, we handle the licensing details so you can focus on growing your cloud offerings and serving your customers.

‍Reach out to our team to simplify your SPLA reporting and maximize the value of your Windows Server hosting.