← All articles
You bought Copilot licences. You sent a communication to all staff. Thirty days later, your adoption report shows 23%. The temptation is to run another training campaign. In most cases, that won't help — because the barrier isn't awareness, it's something technical blocking Copilot from working in the first place.
Low adoption almost never has a single cause. Each Microsoft 365 app has a different most common blocker. Running the same generic adoption campaign for Teams Copilot and Outlook Copilot misses the point — those are different problems with different fixes.
The app-by-app blockers
Teams — low adoption (under 20%)
Most common cause: classic Teams client
Copilot in Teams — specifically meeting summary and intelligent recap — only works in the new Teams client. Users still on the classic Teams desktop app see no Copilot features at all. Check Teams client usage in the Microsoft 365 admin centre before running any adoption campaign. If significant numbers are on classic Teams, the intervention is a migration project, not a training session.
Word — low adoption (under 15%)
Most common cause: Office app not activated
Copilot in Word requires the user to have activated a Microsoft 365 Apps installation on their device. Users who work primarily in a browser, or whose IT deployment didn't complete, won't see Copilot. Check the Office Activation report in the Microsoft 365 admin centre under Usage → Microsoft 365 Apps usage. Users with zero activations cannot use Copilot in any Office application.
Outlook — low adoption (under 20%)
Most common cause: classic Outlook (COM add-in version)
Copilot in Outlook is only available in new Outlook for Windows, Outlook on the Web, and Outlook for Mac. The classic Outlook desktop application — the COM add-in version most organisations have used for years — does not support Copilot. Users see no Copilot button, no coaching features, nothing. The fix is migrating users to new Outlook, which is a larger change than it sounds for organisations with complex customisations.
Excel — low adoption (under 15%)
Most common cause: Python in Excel policy disabled
Basic Copilot in Excel works without Python in Excel. But the more powerful capabilities — the data analysis features that appear in demos — require Python in Excel to be enabled. Check the Microsoft 365 admin centre under Settings → Org settings → Python in Excel. If disabled at the tenant level, advanced Excel Copilot features won't work regardless of licence assignment.
OneNote — very low adoption (under 10%)
Most common cause: OneNote not in the standard desktop build
OneNote adoption is almost always low when OneNote isn't pinned in Teams or included in the standard Microsoft 365 Apps deployment. Users who don't actively use OneNote won't look for Copilot in it. Before addressing Copilot adoption in OneNote, verify that OneNote is actually deployed to users' devices and accessible.
Loop — very low adoption (under 5%)
Most common cause: SharePoint Loop settings not enabled
Microsoft Loop requires explicit tenant-level enablement in SharePoint. If the Loop setting is not turned on, users cannot create Loop pages and Copilot in Loop is inaccessible. Check SharePoint admin centre → Settings → Microsoft Loop. This is the most common single-tenant blocker for Loop adoption and it's invisible to end users — they just don't see the feature.
Copilot Chat — low adoption (under 30%)
Most common cause: pure awareness
Copilot Chat at copilot.microsoft.com is the one app where awareness genuinely is the primary barrier. There's no technical blocker for licensed users. The most effective intervention is a single email with three specific prompts relevant to your organisation's work. "Summarise my emails from the last week and flag anything that needs a response" lands better than "Copilot is available to you."
Diagnose before you campaign
The right order is: measure adoption by app, identify the lowest-performing app, check the most common technical blocker for that app, fix the blocker, then run adoption support. Running adoption support before fixing technical blockers wastes effort and leaves users frustrated when the feature doesn't work as advertised.
The cost of low adoption: A Copilot Premium licence costs £30/user/month. An organisation with 100 licences and 23% adoption is spending £2,300/month on 77 users who are not using it. Understanding the per-app blockers is not just an adoption problem — it's a cost problem.
See your Copilot adoption by app
M365Clarity shows per-app Copilot adoption rates and surfaces the specific intervention most likely to move each app's numbers.
Run a free scan →