AI Prompts for Microsoft 365 Productivity

Quick-Start (Copy This Right Now)

Are you using Microsoft 365 like it's Microsoft Office from 2008 — Word for typing, Excel for tables, Outlook for email? You're not alone. Most organizations pay for the full M365 suite and use maybe 20% of what it can do.

AI prompts for Microsoft 365 don't require you to master Copilot, Power Automate, or advanced features you've never touched. They use your external AI tool to generate the outputs M365 tools can then implement — formulas, document structures, email templates, meeting agendas — faster than you'd produce them manually.

Start with this Excel formula prompt:

I have an Excel spreadsheet tracking [what you're tracking]. My column structure:
Column A: [label and what it contains]
Column B: [label and what it contains]
Column C: [label and what it contains]

I want to calculate: [describe what you want to know — in plain English].
Write the exact Excel formula, explain every function used, and tell me which cell to enter it in. Also write an IFERROR wrapper version in case the formula encounters empty cells.

What this does: Produces a working Excel formula with an explanation and error-handling — the version you'd spend 20 minutes finding on Stack Overflow, produced in 30 seconds.

Understanding the Variables

Microsoft 365 productivity prompts work differently depending on which tool you're using:

Word prompts need: the document purpose, audience, and either the existing draft (for editing) or an outline request (for new content).

Excel prompts need: your column structure, what data lives in the sheet, and what calculation or transformation you want. Raw data sample inputs improve formula accuracy significantly.

Outlook prompts need: the relationship to the recipient, the communication goal, and any specific tone or constraint.

Teams prompts need: meeting type, participants, agenda goal, and time available.

⚡ Pro tip: For any M365 prompt that involves a document or spreadsheet, describe your column/heading structure in order before describing what you want. AI outputs are dramatically more accurate when it knows your data architecture before generating formulas, templates, or structures.

Step-by-Step: Microsoft 365 AI Prompts

Step 1 — Word document structure:

I need to write a [document type: report / proposal / policy / memo] for [audience: executive team / clients / HR / board]. Topic: [describe].

The document should: achieve [goal — e.g., persuade leadership to approve a budget increase].
Length target: [X pages or X words].
Sections it must include: [list any required sections].

Generate: (1) a full document outline with section headings and a 2-sentence description of what each section covers, (2) a recommended opening paragraph that establishes the document's purpose immediately, (3) a note on which section typically takes the most writing effort for this document type and why.

What this does: Produces a structured outline with guidance on where to invest writing time — particularly useful for reports and proposals where one section (usually the executive summary or financial justification) carries most of the persuasive weight.

Step 2 — Outlook email drafting:

I need to send this email in Outlook:
To: [recipient's role — not name]
Relationship: [internal colleague / external client / senior stakeholder / vendor]
Goal: [what this email should accomplish]
Key information to include: [list 3–5 points]
Constraints: [e.g., keep it under 200 words / formal tone / must include a specific deadline]

Write the email with a subject line. Avoid corporate jargon. End with a specific, easy-to-respond-to ask.

⚠️ Common mistake: Writing M365 email prompts without specifying the recipient relationship. The same information requires completely different language for an email to your CEO versus a peer colleague versus a new client. Always specify the relationship tier — it's the single biggest determinant of appropriate tone.

Step 3 — Teams meeting agenda:

I'm running a [meeting type: weekly team standup / project kickoff / client review / retrospective] in Microsoft Teams. 
Duration: [X minutes]
Participants: [list roles, not names]
Meeting goal: [what must be true at the end of this meeting that isn't true now]
Pre-work participants have done: [or "none"]

Generate: (1) a timed agenda with specific discussion prompts for each section, (2) a pre-meeting message to send in Teams chat 30 minutes before, (3) a post-meeting follow-up template with action items and decisions to send after, (4) one icebreaker or energizer suitable for a [remote / hybrid / in-person] meeting if duration is over 45 minutes.

What this does: Creates the full meeting infrastructure — before, during, and after — in one prompt. The post-meeting follow-up template is frequently the most-used output: it converts the meeting from a time-boxed conversation to a documented decision with accountability.

⚡ Pro tip: For recurring Teams meetings, build the agenda once, save it as a prompt template, and update only the agenda items each week. The structure stays the same; only the content changes. This consistency also trains your team to know what to expect, which reduces the "what's this meeting about?" questions before every standup.

Pro-Level Variations

Excel data analysis prompt:

I have Excel data with these columns: [list all columns].
Here are 5 sample rows: [paste 5 representative rows of data]

I want to know: [describe your analysis question — e.g., "which product category has the highest return rate," "which sales rep's pipeline has the most deals stuck in stage 3," "what percentage of support tickets are resolved within 24 hours"].

Write the Excel formulas or steps to answer this question. If a PivotTable would be better than a formula, describe the exact PivotTable setup (rows, columns, values, filters).

⚡ Pro tip: For complex Excel analyses, ask for a PivotTable recommendation alongside any formula. Formulas answer specific questions; PivotTables answer flexible ones. Knowing which to use — and when — is one of the most valuable Excel productivity skills.

Word template creation:

I need a reusable Word document template for [document type] that my team will use repeatedly. The template should: include placeholder text ([VARIABLE] format) for parts that change each time, have standard sections that don't change, and use Word's heading styles (Heading 1, 2, 3) consistently for easy navigation.

The template covers: [describe the document type and typical content]
The team that will use it: [role or department]

Generate the template structure with exact section headings, placeholder text, and 2–3 instructions at the top of the document that remind users what to fill in.

What this does: Creates a complete template spec — not just a content outline, but the structural layer (heading styles, placeholders, instructions) that makes a Word template actually reusable and consistent across team members.

Troubleshooting Common Issues

Problem: Your Excel formula returns #VALUE! or #REF! errors. Fix: Run the troubleshooting prompt: "My Excel formula [paste formula] is returning [error type]. My column structure is [describe]. Diagnose the error and write a corrected version."

Problem: The Word document structure feels generic. Fix: Add your organization's specific context: "We're a [industry] company with a [describe culture: formal / fast-moving / technical] culture. Adjust the document structure and opening tone accordingly."

Problem: Teams meeting agendas go off track. Fix: Ask: "Write a 2-sentence facilitator's script for each agenda item — what to say to introduce it and how to close it and move on."

⚡ Pro tip: Save your top M365 prompts — Excel formula generators, Outlook email templates, Teams meeting agendas — in PromptABCD with the tool name in the tag. When you switch between tools throughout the day, you can pull the right prompt in seconds rather than re-building it from memory.

Your Turn

Power Automate flow design prompt:

I want to automate a workflow using Microsoft Power Automate. Here's the process I want to automate:
Trigger: [what starts the workflow — e.g., "a form response is submitted in Microsoft Forms"]
Actions: [what should happen — e.g., "create a task in Planner, send an email notification to the team lead, add a row to an Excel tracking sheet"]
Data to pass between steps: [describe what information flows from trigger to each action]

Design: (1) the Power Automate flow steps in order, (2) which connector to use for each step, (3) the expression or dynamic content to map data between steps, (4) one common error to watch for when testing this flow.

What this does: Produces a buildable Power Automate flow design — the same output you'd spend 45 minutes building by trial and error in the flow designer, produced in 5 minutes. The connector and expression guidance is the time-saving layer: those are the specific Power Automate mechanics that take the longest to figure out without guidance.

⚡ Pro tip: Save your most-used M365 prompts in PromptABCD tagged by tool (Excel / Word / Outlook / Teams / Power Automate). When a colleague asks for help with a Microsoft 365 task, share the prompt — not just the output. Teaching the prompt is more valuable than doing the task once.

Pick your most time-consuming M365 task — the one you do repeatedly and still find tedious. Run the relevant prompt above with your specific context filled in. Compare the time it takes to the time you usually spend. That delta is your recurring time savings, every time you use it.