A clear, practical guide for anyone getting started with Microsoft Copilot.
Microsoft gives you two Copilot entry points. Choosing the right one from the start makes every interaction faster and more useful. The short version:
| If you are… | Open this Copilot |
|---|---|
| In a Teams chat, meeting, or channel — work is actively happening | Copilot in Microsoft Teams |
| Not inside a specific task — exploring, planning, or searching for something | Microsoft 365 Copilot App |
Copilot in Teams is already built in — no installation needed. The Microsoft 365 Copilot App is a free standalone download available on Windows, Mac, iOS, and Android.
Sign in with your work Microsoft 365 account — the same one you use for Teams and Outlook.
| Windows | microsoft365.com/copilot or Microsoft Store |
| macOS | microsoft365.com/copilot or Mac App Store |
| iOS | Apple App Store — search "Microsoft 365 Copilot" |
| Android | Google Play — search "Microsoft 365 Copilot" |
When you search the app stores, you'll see two different Copilot apps from Microsoft. They are not the same thing. Here's what you need to know:
The general-purpose consumer AI assistant — similar to ChatGPT. It is not connected to your Microsoft 365 work data and does not see your emails, files, or meetings. Good for personal tasks and general questions, but not what this guide is about.
The work-focused AI assistant. Connected to your organization's Microsoft 365 data — email, files, Teams, calendar, SharePoint. This is the app described throughout this guide, and the one you want for everything covered here.
The reason there are two Copilots isn't about features — both can answer questions, write, summarize, and brainstorm. The difference is what you're trying to do when you open them. Microsoft designed each one around a different mental state.
Think of this as a smart teammate sitting next to you while a meeting is happening or a conversation is live. It already knows the chat thread, transcript, and attached files — and skips straight to helping you act.
Best for: Summarizing meetings · Drafting replies · Generating action items · Catching up on threads
Think of this as a quiet research room where nothing is assumed. You can search broadly across your email, files, meetings, and chats without already knowing exactly what you're looking for.
Best for: Finding documents · Researching across projects · Planning · Exploring before you dive in
A useful mental test: do you already know what task you're in? If yes, open Teams. If you're still figuring out what needs to happen, open the M365 Copilot App.
Not sure which to open? Match your situation to one of these common cases.
You joined a 45-minute Teams meeting 20 minutes late
Ask "Catch me up" — Copilot has the live transcript and summarizes what you missed in seconds.
You need to find a proposal from last quarter
Search or chat across all your files and emails without knowing exactly where it was saved.
You want to draft a reply to a long channel thread
Copilot reads the thread and drafts a reply in context — no copy-pasting required.
You're preparing for a client you haven't spoken to in months
Ask Copilot to surface recent emails, shared files, and meeting notes involving that client across all of M365.
You want action items from yesterday's standup
Copilot pulls the recorded transcript and generates a structured action item list automatically.
You don't know what you need — you just know there's something to figure out
Start here. The app's broader, exploratory design is built for open-ended starting points.
Keep this handy for your first few weeks. The choice becomes instinctive quickly.
| Signal | Teams Copilot | M365 App |
|---|---|---|
| You're inside a Teams chat or channel | ✓ | |
| You're in or just finished a meeting | ✓ | |
| You need to search across all your files | ✓ | |
| You want to catch up on a project | ✓ | |
| You're drafting a response to a message | ✓ | |
| You don't know what to search for yet | ✓ | |
| You need action items from a call | ✓ | |
| You need to research across many sources | ✓ | |
| Speed is the priority | ✓ | |
| Exploration is the priority | ✓ |
For IT pros, power users, and anyone who wants to understand what's actually happening.
A common misconception is that Teams Copilot and the M365 Copilot App are different AI systems. They are not. Both run on the same foundation model, the same Copilot orchestration layer, and query the same Microsoft Graph with the same permissions. Your data access is identical in both surfaces.
What differs is the pre-prompt context — the information Copilot receives before it ever reads your message. This pre-loaded context shapes everything: how broadly Copilot searches, how quickly it synthesizes, and what it assumes you're trying to accomplish.
Every Copilot interaction begins with a system prompt — a behind-the-scenes instruction set that tells the model who you are, what you have access to, and what it should prioritize. In Teams, that system prompt is automatically populated with rich contextual data from your current session. In the M365 app, it is not.
When you open Copilot inside a Teams chat, channel, or meeting, the orchestration layer pre-loads the following before processing your prompt:
This dense pre-loading lets Copilot skip the discovery phase entirely. It already knows what's relevant. Retrieval is narrow and fast — optimized for synthesis speed over breadth.
When you open the M365 Copilot App, no session-specific context is pre-loaded. The system prompt gives Copilot access to your full M365 tenant data but does not narrow the scope. Copilot must infer relevance from your prompt alone.
Microsoft 365 Copilot uses semantic search over the Microsoft Graph — an index of your organization's emails, chats, files, calendar events, and SharePoint content. The critical architectural difference between the two surfaces is how aggressively retrieval is scoped before your prompt is processed.
| Retrieval Dimension | Copilot in Teams | M365 Copilot App |
|---|---|---|
| Search scope | Narrow — current thread / meeting | Broad — full Microsoft Graph |
| Source diversity | Low — current context prioritized | High — mail, files, chats, calendar |
| Pre-filtering | Aggressive — time window + thread | Minimal — relies on your prompt |
| Synthesis timing | Immediate | After exploration (on request) |
| Result surface | Composed summary or draft | Search results + optional summary |
| Latency profile | Lower (smaller retrieval surface) | Higher (broader search) |
| Best when you know… | Exactly what task you're in | Nothing yet — still discovering |
Both apps offer Chat. Only the M365 Copilot App prominently offers Search as a standalone, first-class mode. This is not cosmetic — the two modes operate with fundamentally different output objectives.
One of the most important — and least visible — differences between the two Copilots is the reasoning posture embedded in their system prompts. This posture determines how Copilot internally frames your request before reasoning begins.
Microsoft Graph is the unified API powering Copilot's access to your organizational data — indexing Exchange, SharePoint, OneDrive, Teams, and other M365 services. Both Copilot surfaces query the same Graph with identical permissions. Security and compliance policies apply equally.
The difference is how the query is scoped: Teams Copilot appends thread-specific filters automatically; the M365 Copilot App sends broader semantic queries and lets results determine scope.
Each Copilot surface is purpose-built for a different cognitive mode: doing (executing a known task) or thinking (figuring out what to do next).
| Design Dimension | Copilot in Teams | M365 Copilot App |
|---|---|---|
| Assumed cognitive state | Execution | Orientation / Discovery |
| Assumed urgency | High | Low to moderate |
| Retrieval strategy | Narrow and fast | Broad and thorough |
| Synthesis timing | Immediate | On demand |
| UI metaphor | Teammate in the room | Quiet research library |
| Primary failure mode | Misses outside-context info | Can feel slow for urgent tasks |
| Primary UX signal | Speed and completeness | Breadth and control |