Copilot bills per assigned seat, but value follows active users. The gap between the two is the clearest measure of wasted spend and the strongest lever you take into a renewal.
Microsoft 365 Copilot bills per assigned seat, not by monthly active users. The gap between seats you pay for and seats people actually use is the clearest signal of wasted spend, and the strongest lever you carry into a renewal.
Cost follows the seat. Value follows the active user. When those two numbers diverge, the difference is money spent on access nobody uses.
Copilot bills per assigned seat. Microsoft sets this out in the Copilot licensing documentation. Activity has no effect on the invoice.
Once a Copilot license is assigned to a user, it bills for the full annual term. Whether that user runs 200 prompts a week or none, the cost is identical.
Monthly active users counts the people who use Copilot at least once in a period. It is an adoption metric, not a billing metric, and the two are easy to confuse.
Every assigned seat that is not an active user is spend without return. At 30 dollars per seat per month, a 40 percent gap on 1,000 seats is 144,000 dollars a year on idle access.
Seat to active user gap, illustrative 1,000 seat estate
| Metric | Count | Annual cost | Read |
|---|---|---|---|
| Assigned seats | 1,000 | 360,000 dollars | What you pay |
| Monthly active users | 600 | 216,000 dollars | What earns value |
| Idle seats | 400 | 144,000 dollars | Reclamation target |
Idle seats are not free to drop mid term. The annual commitment means an idle seat keeps billing until the anniversary, so the gap compounds across the contract year.
Occasional users and senior leaders show the steepest fall in active use. They are often the first to be licensed and the last to be measured.
Microsoft exposes Copilot usage in the admin center. The Copilot usage report shows active users by app and by period.
Pick a threshold that reflects value, such as weekly use across at least two apps. A user who opened Copilot once in 30 days is technically active but not getting value.
Review usage every month, not just before renewal. The Microsoft Copilot adoption resources outline a measurement rhythm worth aligning to.
The common advice is that low active usage is an adoption problem to fix with more training, never a licensing decision. We disagree. In our reviews, a meaningful share of idle seats belonged to roles that were never going to be daily Copilot users, and no amount of enablement changed that. The buyer side move is to separate the two questions. Drive adoption where the role genuinely benefits, and reclaim seats where it does not. Treating every idle seat as a training failure keeps you paying for access that the work itself does not need.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
You pay for the seat the day you assign it. You get value only on the days the user shows up. Manage the distance between those two and Copilot pays for itself.
Reclamation is a process, not a one time cleanup. Microsoft documents license assignment controls in the Microsoft Product Terms, and the buyer side builds a recurring rhythm on top.
Pull usage monthly, flag seats with no sustained use, confirm with the manager, then unassign and pool. The pooled seats either go to a waitlist or come off the committed count at renewal.
Walk into the renewal with a 12 month active usage trend. A documented gap is the most credible argument for a lower committed seat count and a better unit price.
No. Copilot is billed per assigned seat, not by monthly active users. Once a license is assigned, it bills for the full annual term whether or not the user is active.
Assigned seats measure cost and active users measure value. The seat to active user gap is the share of paid licenses that nobody is actively using, and it is usually 30 to 45 percent within the first quarter.
At 30 dollars per seat per month, a 40 percent gap on 1,000 seats is about 144,000 dollars a year on idle access. The annual commitment means that idle spend compounds until the anniversary.
The Microsoft 365 admin center includes a Copilot usage report that shows active users by app and by period. It is the authoritative source for measuring adoption against assigned seats.
Define active in a way that reflects value, such as weekly use across at least two apps. A user who opened Copilot once in 30 days is technically active but is not getting meaningful value.
Yes. Pull usage monthly, flag seats with no sustained use, confirm with the manager, then unassign and pool them. Pooled seats can come off the committed count at the next renewal.
Sometimes, but not always. Some idle seats belong to roles that will never be daily Copilot users. Separate genuine adoption gaps, which training can fix, from seats the role does not need, which should be reclaimed.
A documented 12 month active usage trend is the most credible argument for a lower committed seat count and a better unit price. It turns an adoption metric into a negotiation lever.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
