In many of the Microsoft 365 tenants I work with, Copilot adoption starts with real enthusiasm when the licences arrive. That enthusiasm fades surprisingly fast. The actual work begins after assignment, not before it. Teams have their new Copilot entitlement but hold back, because they can't see how it fits into their working day. I see this pattern again and again. Interest is high, yet usage gets stuck somewhere between a generic tool and concrete value for the business.

Copilot adoption lives or dies with department-level scenarios

In my experience, the biggest factor in successful Copilot adoption has been concrete scenarios at department level. Generic training along the lines of “here’s how to prompt” rarely sticks unless people see Copilot solving their own team's problems. Workshops with the business units, using the Microsoft Copilot Scenario Library as a starting point, have made a big difference in my projects. HR wants quick meeting summaries, while sales wants proposal drafts done faster. When someone fixes a familiar annoyance with Copilot, behaviour actually changes, and that is the point where adoption picks up.

Champions and prompt galleries spread hands-on know-how

Scenarios on their own won't carry it, though. Without a champions network (users who actively try Copilot and pass on practical tips), adoption stays on the surface. A community of champions across teams is essential, particularly for getting people past their difficulties with prompts. The Copilot Prompt Gallery gets far less attention than it deserves. It contains ready-made prompts that champions can adapt for their own team, which helps with the “prompt writer's block” so many people run into during the first weeks.

Usage reports and the Copilot Dashboard show where adoption really happens

Assigning licences doesn't mean people are using them. Since early summer 2024, the Microsoft 365 Copilot usage reports in the Microsoft 365 admin center have finally shown which groups actually use Copilot and where it sits untouched. The Copilot Dashboard in Viva Insights, launched in spring 2025, goes further and gives a closer view of usage patterns and business scenarios (docs).

This diagram reflects the Copilot adoption journey as I usually see it in practice:

flowchart TD
    LicenceAssign["Assign licences"] --> Scenarios["Find department scenarios"]
    Scenarios --> Champions["Build champions network"]
    Champions --> PromptGallery["Use prompt gallery"]
    PromptGallery --> ActiveUse["Drive active use"]
    ActiveUse --> Measure["Measure and adjust"]
    Measure --> Reallocate["Reallocate licences"]

Figure: Typical steps towards sustainable Copilot adoption, from licensing through to ongoing improvement.

In my projects I use these reports to start targeted conversations with business units where activity is low. More often than not, adoption has stalled because scenarios are missing or people aren't sure how to begin.

You should reallocate licences and set expectations early

In the first months after a rollout I nearly always find unused licences, sometimes quite a lot of them. The newer usage reporting shows clearly where Copilot is in use, so you can move licences to motivated pilot groups instead of wasting budget. Managing expectations matters just as much. Copilot won't fix everything, and it won't replace existing processes overnight. Many works councils expect concrete technical and organisational controls, so it pays to agree early on which Copilot features are enabled, logged or restricted (see also /blog/copilot-works-council-technical-measures).

Pro tip: Hold short walkthroughs in your champions community where you show real prompts in Teams, Outlook, or Word. It lowers the barrier to getting started and gets people curious.

I see adoption as a journey and not as a one-off rollout

A Copilot rollout isn't a single event. It's a process that needs ongoing attention. Organisations that treat it as “set and forget” end up with unused licences and frustrated users. I've had the best results when starting with teams that have real scenarios driven by the business, building up a champions network and keeping an eye on the numbers (see my post on pilot planning and usage reports). Stay flexible, because scenarios, needs and user interest will change over time. That is why I think of Copilot adoption as a journey rather than just another IT deployment.