Microsoft 365 Copilot is easy to buy and hard to adopt. The licences arrive, IT switches them on, people try it a few times, and three months later the usage dashboard is flat. The cause is rarely the tool. It is the rollout.
This is the 90-day plan we use with clients. It works for 20 licences or 2,000.
Days 1 to 15: get the foundations right
Fix oversharing first
Copilot can show a user anything that user can already access. In most tenants that includes old SharePoint sites shared with everyone, Teams files with company-wide links and folders nobody has reviewed in years. Before a broad rollout:
- Find sites and libraries shared with everyone or with large groups.
- Apply sensitivity labels to the most sensitive content.
- Restrict search on sites that should not be surfaced while you clean up.
- Agree who owns the clean-up after launch.
Write a short usage policy
One page is enough: which tools are approved, which data can be used, how to check outputs and who to ask. See our AI usage policy guide.
Take a baseline
Pick three or four tasks per pilot team and time them today: writing the weekly report, preparing for a client meeting, summarising a long document. You will need these numbers at day 90.
Days 15 to 30: choose pilots and train them properly
Pick two to four pilot teams with a lot of email, meetings and documents, a manager who wants it and work you can measure. Then train them on their own work, not on features.
| Team | First exercises |
|---|---|
| Sales | Teams call recap and follow-up email in Outlook; account brief from CRM notes |
| Finance | Variance explanation in Excel; management-pack commentary in Word |
| Operations | Weekly report from Excel data; procedure from a meeting transcript |
| HR | Policy answers; job descriptions from a hiring brief |
Two live sessions of three hours, a week apart, work better than one long day. People practise in between and bring real questions to the second session. This is the format of our Microsoft 365 Copilot training.
Days 30 to 60: build champions and habits
- One champion per team. Someone who uses Copilot daily and helps colleagues. Give them an hour a week for it.
- A shared prompt library. Save the prompts that worked in training, by team, where people can find them.
- A weekly 15-minute show-and-tell. One person shows one task they now do faster.
- A first agent. Build one simple agent in Copilot Studio for a team process, such as answering policy questions from an HR site.
Days 60 to 90: measure and expand
Re-time the baseline tasks and look at the usage reports. Present three numbers to leadership: active users, hours saved on the baseline tasks and one or two stories of work done differently. Then decide which teams get licences and training next.
Some processes will come up that are too big for Copilot alone, such as invoice intake or multi-system reporting. Those are candidates for automation.
Common mistakes
- Rolling out to everyone at once, with one webinar.
- Training on features instead of the team’s own tasks.
- Skipping the permissions review and discovering over-shared files the hard way.
- Measuring licences assigned instead of work done differently.
- Leaving managers out: teams adopt what their manager uses.
Want help with your rollout? We combine the permissions check, training on real work and measurement in one programme. Tell us about your plans.
Frequently asked questions
Why is our Copilot usage low?
Usually because people were given a licence and a feature tour, not practice on their own work. Usage rises when each team sees two or three of its own tasks done faster and then does them itself.
Do we need to fix permissions before rolling out Copilot?
Yes, at least for the sites and teams with the most sensitive data. Copilot shows users anything they already have access to, so over-shared content becomes easy to find.
Who should be in the Copilot pilot?
Teams with lots of email, meetings and documents, a manager who wants it, and work that can be measured. Avoid starting only with enthusiasts; you need realistic results.
