Confirm license and participant base
Form the pilot group from active employees with a suitable Microsoft 365 base license, a primary Exchange Online mailbox and real work cases.
Microsoft 365 Copilot
Plans pilot size, budget, champion needs, readiness and rollout schedule for Microsoft 365 Copilot.
Assess organization, budget, target state and readiness to size the right pilot phase.
Check prioritized sites, sensitive data and sharing before the pilot starts.
Governance checklist
These items make the pilot more robust: not just assigning licenses, but preparing the target group, data access, enablement and measurement.
Form the pilot group from active employees with a suitable Microsoft 365 base license, a primary Exchange Online mailbox and real work cases.
Check Microsoft 365 Apps, Teams, OneDrive, Outlook, update channel, app privacy and network paths before the start.
Assess heavily used SharePoint sites, anonymous links, broad groups, sensitive content and ownerless areas before a larger pilot scope.
Define labels, DLP, site ownership, access control, audit signals and review cadence for the pilot and later rollout waves.
Deploy enough champions per pilot stage, bundle questions and keep business owners available for decisions.
Collect feedback, usage experiences, blockers and good prompts weekly and feed them into the go/no-go decision.
Document readiness, usage, adoption, productivity signals, satisfaction and governance findings with clear measurement points.
Pilot stages
The stages help distinguish between quick validation and a robust rollout decision.
| Stage | Users | Duration | Champions | Monthly | Learning value | Governance effort |
|---|---|---|---|---|---|---|
| Micro pilot | 5 | 4 weeks | 1 | 130.00 € | 35% | 20% |
| Department pilot | 20 | 6 weeks | 3 | 520.00 € | 62% | 42% |
| Cross-functional pilot | 50 | 8 weeks | 6 | 1,300.00 € | 82% | 68% |
| Scaled pilot | 100 | 12 weeks | 10 | 2,600.00 € | 90% | 82% |
| Enterprise wave | 250 | 12 weeks | 20 | 6,500.00 € | 96% | 95% |
Schedule
several roles and departments
5 people are enough for first signals; decisions usually become more robust from 20 to 50 participants with a role mix. Larger companies tend to plan 100 or more people as a first rollout wave.
Suitable licenses, Microsoft 365 Apps, Exchange Online, OneDrive, Teams, network, data hygiene, access controls, champions and feedback channels should be clarified before the start.
Useful criteria are active usage, time saved per use case, feedback rate, satisfaction, support questions, governance findings and a clear go/no-go decision for the next wave.
If base licenses are missing, apps or the network are not ready, or oversharing and sensitive data have not been contained, governance and data hygiene should be stabilized first.
Source check: 2026-05-17. Price assumptions are guide values and must be checked in the respective contract before procurement.
PhinIT | Andreas Hepp
We support you with license analysis, implementation, governance and ongoing optimization.