Why is nobody using our Copilot licences?
Usually because staff were given a tool without a reason to use it. Tie Copilot to specific tasks, train on real work and review who needs a licence.
A common position
Many businesses bought Microsoft 365 Copilot licences in a batch, announced them by email and waited. Months later, a few enthusiasts use it daily and most people have opened it once or twice. The licences renew every month either way.
This is rarely a problem with the product. It is nearly always about how it was introduced.
Why licences go unused
Nobody showed people what to do with it: A new button in Word does not tell an account manager how it helps with a client report.
No tasks were chosen: "Use it where you can" gives people nothing to aim at, so the habit never forms.
It could not find the right information: Copilot draws on the files and emails a person can access. If documents are scattered or badly named, the answers disappoint and people stop trying.
The rules are unclear: Staff are unsure whether they are allowed to use it on client work, so they play safe.
Managers do not use it: If leaders never mention it, staff reasonably conclude it is optional.
A poor first experience: One vague prompt, one weak answer, and many people do not come back.
Find out what is really happening
Start with evidence. Your Microsoft 365 administrator can pull a usage report showing how many licensed people are active and in which apps. Then ask a handful of users and non-users what they tried and what got in the way. Ten short conversations usually explain the numbers.
Tie it to specific tasks
Pick three or four tasks per role where Copilot should help, and say so. Examples include summarising a long email thread before replying, producing meeting notes and actions in Teams, turning notes into a first draft in Word and explaining a spreadsheet someone else built. Named tasks give people a reason to open it.
Train on real work
A feature tour does not change habits. Short, practical sessions using people’s own documents do. Show how to give clear instructions, how to check what comes back and what must not go in. A single session is seldom enough, as covered in whether one-off AI training is enough.
Colleagues who already use Copilot well are your best teachers. Giving them a recognised role helps, which is the idea behind AI champions.
Review who needs a licence
Not every role benefits equally. After a fair trial with proper support, move licences from people who do not need them to people who are asking for one, or reduce the number. Paying for fewer licences that are used is better than paying for many that are not.
Give it a fair test
Set a review date about three months ahead. Measure active use and time saved on your chosen tasks at the start and the end. If use is still low after real support, Copilot may be the wrong fit for some teams, and that is useful to know before the next renewal.
More questions