Fix it now
Count the people who will authenticate, count the devices that will, and buy CALs of whichever type gives the smaller number. Microsoft’s own definitions are the whole rule: a user CAL allows access from any device by one user, and a device CAL allows access from one device by any user. Both reach backwards to earlier server versions but never forwards.
- Buy User CALs where people outnumber the devices they use – office staff with a laptop and a phone, field workers, hybrid working.
- Buy Device CALs where devices are shared by more people than there are devices – shift work, shop floor terminals, ward and warehouse PCs, kiosks.
- Split the estate rather than picking one type for the whole site. Take the smaller number within each group, because a warehouse and a head office are two different problems in one building.
- Buy CALs at least as new as your newest server. Microsoft states that Windows Server 2025 CALs permit access to Windows Server 2025 and prior versions of the server software.
- Do not buy for peak concurrency. The definitions are per named user or per named device, not per simultaneous connection, and buying twenty CALs for a hundred staff is the most common compliance failure in this area.
- Check Essentials before buying any CALs at all. Microsoft publishes Windows Server 2025 Essentials as OEM only for up to 25 users and 50 devices, on single-socket servers of up to 10 cores with one VM.
External access is a separate decision. Microsoft’s rule is CALs for each accessing external user or device, or alternatively a Windows Server External Connector licence per server, which permits access by any number of external users where that access is for the benefit of the licensee.
If one of the two counts is clearly smaller and the estate is uniform, that is the decision made. Below is where the rule breaks down, what multiplexing does and does not change, and how to count before you order.
Why it happens
The server licence covers the software running on the hardware. It grants nobody the right to use it – that right comes from the CAL, and Microsoft treats them as separate purchases because a server with four users and a server with four hundred cost the same on the core side. If a quote for a new server does not have CALs on it, the quote is incomplete.
The two shapes are defined precisely in Microsoft’s Product Terms, and the definitions are the entire decision rule: a user CAL allows access to the corresponding version of the server software or earlier versions from any device by one user; a device CAL allows access to the corresponding version or earlier versions from one device by any user. Neither is better. The cheaper one is whichever of your two headcounts is smaller, and the version wording tells you the other half of the rule – CALs reach backwards but never forwards.
What they are not is concurrent licences. Buying twenty CALs for a hundred staff on the reasoning that only twenty are ever logged on at once is the single most common Windows Server compliance failure, and it is not a grey area: the licence is assigned to a named user or a named device, whether or not everyone is connected at the same moment.
More devices than people
You have this one if Everybody has a laptop and a phone, and several have a desktop as well.
- User CALs, comfortably. One user CAL covers that person from any number of devices.
- Staff turnover is handled by reassignment: the Product Terms permit reassignment on termination of the user’s employment or contract, without the 90-day wait.
- New devices cost nothing extra, which is why this shape suits a growing device estate more than a growing headcount.
More people than devices
You have this one if Shifts, shared terminals, tills or handhelds passed between staff.
- Device CALs, and it will not be close. One device CAL covers that device used by any number of people.
- Turnover does not touch the count at all, because the hardware stays where it is.
- Each new device needs another CAL, so this shape suits a stable device estate with a churning workforce.
The two populations do not overlap neatly
You have this one if A warehouse of pickers sharing handhelds, plus office staff with a laptop each, in the same building.
- Split it and count each group separately. Device CALs for the shared estate, user CALs for the office.
- The definitions are per licence, so nothing in them requires one type across an organisation.
- Buying one type for the whole site because it is tidier is how organisations end up paying for both halves at the wrong rate.
The rule that catches people out afterwards is reassignment. Microsoft’s Product Terms permit reassigning a licence to another device or user, but not less than 90 days since the last reassignment of that same licence – with exceptions for permanent hardware failure or loss, termination of the user’s employment or contract, and temporary reallocation of CALs to cover a user’s absence or a device that is out of service. What that does not permit is rotating a small pool around a large population to cover whoever is working. That is concurrent licensing under another name.
Full reference
User CAL against Device CAL
| Dimension | User CAL | Device CAL |
|---|---|---|
| Microsoft’s definition | Access to the corresponding version or earlier from any device by one user | Access to the corresponding version or earlier from one device by any user |
| Ideal ratio | More devices than people | More people than devices |
| Typical fit | Office staff with a laptop and a phone, field workers, hybrid working | Shift work, shop floor terminals, call centres, ward and warehouse PCs, kiosks |
| Effect of staff turnover | Reassign as people leave and join | None; the hardware stays |
| Effect of new devices | None; the person is already covered | Each new device needs another CAL |
| Contractors and temporary staff | Each named person needs one | Absorbed by the device they share |
| Version reach | Backwards to earlier server versions, never forwards | Backwards to earlier server versions, never forwards |
| Reassignment | Not less than 90 days since the last reassignment of that licence, with documented exceptions | Same rule, same exceptions |
Multiplexing, and the one exception people miss
Putting a middle tier, a web front end, a connection pool or an integration service between your staff and the server does not reduce what you owe. Microsoft states it twice and plainly: multiplexing does not reduce the number of licences needed, and users and devices are always required to have the appropriate licences regardless of their direct or indirect connection to a product. Architectures designed to hide users from the server do not hide them from the licence.
There is, however, a real exception, and it is worth knowing because it is often the difference between a workable design and an unaffordable one. Microsoft’s multiplexing guidance states that where data distribution results from manual activity – a person uploading a file onto a server or emailing the file – a CAL is not required for the users or devices accessing those manually transmitted files. The line is between automated movement, which carries the licensing with it, and a licensed human being deliberately handing something on, which does not.
Where CALs are not required at all
- Access by another licensed server. Microsoft’s Product Terms state that CALs are not required for access by another licensed server.
- Server software running a Web Workload or an HPC Workload. This is the published exemption, and it is defined by workload rather than by whether the visitor was anonymous – which is how it is usually paraphrased, wrongly.
- External users covered by an External Connector. Microsoft’s rule is CALs for each external user or device, or alternatively an External Connector licence per server, which permits access by any number of external users where that access is for the licensee’s benefit rather than the external user’s.
- Windows Server Essentials, within its own limits. Microsoft publishes Windows Server 2025 Essentials as OEM only, for up to 25 users and 50 devices, on single-socket servers of up to 10 cores running one VM; the Product Terms express it as up to 25 user accounts with the Connector software on no more than 50 devices.
How to count properly before you order
- List every human being who will authenticate against the server: part-timers, contractors, directors who only read email, and anyone in a branch office.
- List every device that will authenticate in its own right, including shared terminals, tablets, handheld scanners and network-attached hardware that authenticates rather than passing traffic on behalf of somebody.
- Set aside anything covered by the Web Workload or HPC Workload exemption, or by another licensed server.
- Split the estate into groups where the ratios genuinely differ, and take the smaller number within each group rather than across the whole site.
- Set the version at the newest Windows Server you will run in the next few years, because CALs reach backwards and never forwards.
- Handle external parties separately: per-user or per-device CALs for them, or an External Connector per server if the numbers make that the better shape.
Which type to buy, by situation
- An office where everyone has a laptop and a phone: User CALs, comfortably.
- A factory, warehouse or ward running shifts across shared terminals: Device CALs, and it will not be close.
- A retail chain with fixed tills and rotating staff: Device CALs for the tills, User CALs for head office.
- A business under 25 users and 50 devices on a single-socket server: check Windows Server 2025 Essentials first, since access rights are built in and it needs no separate CALs – but note that Microsoft publishes it as OEM only.
- A public-facing service: no CALs for a Web Workload, and an External Connector or per-external-user CALs where named external parties authenticate.
The version question, stated once
Microsoft’s wording for the current release is that Windows Server 2025 CALs and External Connector licences permit access to Windows Server 2025 server software and prior versions of Windows Server software. Read that in both directions. You do not need a separate set of CALs for every server: one set at the version of your newest server covers every older server you own, which is where organisations most often overbuy. And an older CAL never reaches a newer server, which is what forces a repurchase – not the passage of time, but the day somebody upgrades a server and nobody costed the CALs alongside it.
When a licence is the actual fix
If your headcount is smaller than your device count, Windows Server 2025 User CALs are the simpler licence and they stop needing attention every time somebody is issued a second machine. Arco supplies both User and Device CALs for Windows Server 2025 and earlier versions in the usual pack sizes. Send us your two numbers plus a note on where shift patterns or shared terminals apply, and we will tell you which type each part of the estate should be on rather than pricing one type across the lot. If the site is small enough that Windows Server 2025 Essentials would cover it – up to 25 users and 50 devices, single socket, OEM only – we will say so and quote nothing.
Questions people ask about this
Do I need CALs if the server only runs a database or a line-of-business application?
Yes, if people or devices authenticate to Windows to reach it. The Windows Server CAL is about access to the server software, not about the application, and the application will usually have its own licensing on top. SQL Server in particular has a separate model that has nothing to do with the Windows one.
Does every server need its own set of CALs?
No, and this is where organisations most often overbuy. Microsoft states that Windows Server 2025 CALs permit access to Windows Server 2025 server software and prior versions. Ten servers do not need ten sets. They need one set, sized to your users or devices, at the version of your newest server.
Can we buy fewer CALs than staff if only some are logged on at once?
No. The definitions are per named user or per named device – a user CAL allows access from any device by one user, a device CAL allows access from one device by any user – and neither mentions concurrency. Buying twenty for a hundred staff is the most common compliance failure in this area and it is not a grey area.
Does putting a web front end in front of the server reduce the CALs we need?
No. Microsoft states that multiplexing does not reduce the number of licences needed and that users and devices always require the appropriate licences regardless of direct or indirect connection. The one published exception is manual activity: where a person uploads or emails a file, a CAL is not required for the users accessing those manually transmitted files.
What about a printer, scanner or camera that logs on to the server?
If it authenticates as a device in its own right, it needs a device CAL. In practice much of that hardware writes to a share using a service account on behalf of a licensed person, and the licensing follows the human being whose work it is doing. That distinction is worth confirming against your own agreement rather than assuming, because it changes the count in a large estate.
