CAL Suites and CAL Suite Bridges

Point Value Chart

The value assigned to a Product used to calculate the volume pricing level applicable to Customer’s volume licensing agreement.

Product Conditions:

Provides additional information related to acquiring the Product, such as prerequisites for purchase, prior versions, and the applicable Product Pool.

Process to Determine Applicable Use Rights for CAL Suites

A CAL Suite License is version-less and the access rights are determined by the status of the SA coverage on it. If SA coverage lapses, access rights under perpetual Licenses are determined based on the use rights in effect for the versions that were current prior to the lapse.

Components of CAL Suite

Refer to CAL and ML Equivalency Licenses for the current components of the Core CAL Suite and the Enterprise CAL Suite.

CAL Suite Bridge

A CAL Suite Bridge is an Enterprise Product and may only be acquired to satisfy the Organization Wide requirement of either that CAL Suite Bridge or Core/Enterprise CAL Suites.  When a CAL Suite Bridge is required the number of CAL Suite Bridge User SLs should be the same number of User SLs for the qualifying Online Service.

Identifies the License Terms for each Software Product, including the Universal License Terms, the applicable License Model, and any Product-Specific License Terms. References in Customer’s volume licensing agreement to “Use Rights” refer to the terms included in the Use Rights section of each Software Product Entry.

Academic Programs

The following applies to customers in Academic Volume Licensing Programs.

Exchange Online Archiving for Exchange Server A

Academic Institutions under Enrollment for Education Solutions and Open Value Subscription Agreement for Education Solutions, licensed for Enterprise CAL Suite for their Organization-Wide count and Student count are authorized to a corresponding number of Exchange Online Archiving for Exchange Server A User SLs for all users covered within their Organization-Wide count and Student count.

Per Core/CAL

Server Licenses (per core)

1. Customer may use the server software on a Licensed Server, provided it acquires sufficient Server licenses as described below.
2. The number of Licenses required equals the number of Physical Cores on the Licensed Server, subject to a minimum of 8 Licenses per Physical Processor and a minimum of 16 Licenses per Server.
3. Datacenter edition permits use of the server software in any number of OSEs on the Licensed Server.
4. Standard edition:
   • Standard edition permits use of the server software in two OSEs on the Licensed Server.
   • Standard edition permits use of one Running Instance of the server software in the Physical OSE on the Licensed Server (in addition to two Virtual OSEs), if the Physical OSE is used solely to host and manage the Virtual OSEs.
   • Customer may assign additional Standard edition Licenses to the Licensed Server equal to the number specified in 2 above and use the server software in two additional OSEs on the Licensed Server.
5. As long as the total numbers of Licenses and Physical Cores remains the same, License reassignment is permitted any time Customer repartitions a single piece of hardware.
6. As a one-time alternative to assigning base CALs per user or per device, a number of base CALs may be dedicated to an Instance of the server software on a single Server (per server mode) to permit up to the same number of users or devices to concurrently access that Instance.

Server Licenses (per core) – Licensing by Individual Virtual OSE

Available for subscription licenses or licenses with active Software Assurance only. All CALs used to access the software under this model must also be acquired as subscription licenses or have active Software Assurance.

1. Customer may use the server software in one Virtual OSE on the Licensed Server, provided it acquires sufficient Server licenses as described below.
2. The number of Licenses required equals the number of Virtual Cores in the Virtual OSE, subject to a minimum of 8 Licenses per Virtual OSE.
3. Customer may reassign any of its Licenses to any of its Licensed Servers located within the same Server Farm as often as needed. Customer may also reassign these Licenses from one Server Farm to another, but not on a short-term basis (i.e., not within 90 days of the last assignment).

Access Licenses

1. Except as described here and noted in the Product-Specific License Terms, all server software access requires CALs or CAL Equivalent Licenses.
2. CALs are not required for access by another Licensed Server.
3. CALs are not required to access server software running a Web Workload or HPC Workload.
4. CALs are not required for access in a Physical OSE used solely for hosting and managing Virtual OSEs.

Server/CAL

Server Licenses (per Instance)

For Products under the Server/CAL License Model, customer may use one Running Instance of server software in either a Physical OSE or Virtual OSE on a Licensed Server for each License it acquires.

