Independent practitioner; not affiliated with, endorsed by or certified by Microsoft. Product details on this page were checked against Microsoft Learn in October 2026 and are re-checked at the start of each engagement.
What is different about Microsoft 365 Copilot
Microsoft 365 Copilot does not wait for staff to bring it information. With the full licence, it draws on the work content each user can already reach through Microsoft Graph: their mail, meetings, chats and the SharePoint, OneDrive and Teams files they have access to. Microsoft’s own setup guidance is clear that it respects existing permissions.
That changes the adoption problem in two ways.
First, permissions are the data boundary. If a finance folder is shared with “everyone in the organisation”, Copilot will find it for anyone who asks a relevant question. Nothing new was granted, but content that was obscure becomes easy to retrieve. Microsoft’s readiness guidance for SharePoint describes the reports and controls available for this; which ones you have depends on your licensing.
Second, value depends on the role. Copilot is strongest where a person’s work is spread across meetings, threads and documents: preparing for a client meeting from recent mail and files, turning a Teams meeting into actions, drafting a status update from a channel and a tracker. A role whose work lives in a separate line-of-business system may see little benefit, however good the training.
Licence types, product names and admin features change often. I verify the current position against Microsoft Learn and your tenant during the engagement.
The readiness exercise: permission-readiness dependency list
The exercise starts from the pilot roles, not the whole tenant. For each role, we list the content their workflows will draw on and ask, with your administrator:
- Where does it live? The specific sites, libraries, Teams and shared mailboxes.
- Who can reach it now? Including organisation-wide groups, broad sharing links and inherited permissions.
- Should they? If not, what is the fix: tighten permissions, restrict discovery, apply a sensitivity label, or archive stale content.
- What else is nearby? High-risk content the pilot users could reach through Copilot even though their workflows do not need it.
- Who owns the fix, and is it done? The pilot starts when the items that matter are closed or have an accepted interim control.
Your administrator runs the reports and makes the changes; I coordinate, keep the list and make sure it reflects how the roles actually work.
The pilot approach
Role profiles. For each of two or three roles (illustrative examples: account managers, project managers, an operations coordinator), we write a short profile: their recurring tasks, the apps they spend time in, and two or three workflows where Copilot should help.
Workflows in the apps people use. Copilot appears inside Outlook, Teams, Word, Excel and PowerPoint, so workflows are taught where the work happens: “before each client meeting, ask Copilot in Teams for the last month’s mail and files with this client”, not in a separate tool.
Manager support. Managers of pilot users are briefed on the workflows and asked to request them, for example asking for the Copilot meeting recap as the standard output. Manager requests are among the strongest levers on repeat use.
Coaching on live work. Short role-specific sessions, then working alongside people during their real meetings and documents.
The signature deliverable
You receive a permission-readiness dependency list, role-based pilot and sponsor measurement plan. Illustrative extract from the measurement plan:
| Measure | Source | Who reviews |
|---|---|---|
| Active Copilot use by pilot role | Microsoft 365 admin centre usage reporting | Workplace technology lead |
| Repeat use of each named workflow | Short fortnightly check-in with pilot users | Role managers |
| Time to prepare a client meeting brief | Before-and-after sample | Sponsor |
| Corrections needed on Copilot-drafted status updates | Reviewer log | Project lead |
| Open permission-readiness items | Dependency list | Microsoft 365 administrator |
Illustrative example. It shows the format, not a client’s plan.
How acceptance is judged
The sponsor and your Microsoft 365 owner agree the measures before the pilot starts. Acceptance means the dependency list items for pilot content are closed or have an accepted interim control, each role is using its workflows on live work, and the sponsor report states what changed by role, including where Copilot did not help. Microsoft’s usage reports are one input; they show activity, not whether the work improved.
Ownership and handover
Your administrator owns the tenant and remediation. Role managers own their teams’ workflows. The sponsor owns licence allocation. If an MSP manages your tenant, I work alongside them; see AI enablement partner for MSPs. If you are still choosing between platforms, compare ChatGPT Enterprise and Google Workspace with Gemini, or start with AI tool rollout.