Fix it now
There is a device-based Microsoft 365 licence, but exactly one: Microsoft 365 Apps for enterprise (device), sold only through Enterprise Agreement and Enterprise Agreement Subscription. Everything else in a Microsoft 365 tenant is assigned per user. The genuine per-device choice lives on the on-premises side, where Windows Server, Exchange, SharePoint and SQL Server all sell CALs both ways.
- Buy device CALs wherever several people share one machine on an on-premises server: shift terminals, shop floors, workshops, nursing stations.
- Buy user CALs wherever people reach the server from more than one device, or from hardware you do not own. A device CAL covers the machine, so it will not follow a contractor home.
- Buy both if the estate is mixed. Nothing requires one model across an organisation, and most real estates end up split by population rather than by product.
- Look at Microsoft 365 Apps for enterprise (device) only if you are on an Enterprise Agreement and the devices are Microsoft Entra joined or hybrid joined. Outside that channel it is not something you can order.
- For shift workers who need Microsoft 365 services, price the frontline plans rather than hunting for a device licence. F3 gives a 2 GB mailbox through Outlook on the web and no desktop apps; F1 has no mailbox rights at all.
- Use the device licences that exist for hardware nobody owns – Microsoft Teams Rooms Basic and Pro are device-based – and do not try to stretch them to cover staff.
Counting is per product, not per organisation. The same building can correctly need device CALs for Windows Server, user CALs for Exchange, and per-user Microsoft 365 seats for everybody.
If you have counted heads and machines per product and one number is clearly smaller, you have your answer. Below is where each model exists, what the device SKU actually requires, and the three places the simple rule breaks.
Why it happens
Split the estate in two before you count anything, because cloud subscriptions and on-premises server products follow different rules. Microsoft 365 services are provisioned against the identity that signs in, so with one narrow exception the licence belongs to a person and travels with them. On-premises server software is licensed by a server licence plus a client access licence, and the CAL can be attached to a user or to a device at your choice, per product.
The exception is worth naming properly because it is often described as not existing. Microsoft 365 Apps for enterprise (device) is a real licence, assigned to a device rather than a person, and anyone who signs in on that device can use Microsoft 365 Apps to create and edit documents. It is available to commercial customers through Enterprise Agreement and Enterprise Agreement Subscription only, with an education equivalent sold through Enrollment for Education Solutions. It is not something a small business on a partner subscription can order, which is why the folklore that it does not exist survives.
It also carries prerequisites that rule out a lot of the estates people would want it for. The device has to be Microsoft Entra joined or Microsoft Entra hybrid joined, running a supported Windows client or Windows Server 2019 or 2022, on version 1907 or later of Microsoft 365 Apps for enterprise. The licence is set to expire in 90 days so the device does not need constant internet access, and licences are assigned to one group with no support for nested groups.
Many people, few machines
You have this one if Three shifts sharing twelve terminals, a warehouse floor, a set of tills, a shared clinical workstation.
- Count devices for the on-premises products: a Windows Server device CAL permits one device, used by any user, to access instances of the server software.
- Do the same count separately for Exchange, SharePoint and SQL Server if those servers are reached from the same machines. SQL Server’s Server+CAL model exists on Standard edition only.
- For Microsoft 365 services on those same shared screens, price frontline seats per person instead. There is no shared seat, and the design intent is a cheaper user licence rather than a device one.
Few people, many machines
You have this one if Office staff with a laptop, a desktop and a phone each, or anybody working from home on their own equipment.
- Count users. A Windows Server user CAL permits one user, using any device, to access instances of the server software.
- Remember that a device CAL does not follow a person home. An unlicensed home machine reaching the server is an uncovered access however well the office is licensed.
- For Windows itself, note that Windows 11 Enterprise E3 and E5 are available per user in Commercial Licensing and allow five Windows instances per licensed user – but they are upgrade licences and need Windows Pro underneath.
Hardware with nobody behind it
You have this one if Meeting rooms, reception screens, common-area phones, unattended kiosks and signage.
- Use the licences built for it. Microsoft Teams Rooms Basic and Microsoft Teams Rooms Pro are device-based and assigned to the resource account that authenticates the device.
- Do not assign a Teams Shared Space licence to a Teams Rooms device – Microsoft states they are not supported on and will not work with those devices.
- On the server side, an unattended scanner, till or monitoring appliance still consumes a device CAL. There is no user to attach one to, and no exemption for machines.
Full reference
Where each model genuinely exists
| Product area | Per user | Per device | Usual answer |
|---|---|---|---|
| Microsoft 365 seats (Business and Enterprise plans) | The model | Not available | Per user |
| Microsoft 365 Apps for enterprise | Yes | Yes – Microsoft 365 Apps for enterprise (device), EA and EAS only | Per user unless you are on an EA with shared, Entra-joined devices |
| Windows Server CALs | One user, any device | One device, any user | Whichever count is smaller |
| Remote Desktop Services CALs | Yes, tracked in Active Directory | Yes, tracked by the licence server | Device for fixed thin clients, user for roaming staff |
| Exchange Server SE CALs | Yes | Yes | User, because mail follows the person |
| SharePoint Server CALs | Yes | Yes | User in most deployments |
| SQL Server Server+CAL | Yes | Yes | Standard edition only; core licensing above that |
| Windows client operating system | Enterprise E3 and E5 are per user | OEM and retail are per device | Device, for most organisations |
| Meeting room systems | Not applicable | Teams Rooms Basic or Pro | Device, always |
What the device-based Apps licence needs before it will work
If you are on an Enterprise Agreement and the shared-device problem is specifically about Office applications, the device licence is worth a look – but read the prerequisites before you plan around it. The device must be Microsoft Entra joined or Microsoft Entra hybrid joined; it must run a supported version of Windows 11, the Windows 10 General Availability Channel, Windows Server 2022 or Windows Server 2019; and Microsoft 365 Apps for enterprise must be at version 1907 or later. The licence expires after 90 days without a check-in, which is deliberate so the device need not be online constantly.
One operational detail catches people out. Licences are assigned to a single group and provided to all devices in that group, and devices in groups nested underneath it do not receive a licence. If your device groups are built as a hierarchy, they will need flattening for the assignment to work.
Shared screens on Microsoft 365, without a device licence
For most organisations the shared-screen problem is answered by a cheaper user seat rather than a device one. Microsoft 365 F3 and F1 are per-user frontline plans, and the split between them matters: neither includes the desktop client apps, F3 provides a 2 GB mailbox reached through Outlook on the web and full access to the web and mobile apps, and F1 has no mailbox rights at all – it includes the Exchange Kiosk plan to enable the Teams calendar only, with read-only access to the web and mobile apps. Both give 2 GB of OneDrive storage.
Six people on a shared kiosk still need six seats. What changes is which seat. Choosing F1 for staff who need to send mail is the mistake that follows from reading only the price, and it is not recoverable by configuration.
Mixing models, and proving you did it correctly
You may hold user and device CALs against the same server, and most estates should. The requirement is simply that every access is covered by one or the other. In practice that means keeping the count as two documented populations – the shared machines, and the people who reach the server from anywhere else – rather than a single total that nobody can reconstruct a year later.
Note also that no licensing model changes what a CAL is for. Putting a web front end, an application server or middleware between people and the server does not reduce the count: Microsoft’s Universal License Terms state that any method used to pool connections or reduce the number of operating system environments, devices or users a product directly manages does not reduce the number of licences needed.
The ceiling that ends the conversation
One number sits above all of this for smaller organisations. Microsoft 365 Business Basic, Business Standard and Business Premium share a single cap of 300 seats in total across the Business family, and Microsoft reserves the right to enforce it. If a shared-device plan exists because headcount is growing faster than the seat budget, the seat model is not the constraint you are about to hit.
When a licence is the actual fix
For staff who each need their own mailbox, files and desktop applications, a per-user Microsoft 365 seat is the only model on offer and Microsoft 365 Business Standard is the ordinary answer for that population. The genuine per-device saving is on the on-premises side, and it is worth getting right before the order: Arco supplies both user and device CALs for Windows Server, Remote Desktop Services and Exchange, and will count your shared machines and your roaming users separately so the quote reflects the mix rather than one model applied to everybody. If your shift workers only need mail and the web apps, we will quote frontline seats rather than Business Standard, and say so.
Questions people ask about this
Is there really no per-device Microsoft 365 plan?
There is one: Microsoft 365 Apps for enterprise (device), available to commercial customers through Enterprise Agreement and Enterprise Agreement Subscription. It licenses the device rather than a person, so anyone signing in can create and edit documents. It requires the device to be Microsoft Entra joined or hybrid joined, on a supported Windows build, and it covers the Office applications – not the mailbox, not the tenant services.
Can I mix user CALs and device CALs on the same server?
Yes, and most estates should. You may hold both and use each where it fits, provided every access is covered by one or the other. Keep the two populations documented separately so the count can be reproduced later, because a CAL total nobody can explain is worth very little in a review.
Do device CALs cover people working from home?
Only if they use a licensed device. A Windows Server device CAL permits one device, used by any user, so an unlicensed home computer reaching the server is not covered. Home and roaming work is the classic case for user CALs, which permit one user using any device.
What licence does a meeting room system need?
A device licence built for it: Microsoft Teams Rooms Basic or Microsoft Teams Rooms Pro, assigned to the resource account the device signs in with. Microsoft states that Teams Shared Space licences are not supported on and will not work with Teams Rooms devices, so do not substitute one to save money.
Which model is cheaper overall?
Whichever number is smaller, product by product. Count people, count devices, and compare per product rather than assuming a model. The answer commonly differs between two servers in the same building, and the frequent result is a mixed estate rather than a single model.
Does putting an application in front of the server reduce the CAL count?
No. The Universal License Terms state that any method used to pool connections or reduce the number of operating system environments, devices or users a product directly manages does not reduce the number of licences a customer needs. You license the users and devices at the far end of the chain, however many hops sit in between.
