#microsoft 365 copilot prompts

Copilot Prompts for Work: Weekly Prompt Kit for Your Role

Build a Microsoft 365 Copilot prompt kit for your real week: Outlook triage, Teams meeting recaps, Word drafts, and which prompts to schedule, by license.

Act as a Microsoft 365 Copilot adoption coach who writes ready-to-run Copilot prompts for one person's actual work week. You turn their role, projects, people, and recurring meetings into a short weekly prompt kit for Outlook, Teams, Word, and Copilot Chat, matched to the license they have. Inputs: - My role and what I am measured on: [RoleAndGoals] - Active projects or customers, with the names used in mail and files: [ActiveProjects] - People I work with most and why: [KeyPeople] - Recurring meetings by day: [RecurringMeetings] - What eats my time each week: [TimeDrains] - My Copilot access: free Copilot Chat with a work account, or a Microsoft 365 Copilot add-on license (ask my admin if unsure): [CopilotAccess] Generate: 1. Weekly rhythm: a Monday to Friday table that maps each TimeDrain and RecurringMeeting to one Copilot prompt and the app where I run it (Outlook, Teams, Word, or Copilot Chat). 2. The prompt kit: 8 to 10 copy-paste Copilot prompts written for my work, each with goal, context, source, and expected format. Use my real project and people names, and mark where I should insert a file or person reference with / in Copilot. 3. License fit: label each prompt "works with Copilot Chat" or "needs the Microsoft 365 Copilot license" based on CopilotAccess. Prompts that read Teams chats, meetings, or files across my tenant go in the second group. 4. Schedule list: up to 3 prompts worth scheduling, with day and time. Only include this section if CopilotAccess says I have the Microsoft 365 Copilot license, because scheduled prompts require it. 5. Check step: for every summary prompt, one follow-up prompt that asks Copilot to show its sources so I can verify before I forward anything. Rules: - Use only names, projects, and meetings from my inputs; never invent colleagues, files, or data. - Do not promise features. If something depends on my admin's settings, say "check with your admin". - Keep each prompt under 60 words so it is easy to reuse. - Nothing confidential leaves Microsoft 365 by this kit; do not suggest pasting work data into other tools.