Windows Server and SQL Server licensing guide
A planning guide to physical hosts, virtual machines, cores, CALs, SQL licensing models, high availability, disaster recovery, Azure, and buying validation.
Server licensing starts with the deployment topology and access model. Record what runs where, then apply product rules and validate agreement-sensitive rights before choosing packs, subscriptions, or benefits.
Model the topology first
Separate physical hosts, processors, physical cores, virtual machines, operating systems, SQL instances, active and passive roles, and Azure workloads. SQL runs inside an operating system or VM; it is not automatically another server.
- Physical host and installed cores
- VM count and placement
- Windows edition
- SQL edition and role
Model access independently
Windows Server CALs, RDS CALs, and SQL Server plus CAL each answer different access questions. Administrative remote access is not automatically the same as an RDS session-host deployment.
- Named users or devices
- External access
- RDS session hosts
- Countable or public SQL access
Validate the commercial path
Azure license-included pricing, Azure Hybrid Benefit, per-VM options, mobility, passive recovery, downgrade rights, editions, and legacy agreements can depend on active coverage and current Product Terms.
- Purchase program and geography
- Active subscriptions or Software Assurance
- Existing entitlements
- Exact SKU, term, and fulfillment
Bring evidence for each item.
Use the checklist to prepare an internal discussion or a Temen working session. An unknown answer is useful when it is recorded as an explicit decision to resolve.
Ungated and available without submitting a formOfficial guidance, organizational authorship, and a visible review date.
- Author
- Temen Systems Licensing and Solution Engineering
- Reviewer
- Microsoft Licensing Practice Review
- Published
- August 1, 2026
- Last reviewed
- August 1, 2026
Turn the guide into a customer-specific decision.
Temen can assess the current state, frame the options, validate dependencies, and create an accountable path into delivery or operation.
