How to Prompt Microsoft Copilot Like a Pro: A Practical Cheat Sheet for Better Results
Better prompts produce better outcomes. Use this practical framework to get clearer, more useful results from Microsoft Copilot in Outlook, Excel, PowerPoint, Teams, and beyond.
Quick takeaway: Tell Copilot what you need, why you need it, what a good answer looks like, and which information it should use.
Formula: Goal + Context + Expectations + Source
Microsoft Copilot can help draft emails, analyze data, create presentations, summarize meetings, and surface work information. But it is not a mind reader. The quality of its response depends heavily on the quality of the instruction you give it.
A short prompt such as “Find emails about the Brown Project” may technically be valid, but it leaves many unanswered questions:
-
Which emails count as relevant?
-
What time period matters?
-
Which people or teams are most important?
-
Do you want a list, a summary, risks, decisions, or action items?
-
Is this for your personal review or an executive audience?
When a prompt leaves gaps, Copilot has to make assumptions. A well-structured prompt reduces those assumptions and gives you a response you can actually use.
Start with the four-part formula
Use this reliable structure whenever you want a high-quality Copilot response:
Copy-and-paste prompt template
[Goal][Context] [Expectations] [Source]
A stronger prompt in action
Weak prompt
Find emails about the Brown Project.
Better prompt
Create a summary of emails related to the Brown Project.Prompt cheat sheet
Use these prompt patterns as a starting point. Replace the text in brackets with your own details.
Summarize information
Summarize [topic, project, document, meeting, or email thread].This is for [audience or purpose].Include [key decisions, milestones, risks, deadlines, owners, or actions].Use a [formal, executive, technical, concise] tone.
Format the result as [bullets, table, email, briefing, or report].Use [specific files, emails, chats, dates, meetings, or SharePoint site].
Draft an email
Draft an email to [recipient or group] about [topic].The purpose is to [inform, request approval, follow up, apologize, or escalate].Use a [professional, friendly, concise, confident] tone.Keep it under [word count] words.
Include [specific details, deadlines, requested actions, or next steps].Use the attached [file, meeting notes, proposal, contract, or project update] as the source.
Analyze data in Excel
Analyze the data in this workbook.Identify the most important trends, outliers, and potential risks.Compare [metric] by [region, product, customer, month, team, or other field].Create a chart that best explains the main finding.
Then provide a short executive summary with three recommended next actions.
Create a presentation
Create a [number]-slide presentation about [topic].The audience is [executive leadership, clients, employees, technical team, or board members].The goal is to [inform, persuade, secure approval, train, or provide an update].Include slides for [background, key findings, risks, recommendations, timeline, and next steps].
Use a [professional, modern, minimal, data-driven] style.
Use the attached [Word document, outline, meeting recap, or file] as the source.
Catch up on a Teams meeting
Summarize this meeting for someone who could not attend.Include:– Main discussion points
– Decisions made
– Open questions
– Action items
– Owners
– Due datesFlag anything that requires executive attention.
Pro tip: Copilot in Teams can help recap key discussion points and action items, but post-meeting questions typically depend on a meeting transcript being available. Turn on transcription when appropriate and permitted by your organization. support.microsoft
Do’s and don’ts
Do: be specific
Specificity reduces ambiguity. Instead of saying “Make this better,” tell Copilot what “better” means.
Try this:
Rewrite this project update for senior leadership.
Keep it under 250 words.
Use a confident but transparent tone.
Lead with business impact, then include risks and requested decisions.
Do: define the audience
A technical team, a client, a manager, and an executive board need different kinds of information.
Explain this security issue for a non-technical executive audience.
Avoid jargon, define any necessary terms, and focus on business impact and recommended next steps.Do: specify format and length
Give Copilot a container for the response.
Return the result as a table with these columns:
Task, Owner, Due Date, Status, Risk, and Next Step.Create a five-bullet executive summary. Each bullet must be no longer than two sentences.Do: provide an example
If you have an ideal format, tone, or structure, show it.
Use this style for the summary:
- Decision:
- Business impact:
- Owner:
- Next action:
- Deadline:Do: treat Copilot like a conversation
Your first prompt does not have to be perfect. Ask for a revision, a different format, more evidence, a shorter version, or a different audience.
Useful follow-up prompts include:
-
“Make this more concise and remove technical jargon.”
-
“Turn this into an executive-ready email.”
-
“Add a section for risks and mitigation steps.”
-
“Create a table instead of narrative paragraphs.”
-
“What assumptions did you make?”
-
“List the source documents or messages used.”
-
“Challenge this recommendation and identify potential weaknesses.”
Do: review and verify
Copilot can accelerate drafting and analysis, but you remain responsible for the final output. Review names, dates, numbers, calculations, claims, citations, recommendations, and confidential information before sharing anything externally.
Microsoft’s guidance similarly emphasizes providing details and structure, iterating on prompts, and reviewing and verifying AI-generated content. learn.microsoft
Don’t: be vague
Avoid prompts such as:
Help with this.Make this good.Tell me everything about the project.Instead, define the outcome, audience, scope, and desired format.
Don’t: mix unrelated tasks
A single prompt with several unrelated goals often leads to a scattered response. Break work into separate requests.
Less effective
Summarize the budget, draft an email to the vendor, create slides, and explain the HR policy.More effective
Start with the budget analysis. Then use that output as context for the vendor email. Finally, create the presentation from the approved findings.
Don’t: provide conflicting instructions
Avoid pairs such as:
Keep it extremely short but include every important detail.Use a casual tone but make it highly formal.
Prioritize the outcome you care about most, then state any tradeoff clearly.
Choose the right information source
One of the biggest reasons Copilot responses miss the mark is that Copilot is using the wrong source of information.
Microsoft’s current Copilot experience uses a Work IQ control rather than separate “Work” and “Web” tabs. When Work IQ is enabled, Copilot can reference Microsoft 365 work content that you already have permission to access—such as emails, files, chats, meetings, people, and projects—alongside attached content and web information. When it is off, Copilot does not use your Microsoft 365 work data; it can use attached content, public web information, and your personalization settings instead. support.microsoft
Important: Copilot only works with organizational content you are authorized to access. It does not bypass your organization’s existing permissions. support.microsoft
Where Copilot adds value
Microsoft 365 Copilot works across familiar productivity applications, including Word, Excel, PowerPoint, Outlook, and Teams. The best use case is not “ask AI anything.” It is using the right prompt inside the place where your work already lives.microsoft+1
Excel: turn data into decisions
Copilot in Excel can assist with analyzing data, surfacing insights, and creating charts. It is especially useful when you know the business question but do not want to manually build formulas, filters, pivot tables, or visuals from scratch. microsoft
Use it for:
-
Finding trends, patterns, anomalies, and outliers
-
Comparing performance across regions, products, customers, or periods
-
Generating or explaining formulas
-
Creating charts from existing data
-
Organizing, filtering, and categorizing records
-
Producing a short executive interpretation of the numbers
Example prompt
Review the sales data in this workbook.Compare year-to-date revenue and gross margin by region.Identify the three largest performance changes and any unusual outliers.
Create one chart that best explains the most important trend.Then write a four-bullet executive summary with recommended actions.
PowerPoint: move from outline to presentation
Copilot in PowerPoint can create presentations from prompts or existing content, summarize decks, add content, and help with deck-wide formatting changes.learn.microsoft+1
Use it for:
-
Turning a Word document, outline, or meeting recap into slides
-
Creating a first-draft leadership update
-
Building training decks and project status presentations
-
Generating speaker notes
-
Condensing a long deck into an executive summary
-
Reworking a presentation for a different audience
Example prompt
Create an eight-slide executive presentation using the attached project update.The audience is the leadership team.Include: project objective, progress to date, milestones, budget status, risks, decisions needed, and next steps.Use a concise, data-driven style with minimal text per slide.
Add speaker notes for each slide.
Teams: make meetings actionable
Copilot in Teams can summarize discussions, capture key decisions, identify action items, and answer questions about meeting content when the needed meeting data is available.
Use it for:
-
Catching up after a meeting you missed
-
Turning a conversation into decisions and tasks
-
Identifying who owns each follow-up
-
Preparing a stakeholder update
-
Finding what was said about a specific topic
-
Reviewing open questions and unresolved risks
Example prompts
What decisions were made about the deployment timeline?
List the decision, the owner, the date discussed, and any dependencies.Create a follow-up message from this meeting.
Thank attendees, summarize the three major decisions, and list action items with owners and deadlines.Outlook and email: draft from real context
Copilot is particularly valuable when you give it source material. Rather than asking it to invent an email from scratch, attach or reference the information it should use: a proposal, contract, project update, meeting notes, or client correspondence.
Example prompt
Using the attached project update, draft a professional email to the client.Explain the revised timeline, acknowledge the dependency that caused the change, and propose a 30-minute meeting next week to confirm priorities.Keep the tone transparent, confident, and solution-focused.Limit the email to 200 words.This produces a more grounded draft than a generic request because Copilot has the relevant context.
Get more from agents
Agents can extend Copilot by handling focused tasks with defined instructions and access to approved organizational or web data. Microsoft describes agents as tools that can automate or execute business processes based on predefined instructions and available organizational data. learn.microsoft
Depending on your organization’s licensing, configuration, and permissions, agents may help with recurring work such as research, planning, summarization, task tracking, and structured analysis. Microsoft highlights agents such as Researcher and Analyst for insight-oriented work, while Teams-focused capabilities can support meeting notes, decisions, and action tracking.
When an agent makes sense
Consider an agent when the same request happens repeatedly:
-
Weekly project-status briefings
-
Account or customer research
-
Policy and process Q&A
-
Meeting follow-up tracking
-
Sales or pipeline summaries
-
New-employee onboarding guidance
-
Contract or document intake workflows
Example agent instruction
Create a weekly project briefing using updates from the Brown Project Teams channel, the project SharePoint site, and stakeholder emails from the past seven days.Include:– Progress completed this week
– Upcoming milestones
– Risks and blockers
– Decisions needed
– Action items with owners and due datesWrite for executive leadership and keep the briefing under 600 words.
Always confirm which sources the agent is allowed to use, test its outputs on low-risk work first, and build a review step into any workflow that affects customers, finances, legal matters, or operational decisions.
Document and PDF analysis
Long documents can be difficult to review manually. Copilot can help you work through contracts, vendor proposals, policies, technical specifications, project documents, and other large files—especially when you give it a focused review question.
Useful document prompts
Extract the essentials
Summarize this document in plain language.Include the purpose, key obligations, deadlines, financial commitments, risks, and decisions required.Provide a final section called “Questions to Resolve.”
Compare two documents
Compare the attached contract with the previous version.Create a table with:Clause or topic, what changed, business impact, potential risk, and recommended follow-up question.
Focus on payment terms, liability, termination, data protection, service levels, and renewal terms.
Prepare an executive briefing
Review this vendor proposal and prepare a one-page executive briefing.Include the vendor’s proposed solution, total cost, expected value, implementation timeline, major assumptions, risks, and a recommendation.Use only the information in the attached document.
Important: Copilot can help identify differences and generate questions, but it is not a substitute for legal, financial, security, compliance, or subject-matter review. Treat its findings as a starting point for human evaluation.
A simple prompt improvement exercise
Here is how to turn a generic request into a useful one.
Every added instruction gives Copilot a clearer path to a useful result.
Final checklist
Before sending a prompt, ask yourself:
-
Goal: Did I clearly state what I want Copilot to do?
-
Context: Did I explain why I need it and who will use it?
-
Expectations: Did I specify the tone, format, length, and level of detail?
-
Source: Did I tell Copilot which files, emails, meetings, dates, chats, or web sources to use?
-
Scope: Did I avoid mixing unrelated tasks into one request?
-
Verification: Will I review the output before I use or share it?
The bottom line
Microsoft Copilot is most effective when you give it a well-defined job rather than a vague question. The essential habit is simple:
Goal + Context + Expectations + Source
Use that framework in Outlook, Excel, PowerPoint, Teams, documents, and agents. Be explicit about the audience and desired result. Point Copilot to the right information. Then refine the first draft through follow-up prompts and human review.
The people who get the best results are not necessarily AI experts. They are the people who communicate clearly, provide the right context, and know how to turn a broad request into a specific, reviewable outcome.



















