Microsoft licensing guide for On-Premise Windows Server & SQL Server
Discover the essential March 2026 guide to Microsoft Windows Server 2025 and Microsoft SQL Server 2025 licensing, including core-based rules, virtualization rights, CAL requirements, and the latest compliance and audit updates – all in one concise resource.
Windows Server 2025 Core Licensing Overview
Model is Core-Centric: Licensing is based on the physical processing capacity (number of physical cores) of the server hardware. These rules apply to all perpetual licenses, whether acquired new or through secondary market.
Minimum Core Requirements:
Per Server: Minimum of 16 core licenses (acts as a floor, even for low-core servers).
Editions & Virtualization Rights (Per Full License Set):
Standard Edition: Grants rights for 2 virtual Operating System Environments (OSEs) or Hyper-V isolated containers.
Requires "Stacking" (re-licensing all physical cores) for every additional pair of 2 VMs.
Datacenter Edition: Grants Unlimited virtualization rights on the fully licensed host.
Crossover Point: Datacenter is typically more cost-effective when planning to run more than 7 to 10 VMs on a single host.
Datacenter Exclusive Features: Includes Storage Spaces Direct, Shielded Virtual Machines, and Hotpatching (via Azure Arc) - extra payment required.
SQL Server 2025/2022 Licensing Frameworks
Two Primary Models: Per Core and Server + CAL.
Per Core Model:
Mandatory for SQL Server Enterprise.
Optional for SQL Server Standard.
Minimums: Requires a minimum of 4 core licenses per physical processor or per Virtual Machine (VM).
Critical SA Requirement: Licensing by Virtual Machine is only permitted with active Software Assurance (SA) or subscription licenses. Without SA, the entire physical host must be licensed. This only applies to versions 2022 and newer and does not apply to “Server+CAL” model.
Server + CAL Model:
Available only for SQL Server Standard Edition.
Ideal for environments with a fixed, known user count.
SQL Server 2025 Standard Capacity Increases:
Compute capacity raised to 32 cores / 4 sockets.
Memory limit doubled to 256 GB.
Now includes Resource Governor (previously Enterprise-exclusive).
Client Access Licenses (CALs) and Indirect Access
CAL Purpose: Legal mechanism authorizing users or devices to access server services (Windows Server, SQL Server). CALs are version-specific (e.g., 2022 CALs do not access a 2025 server).
CAL Strategy:
User CALs: One user, unlimited devices (best for multi-device employees).
Device CALs: One device, unlimited users (best for shared/shift-based terminals).
Multiplexing (Indirect Access):
Rule: The use of hardware or software (like a web application) to pool connections or reroute information does not reduce the required number of CALs.
Example: A user accessing SQL data through a front-end web portal still requires a CAL.
Exception: Strictly manual activity (e.g., a person manually emailing a PDF report) does not create a CAL obligation for the recipient.
Advanced Access:
Remote Desktop Services (RDS): Requires an Additive CAL (RDS CAL) in addition to the base Windows Server CAL.
External Connector (EC) License: Provides unlimited access for external users (non-employees) to a specific server, often more cost-effective than individual CALs for large external portals.
Commercial and Compliance Outlook (2025-2026)
Commercial Shifts (Effective Nov 1, 2025):
Elimination of volume-based discount tiers (Levels A–D) for Online Services in Enterprise Agreements (EA).
Shift toward Cloud Solution Provider (CSP) program as the primary licensing vehicle.
Key Audit Focus Areas: Auditors are heavily focused on compliance in hybrid/virtual environments.
Virtualization Ratios: Checking for meticulous tracking of Standard Edition "stacking" licenses.
Multiplexing: Investigation of custom applications to ensure all front-end users have a CAL (or the server is correctly licensed Per-Core).
Developer Edition Misuse: Identifying the use of Developer Edition in "production" environments (e.g., UAT, staging with end-users).