Blog Details

Everyone’s asking how to roll out Microsoft 365 Copilot. The better first question is: what can each of your users already see? And once licences are bought, the next question is why nobody is using them. This guide covers both: getting your data ready, and a 90-day adoption plan.

Readiness starts with permissions, not licences

Copilot works within your existing Microsoft 365 permissions. It can only surface what a user already has access to. That’s good design, but it also means Copilot makes old permission mistakes much easier to find: the HR folder shared with “Everyone” years ago, the finance spreadsheet shared with “anyone in the organisation”, the project site nobody cleaned up. With Copilot, a simple prompt could bring them to the surface in seconds.

1. Find overshared sites, folders and files, especially “Everyone” and organisation-wide links.
2. Fix permissions on sensitive areas: HR, finance, legal and leadership.
3. Label sensitive information so it stays protected wherever it goes.
4. Start with a pilot group, measure the value, then scale.

A 90-day adoption plan

1. Weeks 1–2: fix permissions first. Tidy access before you switch Copilot on.
2. Weeks 2–3: pick three use cases. For example meeting summaries, first drafts of proposals, and finding information across email and files. Specific beats “use it for everything”.
3. Weeks 3–8: pilot with about ten people, a mix of keen and sceptical users from different teams.
4. Train with real tasks. Show people their own work done faster, not a generic demo.
5. Weeks 9–12: measure, then expand. Track usage and time saved, then decide who gets licences next.

The tool is the easy part. Adoption is a change project.

Put rules around AI

Alongside Copilot, give staff a one-page AI policy: which tools are approved, what data never goes into an AI tool, and that a person checks every AI draft before it goes out. It keeps company data in approved tools and away from free ones.