Copilot Prompt Library: 50 Essential Prompts for Enterprise Productivity

Organizations that standardize on a vetted prompt library realize Microsoft 365 Copilot value two to three times faster than those relying on ad-hoc experimentation, because standardization eliminates the most common failure mode in enterprise Copilot rollouts: users who try the tool once, get a mediocre result, and never come back.

This library contains 50 production-tested prompts across the Microsoft 365 applications where Copilot delivers the highest return — Word, Excel, PowerPoint, Outlook, Teams, Loop, and the specialized agent surfaces. Every prompt follows a consistent structure: goal, when to use it, the prompt itself, expected output quality, and suggested variations. Teams should treat this library as a starting point, not a ceiling; the best prompts come from fusing patterns like these with domain context that only the people inside your organization possess.

How to Use This Library

Three rules make prompt libraries actually stick inside organizations:

1. Always start from a template, then personalize. A prompt that mentions your specific audience, deliverable format, and tone outperforms a generic prompt every time. Copy the template, then edit.
2. Feed Copilot real artifacts, not just instructions. The prompts below are designed to be combined with / references to files, emails, meetings, and pages. Reference content is where Copilot's advantage over a general-purpose chatbot comes from.
3. Review every first draft before you ship. Copilot is a draft engine, not a publisher. Every output on this list should be edited for factual accuracy, voice, and sensitive-information exposure.

Word: Drafting and Editing (Prompts 1-10)

1. Draft a structured executive summary

When to use: You need a one-page summary of a longer document for a senior audience. Prompt: "Summarize this document for a busy executive in one page. Lead with the recommendation, followed by three supporting findings, then risks and open questions. Use a formal business tone. Preserve any financial figures exactly." Expected quality: Usable first draft; always verify financial figures against the source. Variation: Swap "busy executive" for "board of directors," "regulator," or "new team member" for different audiences.

2. Rewrite a paragraph in a specific voice

Prompt: "Rewrite the highlighted paragraph in a confident, concise voice. Eliminate hedging language. Keep every fact unchanged. Do not invent new claims." When to use: Turning hedged internal drafts into customer-ready copy. Variation: Change "confident, concise" to "warm and empathetic" for customer service, or "neutral and factual" for regulatory filings.

3. Structure an unstructured draft

Prompt: "Reorganize this document into H1 introduction, H2 background, H2 analysis, H2 recommendations, H2 next steps. Preserve every sentence; only reorder and add headings. Note any content that does not fit an obvious section." When to use: Taming a stream-of-consciousness draft without rewriting.

4. Generate an FAQ from a long document

Prompt: "Read the attached whitepaper and generate 10 frequently-asked questions with concise answers. Order them from most common to most technical. Include citations to the section of the document where each answer is grounded." When to use: Converting a long-form piece into multiple derivative assets.

5. Create a plain-language version

Prompt: "Rewrite this document at a Grade 8 reading level. Preserve all facts and numbers. Define any technical terms parenthetically the first time they appear. Output length should not exceed 60% of the original." When to use: Audience adaptation for broader readership or compliance-driven plain-language requirements.

6. Draft responses to document comments

Prompt: "For each comment on this document, draft a reply that either accepts the change, defers to a stakeholder by name, or politely disagrees with a supporting reason. Keep each reply under three sentences." Variation: Ask Copilot to group comments by theme before responding.

7. Generate a title and three subtitles

Prompt: "Propose five title-and-subtitle pairs for this document aimed at a CIO audience. Each should be specific, avoid jargon, and clearly signal the reader benefit."

8. Convert narrative to bullet points

Prompt: "Convert this document to a scannable, bulleted format. Keep every heading. Each bullet should be a complete thought, under 20 words, and should start with a verb where possible."

9. Tighten word count

Prompt: "Reduce this document's length by 30% without cutting any section. Prefer shortening sentences, removing hedges, and combining redundant paragraphs. Preserve every claim and every number."

10. Produce a change log from track changes

Prompt: "Summarize every edit in this document as a bulleted change log. Group by section. For each change, note the type (clarification, factual correction, new claim, deletion). Call out any changes that need stakeholder sign-off."

Excel: Analysis and Modeling (Prompts 11-20)

11. Highlight anomalies in a data column

Prompt: "Analyze column C for anomalies. Flag any values that are more than two standard deviations from the mean or that violate the expected sign convention. Return a short summary plus a filtered view of the suspect rows." Expected quality: Strong for tabular data; always cross-check methodology.

12. Build a reconciliation between two ranges

Prompt: "Compare Range1 and Range2 by the Transaction ID column. List matches, differences with a delta column, and records that appear in only one range. Return a pivoted summary of totals by category."

13. Build a cohort retention table

Prompt: "Using the Signup Date and Activity Date columns, build a monthly cohort retention table for the last 12 cohorts. Return a heat-mapped grid with percentages and an explanation of the logic."

