SamTech 365

Power Platform, Copilot & SharePoint guides by Samir Daoudi

Copilot Licences: Assigned vs Active, and When to Reclaim Idle Seats

Assigned isn’t adopted. Learn how to measure active Copilot users, set a fair dormancy threshold and reclaim idle Copilot licences without a backlash.
Copilot Licences: Assigned Is Not Adopted

Open the Microsoft 365 admin centre and in about four clicks you can see how many Copilot licences you bought and how many you’ve assigned. Both numbers are accurate. Neither answers the question you’ll be asked at renewal: “Is this actually working?”

Assignment is something IT does. Adoption is something users do. In this post I explain how I help clients measure Copilot licences assigned vs active, how to set a sensible dormancy threshold, and how to reclaim idle seats without it feeling like a cost-cutting exercise.

Three numbers, not one

Every Copilot estate has three populations, and the gaps between them are where the money is:

  • Purchased: what finance pays for every month.
  • Assigned: licences attached to a named person.
  • Active: people who actually used Copilot in a real app, within a time window you define.

The two gaps are different problems with different owners:

Gap What it is Owner Fix
Purchased but not assigned Procurement debt: seats bought for a phase two that slipped, or for leavers never replaced Licensing and procurement Assign or release at renewal
Assigned but not active Real people who aren’t using their licence Adoption first, then licensing Coach first, reclaim second

Report them as one “utilisation %” and you’ll get one answer, usually “more training”, applied to a population where half of it won’t help.

Why assignment looks like success

Rollout programmes report on assignment because it’s the bit IT controls. “300 of 300 licences deployed” fits neatly in a steering pack. Usage depends on training, on whether managers use Copilot visibly, and on whether people’s work suits Copilot at all. So it gets watched for a month after go-live, then quietly forgotten. The bill doesn’t stop.

Decide what “active” means before you measure it

“Active” isn’t a fact you discover. It’s a definition you commit to, and it has two parts:

  • The signal. Opening Copilot Chat isn’t the same as using Copilot in Word, Excel, Outlook or Teams. Use the per-app view in the Microsoft 365 Copilot usage report. Someone counted as active because the chat page loaded on their phone isn’t evidence of anything.
  • The window. 30 days flatters a tenant in a busy month and punishes seasonal roles. 90 days is defensible but slow. Pick one, write down why, and keep it the same between reviews.

How many quiet days make a seat reclaimable?

Every tool that “finds unused Copilot licences” is really applying a threshold. Both extremes are wrong:

  • Too tight (say 14 days) catches people on annual leave, finance in the week before year-end, and anyone on a project that isn’t Copilot-shaped this month. Send that list to managers once and you won’t be allowed to send another.
  • Too loose (say 6 months) is honest, but you’ll be reclaiming seats from people who stopped using Copilot two renewals ago.

Your threshold has to survive three things:

  1. Annual leave: anything shorter than your longest normal absence creates false positives. In most organisations that means at least 45 days, and not running the review in August.
  2. Seasonal roles: finance at year-end, HR in recruitment season, legal around a transaction. Exclude these roles by name or make the window long enough to cover their quiet periods.
  3. The low-frequency, high-value user: someone who uses Copilot four times a month to save a full day each time is getting great value. Frequency is a prompt to ask, not a verdict.

Use bands, not a yes/no

The biggest improvement you can make is to split users three ways:

  • Active: leave them alone.
  • Low usage: a coaching list, not a reclaim list. Twenty minutes with a peer in the same role who uses Copilot well does more than another all-staff webinar.
  • Dormant: reclaim candidates, and still only candidates.

The low-usage band is what stops the exercise from feeling like a cost cut, because there’s something positive to do for most people.

Reclaiming is a conversation, not a script

  • Tell people before, not after. A short note to the user and their manager, explaining the threshold, when the seat will be released and how to keep it. Expect some to reply “actually I need that”, which is itself useful information.
  • Write down your exclusions: for example executives, new joiners in their first month and seasonal roles.
  • Re-measure. If the same names are dormant two quarters in a row despite coaching, reclaiming is the obvious answer rather than a contested one.

The number that survives the renewal meeting

Finance doesn’t want an adoption percentage. It wants money per month, with a date on it, and evidence the figure moved last time you acted. So express the dormant band as reclaimable monthly spend, and keep the previous review so you can show a trend. A single number invites an argument about methodology. A trend invites a decision.

A defensible statement sounds like this: “We used a 60-day threshold because our longest standard leave is five weeks. We excluded the four seasonal roles listed. On that basis, reclaimable spend is £X per month.” Nobody argues with that.

You can build this from the Copilot usage reports and PowerShell, or use a tool such as LogiSam’s Copilot Insights, which shows purchased, assigned and active seats side by side, bands users against your own threshold and prices the dormant band. It reads activity metadata only, never prompts or file content.

FAQ

Where can I see Copilot usage per user?

In the Microsoft 365 admin centre, under Reports → Usage → Microsoft 365 Copilot, which shows per-user and per-app activity. Your tenant’s privacy settings may anonymise user names in reports.

What dormancy threshold should I use?

Most organisations land between 45 and 90 days. Choose a window longer than your longest normal absence, and exclude seasonal roles.

Should we reclaim licences automatically?

I don’t recommend it. Notify users and managers first, and give them a simple way to keep the licence if they need it.

Related reading: Copilot licensing explained · Building a business case for Copilot Studio · Copilot readiness is human

Discover more from SamTech 365

Subscribe now to keep reading and get access to the full archive.

Continue reading