User CAL vs Device CAL — which one is cheaper?
Last reviewed by the MSLicenseHub Licensing Desk.
The math is simple. Count how many users and how many devices will access the server. Whichever number is smaller is the SKU you want.
If 30 staff each have a laptop, a phone and a desktop (90 devices, 30 users), User CALs win — you buy 30 instead of 90. If 20 shift workers share 5 shop-floor terminals around the clock (5 devices, 20 users), Device CALs win — you buy 5 instead of 20. The CAL type is set per server role, so the Exchange Server and the Windows Server in the same rack can use different CAL types.
Apply this to your deployment
- Server licence
- User or device
- CAL version
Check the server licence separately from access rights. Concurrent connections do not replace the count of licensed users or devices; verify exceptions and CAL versions against the specific product terms.
Decision checklist
| Check | What to record |
|---|---|
| Product and version | Record the full name, edition, version and part number in the quote. |
| Scope of use | Identify the user, device or deployment; count only the metric applicable to this product. |
| Evidence and support | Retain the agreement, invoice and support lifecycle date; perpetual licensing does not mean perpetual support. |
Official Microsoft terms and licensing guidance · Product support lifecycle
Practical checklist
- Choose User CALs when people use several devices each (laptop, phone, home PC).
- Choose Device CALs when several people share one device, such as shift workers or kiosks.
- Count both options for your real environment; the cheaper choice is simply whichever number is lower.
- You can mix User and Device CALs in the same deployment, but each person or device must be covered by one of them.
- CALs must be the same version as or newer than the server software.
Common mistakes to avoid
- Counting concurrent connections instead of users or devices.
- Buying User CALs for a shared-terminal environment.
- Mixing up Windows Server CALs with RDS CALs.
Official source: Microsoft documentation. Licensing terms change; confirm against the current Product Terms before buying.
Still unsure?
Talk to a licensing specialist for a written, signed quote tailored to your environment.
Contact sales