- A strong prompt names the goal, context, source, and format.
- Type a slash to point Copilot at a specific file, person, or site.
- Concrete prompts cover thread summaries, drafts, spreadsheets, and recaps.
- Copilot can sound confident while wrong, so verify before you send.
This guide is for anyone with a Microsoft 365 Copilot license who has tried it once or twice, gotten a so-so answer, and quietly gone back to doing the work by hand. By the end, you'll have a repeatable way to write prompts that get useful results, plus a set of concrete prompts you can paste into Outlook, Word, Excel, and Teams today.
Before you start
You need a Microsoft 365 Copilot license assigned to your account, and you need to be signed in to the Microsoft 365 apps with that work account (not a personal one). Copilot shows up as a button in the ribbon or a side pane in Outlook, Word, Excel, Teams, and the standalone Microsoft 365 Copilot Chat app. If you don't see it, your IT admin may still be rolling it out, so check before you assume something is broken.
One more thing worth knowing up front: Copilot can only see content that you already have permission to open. It reads your mail, your files in OneDrive and SharePoint, and your Teams chats and meetings. It does not invent access. That's why pointing it at the right file matters so much, which we'll come back to.
Step 1: Learn the anatomy of a good prompt
A weak prompt is a one-liner like "summarize this." A strong prompt has four parts, and you don't need all four every time, but the more you include, the better the answer.
- Goal: what you want Copilot to actually produce. "Write a reply," "build a summary," "find the risks."
- Context: who it's for and why. "For my manager, who missed the meeting," or "for a client who is frustrated about a delay."
- Source: the specific material to use. A file, an email thread, a meeting, or a SharePoint site.
- Format: how you want it back. "Three bullet points," "a short paragraph," "a table with two columns."
A prompt that names all four sounds like this: "Draft a friendly reply (goal) to this email thread for a client who is worried about timing (context), using the project status in the file Q3-Plan.docx (source), and keep it under 120 words (format)."
Step 2: Point Copilot at the right files
This is the single biggest lever on answer quality. In Microsoft 365 Copilot Chat (work mode) and in the app side panes, you can reference a specific file, email, person, or site instead of hoping Copilot guesses right.
- Type a forward slash / in the prompt box, then start typing a file name, a person's name, or a SharePoint site name. Copilot shows matching items you can pick.
- You can attach more than one source this way, for example two reports plus a meeting recap, and ask Copilot to compare them.
- In Outlook, you can pull an email thread directly into Copilot Chat as context so it answers using that conversation.
When you ground a prompt on a named source, Copilot stops guessing and starts reading. That one habit fixes most "the answer was generic" complaints.
If an answer comes back vague or slightly wrong, ninety percent of the time it's because Copilot didn't know which file you meant. Re-ask with a / reference to the exact document, and the quality usually jumps.
Step 3: Summarize a long email thread (Outlook)
Open the thread in Outlook, then open Copilot in the message. Try:
"Summarize this thread in five bullet points, then list any action items with who owns each one and any due dates mentioned."
Copilot reads the whole conversation, not just the last reply, so it catches the decision buried in message three that everyone forgot.
Step 4: Draft a document from bullets (Word)
Open a new Word document, open Copilot, and instead of staring at a blank page, hand it your rough notes:
"Write a one-page project update from these bullets: [paste your bullets]. Use a friendly, plain tone, add short section headings, and end with a 'Next steps' list."
Then refine in place: "Make the second paragraph shorter," or "Add a sentence about the budget being on track." Treat the first draft as clay, not stone.
Step 5: Analyze a spreadsheet (Excel)
Open your data in Excel, format it as a table if it isn't already (select the range, then Insert > Table), and open Copilot. Tables matter here, because Copilot works far better on structured data with clear column headers. Try:
"Which three regions had the biggest drop in sales from Q1 to Q2, and by what percentage? Show your answer as a small table."
You can also ask it to add a formula column, highlight rows that meet a condition, or suggest a chart. Always sanity-check the numbers against a total you already know.
Step 6: Produce a meeting recap (Teams)
If a Teams meeting was recorded and transcribed, open it afterward, open Copilot, and ask:
"Give me a recap of this meeting: the main decisions, the open questions, and the action items with owners. Then draft a short follow-up email I can send to attendees."
This turns an hour-long call into something you can act on in two minutes.
Copilot is weak at precise math on messy data, at anything it can't actually see (it won't read a file you didn't share with it), and at recent facts outside your tenant. It can also sound confident while being wrong. Verify numbers, dates, names, and any claim you'd put your name behind.
Step 7: Verify the answer
Before you send or save anything Copilot produced, do a quick check. Does it cite or reflect the source you pointed it at? Are the names, dates, and figures right? Does the tone fit the audience? Copilot often shows reference links to the files it used, so click through on anything that matters. The goal is a fast review, not blind trust.
What to do next
Pick one of these prompts and use it on real work this week, an email thread you need to summarize or a spreadsheet you need to read. Keep a short note of the prompts that work well for you; that personal list becomes your own playbook. If your team wants a hands-on Copilot session, or you're not sure your SharePoint and permissions are ready for it, that's a conversation we're glad to have. Let's talk it through.