SECURE CLOUD. CLEAR OUTCOMES. · Transform, enable, optimize, and operate with one accountable partner.Start a conversation
Insights / LicensingBuy · 14 minute guide

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.

Temen point of view

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.

01

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
02

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
03

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
Downloadable working artifact

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 form
01Deployment boundaryOwner and evidence02Physical core inventoryOwner and evidence03VM and workload mapOwner and evidence04Windows editionsOwner and evidence05SQL editions and modelsOwner and evidence06Access populationOwner and evidence07HA and DR rolesOwner and evidence08Agreement and coverage evidenceOwner and evidence
Download checklist
Sources and accountability

Official 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
OFFICIAL SOURCESMicrosoft LicensingWindows Server 2025 licensing guidanceMicrosoft LicensingWindows Server virtualization licensing guidanceMicrosoft LicensingSQL Server licensing guidanceMicrosoftMicrosoft Product Terms
Next step

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.