Copilot in Your Daily Apps
Copilot is available across Word, Outlook, Teams, Excel, and PowerPoint. The tool is the same; the context differs, and Copilot behaves differently inside each app.
Lesson 3
Same tool, different rooms.
This lesson walks through what to use where. Spend your next 30 minutes in the app that causes the most friction in a typical week.
Copilot across Microsoft 365 apps
Core principles
- Word, drafting room: draft from a brief, rewrite tone, summarize long docs, turn notes into prose. Access: Copilot on the Home ribbon or Draft with Copilot on a new document; highlight text for rewrite options.
- Outlook, inbox manager: draft replies faster, summarize long threads, coach tone on drafts you wrote. Access: Copilot in the compose toolbar; Summarize on a thread.
- Teams, meeting co-pilot: recap meetings, action items with owners, answer "what did X say about Y?" Requires meeting transcription, without it. Copilot only sees chat, not spoken content. Check meeting settings or IT if recap is missing.
- Excel, data assistant: plain-English questions, formulas from descriptions, trends and charts. Format data as a table (Insert → Table) before prompting.
- PowerPoint, deck builder: first-draft decks from outlines or documents, summarize into slides, speaker notes, layout polish. Best at the start (blank deck) or end (polish).
Go deeper: Multimodal AI at Work
Check yourself
What does Teams Copilot require to recap what was actually said during a meeting?
Teams Copilot needs transcription to access spoken content. Without it, it can only recap the chat thread, everything said out loud is invisible to it. Check meeting settings or IT if the recap option is missing from your meetings.
Do this in Copilot
Which app causes the most friction in a typical week? Start there.
Open a real document in Word, launch Copilot, paste:
Word, executive summary
Based on the notes in this document, draft a two-page executive summary. Audience: senior leaders who did not attend the meeting. Tone: confident and clear. Structure: opening context, three key findings, recommended next step. No jargon.
- Source material
- Outlook, decline without burning the bridge: I need to decline a vendor's proposal without burning the relationship. We appreciate their work but chose a different direction. Draft a professional, warm response that is honest but not detailed about why. Keep it under 100 words.
- Teams, after a transcribed meeting: Summarize this meeting. List: (1) key decisions made, (2) open questions still unresolved, (3) action items with owners and any deadlines mentioned. Format as three separate sections.
- Excel, on a table of real data: Analyze this sales data. Tell me which region had the highest growth from Q1 to Q2, which had the lowest, and the overall trend. Then create a bar chart showing Q1 vs. Q2 by region.
- PowerPoint, new deck: Create a 6-slide presentation for a 15-minute team briefing on [topic]. Audience: [who]. Goal: [what they should understand or decide]. Include title slide, context, three main points, and a closing call to action. Add speaker notes for each slide.
- Going deeper: use /learning-development/copilot-excel-analysis for a step-by-step Excel analysis workflow, or /learning-development/copilot-powerpoint-decks for client and team decks built inside the template.
Did you run this in Copilot? Mark complete when you have tried it.
RecordedNext lesson: Judgment, Verification, and Trust →
Navigate: press j for next lesson, k for previous.