Resources — Hub 2: Copilot adoption
Why only a third of employees keep using Copilot
Access isn't adoption. A license sitting unused in the admin console isn't infrastructure, it's a subscription.
6 min read
Assigning a Copilot license takes about four seconds in the admin center. Getting someone to still be using it in March is a different project entirely. Across rollouts without dedicated enablement, roughly a third of licensed employees are active months later. The other two-thirds didn't reject the tool nobody ever connected it to the work they actually do on a Tuesday.
01
Generic training teaches features, not jobs
A one-hour all-hands demo shows what Copilot can do. It doesn't show your accounts payable clerk what to do with it at 9am Monday. People adopt tools that solve a task they already own, not tools that demonstrate capability in the abstract.
Try this
Run enablement by role, not by company. Give each role three named prompts tied to work they already do this week, and nothing else.
02
Managers set the ceiling
Adoption tracks almost perfectly with whether the person running the meeting uses it visibly. When a manager pastes an AI-drafted summary into the channel and says so, the team follows. When the manager quietly opts out, the team reads that as permission.
Try this
Pick one recurring meeting and make the AI-drafted recap the official artifact produced by the manager, in front of everyone.
03
Measure depth, not logins
License counts and monthly actives tell you almost nothing. Somebody who opens Copilot once a month to summarize an email is a statistic, not an outcome. What matters is whether it sits inside a workflow that repeats.
Try this
Track four layers separately: who uses it, how deep it sits in the workflow, what output changed, and whether the business baseline moved.
What this actually means for you
Adoption isn't a personality problem or a training gap you close with one webinar. It's a habit installed one workflow at a time, with a manager modeling it and a baseline to point at. If you're at a third, you don't need more licenses you need one role, one workflow, and ninety days.
Sources: Microsoft 2025 Work Trend Index Annual Report; ITontology client rollout data, 2025–2026.
Copilot sitting mostly unused?
That's exactly what a licensing and AI-readiness assessment is for: what you actually have, where the real bottleneck is, and which one workflow is worth fixing first.
Book the assessment