Do not start a Microsoft Copilot rollout with a licence count. Start with a small set of work problems, the data needed to solve them, and a way to prove whether the pilot helped.
Pricing and eligible base subscriptions change. Check Microsoft's current licensing page or your agreement rather than relying on the dollar figure preserved in this article's legacy URL (Microsoft Learn).
Business fit
1. Which work problem are we trying to improve?
Name a task, owner and current pain. "Use AI" is not an outcome. "Prepare a first draft of the weekly project update from approved source files" is testable.
2. What is the baseline?
Record the current cycle time, rework, error rate or user effort before the pilot. Without a baseline, a busy pilot can look successful while proving nothing.
3. Which users have repeatable, information-heavy work?
Choose people with a real use case and enough Microsoft 365 activity to test it. Do not select only enthusiasts or only senior leaders.
Data and security
4. Are SharePoint and Teams permissions already defensible?
Microsoft states that Copilot honours the user's existing permissions. That is not a cure for oversharing. It can make already-accessible content easier to find. Review high-use and high-risk sites, broad sharing links, ownerless sites and sensitive content before wider deployment (Microsoft security guidance).
5. Are identity and device controls ready?
Check multifactor authentication, Conditional Access, device policy and sign-in monitoring. Microsoft lists the relevant admin roles and security measures in its setup guide (Microsoft Learn).
6. Do sensitivity, retention and audit controls match the data?
Decide what must be labelled, retained, audited or excluded. Some Purview and SharePoint Advanced Management capabilities require additional licensing. Confirm entitlement in your tenant rather than assuming every control is included.
7. Have we reviewed agents, connectors and web grounding?
An agent or connector expands the data and actions available to Copilot. Record who can enable each connection, what it can read, what it can change and how it is disabled.
Product and licensing
8. Which Copilot experience do users actually need?
Microsoft Copilot Chat and the licensed Microsoft Copilot experience are not interchangeable. Copilot Chat is primarily web-grounded unless users provide content or access an enabled agent. The licensed product adds work-data grounding and deeper app integration (Microsoft comparison).
9. Are the base licence, app and update-channel requirements met?
Check eligible subscriptions, supported apps, accounts and update channels. Microsoft notes that Copilot is not available on the Semi-Annual Enterprise Channel for Microsoft 365 Apps.
Adoption and operations
10. Who will support users when an answer is wrong?
Give pilot users a route for product questions, data incidents and inaccurate outputs. Define when they must stop and escalate instead of quietly working around a problem.
11. What will users be taught to verify?
Teach source checking, permission awareness and the difference between a draft and an approved business record. Prompt tips alone are not a safe-adoption plan.
12. What are the expand, pause and stop criteria?
Agree thresholds before the pilot. Continue when the named task improves without unacceptable risk. Pause when the evidence is unclear. Stop when data exposure, unreliable outputs or operating cost cannot be controlled.
A sensible pilot record
For each use case, capture:
- owner and users
- input data and permissions
- expected output
- baseline and target measure
- licences and extra controls required
- human review point
- failure and rollback route
- review date and decision
Microsoft recommends a staged pilot, deployment and operating approach. That is useful guidance, but it does not prove value in your organisation. Your own measured task results do that.
If you are preparing a real tenant rather than a slide deck, join Microsoft Copilot Adopters.