Most people write a Copilot prompt the way they type a search query: three words and a hope. Microsoft's own training says the opposite. Unlike traditional search, it notes, Copilot responds best to detailed, descriptive prompts.
This guide gives you the method Microsoft teaches, the file-reference shortcuts that most users never find, a prompt library for six apps, and the mistakes that waste the most time. It pairs with our guides to Copilot in Outlook, Word, Excel, PowerPoint and Teams.
TL;DR: the method and the shortcuts
| Question | Short answer |
|---|---|
| What is the method? | Goal, context, source, expectations. Only the goal is required |
| How do I reference a file? | Type a slash, then the file or folder name |
| How do I reference a meeting or topic? | Type a hash. Needs a Microsoft 365 Copilot licence |
| How do I mention a person? | Type an at sign, useful in shared Copilot Pages |
| What if the answer is off? | Send a follow-up. Do not start over |
| Is the answer correct? | Not guaranteed. Open the sources and check |
What are the four parts of a good Copilot prompt?
Microsoft's support article on writing a great prompt names four parts, and its training modules use the same framework across Word, PowerPoint, Teams, Excel and Outlook. In Microsoft's words:
- Goal: What do you want Copilot to do? This is the only required part.
- Context: Why do you need it, and who is involved?
- Source: What information or samples should Copilot use? That can be an attached file, a web page, or work emails, chats and files, depending on your account.
- Expectations: How should Copilot respond? Audience, tone, length or structure.
Microsoft's Learn module on prompts adds a useful line: generative AI excels at imitation, so provide examples to guide the response. It also warns that a clear goal is the foundation, and the other three can make responses more accurate, but they do not guarantee factual accuracy.
Here is the same request written badly and well.
| Version | Prompt |
|---|---|
| Weak | "Write an update." |
| Better | "Write a project update for the leadership team. We finished the vendor migration but missed the training date by two weeks. Use /ProjectNotes.docx. Plain language, under 150 words, end with the one decision we need." |
The better version has all four parts. The goal is the update. The context is the audience and the slip. The source is the file. The expectations are plain language, length and the ending.
A speech bubble pointing at a blueprint held by a hand, showing a Copilot prompt that follows a plan of goal, context, source and expectations
How do you reference files, meetings and people?
This is the shortcut most users miss. Microsoft's training module documents three symbols you can type inside a prompt:
| Symbol | Use | Example from Microsoft |
|---|---|---|
| Slash | Reference a file or folder | "Summarize the key points from /Q4MarketingStrategy.pptx" |
| Hash | Reference a topic, meeting name or recurring event. Requires a Microsoft 365 Copilot licence | "What were the action items from #WeeklyOpsSync?" |
| At sign | Mention a person, to include their perspective, such as in a shared Copilot Page | "@" followed by a name |
References to organisational content, such as meetings and chats, require a Microsoft 365 Copilot licence, the same note says. If you are on the free Copilot Chat tier, expect fewer work-data sources. Our pricing and licensing guide explains the split.
One practical point: Copilot can only use files you already have permission to open. If a file is missing from the picker, the problem is usually access, not your wording. Admins can read why in our Copilot readiness guide.
How should you iterate?
Microsoft's article says to expect "some back-and-forth conversation to get the results you're looking for." The Learn module is firmer: Copilot works best as a back-and-forth conversation, not a one-shot transaction. If a detail is missing, send a follow-up. If the tone is wrong, ask it to adjust.
Microsoft's separate Write a great prompt article, last updated February 2026, adds four habits worth copying:
- Know the limit. Copilot is limited to your current conversation, so give lots of detail.
- Use quotation marks. Microsoft says this helps Copilot know what to write, modify or replace.
- Start fresh. Type "new topic" when you switch tasks, instead of interrupting.
- Check the sources. After a response, select the sources to see where content came from.
Microsoft also notes that running the same prompt again can produce different results because of built-in randomness. For anything that matters, run it twice and compare.
A spiral path tightening toward a green dot, showing Copilot prompts that improve through follow-up questions
Follow-up prompts that work:
- "Shorter. Cut it to five bullets and keep the numbers."
- "Rewrite 'we regret the delay' to sound confident, not apologetic."
- "Which of these claims came from the file, and which from the web?"
- "What did you assume that I did not tell you?"
The last one is the most useful. It makes Copilot list its guesses, and the guesses are where errors hide.
A prompt library by app
Replace the file names and people. Each prompt carries a goal, context, source and expectations.
Outlook
| Job | Prompt |
|---|---|
| Catch up | "Summarise the thread 'Vendor renewal' in four lines: decided, open, and what I must answer." |
| Reply | "Draft a reply to Sam confirming Friday delivery. He is anxious about the delay. Under 80 words, calm and specific." |
| Triage | "List unread mail from the last 7 days that needs a reply from me. Do not move or delete anything." |
Word
| Job | Prompt |
|---|---|
| First draft | "Draft a one-page project update for leadership using /ProjectNotes.docx. Plain language, end with three decisions needed." |
| Rewrite | "Rewrite this section for a non-technical reader. Keep the figures. Cut it by a third." |
| Summarise | "Summarise this report in five bullets, then list risks and who owns each." |
Excel
| Job | Prompt |
|---|---|
| Analyse | "In this table of monthly sales by region, find the three biggest month-on-month drops and suggest one chart." |
| Clean | "Find inconsistent spellings in the Region column and propose one standard list. Do not change anything yet." |
| Formula | "Write a formula that returns the average order value per region. Explain it in one sentence." |
PowerPoint
| Job | Prompt |
|---|---|
| New deck | "Create a 10-slide update for executives. Decision first, then three results, two risks, next steps. Use our template." |
| From a file | "Turn /Proposal.docx into a 12-slide client deck. One message per slide." |
| Notes | "Add speaker notes to every slide, two sentences each. Do not repeat the slide text." |
Teams
| Job | Prompt |
|---|---|
| Recap | "Summarise #WeeklyOpsSync in five bullets, then list action items with owners and dates mentioned." |
| Follow-up | "Draft a follow-up message to attendees with decisions and deadlines. Friendly, under 100 words." |
| Gaps | "What questions in this meeting were not answered?" |
Researcher and chat
| Job | Prompt |
|---|---|
| Brief | "Research how our three main competitors price onboarding. Use the web and /CompetitorNotes.docx. Return a one-page report with sources." |
| Scope | "Use only internal documents. Do not use the web." |
Microsoft's own advice for the Researcher agent is to be specific, define your search scope as work resources, the web or both, and answer its clarifying questions. We cover it in Researcher and Analyst in Microsoft 365 Copilot.
What are the most common prompt mistakes?
The first four come from Microsoft's guidance. The rest are our own advice.
- Skipping the source. If Copilot does not know where to look, it looks everywhere or nowhere. Use the slash.
- Mixing tasks in one chat. Microsoft says to type "new topic" when you switch.
- Trusting the first answer. Open the sources. Microsoft says AI-generated content can be incorrect.
- Re-running instead of refining. The same prompt can give a different answer, so use a follow-up.
- No audience. "Write a summary" has no reader. "Write a summary for a finance director" does.
- No stop rule. For anything that acts, add "Do not send, move or delete anything." Our Outlook guide explains why.
- Pasting regulated data. Microsoft's Purview documentation says DLP can block sensitive information types in prompts, and that DLP cannot scan files you upload into a prompt, only the text you type. Ask your admin what applies.
How do you build a team prompt library?
A library beats individual cleverness. Start with the ten tasks your team repeats each week. Our top 10 Copilot use cases is a good source list.
- Write each prompt with all four parts and bracketed blanks, such as [client], [file] and [date].
- Test it three times on real work. Keep it only if the checked result beats doing it by hand.
- Store it where the team already works, such as a SharePoint page or a Copilot Page.
- Add one line on what to check, for example "verify totals against the source sheet".
- Review the library monthly and delete prompts nobody uses.
Microsoft also maintains a Copilot Prompt Gallery, which its Learn modules point to. Use it for ideas, then adapt the prompts to your files and tone. When a repeatable prompt grows into a full workflow, move it into an agent. Our guide to Agent Builder versus Copilot Studio explains when.
If you would rather practise on your own documents with feedback, we teach this live in our Microsoft Copilot and Copilot Studio workshop on December 20 and 21, 2026, and the prompt templates are part of the course pack.
Related reading
- What is Microsoft 365 Copilot? A beginner's guide
- Top 10 Microsoft Copilot use cases at work
- Microsoft Copilot in Outlook: triage, drafts and scheduling
- Microsoft Copilot in PowerPoint: build, rework and present
- Microsoft Copilot in Word
- Microsoft Copilot in Excel
- Researcher and Analyst agents in Microsoft 365 Copilot
- Top 7 ways to learn Microsoft Copilot in 2026
- Official: Write a great prompt in Microsoft 365 Copilot, Write an effective prompt (Microsoft Learn)
Prompt guidance and symbol behaviour reflect Microsoft Learn and support pages as of November 19, 2026. The prompt library examples are our own. Features such as the hash reference and work-data sources depend on your licence and tenant settings, so test them in your own account.
