The AI you already pay for
Why Copilot seats go unused, and what to fix first
Copilot answers from what each person can open. When that's too little or too much, people stop using it. Fix access, then permissions, then one task.
A company buys Copilot seats. For a week or two, people try it. Someone asks it where things stand with a customer and gets a vague answer. Someone else gets an answer that quotes a file they didn’t know they could open. By the end of the month most of the seats are quiet, and the licenses renew anyway.
The usual reaction is to book a training day. Training is the last thing I’d fix. Copilot isn’t failing because people can’t write prompts. It’s failing because of what it can and can’t see. Here’s the order I’d work in.
1. Data access: can Copilot reach the answer?
Copilot answers from the content a person can already open in Microsoft 365: their mail, calendar, chats and meetings, and files in OneDrive and SharePoint. That’s the point of it, and it’s also the first limit.
If the customer list is a spreadsheet on someone’s laptop, the contracts sit on an old file server and the real history of each account lives in a separate CRM, Copilot has nothing to work with. It isn’t broken. It’s blind.
The fix starts with a short list. Write down five questions people would actually ask Copilot in a normal week, then find where each answer lives today. Anything outside Microsoft 365 either moves in, gets connected, or comes off the list. You’ll learn more from that hour than from a day of training.
2. Permissions: what can it see that it shouldn’t?
The opposite problem stops rollouts cold. Copilot shows each person only what they already have access to, which sounds safe until you look at what people have access to. The HR folder shared with the whole company. The site someone made for a project years ago, open to everyone, with payroll exports in it. Copilot didn’t create those permissions. It just makes them easy to find.
One surprise like that and the owner quietly decides not to buy more seats. So before you expand, look for content shared with everyone in the company or with anyone who has the link, starting with HR, finance and anything holding customer or patient data. Close what shouldn’t be open, and give each of those areas a named owner.
It’s dull work. It’s also the work that lets you say yes to Copilot without worrying about what it will surface next.
3. One task: give it a real job
“Use Copilot” isn’t a job. People don’t change how they work because a new button appeared. They change when one task they do every week gets easier.
Pick one recurring task with a clear owner. The follow-up email after a client meeting. The weekly status summary for the leadership meeting. The first draft of a proposal from the notes of the last three calls.
Sit with the person who does it, write the prompt together, save it where colleagues can reuse it, and check after two weeks whether it saves them time. If it does, pick the next task. If it doesn’t, you’ve learned something cheaply.
How to tell where you stand
Open the Copilot usage report in the Microsoft 365 admin center and compare the seats you’ve assigned with the people who actually used Copilot in the last month. If the gap is wide, start at step one. Not with a training day, and not with more seats.
On our four-stage ladder, this is the work of reaching Assisted: Copilot and AI tools licensed and governed, a security baseline in place, and the data cleaned and reachable. It comes before any agent, because an agent built on scattered data and loose permissions inherits both problems.
If you’d like an outside view first, the free Scorecard includes the value you’re not using yet.