What makes a good Copilot prompt?

Microsoft describes four parts of a Copilot prompt: the goal, the context, the source and the expectations. Only a clear goal is required, but the other three are what turn a generic answer into one you can use.

Goal is what you want Copilot to do. Context is why you need it and who is involved. Source is the information Copilot should rely on, such as an attached file, a web page or your work emails, chats and files. Expectations describe the format or style of the response. Microsoft's own example of a work prompt combines a goal, context and expectations: an outline for a training manual on time management for hybrid workers, in a friendly tone.

Goal

Draft a reply, recap a meeting, outline a deck, rewrite a paragraph.

Context

The reader, the purpose and the decision the output supports.

Source

The named file, email thread, meeting or chat, referenced directly.

Expectations

Length, tone, structure and what to flag if the source does not cover something.

How do you point Copilot at the right file or email?

In Microsoft 365 Copilot Chat, type a forward slash and start typing the name of the person, file, meeting or email you want to reference. Naming the source this way is more reliable than describing it, because Copilot does not have to guess which document you meant.

What you can reference depends on your licence and settings. Microsoft's support page says that with a Microsoft Copilot licence and Work IQ turned on, people, files, meetings and emails are available; with Work IQ turned off, or without a Microsoft Copilot licence, only files can be referenced. If a prompt that worked for a colleague fails for you, check this first. Microsoft also notes that later parts of a prompt are likely to be emphasised more, and suggests putting source references towards the end.

What are good Copilot prompts for Outlook, Teams, Word and PowerPoint?

The prompts below follow goal, context, source and expectations. Replace the brackets, and use the forward slash to insert the named source where your licence allows. Microsoft lists similar tasks among its examples, including recapping a Teams meeting, writing a short thank-you note in Outlook, rewriting a Word paragraph and building a presentation.

Outlook: reply from a thread

Draft a reply to [thread] for the client contact. They asked for a revised timeline. I can confirm only these dates: [dates]. Keep it under 120 words, courteous and direct, and end with one question. Flag anything in the thread I have not answered.

Outlook: catch up after leave

Summarise emails from [person] about [project] from the past two weeks. Group by decision, request and information. List anything that still needs a reply from me.

Teams: meeting recap

Recap [meeting] for a colleague who missed it. List decisions, actions with owners and unresolved questions. If an owner was not stated in the meeting, write not stated.

Word: rewrite for a new reader

Rewrite the selected paragraph for a finance reader who has not seen the project before. Keep all figures and commitments unchanged. Plain sentences, under 100 words.

Word: draft from a source

Draft a one-page brief on [topic] for the operations team using [file]. Use headings for background, proposal and open questions. Do not add figures that are not in the file.

PowerPoint: outline from a document

Create a six-slide outline for a project kick-off based on [file]. One message per slide, with speaker notes listing which section of the file supports each point.

Copilot Chat: prepare for a meeting

Using [file] and [email thread], list the five questions [client] is most likely to raise in tomorrow's review, with the facts from those sources that answer each. Mark any question the sources cannot answer.

Want to see how this connects to a role?

Explore the planned team trial ↗

What does a reviewed Copilot answer look like?

A reviewed answer is checked against the sources Copilot was pointed at, because grounding in your files does not make an answer correct. Microsoft says plainly that Copilot responses can be inaccurate and should be reviewed and validated.

Consider a fictional 60-person software company, Northgate Systems. A customer success lead used the Teams recap prompt on a renewal call. Copilot's recap said the customer had agreed to renew for two years and that Priya would send the contract. The meeting transcript showed the customer had said they would consider a two-year term if pricing was confirmed, and that Priya had offered to send a pricing summary, not a contract.

The reviewed recap reads: the customer is considering a two-year renewal, subject to confirmed pricing; Priya will send a pricing summary; no decision on term length yet. The prompt asked for unresolved questions, which is what made the gap visible: the original recap had none, and a renewal call with no open questions was the signal to check.

How do you improve a Copilot answer that missed?

Refine with a specific follow-up rather than starting again. Microsoft notes that the first result is often not the final or best one and that you should expect back-and-forth.

Microsoft also recommends telling Copilot what to do rather than what not to do. Instead of do not make it long, write keep it to three bullet points. Instead of do not invent actions, write list only actions that someone explicitly agreed to in the meeting. Positive instructions give Copilot a target, and they give you a clearer standard to check against.

Can you save and reuse Copilot prompts?

Yes. Microsoft 365 Copilot lets you save a prompt after it has run successfully: hover over the prompt, select the bookmark and choose to save it. Saved prompts are visible only to you, while Microsoft-curated prompts are visible to everyone in your organisation.

Before saving a prompt for reuse, remove anything specific to one occasion, such as a date or a named client, and replace it with a bracketed blank. The prompt templates guide explains how to keep a small shared library current, including who owns it and how often it is reviewed.

When are Copilot prompts not the fix?

Better prompts will not help if Copilot cannot reach the source, if the source itself is wrong or out of date, or if your team has the licence but not the habit of using it. Low use after a rollout is usually a practice and confidence problem rather than a wording problem.

For questions about how a specific Copilot feature works in your tenant, Microsoft's own support and Learn pages are the better source, because features and licence rules change. This page covers prompting habits that stay useful across those changes. For a structured team rollout, see the Copilot training guide.

Tosheo.ai is planned to support teams that use Copilot alongside other assistants, with role-specific lessons that end in a hands-on task in the tool the team uses, graded against a visible rubric. The product is pre-build. It does not include any Microsoft Teams bot or browser extension, and it is not a replacement for Microsoft's administrator training.

Sources and scope

Microsoft Support, Get started writing prompts in Microsoft Copilot, accessed 16 October 2026 ↗

Microsoft Support, Get better Copilot responses with great prompting, accessed 16 October 2026 ↗

Microsoft Support, Refer to specific files and more in Microsoft Copilot, accessed 16 October 2026 ↗

Microsoft Support, Saving prompts to use again in Microsoft 365 Copilot, accessed 16 October 2026 ↗