Microsoft Per Core (with CAL) licensing rules

  • Release version: Xanadu
  • Updated August 1, 2024
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Microsoft Per Core (with CAL) licensing rules

    The Microsoft Per Core (with CAL) licensing model applies to several Microsoft Server products, including Windows Server, System Center, and Core Infrastructure Server Suite. Licensing depends on the number of installations and operating system environments (OSE) and differs between on-premise and cloud deployments. Cloud licensing follows Bring Your Own License (BYOL) rules, while on-premise licensing can be done via two main methods: licensing by physical cores or by individual virtual machines (VMs).

    Show full answer Show less

    Licensing Methods

    • Licensing by physical cores: Licenses are assigned based on the number of physical cores in the server.
    • Licensing by individual virtual machines: Licenses are assigned based on the number of virtual cores allocated to each VM.

    Licenses can be allocated manually or automatically optimized using the Software Asset Management (SAM) application to minimize costs. Allocation must be done at the host or VM level, not at the cluster level.

    Licensing by Physical Cores

    • Licensing is based on the total physical cores (CPU count multiplied by core count) on a server.
    • Minimum license requirements: 8 licenses per physical processor, 16 per server.
    • Client Access Licenses (CALs) are required for each user or device accessing the server.
    • Virtualization rights allow running 2 VMs if all cores are licensed; additional VMs require licensing the host again. Windows Server Datacenter edition allows unlimited VMs when fully licensed.
    • License mobility within server farms (software assurance benefit) allows reassigning licenses every 90 days, but this is not supported for Windows Server.
    • For clustered virtualization environments (e.g., VMware vSphere, Microsoft Hyper-V, Nutanix AHV), all hosts that a VM can potentially migrate to must be fully licensed, accounting for live migration capabilities.

    Licensing by Virtual Machines

    • Licensing is based on the number of virtual cores (CPU count × core count × CPU thread count) assigned to each VM.
    • Minimum of 8 licenses per virtual machine.
    • This licensing option requires software assurance or a subscription license.
    • License mobility within the same server farm is supported with no 90-day reassignment limitation, allowing flexible license reallocation.

    Practical Implications for ServiceNow Customers

    • Use the SAM application to determine the most cost-effective licensing strategy between physical cores and virtual machines.
    • Ensure compliance with Microsoft’s licensing rules regarding CALs, minimum license counts, and virtualization rights.
    • In virtualized cluster environments, account for potential VM migration when licensing hosts to avoid compliance gaps.
    • Understand the benefits and limitations of license mobility, especially the 90-day reassignment rule and its exceptions.

    The Per Core (with CAL) metric licensing model is followed by various Microsoft Server products such as Windows Server, System Center, and Core Infrastructure Server Suite. The number of licenses depends on the number of installations and operating system environments (OSE).

    The licensing rules for on-premise installations of these products and the cloud installations are separate. The cloud licensing rules follow Bring Your Own License (BYOL). For more information, see Licensing rules for BYOL and BYOS.

    To license the on-premise installation of these products using the Per Core (with CAL) licensing model, consider the following two options.
    • Licensing by physical cores, also known as licensing by physical hosts
    • Licensing by individual virtual machines
    Note:
    You can either allocate to individual hosts or individual virtual machines, not to cluster.
    You can either allocate manually, or the Software Asset Management application can automatically select the most cost-effective licensing option based on optimization criteria. For more information about how to perform allocation, see Allocation management and how the Software Asset Management application performs automated optimization, see View realized and potential cost-based licensing optimizations for Microsoft.
    Note:
    Both options, whether licensing by physical cores or licensing by individual virtual machines, come with their own set of Microsoft rules that must be followed. For more information, see Windows Server Standard, Datacenter, and Essentials.

    Licensing by physical cores

    The Software Asset Management application supports licensing by physical core rules, introduced by Microsoft in 2016.
    Table 1. Licensing by physical core rules
    Rule Windows Server Standard Windows Server Data Center
    Required number of licenses Equals the number of physical cores on the licensed server

    The physical cores on servers are equal to CPU count * Core count.
    Min licenses required
    • 8 per physical processor
    • 16 licenses per server
    CAL requirement Device or user CALs are required for users or devices accessing the server
    Virtualization rights Rights to use 2 virtual machines if all cores of the host are licensed with the option for license stacking
    Note:
    You must license the host again to get rights to use 2 additional virtual machines.
    		 Rights to run unlimited virtual machines when all cores of the host are licensed
    License mobility within Server Farms (Software assurance benefit)
    Note:
    License mobility isn't available for Windows Server. Licenses can be reassigned to servers as often as every 90 days.
    		 Not supported
    When deploying Microsoft products like Windows Server or System Center (using the core with CAL license model) on cluster virtualization technologies such as VMware vSphere, Microsoft Hyper-V, or Nutanix AHV, the number of licenses required for the physical host depends on the virtual machines that could potentially migrate to it within the cluster.

    Technologies like VMware vMotion, which enables live migration of virtual machines across all hosts, and host affinity, which helps lock virtual machines to hosts within a cluster, manage the movement of virtual machines across hosts. To understand more about cluster virtualization technology and its support on the Software Asset Management application, see Understanding your cluster infrastructure.

    According to Microsoft licensing rules, if a virtual machine with a Microsoft product like Windows Server installed is hosted on one server but can potentially migrate to another, the destination server must be licensed as if the virtual machine is already running on it.

    Licensing by virtual machines

    The Software Asset Management application supports licensing by individual virtual machines rules, introduced by Microsoft in 2022.

    Table 2. Licensing by individual virtual machines rules
    Rule Windows Server Standard and Windows Server Data Center
    Required number of licenses Equals the number of virtual cores on the virtual machine

    The virtual cores on servers are equal to CPU count * Core count * CPU thread count.
    Min licenses required 8 licenses per virtual machine
    Software assurance or subscription license
    Note:
    The option to license by virtual machine is only available with software assurance or a subscription license.
    		 Required
    License mobility within Server farms (Software assurance benefit)
    Note:
    Licenses can be reassigned within the same server farm as often as needed. The 90-day rule applies only when moving to another server farm or cloud provider.
    		 Supported