The AI layer baked into Outlook, Teams, Word, Excel and SharePoint, useful only if you actually live in Microsoft 365.
Copilot is a serious tool when your work already happens inside Outlook, Teams, and SharePoint, because nothing else can read your mailbox and your file shares at the same time with proper permissions. It is mediocre when judged purely as a chatbot: the underlying model trails ChatGPT and Claude on reasoning, the Excel and PowerPoint experiences still feel half finished, and the price per seat is high once you add it across a team. Buy it for the integration, not for the intelligence.
Reach for Copilot when the work you need help with lives inside the Microsoft tenant: drafting an Outlook reply that references three prior threads, building a Teams meeting recap with action items, querying SharePoint for the latest version of a policy, or asking Excel to explain a model someone else built. It earns its seat fee on Outlook and Teams alone for a busy operator.
Do not reach for Copilot if your primary stack is Google Workspace; the integration is the entire point and you will not get it. Do not pay for it as a general chatbot, ChatGPT and Claude are better and cheaper at that. Avoid it for long-form deliverable drafting (proposals, board papers, research), the writing is flat and the slide generation is genuinely poor. And do not expect Copilot Studio to replace n8n or a real agent framework, it is governed and slow to iterate on.
Grounding answers in your own tenant data (email, files, chats, calendar, SharePoint) without that data leaving the Microsoft trust boundary.
Microsoft 365 Copilot is a brand that covers several products. The one to reach for depends on whether you want the AI inside an app you already use, or on its own.
| If the work happens in… | Reach for |
|---|---|
| Outlook, Teams, Word, Excel, PowerPoint, OneNote | In-app Copilot for that app |
| A new collaborative document that updates as you iterate | Copilot Pages |
| A standalone chat surface (no specific app) | Copilot Chat |
| A custom agent for your team that connects to your M365 data | Copilot Studio |
| SharePoint and Drive searches across your organisation | Copilot Chat with M365 connectors enabled |
| In-app Copilot | Copilot Chat | Copilot Pages | Copilot Studio | |
|---|---|---|---|---|
| Where it runs | Within Outlook / Teams / Word / Excel / PowerPoint | Browser or Teams | Browser, generates a Page document | Copilot Studio app |
| Output type | Edit suggestions, draft replies, summaries | Chat responses | Live collaborative Pages | Custom agents for your org |
| Persistence | Per email / document / sheet | Per chat | Page persists like a doc | Agent persists; conversations don't |
| M365 graph access | Yes — deep | Yes — via connectors | Yes | Yes |
| Best for | Operators already in Office | Quick standalone questions | Multi-person collaborative AI docs | Engineering + IT building custom agents |
Pages are Microsoft's answer to Claude Artifacts: a live, editable, multi-person document a chat can produce. Where they differ:
Each sub-product has its own focused page. Tap any card to open the full breakdown.
The reason to pay for Copilot at all; the only AI that legally sees inside your Microsoft tenant.
View details →Free, web-only, and not the reason anyone should be picking Copilot.
View details →Useful as a workshop canvas; underdiscovered even inside teams that pay for it.
View details →Earns its seat fee on Outlook alone for a busy operator.
View details →Solid for internal meetings; an external recorder still produces better transcripts.
View details →Useful connectors worth knowing for this tool. Ranked by everyday usefulness.
Lets Claude query Outlook mail, OneDrive, and SharePoint via OAuth, useful when you want better reasoning over M365 content than Copilot itself gives.
Build your own MCP server against Microsoft Graph for tenant-specific automations where Copilot Studio is too rigid.
Hundreds of pre-built triggers and actions Copilot Studio can call without code, the practical way to wire Copilot to non-Microsoft systems.
The default backing store for Copilot Studio agents that need persistence; worth understanding before building anything serious in Studio.
Microsoft's own control plane for managing custom agents at scale, mandatory once you go past five agents in the tenant.
If you live in M365, in-app Copilot is free productivity that you should turn on. Pages is genuinely useful for collaborative AI docs. Studio is for IT, not operators. The Claude vs Copilot decision is not either/or; most teams use Copilot for inside-Office tasks and Claude for everything else.
May 2026. Microsoft ships rapidly; integration depth in any given app changes monthly.
Use for first drafts inside the M365 fence; expect to rewrite every paragraph.