The license type sets the bill before the price is ever discussed
Every Microsoft negotiation argues about the price per unit. The quieter decision, which unit, moves more money, because the type changes the denominator the price multiplies: user or device, subscription or perpetual, base or access. Three shifts on one workstation is three user licenses or one device license for the same work.
Prepared by Redress Compliance · August 15, 2026 · Microsoft advisory. License position reviews across enterprise estates, 2024 to 2026.
Executive summary
Microsoft licensing runs on three type decisions: user or device, subscription or perpetual, and base or access license. Each one changes what gets counted, and the count moves more money than the rate applied to it.
User covers one person on any device; device covers one machine for any number of people. Knowledge workers with a laptop and a phone price better per user; shift floors, shared workstations, and kiosks price better per device, and the uniform default overpays one of them.
Subscription grants rights while you pay; perpetual is owned at a version. Microsoft's commercial direction is subscription first and the perpetual channel keeps narrowing, so the real question is which workloads justify the subscription premium for currency and cloud rights.
Server products bill twice: the server license runs the software and Client Access Licenses cover what connects. A User CAL is one named person on any device, a Device CAL one machine for any user, and CALs should retire when their server retires. Mostly, they do not.
The same logic now runs through the cloud estate. E3 against E5 against F3, per user add ons, and consumption meters are the modern type decisions, each one setting the denominator before any discount is discussed.
The taxonomy, on one page
| Type | What it covers | Where it wins |
|---|---|---|
| User license | One named person, any device | Knowledge workers with multiple devices |
| Device license | One machine, any number of users | Shift floors, shared workstations, kiosks |
| Subscription | Rights while you pay, updates included | Workloads needing currency and cloud rights |
| Perpetual | Owned at a version, SA optional | Stable workloads that can hold a version |
| User CAL | One named user into the server estate | People outnumbered by devices |
| Device CAL | One device into the server estate | Devices outnumbered by people |
The table is symmetric, and estates are not. Wherever people outnumber machines, the device metric divides the bill; wherever machines outnumber people, the user metric does. The estate that counts both ways per population, from real headcount and device data, finds the split; the estate that standardizes on one type for administrative comfort pays the difference every year, invisibly, as the baseline.
The decisions that move the bill
- Count each population both ways before assigning a type: the user path and the device path, priced from actual headcount and device inventories, with the smaller honest number winning.
- Segment shift and frontline work explicitly, because the shared workstation pattern is where the device metric routinely divides the count by two or three.
- Choose subscription deliberately, not by default: the premium buys currency and cloud rights, and stable severable workloads on a held version are what perpetual still exists for.
- Tie every CAL to its server in the asset register, so the access licenses retire on the same day the server does instead of billing for a connection nobody can make.
- Apply the same discipline to the cloud tiers, since E3 against E5 against F3 and the add on stack are the same denominator decision in modern clothes.
The Microsoft licensing changes 2026 guide
The current program map, the SKU and type decisions, and the changes reshaping how Microsoft licenses are bought this cycle.
Get the guide →The denominator decision
Enterprise procurement is organized around the numerator. The price per seat gets benchmarked, negotiated, escalated, and reported, because the price is where the vendor conversation happens. The denominator, what actually gets counted, is decided earlier, usually by an administrator choosing whichever type is simplest to manage, and it never appears in a negotiation summary.
Run the arithmetic on why that allocation of attention is backwards. A hard fought 10 percent discount on user licenses covering a three shift floor saves a tenth of the bill. Moving that floor to device licenses divides the count by up to three, before any discount is discussed. The type decision routinely moves multiples of what the rate decision moves, and it is made by whoever fills in the enrollment defaults.
The CAL estate shows the same dynamic in slow motion. Access licenses attach to servers, servers retire, and the CALs mostly do not, because no process links the two. Year over year, the access layer accretes into a bill for connections that no longer exist, renewed on the strength of nothing but continuity. Zero CALs is what a retired server should leave behind; an unlinked asset register leaves all of them.
The subscription shift raises the stakes rather than retiring the question. As the perpetual channel narrows, the type decisions migrate: user against device becomes E3 against F3, the CAL question becomes the add on stack, and the version hold becomes the consumption meter. Every one of them is still a denominator decision, still made upstream of price, and still invisible in the discount report.
The practical inversion is to negotiate the count before the rate, exactly the sequence the renewal rewards: type per population, CALs tied to servers, tiers mapped to roles, and only then the percentage conversation, applied to a denominator you chose on purpose. The wider structure sits in the Microsoft licensing guide and the Microsoft practice.
Watch the briefing · 4:51Negotiating Microsoft E5, E7, and Copilot Cowork: The Two-Layer BillThe modern type decision: the license floor, the meter on top, and the truth the proposals omit.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What the license position reviews showed, 2024 to 2026
Across the Microsoft license position reviews we ran, the type layer carried the same findings in estate after estate:
Workers per shared workstation on frontline estates, the population where the device metric divides the user count.
Access licenses surviving their servers because nothing in the asset register linked the two lifecycles.
Three patterns recurred. Uniform user licensing across populations whose shape favored devices. CAL counts renewed on continuity rather than reconciliation, long after the servers changed. And cloud tier assignments inherited from the on premise defaults, carrying the old type mistake into the subscription bill.
The buyer side move is to own the denominator. The wider library sits in the Microsoft practice.
Your first five moves
- Map the estate into populations by how people and devices actually pair: knowledge workers, shift floors, kiosks, task workers.
- Price each population both ways, user path against device path, from real headcount and device data, and let the smaller honest number pick the type.
- Link every CAL to its server in the asset register and retire them together, starting with the servers decommissioned in the last three years.
- Revisit subscription against perpetual per workload where the choice still exists, paying the premium only where currency and cloud rights earn it.
- Carry the same audit into the cloud tiers, E3, E5, F3, and the add on stack, before the next renewal freezes the denominator. The Microsoft practice runs the review with you.
Frequently asked questions
What is the difference between a user and a device license?
A user license covers one named person on any device; a device license covers one machine used by any number of people. The choice changes the count the price multiplies: knowledge workers with laptops and phones price better per user, while shared workstations, shift floors, and kiosks price better per device.
What is the difference between subscription and perpetual Microsoft licenses?
A subscription grants rights while you pay, with updates included; a perpetual license is owned at a version, with Software Assurance optional on top. Microsoft's commercial direction is subscription first, and the perpetual channel keeps narrowing, so the real decision is which workloads justify the subscription premium for currency and cloud rights.
How do Microsoft CALs work?
Server products are licensed in two parts: the server license runs the software, and Client Access Licenses cover whatever connects to it. A User CAL covers one named user on any device; a Device CAL covers one device for any user. CALs attach to the server estate, which is why they should retire when their server retires.
How do you pick the right Microsoft license type?
Count both ways. For each population, price the user path against the device path from real headcount and device data, price subscription against perpetual where a choice still exists, and let the smaller honest number decide. The type decision changes the denominator, which is why it outweighs the discount conversation that follows it.
Why do device CALs beat user CALs on shift work?
Because three shifts of workers sharing one workstation is three user licenses or one device license for the same access. Wherever people outnumber machines, the device metric divides the bill; wherever machines outnumber people, the user metric does.
What is the most common license type mistake?
Defaulting the whole estate to one type because it is administratively simple: every worker a user license, every server's CALs bought once and never retired. The uniform default overpays wherever the population's shape does not match the metric, and CALs that outlive their servers keep billing for access nobody can use.
Do license types still matter in a cloud first estate?
More than ever, because the same logic now runs through SKU tiers and add ons. E3 versus E5 versus F3, per user add ons, and consumption meters are the modern type decisions, and each one changes the denominator before any discount is discussed.
Negotiating Microsoft E5, E7, and Copilot Cowork: The Two-Layer Bill
E7 at $99 vs $117 in components, and the truth proposals omit: $99 is the governance floor. Agent execution bills separately through Copilot Credits with no rollover, Security Copilot overages at $6 per unit, and Cowork priced as license plus meter.
