Microsoft 365 Copilot
Which tool when: ask what am I accomplishing?
The Modern Collaboration Architecture (MOCA) helps organisations answer “which tool when?” across Microsoft 365. The same question now includes Copilot Home, Code and Autopilot. Start from the outcome, not from the product name.
MOCA also frames digital culture change at four levels: individual, team, community and organisation — with attention as the scarce resource technology should harness rather than scatter.
Individual
How I organise myself
Files, time, wellbeing, personal tasks, finding people and documents. Copilot Chat and Office in Copilot often land here.
Team
Where we deliver initiatives
Shared files, meetings, tasks, chat. Cowork and shared documents in Copilot support team outcomes when the deliverable is shared.
Community
Where we learn and stay engaged
Communities of practice, knowledge capture, events. Choose channels that preserve attention rather than duplicate every announcement.
Organisation
How the whole place works
Corporate knowledge, policy, shared systems. Autopilot and organisation-wide agents need governance, identity and spending policy.
| What you are trying to do | Start here | Watch for |
|---|---|---|
| A quick answer or a first draft | Home · Chat | Everyday licence; still check what you paste in |
| A multi-step deliverable you would hand to someone | Home · Cowork | Credits; spending policy must be on |
| A real document the team will edit | Office in Copilot | Keep the file where colleagues already work |
| A small tracker, dashboard or app | Code | Sandbox, Managed Runtime, IT plugin rules |
| Recurring work that should continue without you | Autopilot | Objectives, boundaries, identity, credits |
| Professional software development | GitHub Copilot | Different product; still connect to the platform |
This map is teaching guidance grounded in Microsoft’s 25 September 2026 framing and MOCA. Your tenant’s licence, preview flags and policy decide what you can actually open.