Subscription licenses or licenses with active Software Assurance only. All CALs used to access the software under this model must also be acquired as subscription licenses or have active Software Assurance: When licensing by Virtual OSE, Customer may reassign any of its Licenses to any of its Licensed Servers located within the same Server Farm as often as needed. Customer may also reassign these Licenses from one Server Farm to another, but not on a short-term basis (i.e., not within 90 days of the last assignment).

Access Licenses

1. Except as described here and noted in the Product-Specific License Terms, all server software access requires CALs or CAL Equivalent Licenses.
2. CALs are not required for access by another Licensed Server.

Management Servers

The Management License version, not the version of software used, determines the version of applicable License Terms (including use under downgrade rights notwithstanding terms to the contrary).

Server Management Licenses (per core)

1. Customer may use the software on Azure or a Server to Manage OSEs on a Licensed Server, provided it acquires sufficient Server Licenses as described below.
2. The number of Licenses required equals the number of Physical Cores on the Licensed Server, subject to a minimum of 8 Licenses per Physical Processor and a minimum of 16 Licenses per Server.
3. Datacenter edition permits use of the server software to Manage any number of OSEs on the Licensed Server.
4. Standard edition:
   • Standard edition permits use of the software to Manage up to two OSEs on the Licensed Server.
   • Standard edition permits Management of the Physical OSE on the Licensed Server (in addition to two Virtual OSEs), if the Physical OSE is used solely to host and Manage Virtual OSEs.
   • Customer may assign additional Standard edition Licenses to the Licensed Server equal to the number specified in 2 above and Manage two additional OSEs.
5. OSEs running Server operating systems require Server Management Licenses.

Server Management Licenses (per core) – Licensing by Individual Virtual OSE

Available for subscription licenses or licenses with active Software Assurance only:

1. Customer may use the software on Azure or a Server to Manage a Virtual OSE on a Licensed Server, provided it acquires sufficient Server Licenses as described below.
2. The number of Licenses required equals the number of Virtual Cores in the Virtual OSE, subject to a minimum of 8 Licenses per Virtual OSE.
3. Customer may reassign any of its Licenses to any of its Licensed Servers located within the same Server Farm as often as needed. Customer may also reassign these Licenses from one Server Farm to another, but not on a short-term basis (i.e., not within 90 days of the last assignment).

Client Management Licenses (per OSE or user)

1. Customer may use the software on Azure or a Server* to Manage an OSE on a Licensed Device or OSEs on devices used by a Licensed User for each Client Management License it acquires.
2. OSEs running operating systems other than Server operating systems require Client Management Licenses or Management License Equivalent Licenses.
3. The number of Client Management Licenses required depends on License type (per OSE or user) assigned.
4. Management of an OSE accessed by more than one user requires an OSE Client Management License or a User Client Management License for each user.

*Any Server that is under the management or control of an entity other than Customer or one of its Affiliates is subject to the Outsourcing Software Management clause.

Management Licenses are not required for:

1. OSEs in which there are no Running Instances of software;
2. Any of Customer’s network infrastructure devices functioning solely for the purpose of transmitting network data and not running Windows Server software;
3. Conversion of OSEs from Physical to Virtual; or
4. Any device solely monitored or managed for the status of its hardware components with respect to system temperature, fan speed, power on/off, system reset or CPU availability.

Data Sets

Customer may not copy or distribute any data set (or any portion of a data set) included in the software.

Identifies terms and conditions associated with Software Assurance coverage. For details on purchasing Software Assurance and general Software Assurance Benefits, refer to Software Assurance Benefits.

Extended Use Rights for Microsoft 365 Customers

Qualifying customers licensed for Microsoft 365 or a combination of Office 365 and Enterprise Mobility + Security provides have the same access to Exchange Online Archiving for Exchange Server as the Enterprise CAL Suite provided. “Qualifying Customers” are Enterprise Enrollment, Enterprise Subscription Enrollment, or Enrollment for Education Solutions customers who have active Software Assurance coverage for the Enterprise CAL Suite as of November 30, 2014.

Online Services Included with Enterprise CAL Suite

Enterprise CAL Suite with active SA coverage also includes the rights to Exchange Online Archiving for Exchange Server, Data Loss Prevention, and Exchange Online Protection.

Please note these resources are provided for reference purposes only and are not considered to be part of the Product Terms. To see more versions and languages click here.