User CAL vs. Device CAL – which is right for your business?
Anyone running a Windows Server in their business will, sooner or later, face the question: User CAL or Device CAL? At first glance, the decision may seem like a minor procurement detail – but in reality, it determines whether you end up overpaying by several hundred euros a year for your access licences, or whether you discover a gap in your licence inventory during an audit. The short answer is: if your staff each use multiple devices, User CALs are the more cost-effective choice. If, on the other hand, several people share the same devices – for example, in shift work, at till terminals or on workshop computers – you’ll find Device CALs more cost-effective. In practice, the answer is rarely so clear-cut, as most organisations face both situations simultaneously.
In this guide, we explain how Microsoft access licences work, where the typical cost pitfalls lie, and how you can use a simple decision tree to find the right model for your business in just a few minutes.
Key points at a glance
- A CAL (Client Access Licence) is not software, but an access right. It is required in addition to the server licence.
- A User CAL licences a named individual – who may access the software from any number of devices.
- A Device CAL licences a specific device – any number of people may work on it.
- Rule of thumb: more devices than people in the company? User CALs. More people than devices? Device CALs.
- User CALs and Device CALs can be freely combined within the same environment.
- CALs are backwards compatible but not forwards compatible: a 2025 CAL can access older servers, but a 2022 CAL cannot access a Windows Server 2025.
- For Remote Desktop Services, you require a separate RDS CAL in addition to the Windows Server CAL.
What is a CAL? Microsoft access licences explained briefly
CAL stands for Client Access Licence. The term often misleads newcomers, as a CAL is not a piece of software that you install, nor, in most cases, a product key that you enter anywhere. A CAL is purely a right of use: the permission for a specific person or device to access the services of a server.
A server licence is not the same as a right of access
With its server products, Microsoft consistently distinguishes between two things: the right to run the software and the right to use it. The server licence – which, with Windows Server, is now generally based on the number of processor cores – allows you solely to install and run the operating system on the hardware. It does not include any access rights for your staff.
This is precisely where the most common misunderstanding arises in practice. A Windows Server does not deny a client access simply because no CAL is available. Unlike with product activation, there is no technical enforcement for standard CALs. So, just because everything works does not mean that everything is licensed. The CAL requirement is a purely legal one – and becomes relevant at the latest during a licence audit, when additional licences are required.
Direct and indirect access: why multiplexing does not help
It is not only obvious forms of access that require a licence, such as opening a file on a network share or printing via a print server. Logging on to Active Directory, obtaining an IP address via DHCP or name resolution via DNS are also considered to be the use of server services.
A special case that regularly leads to additional charges in audits is what is known as ‘multiplexing’. This refers to access being bundled via an intermediate layer – for example, via a web application, an application server or an ERP system, which in turn accesses the server using its own service account. Microsoft explicitly states in its licence terms that such technical bundling does not reduce the number of licences required. The decisive factor is always how many people or devices at the end of the chain actually access the server services.
Which products require access licences
The ‘server plus CAL’ model applies to Microsoft’s traditional on-premises server products. These primarily include Windows Server in the Standard and Datacentre editions, as well as – depending on the chosen licensing model – SQL Server and Exchange Server. For specific functional areas, additional, so-called additive access licences are required; the best-known of these is the RDS CAL for Remote Desktop Services.
There are a few defined exceptions to the CAL requirement. These include publicly accessible web content, certain high-performance computing scenarios, and access by a maximum of two users who access the server exclusively for administrative purposes. For external users such as customers or partners, Microsoft offers the External Connector licence as a server-based alternative to purchasing multiple individual CALs.
What is a User CAL?
A User CAL is assigned to a named individual. This person may then access the server services from any number of end devices – from their office computer, from a laptop whilst working from home, from a work mobile phone, and from a tablet in a meeting room – without incurring additional licences for each device.
How per-user licensing works
The allocation is organisational, not technical: you maintain a list of which CAL is assigned to which person. What matters is the number of people, not the number of devices or concurrent connections. A company with 40 employees who collectively use 95 end devices requires 40 User CALs under the user model – regardless of how many devices are connected to the network.
Typical use cases for User CALs
- Knowledge work and administration, where each person uses a desktop, laptop and smartphone simultaneously
- Companies with home-office or hybrid models, where staff work from different locations
- Environments where personal devices are permitted for business access
- Field staff, installation teams and sales staff with mobile access via tablets and mobile devices
- Environments with Active Directory, where user accounts are already properly maintained
What is a Device CAL?
A Device CAL is assigned to a specific device. From a licensing perspective, it does not matter who is working on that device: whether one person or twelve people take turns using it, only a single licence is required.
How per-device licensing works
The key factor here is the number of devices accessing server services. A manufacturing plant with 90 employees working in a three-shift system, who share 18 workshop terminals, requires only 18 Device CALs. This is the classic scenario in which the device-based model fully demonstrates its cost advantage.
It is important not to interpret the term ‘device’ too narrowly. Thin clients, hand-held scanners, time-and-attendance terminals, point-of-sale systems and machine control computers can also be devices subject to licensing as soon as they use server services. It is precisely these devices that are often overlooked when assessing requirements.
Typical use cases for Device CALs
- Shift work and rotating shifts in production, logistics and care
- Shared workstations in warehouses, workshops, laboratories or service points
- Point-of-sale, kiosk and self-service terminals
- Training rooms, libraries and publicly accessible computer workstations
- Environments without Active Directory, where user-specific allocation is difficult to document
User CAL vs. Device CAL: a direct comparison
The following overview summarises the practical differences:
| Criterion | User CAL | Device CAL |
|---|---|---|
| Licensed to | a named individual | a specific end device |
| Access is permitted for | that person from any number of devices | any number of people using this device |
| Requirements depend on | the number of staff | Number of devices accessing the system |
| Cost-effective for | more devices than people | more people than devices |
| Working from home and BYOD | very well suited | usually uneconomical |
| Shift work | usually uneconomical | Very well suited |
| Administration | Assignment to user accounts, ideally with Active Directory | Inventory of end devices required |
| Staff turnover | Re-assignment possible at any time upon leaving the organisation | Not an issue, as it is device-dependent |
| Device replacement | Not an issue, as it depends on the individual | Reassignment to the replacement device required |
Decision tree: Which CAL is right for your business?
In the vast majority of cases, you can reach a sound decision in just three steps.
Step 1: Count users and devices
First, work out how many people access server services and how many devices are used for this purpose. Include all devices in your count, not just traditional desktop computers – that is, also laptops, work mobile phones, tablets, terminals and scanners.
If the number of devices is significantly higher than the number of users, this favours User CALs. If it is significantly lower, this favours Device CALs. If the ratio is close to one-to-one, Step 2 will be the deciding factor.
Step 2: Review working practices
A simple headcount is insufficient if changes to your work organisation are foreseeable. Ask yourself: Will working from home be expanded? Should personal devices be permitted? Is the workforce growing faster than the number of devices? Each of these developments shifts the balance in favour of User CALs, as additional devices do not incur extra costs under this model.
Conversely, Device CALs remain the right choice if fixed workstations are occupied on a rotating basis and staff numbers fluctuate – for example, due to seasonal staff or agency workers. In such cases, demand does not increase with every new employment contract.
Step 3: Clarify special cases
- External users: If customers, suppliers or partners access server services, consider an External Connector licence instead of numerous individual CALs.
- Machines and automation: Control computers and unattended systems are devices in the licensing sense and require a Device CAL if they cannot be assigned to a specific person.
- Administration: Microsoft provides an exemption from the CAL requirement for purely administrative access by a maximum of two users.
- Remote Desktop: If work is carried out via Remote Desktop, an additional RDS CAL is required.
Combining User and Device CALs: when it’s worth it
Microsoft expressly permits the combination of both licence types within the same environment. In practice, this is precisely the most cost-effective solution for many medium-sized businesses: User CALs for administration, sales and management, and Device CALs for shared workstations in the warehouse and production.
The price of this optimisation is a greater administrative burden. You must be able to document at any time which person and which device is covered by which licence. A neatly maintained licence register is therefore essential – those who do not keep one are often better off with a uniform model.
Three practical calculation examples
Example 1: Office team with 15 staff members
A planning office employs 15 people. Each of them uses a desktop computer, a laptop for client meetings and a work mobile phone – a total of 45 end devices. Under the device model, 45 licences would be required; under the user model, 15 are sufficient. The decision is clear: user CALs, with potential savings of two-thirds.
Example 2: Manufacturing plant operating in shifts
A manufacturing company employs 60 people working in three shifts. There are 14 terminals in the production hall for order confirmations and material postings, plus 4 computers in the workshop management office. In total, therefore, 18 devices access the Windows Server. Instead of 60 user CALs, 18 device CALs are sufficient here.
Example 3: Mixed environment comprising administration and warehouse
A retail company has 22 administrative staff, each working with a laptop and a mobile device, as well as 35 warehouse staff who share 9 hand-held scanners and 3 packing station computers.
A uniform model would be expensive in both scenarios: 57 User CALs or 56 Device CALs. The mixed solution requires just 22 User CALs for administration and 12 Device CALs for the warehouse – that is, 34 licences instead of 56 or 57.
Special case: RDS CAL – the additional licence for Remote Desktop Services
Hardly any other topic in licensing consultancy generates as many queries as the distinction between Windows Server CALs and RDS CALs.
Why RDS CALs are additionally required
The Windows Server CAL covers general network access: file sharing, print services and logging into Active Directory. However, as soon as users open a graphical session on the server via Remote Desktop – the classic terminal server setup – an additional RDS CAL is required. The two licences are not interchangeable; they complement one another. Anyone using Remote Desktop Services generally requires both.
This does not apply to remote maintenance alone: two simultaneous administrative sessions are permitted without an RDS CAL. Anything beyond that requires the Remote Desktop Session Host role and the appropriate access licences.
Per user or per device: the technical difference
RDS CALs are also available on a per-user or per-device basis, and the selection criteria correspond to those of Windows Server CALs. However, there is an important difference in the technical implementation: unlike standard CALs, RDS CALs are installed and activated on a licence server.
Device-based RDS CALs are technically enforced. Once all available licences have been issued, the server will deny connections to further devices. User-based RDS CALs are issued from a pool and are not technically enforced – compliance in this case is entirely your responsibility. When using RD Web Access, the user-based model is recommended, as otherwise every device that accesses the portal will consume a licence.
Version locking, reallocation and compliance
CALs are backwards compatible, but not forwards compatible
Access licences are tied to a specific product version. The rule is: the CAL version must be at least as high as the version of the server being accessed. A Windows Server 2025 CAL therefore also entitles the user to access a Server 2022, 2019 or 2016. The reverse is not true – a 2022 CAL does not cover a Windows Server 2025.
This is why CALs must regularly be updated when upgrading a server. Anyone with an active Software Assurance or subscription will receive the new CAL version as part of the agreement; without this cover, a new purchase is required. The edition, however, is not version-specific: the same CAL applies to both Windows Server Standard and Datacentre.
The 90-day rule for reallocation
A CAL may be reassigned to another person or device; however, according to the Microsoft Product Terms, this can generally only take place at the earliest 90 days after the last assignment. Microsoft provides for clearly defined exceptions to this period: in the event of a permanent hardware fault in the licensed device, when an employee leaves the organisation, and in the case of a temporary replacement during an absence or a device failure.
In practical terms, this means you cannot move licences back and forth between employees on a day-to-day basis to reduce your licence count. Organisations with significantly fluctuating team sizes should factor in a small licence buffer. The deadlines and exceptions that apply to you in individual cases depend on the licence programme and your contract – the current version of the Microsoft Product Terms always takes precedence. If in doubt, we will clarify this with you before you implement any reallocation.
Obligation to provide evidence in a licence audit
As standard CALs are not technically enforced, there is often no report that you could simply export in the event of an audit. The burden of proof lies with you. You should therefore keep the following on hand at all times:
- Purchase receipts and licence certificates for all CALs purchased, sorted by version
- an up-to-date allocation list: which CAL is assigned to which person or device
- an overview of the servers in use, including version and edition
- Documentation of re-assignments, including the date and reason
- in mixed environments, a clear distinction as to which area is licensed under which model
Conclusion: How to make the right decision
The choice between a User CAL and a Device CAL is, at its core, a simple calculation, weighted by how your organisation operates. Count the number of people and devices, assess the direction in which your business is heading, and do not shy away from a hybrid solution if administration and production operate differently.
For most office-based and service-sector companies, User CALs are now the obvious choice, as several end devices are typically in use per person. Where workstations are shared, however, Device CALs remain the clear advantage. In both cases, it is not so much the type of licence that matters as the clear documentation behind it.
Are you unsure which model is more cost-effective for your environment? Tell us the number of your staff and end devices – we’ll assess your requirements and put together the right combination of server licences and access licences for you. Get in touch with our team of experts now!
FAQ: Frequently asked questions about User CALs and Device CALs
Your decision. Our support.
Would you like to implement your Microsoft Server licensing securely and in a way that suits your business? Lizenzdeals24 supports you in making your selection, prepares a bespoke quote on request and is available to answer your questions personally.
Still unsure?
We’ll help you choose between User CALs and Device CALs to suit your business structure.
Request licensing advice →Tailored quote
Do you need multiple licences or would you like to discuss your specific requirements before purchasing?
Send a quote request →Available in person
Our customer service team is available to assist you directly by telephone.
+49 2173 2643330 Mon–Fri · 09:00–18:00Rheinpromenade 2 · 40789 Monheim am Rhein · Germany