14. Explain a formula in plain language

Prompt: "Explain what this formula does in plain language. Note any edge cases it handles and any it does not. Flag any assumptions that could silently produce wrong results." When to use: Inherited spreadsheets and audit reviews.

15. Convert a messy range to a structured table

Prompt: "Convert this range to a structured table. Propose clean header names. Infer data types. Flag any cells that look like text masquerading as numbers, or dates stored as text."

16. Forecast with assumptions

Prompt: "Forecast the Revenue column for the next six months using a simple linear trend. Include an upper and lower bound using a 10% sensitivity range. Plot it and explain your assumptions."

17. Generate a narrative insight section

Prompt: "Write a narrative insight section suitable for a monthly report that summarizes the three most important findings in this workbook. Lead with the business implication. Do not repeat raw numbers already visible in the table."

18. Build a KPI definitions glossary

Prompt: "List every named metric referenced in this workbook. For each, propose a plain-language definition, the columns and formulas used, and any known caveats."

19. Create conditional formatting rules

Prompt: "Propose conditional formatting rules that highlight top-quartile and bottom-quartile values by category, flag overdue rows, and subtly shade weekends in date columns. Return the rules as a summary and apply them."

20. Draft release notes for a model

Prompt: "Draft release notes for this model that list the structural changes since the last version, assumption updates, and any known limitations. Format as a bullet list suitable for sharing with downstream consumers."

PowerPoint: Slide and Story Construction (Prompts 21-28)

21. Draft a 10-slide narrative deck from a document

Prompt: "Create a 10-slide deck from this document aimed at a steering committee. Use a problem-solution-recommendation arc. Each slide should have a single punchy title, three bullets, and speaker notes. Do not exceed 30 words per slide body."

22. Produce an executive appendix

Prompt: "Generate an appendix of supporting evidence for this deck: methodology, assumptions, citations, and glossary. Put each on its own slide with a consistent header."

23. Rewrite slide titles as takeaways

Prompt: "Rewrite every slide title in this deck so it states the single takeaway rather than the topic. Keep titles under ten words. Example: 'Q3 Financials' becomes 'Q3 revenue beat plan by 8%.'"

24. Convert a document into a design-ready outline

Prompt: "Turn this document into a design-ready outline with slide labels, suggested layouts (title, two-column, comparison, data), and placeholder notes for where imagery or charts should live."

25. Polish speaker notes

Prompt: "Rewrite the speaker notes on every slide so they sound natural when spoken aloud. Target 60-90 seconds per slide. Include a smooth transition to the next slide."

26. Translate a deck while preserving formatting

Prompt: "Translate every slide in this deck to [language]. Preserve all formatting, numeric formatting conventions, and placeholder structure. Flag idioms that may not translate cleanly."

27. Generate an internal versus external version

Prompt: "Produce two versions of this deck: an internal version with candid commentary and a public version that removes sensitive commentary and replaces specific customer names with anonymized descriptions."

28. Build a discussion-guide companion

Prompt: "Create a discussion-guide companion for this deck. For each slide, provide two open-ended questions, one likely objection, and a suggested response."

Outlook: Email and Triage (Prompts 29-36)

29. Summarize a long email thread

Prompt: "Summarize this email thread in under 150 words. List key decisions, open action items with owners, and any unresolved questions."

30. Draft a polite reply declining a request

Prompt: "Draft a reply that politely declines this request. Acknowledge the sender's effort, explain one clear reason, and offer one concrete alternative. Keep under 120 words."

31. Triage the inbox

Prompt: "Review my inbox from the last 24 hours. Group messages into: needs reply from me, needs a decision, informational, and newsletter. For each 'needs reply,' suggest a one-line draft reply."

32. Follow up on a stalled thread

Prompt: "Write a follow-up to this email that is brief, warm, and not pushy. Reference the last exchange, restate the ask clearly, and propose a specific next step."

33. Produce meeting-prep email

Prompt: "Using my calendar and recent emails with this person, draft a prep email summarizing the relationship context, the three most important recent threads, and three questions I could ask. Keep under 200 words."

34. Draft a difficult message

Prompt: "Draft a message delivering this difficult news to this audience. Be direct in the first sentence, compassionate throughout, and concrete about next steps. Offer to discuss live."

35. Extract tasks into a list

Prompt: "Review my unread mail and extract every task directed at me. Return a list grouped by sender, with deadline if stated, and mark anything ambiguous."

36. Convert an email to a one-paragraph brief

Prompt: "Convert this email thread to a one-paragraph brief suitable for sharing with a colleague who was not on the thread. Preserve facts, strip out pleasantries, and end with the current decision needed."

Teams and Meetings (Prompts 37-41)

37. Recap the meeting with decisions and actions

