Windows Server runs in every enterprise data centre. It hosts Active Directory, file servers, SQL Server, Exchange, web applications, virtualised workloads, and the infrastructure layer that everything else depends on. And its licensing model — core-based, edition-dependent, virtualisation-sensitive, and CAL-gated — is responsible for more Microsoft audit findings than any other product in the portfolio. The core-based licensing model introduced with Windows Server 2016 replaced the simpler processor-based model, and in doing so created a licensing framework where the number of physical cores in a server, the number of virtual machines running on that server, the edition installed, the hypervisor in use, and the Software Assurance status each affect the licensing requirement. A single miscalculation — choosing Standard when Datacenter is needed, under-counting cores on a virtualisation host, or forgetting CALs for external users — can create compliance exposure measured in hundreds of thousands of dollars. This guide covers every dimension of Windows Server licensing in 2026: the edition decision, the core counting rules, the virtualisation mechanics, the hybrid cloud implications, the CAL requirements, and the optimisation strategies that save enterprises 15–30% on their Windows Server licensing costs.
Since Windows Server 2016, Microsoft has licensed Windows Server based on physical cores rather than physical processors. This fundamental change means the licensing cost scales with the processing power of the hardware, not just the number of sockets.
Windows Server licences are sold in 2-core packs. Every physical server requires a minimum of 16 core licences (purchased as eight 2-core packs), regardless of the actual number of physical cores in the server. If the server has more than 16 physical cores, the enterprise must purchase licences for the actual core count.
Example: A server with two 8-core processors has 16 physical cores. This requires 16 core licences (the minimum). A server with two 16-core processors has 32 physical cores. This requires 32 core licences — double the minimum. A server with two 24-core processors has 48 physical cores and requires 48 core licences — triple the minimum.
The cost implication: As processor core counts increase with each hardware generation, the licensing cost per server increases proportionally. A refresh from 16-core servers to 48-core servers triples the Windows Server licensing requirement per server, even though the number of physical servers may decrease. Enterprises planning hardware refreshes must model the licensing impact alongside the infrastructure cost — the licensing increase can offset a significant portion of the consolidation savings.
Hyper-threading does not count: Windows Server licensing is based on physical cores, not logical processors. A 16-core processor with hyper-threading presents 32 logical processors to the operating system, but only the 16 physical cores require licensing. This distinction matters when auditing licence compliance: verify the count against physical cores, not the logical processor count reported by Windows.
In a non-virtualised environment, each physical server requires core licences for all physical cores (minimum 16). The licence covers one instance of Windows Server operating system running on the physical hardware. If the server does not run any virtualisation, the licensing is straightforward: count the cores, buy the licences, install the edition.
Windows Server comes in two editions that affect licensing cost, virtualisation rights, and available features. Choosing the wrong edition is the second most common licensing mistake after virtualisation miscounting.
Windows Server Standard is licensed per physical core (minimum 16 cores per server) and provides rights to run up to 2 Operating System Environments (OSEs) — that is, 2 virtual machines — per licence set. A “licence set” is the 16-core minimum (or the actual core count if higher). Each additional set of core licences for the same physical server adds rights for 2 more OSEs.
Stacking Standard licences for more VMs: If a 16-core server runs 6 VMs, the enterprise needs 3 sets of Standard core licences (each set covering 2 VMs). If the server has 32 cores, each set requires 32 core licences. Three sets of 32 core licences for a single server running 6 VMs can become very expensive very quickly.
Standard Edition list pricing: Approximately $1,069 per 2-core pack (2026 list). A 16-core server requires eight 2-core packs = ~$8,555. A 32-core server requires sixteen 2-core packs per set = ~$17,110 per set. Three sets for 6 VMs on a 32-core host = ~$51,330. EA pricing provides significant discounts from list, but the stacking multiplication remains the same.
Windows Server Datacenter is licensed per physical core (same minimum 16 cores) and provides unlimited virtualisation rights on the licensed server. Regardless of whether the server runs 2 VMs or 200 VMs, one set of Datacenter core licences covers every VM on that physical host.
Datacenter Edition list pricing: Approximately $6,155 per 2-core pack (2026 list). A 16-core server requires eight 2-core packs = ~$49,240. A 32-core server requires sixteen 2-core packs = ~$98,480. Datacenter costs approximately 5.7x more per core than Standard — but the unlimited virtualisation rights mean the cost does not multiply as VMs are added.
The edition decision is a mathematical calculation, not a feature preference. Datacenter becomes cheaper than stacked Standard licences when the number of VMs per host exceeds a specific threshold. For a 16-core server: Standard covers 2 VMs per licence set at ~$8,555. Datacenter covers unlimited VMs at ~$49,240. The crossover is approximately 12 VMs (6 Standard sets × $8,555 = $51,330 vs one Datacenter set at $49,240). For a 32-core server, the crossover is approximately 6 VMs (3 Standard sets × $17,110 = $51,330 vs one Datacenter set at $98,480 — wait, that is actually still Standard-favourable at 6 VMs on 32-core). The exact crossover depends on the core count.
The practical rule: In modern virtualisation environments where consolidation ratios of 10–30 VMs per host are common, Datacenter is almost always the correct and cheaper choice for virtualisation hosts. Standard is the right choice for physical servers (no virtualisation), servers running only 1–2 VMs, and specific non-virtualisation workloads like domain controllers, DHCP servers, or print servers that run on dedicated physical hardware. For the detailed calculator, see the licensing calculator.
Beyond virtualisation rights, Datacenter includes features not available in Standard: Shielded VMs (encrypted virtual machines for security-sensitive workloads), Storage Spaces Direct (software-defined storage across multiple servers), Software-Defined Networking (SDN), and Storage Replica (synchronous block-level replication). If any of these features are required, Datacenter is mandatory regardless of the VM count. For the complete feature comparison, see the CIO playbook for hybrid environments.
Windows Server licensing in virtualised environments is the single largest source of Microsoft audit findings. The rules are precise, the consequences of miscounting are expensive, and the complexity increases with each layer of virtualisation technology.
Windows Server is licensed based on the physical host, not the virtual machine. The physical cores of the host server determine the licensing requirement. The number of VMs determines whether Standard (with stacking) or Datacenter (unlimited) is more cost-effective. Every VM running a Windows Server operating system must be covered by licences assigned to its physical host.
In Hyper-V environments, the licensing is the most straightforward because Microsoft’s own hypervisor is the virtualisation platform. The physical host requires core licences. If using Datacenter, all VMs on the host are covered. If using Standard, each licence set covers 2 VMs, and additional sets must be stacked for additional VMs. The Hyper-V host operating system (the management OS) does not consume one of the Standard Edition’s 2-OSE rights — it runs outside the VM count, which is a subtle but financially important detail.
In VMware environments, the licensing rules are the same as Hyper-V — licence the physical cores of the ESXi host — but the operational reality is more complex. VMware clusters often use vMotion to move VMs between hosts automatically for load balancing and failover. When a VM moves from Host A to Host B via vMotion, the VM must be covered by licences on the destination host.
The cluster licensing requirement: In a VMware cluster where VMs can move to any host, every host in the cluster must be licensed for the maximum number of VMs it could potentially run. Alternatively (and more commonly), every host must have Datacenter licences, which cover unlimited VMs regardless of vMotion activity. Licensing only the hosts that “currently” run VMs, while leaving other cluster hosts unlicensed, creates a compliance gap every time vMotion moves a VM to an unlicensed host — which may happen automatically without any administrator action.
The audit scenario: Microsoft’s audit team requests the VMware vCenter inventory, which shows every physical host in every cluster and every VM that has run on each host. If Host C has 32 cores and ran Windows Server VMs during the audit period but does not have 32 core licences assigned, the audit finding is immediate. The resolution is either retrospective licence purchase at list price or licence reallocation from elsewhere in the estate. For the detailed VMware licensing analysis, see licensing in virtualised environments.
Windows Server containers add another licensing layer. Windows Server containers (process-isolated) are permitted in unlimited numbers on a host licensed with either Standard or Datacenter. Hyper-V containers (VM-isolated) follow the same rules as VMs: each Hyper-V container counts as an OSE and requires licensing accordingly (2 per Standard licence set, unlimited with Datacenter). In Kubernetes environments running Windows containers on Windows Server nodes, the physical host must be licensed for the total number of Hyper-V-isolated containers if using that isolation mode. For container-heavy environments, Datacenter is typically the only practical choice.
Core licences grant the right to run Windows Server on the physical hardware. Client Access Licences (CALs) grant the right for users or devices to access the services provided by Windows Server. Both are required. Core licences without CALs (or CALs without core licences) create a compliance gap.
User CALs are assigned to a specific person and allow that person to access Windows Server services from any number of devices. An employee with a User CAL can access servers from their desktop, laptop, phone, and tablet — one CAL covers all devices for that user. User CALs are the right choice when users access servers from multiple devices, which is the norm in hybrid and remote work environments.
Device CALs are assigned to a specific device and allow any number of users to access Windows Server from that device. Device CALs are the right choice in shared-device scenarios: a call centre desktop used by three shifts of operators needs 1 Device CAL rather than 3 User CALs. Kiosks, nursing stations, and factory floor terminals are typical Device CAL scenarios.
The cost of getting it wrong: An enterprise with 5,000 employees who each use 2 devices needs either 5,000 User CALs or 10,000 Device CALs. Choosing Device CALs when User CALs are appropriate doubles the CAL cost. Conversely, a call centre with 100 shared desktops and 300 shift workers needs 100 Device CALs rather than 300 User CALs — choosing User CALs triples the cost.
When external users (customers, partners, members of the public) access services hosted on Windows Server, the enterprise has two options: purchase individual CALs for every external user (impractical when the user count is unknown or very large), or purchase an External Connector licence for each server that external users access. The External Connector licence provides unlimited external access to a single server at a fixed cost. For customer-facing web applications, portals, or APIs hosted on Windows Server, the External Connector is almost always the correct choice. It is also frequently overlooked in licensing assessments, creating a compliance gap for every customer-facing Windows Server workload.
If users access Windows Server through Remote Desktop Services (terminal services, RemoteApp, session-based desktops), they need RDS CALs in addition to Windows Server CALs. RDS CALs are a separate per-user or per-device licence that grants the right to connect to the RDS Session Host role. In remote and hybrid work environments where RDS is used to provide virtual desktops or published applications, the RDS CAL requirement is the most frequently missed licensing element. See the remote and hybrid work licensing guide for the complete RDS analysis.
Software Assurance (SA) for Windows Server costs approximately 25% of the licence price annually and provides several benefits that are particularly valuable for organisations with hybrid cloud strategies.
Azure Hybrid Benefit (AHB) is the single most valuable SA benefit for Windows Server. It allows enterprises to use their on-premise Windows Server licences (with active SA) to run Windows Server VMs in Azure at the Linux compute rate — effectively eliminating the Windows Server licence cost component of the Azure VM price. The savings are 40–55% of the VM compute cost, depending on VM size and region.
How it works: Each set of Windows Server core licences with active SA can be applied to Azure VMs. Datacenter Edition licences cover unlimited VMs in Azure (mirroring the on-premise unlimited virtualisation right). Standard Edition licences cover up to 2 VMs in Azure per licence set. The benefit can be applied to Reserved Instances, compounding the savings: AHB (40–55% saving) plus Reserved Instance (30–72% saving on the remaining compute cost) can reduce Azure VM costs by 70–80% compared to pay-as-you-go pricing without AHB.
The SA investment calculation: SA costs ~25% of the licence price per year. For a $49,240 Datacenter licence set (16-core), SA costs ~$12,310/year. If that licence set enables AHB savings of $2,000–$4,000/month on Azure VMs ($24,000–$48,000/year), the SA investment delivers 2–4x ROI from AHB alone, before considering version upgrade rights and other SA benefits. For organisations actively migrating to Azure, SA on Windows Server Datacenter licences is one of the highest-ROI investments in the Microsoft portfolio. See the BYOL vs Azure licensing calculator for modelling.
SA includes the right to upgrade to the latest version of Windows Server at no additional licence cost. When Windows Server 2025 releases, enterprises with active SA on Windows Server 2022 licences can upgrade without purchasing new licences. Without SA, upgrading to a new version requires purchasing new licences at the current price. For organisations that upgrade Windows Server versions every 3–5 years, the upgrade right alone may justify the SA investment.
SA provides License Mobility rights that allow Windows Server workloads to move between on-premise servers and authorised outsourced hosting environments. This is distinct from Azure Hybrid Benefit (which specifically covers Azure) and applies to third-party hosting providers that are part of Microsoft’s Authorized Mobility Partners programme. See Software Assurance benefits for the complete set of SA entitlements relevant to server products.
Windows Server 2025 introduces licensing changes that enterprises should understand before deployment:
Hotpatching: Windows Server 2025 Datacenter introduces hotpatching (the ability to apply security updates without rebooting), but this capability requires an Azure Arc subscription. Azure Arc for Windows Server hotpatching is priced per server per month, adding a recurring consumption cost on top of the perpetual licence. Enterprises that deploy Windows Server 2025 Datacenter expecting hotpatching at no additional cost will discover the Azure Arc requirement at deployment time.
Azure Arc integration: Windows Server 2025 deepens integration with Azure Arc for hybrid management, monitoring, and policy enforcement. While Azure Arc agent installation is free, many of the management capabilities (update management, change tracking, monitoring) consume Azure services that are billed on consumption. The licensing model for Windows Server is evolving from purely perpetual-licence-based to a hybrid of perpetual licences plus cloud consumption for advanced capabilities.
Same core-based model: Windows Server 2025 retains the core-based licensing model with the same Standard and Datacenter editions, the same 16-core minimum, the same virtualisation rules, and the same CAL requirements. The fundamental licensing mechanics remain unchanged from 2022. See the SAM professional’s guide for the detailed technical reference.
Azure Stack HCI is Microsoft’s hyperconverged infrastructure solution that runs on-premise but is managed through Azure. Its licensing model is distinct from standard Windows Server licensing: Azure Stack HCI is licensed as an Azure service billed per physical core per month (~$10/core/month), not as a perpetual licence.
The licensing distinction: Azure Stack HCI provides the right to run unlimited Windows Server VMs on the HCI cluster nodes (similar to Datacenter Edition) as part of the Azure subscription. Separate Windows Server Datacenter licences are not required for VMs running on Azure Stack HCI — the VM rights are included in the Azure Stack HCI subscription. However, Windows Server CALs are still required for users and devices accessing services on the HCI cluster.
The cost comparison: For a 4-node cluster with 32 cores per node (128 total cores), Azure Stack HCI costs approximately $1,280/month ($15,360/year). The equivalent Windows Server Datacenter licensing for 4 nodes would cost approximately $197,000 in perpetual licences plus ~$49,000/year in SA. The Azure Stack HCI subscription model converts the large upfront capital expenditure into a predictable operating expense, but over a 5–7 year lifecycle, the cumulative subscription cost may exceed the perpetual licence + SA total. Model both options across the expected hardware lifecycle before choosing. For the broader hybrid comparison, see the on-premise to cloud migration cost estimator.
Windows Server virtualisation licensing is the most common area of Microsoft audit findings. The typical findings:
Under-licensed virtualisation hosts: The most frequent finding. The enterprise has Standard Edition licences covering 2 VMs on a host that runs 8 VMs, or has no Datacenter licences on hosts that clearly require them. The gap is the difference between the actual VM count and the licensed VM rights, multiplied by the per-core licence cost at list price.
VMware cluster licensing gaps: VMs that migrated between hosts via vMotion, DRS, or manual migration ran on hosts that were not licensed for them. The audit team identifies every host that hosted a Windows Server VM during the audit period and compares against the assigned licence count.
Missing CALs: Core licences are purchased but CALs are not. Or User CALs are purchased but external users accessing customer-facing applications are not covered by an External Connector licence.
RDS without RDS CALs: Users connect to Windows Server via Remote Desktop but no RDS CALs are purchased. The 120-day RDS grace period allows connections without enforcement, masking the gap until audit.
Core count discrepancies: The enterprise licensed based on a historical hardware inventory that does not reflect processor upgrades or server additions. The physical core count at audit time exceeds the licensed core count.
Prevention: Conduct an annual Windows Server licence reconciliation that compares physical host inventory (core counts), VM inventories (per-host VM counts), assigned licences (edition, core count, and assignment), CAL entitlements (User vs Device, total count vs user/device population), and RDS deployment against RDS CAL purchases. This reconciliation, performed before Microsoft asks for it, is the single most effective audit prevention measure. See the audit CIO playbook, the audit survival checklist, and SAM tools for audit preparedness.
Windows Server licensing costs are substantial, but they are also highly optimisable. The following strategies consistently deliver 15–30% savings:
Audit every physical server. Servers running 1–3 VMs should be on Standard. Servers running 4+ VMs should almost certainly be on Datacenter. Servers running zero VMs (physical-only workloads) should be on Standard. The edition should be a per-host decision based on the actual VM count, not a blanket policy applied across the data centre. See the Windows Server licensing models overview. For more detail, see our Microsoft licensing models explained.
If you have Datacenter licences on a host, every additional VM on that host is “free” from a licensing perspective. Consolidating VMs onto Datacenter-licensed hosts (rather than spreading them across Standard-licensed hosts) reduces the total licence count. Conversely, running only 2–3 VMs on a Datacenter-licensed host wastes the unlimited virtualisation rights you paid for.
Every Windows Server licence with active SA that is not being applied as Azure Hybrid Benefit is a missed savings opportunity. Audit your Azure VM estate for Windows Server VMs running without AHB and apply the benefit. For many enterprises, the AHB savings on Azure VMs exceed the annual SA cost on the corresponding on-premise licences, making SA a net positive investment. See the BYOL vs Azure licensing calculator.
SA is not mandatory and should not be renewed automatically on every licence. Evaluate each Windows Server licence set: is the SA delivering value through AHB, version upgrades, License Mobility, or other benefits? If a licence set covers a stable, non-virtualised server with no planned Azure migration or version upgrade, SA may be a pure cost with no return. Drop SA on licences where it does not deliver value and reinvest the savings where SA delivers the highest ROI. See the Software Assurance CIO playbook.
Windows Server licensing purchased through the Enterprise Agreement or Server and Cloud Enrollment (SCE) provides volume discounts that are significantly better than list pricing. The SCE is specifically designed for infrastructure-focused licensing (Windows Server, SQL Server, System Center) and can provide 15–40% discounts on server products depending on commitment level. See EA negotiation strategies and benchmarking EA discounts.
When refreshing data centre hardware, model the Windows Server licensing impact of the new core counts. A consolidation from 20 servers with 16 cores each (320 total cores to license) to 10 servers with 48 cores each (480 total cores to license) increases the total core licence requirement by 50%, even though the server count halved. The infrastructure savings must be evaluated net of the licensing increase.
Audit the user and device access patterns to Windows Server services. Calculate the cost under User CAL and Device CAL models separately. For most organisations with a mobile/hybrid workforce, User CALs are cheaper. For organisations with shared-device environments (manufacturing, healthcare, retail), Device CALs for the shared devices and User CALs for mobile workers may be the optimal mixed approach. Do not default to one type without modelling both.
Enterprise data centres are not static. Servers are refreshed, workloads migrate to Azure, virtual environments are consolidated, and mergers create overlapping infrastructure. Each transition creates Windows Server licensing decisions that must be managed proactively.
When migrating Windows Server workloads from on-premise data centres to Azure, the licensing model shifts from perpetual core licences to one of three options: pay-as-you-go (the Windows Server licence cost is embedded in the Azure VM hourly rate — the most expensive option), Azure Hybrid Benefit (apply existing on-premise licences with active SA to eliminate the Windows licence component of the Azure VM — the optimal option for enterprises with SA), or Azure Reserved Instances with AHB (the lowest-cost option, combining pre-commitment discounts with licence re-use).
The transition window: During migration, the enterprise often runs workloads in parallel: the same application running on-premise and in Azure simultaneously for validation, testing, or phased cutover. During this parallel period, the on-premise server still requires its Windows Server licence. If that licence is also applied as AHB to the Azure VM, Microsoft’s licensing terms permit dual use for up to 180 days during migration. After 180 days, the licence must be assigned to either the on-premise server or the Azure VM, not both. Plan migration timelines with this 180-day window in mind. See the migration cost estimator and hybrid cloud licensing.
When consolidating multiple data centres into fewer facilities, the VM density per host typically increases. This is the moment to reassess the Standard vs Datacenter decision. Hosts that ran 3–4 VMs pre-consolidation and were correctly licensed with Standard may run 15–20 VMs post-consolidation and require Datacenter. The consolidation plan should include a licensing model that maps the post-consolidation VM-per-host density and identifies which hosts need edition upgrades.
Hardware refresh interaction: Consolidation often coincides with hardware refresh. New servers with higher core counts require more core licences per host. A consolidation from 40 older servers (16 cores each, 640 total cores) to 15 new servers (48 cores each, 720 total cores) increases the total core licence requirement by 12.5% despite reducing the server count by 62%. The licensing cost increase should be modelled explicitly in the consolidation business case, not discovered after the hardware arrives.
Mergers create the most complex Windows Server licensing scenarios. Two enterprises with separate EAs, different edition strategies, different SA renewal dates, and overlapping data centres must reconcile their Windows Server licensing positions. The acquired entity’s EA may not survive the acquisition (depending on the M&A structure and Microsoft’s agreement assignment policies). Licences purchased under one EA may not be transferable to the acquiring entity’s EA without Microsoft’s consent.
The M&A licensing checklist for Windows Server: Inventory both entities’ Windows Server deployments (editions, core counts, SA status). Map licence assignments to physical hosts in both environments. Identify overlap (servers in both entities that will be consolidated) and gaps (servers in the acquired entity not covered by the acquiring entity’s EA). Engage independent advisory to negotiate licence transfer or novation with Microsoft before the integration begins. See Microsoft licensing in M&A and the Enterprise Agreement guide.
Running Windows Server on AWS, Google Cloud, or other non-Azure cloud providers requires careful licensing attention. Azure Hybrid Benefit applies only to Azure (and Azure Stack). For Windows Server workloads on AWS or GCP, the enterprise must either use the cloud provider’s Windows Server licence (included in the VM hourly rate, typically at a premium), or bring their own licences to dedicated hosts. AWS Dedicated Hosts and GCP Sole-Tenant Nodes allow the enterprise to license Windows Server on specific physical hardware in the cloud using existing perpetual licences with SA (under License Mobility rights). Shared tenancy (the default) does not support BYOL for Windows Server.
The licensing cost difference between Azure (with AHB) and AWS/GCP (without equivalent benefit) can be 30–50% for Windows Server workloads. This licensing differential is one of the strongest commercial reasons for running Windows Server workloads on Azure rather than competing clouds. See comparing cloud licensing economics.
“Windows Server licensing is not complicated for the sake of complexity. It is complicated because data centres are complex: different hardware generations, different virtualisation platforms, different VM densities, different workload types, different access patterns. The licensing model must account for all of this. The enterprises that manage Windows Server licensing well start with an accurate inventory, make the edition decision per host rather than per data centre, apply Azure Hybrid Benefit to every eligible Azure VM, and reconcile their licence position annually before Microsoft does it for them. The ones that manage it poorly discover the gaps at audit time and pay list price to resolve them.” — Fredrik Filipsson, Co-Founder, Redress Compliance
Windows Server requires a minimum of 16 core licences per physical server, regardless of the actual core count. If the server has more than 16 physical cores, you must license the actual core count. Licences are sold in 2-core packs, so a 16-core server needs eight 2-core packs and a 32-core server needs sixteen 2-core packs. In virtualised environments, Standard Edition covers 2 VMs per licence set and can be stacked for additional VMs. Datacenter Edition covers unlimited VMs with a single licence set.
Use Datacenter for any virtualisation host running more than approximately 4–6 VMs (the exact crossover depends on your core count). In modern environments with consolidation ratios of 10–30 VMs per host, Datacenter is almost always cheaper than stacked Standard licences. Also use Datacenter when you need Datacenter-only features: Shielded VMs, Storage Spaces Direct, Software-Defined Networking, or Storage Replica.
Yes. Windows Server core licences grant the right to run the operating system on the hardware. Client Access Licences (CALs) grant the right for users or devices to access the services provided by the server. Both are required. A server with core licences but no CALs for its users is not fully licensed. Choose User CALs for mobile/hybrid workers who access from multiple devices, or Device CALs for shared-device scenarios.
Azure Hybrid Benefit allows you to use on-premise Windows Server licences with active Software Assurance to reduce the cost of Windows Server VMs in Azure by 40–55%. Datacenter licences provide unlimited Azure VM rights. Standard licences cover up to 2 Azure VMs per licence set. AHB can be combined with Azure Reserved Instances for total savings of 70–80% versus baseline pay-as-you-go pricing.
The most common findings are under-licensed virtualisation hosts (Standard Edition covering fewer VMs than are actually running), VMware cluster licensing gaps (VMs that moved between hosts via vMotion to unlicensed hosts), missing CALs (core licences purchased but CALs not), RDS without RDS CALs, and core count discrepancies from hardware changes not reflected in the licence inventory. Annual licence reconciliation prevents most of these findings.
No. Windows Server licensing is based on physical cores, not logical processors. A 16-core processor with hyper-threading shows 32 logical processors in Windows but requires only 16 core licences. Always verify your licence count against physical cores, not the logical processor count reported by the operating system or management tools.
Redress Compliance provides independent Windows Server licensing assessments, virtualisation compliance audits, Azure Hybrid Benefit optimisation, and EA negotiation support for server infrastructure. We help enterprises right-size editions, prevent audit exposure, and maximise the value of Software Assurance investments.