Prompt: "Summarize this meeting in three sections: decisions made, action items with owners and due dates, and open questions. Flag any item that seemed like it needed escalation."

38. Catch me up on a meeting I missed

Prompt: "I missed this meeting. In under 200 words, tell me what I need to know, who took positions on what, and what I need to do next if anything."

39. Draft a channel post from a Loop page

Prompt: "Convert this Loop page into a Teams channel announcement. Lead with one sentence that states the outcome. Include a three-bullet summary and a call-to-action to read the page."

40. Prepare for a meeting

Prompt: "Using my recent emails, Loop pages, and documents related to this meeting, prepare me: what is the objective, who will be there, what did we decide last time, what is likely to come up, and what should I say in the first five minutes?"

41. Generate a coaching summary

Prompt: "Review this meeting transcript and provide coaching feedback for me personally: when I spoke, when I interrupted, moments I could have been clearer, and three specific improvements I could make next time."

Loop and Copilot Pages (Prompts 42-44)

42. Turn a conversation into a working page

Prompt: "Convert this chat thread into a working Copilot page with headings, a decision log, and a tasks section. Preserve attribution. Resolve simple contradictions and flag the ones that need human judgment."

43. Generate a weekly rollup page

Prompt: "Create a weekly rollup page combining this team's recent chats, shared files, and open tasks. Organize as: wins, decisions, blockers, tasks for next week."

44. Draft an onboarding brief

Prompt: "Create an onboarding brief for a new joiner to this workspace. Include: who works here, what we do, active projects, key documents, and the rhythms (meetings, reviews, norms)."

Specialized Agents (Prompts 45-50)

45. Build a research agent prompt

Prompt: "I want to build a research agent that answers questions only from the documents in [specified SharePoint site]. Draft its system prompt, including citation requirements, refusal when no grounded answer exists, and tone guidelines."

46. Build a policy-lookup agent prompt

Prompt: "Draft the system prompt for an HR-policy lookup agent that answers employee questions from the policy library. Require citations. Refuse to give legal advice. Escalate to HR contact when in doubt."

47. Produce evaluation test cases for a new agent

Prompt: "Here is the system prompt for a new agent. Produce 25 evaluation test cases across correct-answer cases, edge cases, refusal cases, and adversarial prompts. For each, include the expected response pattern."

48. Audit an agent for hallucination risk

Prompt: "Review this agent's system prompt and retrieval configuration. Identify the three biggest hallucination risks and propose a concrete mitigation for each."

49. Draft a release note for an agent update

Prompt: "Draft release notes for this agent covering: what changed, why, expected user impact, any migration steps, and who to contact with questions."

50. Retire an agent

Prompt: "Draft a retirement plan for this agent: user communication, redirect targets, timeline, data retention decisions, and a final audit log entry."

Prompt Engineering Principles to Internalize

Once teams have used this library for 30 days, the next step is coaching users to build their own. Five principles deliver most of the gain:

1. State the audience. "For a board audience" or "for a new joiner" does more work than any adjective.
2. State the artifact. Format, length, tone, and structure should all be specified.
3. Ground in references. Copilot without references is a chatbot; Copilot with references is an enterprise tool.
4. Constrain what not to do. "Do not invent new claims," "preserve every number exactly," and "flag uncertainty" shift model behavior substantially.
5. Review, then reuse. The prompts that produce good output on Monday will produce good output on Thursday. Save them.

Organizations that measure prompt usage — through the adoption dashboard, through champion reporting, or through shared prompt libraries — see the fastest learning curves. Treat the prompt library as living infrastructure, not a one-time artifact.

Frequently Asked Questions

Is a prompt library a substitute for training?

No. A prompt library is the scaffold that makes training stick. Users remember 10-15% of generic training; they remember 50-70% of a task they performed themselves using a template. The library plus hands-on sessions outperforms either alone.

How do we keep the library current?

Appoint owners per application area (one for Word, one for Excel, and so on). Review quarterly. Retire prompts that no longer produce good output after model updates. Add prompts that surface through champion programs or adoption dashboards.

Who should contribute to the library?

Start with a small curation team of three to five people across IT, change management, and one or two business departments. Once the library exists, open contributions through a lightweight review: any user can propose a prompt; an owner reviews and promotes.

Should we share the library with external parties?

Internal-only unless your legal team has reviewed. Some prompts reference proprietary workflows that you may not want to disclose. Treat the library as you would any other internal process asset.

How do prompt libraries interact with governance?

They are a governance asset. A well-maintained library is evidence that the organization is directing AI usage toward approved, reviewed patterns rather than letting every user experiment independently on sensitive data. Governance teams should sample prompts quarterly for compliance review.

What is the first prompt new users should learn?

The summarization prompt. It is low-risk, demonstrates value immediately, and builds confidence. From there, users graduate to editing prompts, then drafting, then analysis.