Copilot in ActionPowerPoint · Outlook
Section 1 of 118 scenarios · 2 apps
Microsoft 365 Copilot · PowerPoint & Outlook

Copilot in Action

Making Copilot real across PowerPoint and Outlook. Eight scenarios across two applications — and every file you need to run them yourself, during the lab or long after it.

Start with zero experience. The new beginner path covers your first prompt, working with sources, safe review, and everyday use in Word, Excel, PowerPoint, Outlook, Teams, OneNote, and Pages. Optional guides introduce Create, agents, and Notebooks.

Start the beginner learning path

13 core guides · 3 optional explorations · fictional practice content. Already comfortable with the basics? Continue with the original eight scenarios below.

Ground it

Turn a research document into a working draft deck with referenced content, instead of starting from a blank slate.

Brand it

Move from generic output to a polished, on-brand asset using a template, a Brand Kit, and Skills.

Prioritize it

Tell Copilot what matters in your inbox, and have it flag and explain as mail arrives.

Automate it

Set standing rules for your calendar and inbox, then build an assistant that briefs you each morning.

PowerPoint

Four scenarios: grounded generation, template-based creation, Brand Kits, and Skills. Each one builds on the artifact from the last.

Outlook

Four scenarios: inbox prioritization, calendar governance, inbox clean-up, and a scheduled executive triage assistant.

Q&A

Open floor. Bring the workflow you could not make work — that is usually where the useful conversation is.

Before you start: Sign in to Microsoft 365 Copilot with your work account. For the PowerPoint scenarios, save the lab files to OneDrive or SharePoint — Copilot in PowerPoint references cloud-stored files, not files sitting on your desktop. Close anything you would not want visible during a shared exercise.
Practice data note: The lab files use Zava, a fictional materials brand, and Project Northstar, a fictional consumer research programme. Every company, person, figure, and research finding in them is invented for Microsoft 365 Copilot demonstration purposes and does not represent real data.
Section 2

The lab files

Three files support the eight scenarios. Two are inputs you hand to Copilot. The third is the prompt guide — every prompt on this site, in one document you can take back to your desk.

Word document · 39 KB

Project Northstar — Consumer Research Summary

A fictional research summary from Insights & Analytics covering four headline findings: a 25–34 segment that behaves differently than assumed, product-finder friction, a channel mix that has fallen behind consumer behaviour, and a conditional willingness to trade data for relevance. It closes with three Open Questions — which both PowerPoint prompts deliberately fence the final slide to.

PowerPoint 1PowerPoint 2
Download the summary
PowerPoint template · 24.4 MB

Zava Corporate Template

A 33-slide, 36-layout corporate template for the fictional Zava brand, in 16:9. It carries title, section header, agenda, content, photo, comparison, conclusion, large-number, statement, and quote layouts, plus the brand's typography, palette, and imagery treatment. This is the style guide Copilot reads in scenario 2.

PowerPoint 2PowerPoint 3
Download the template
Word document · 18 KB

Copilot Prompt Guide

Every prompt used in this lab in a single document: the three PowerPoint prompts, the Outlook prioritization and calendar instructions, the inbox clean-up pair, and the full executive triage brief. The prompts on this site match it exactly — the guide is the take-home copy.

All 8 scenarios
Download the prompt guide

Which file goes with which scenario

ScenarioWhat you needWhy
PPT 1 Grounded content generationNorthstar summaryThe document is the sole source for the deck's content.
PPT 2 Template-based creationNorthstar summary and Zava templateSame content, but the template supplies layout, colour, type, and graphics.
PPT 3 Brand KitsAn unpolished deck — use your scenario 1 outputThe point is watching a generic deck get restyled to brand in place.
PPT 4 PowerPoint SkillsYour deck from scenario 2Skills run against a finished artifact, so scenario 2's output is the test subject.
OTL 1 Inbox prioritizationNo file — your own mailboxPrioritization is only meaningful against mail you actually receive.
OTL 2 Govern your calendarNo file — your own calendarThe rules govern your real meeting load.
OTL 3 De-clutter the inboxNo file — your own mailboxCopilot proposes a structure based on what is actually in your inbox.
OTL 4 Executive triage assistantNo file — your own work contextThe brief reads across your mail, chats, invitations, and tasks.
The PowerPoint scenarios are a chain, not four independent exercises. Scenario 1 produces the unpolished deck that scenario 3 restyles. Scenario 2 produces the on-brand deck that scenario 4 runs Skills against. Keep both outputs open as you go.
PowerPoint · Scenario 1

Grounded content generation.

Turn a blank slate into a working draft with referenced content — sourced from a document you supply, not from the model's general knowledge.

What to expect: Artifact creation based on input file(s) — turn a blank slate into a working draft with referenced content.
  1. Put the summary in OneDrive or SharePoint. Copilot in PowerPoint references cloud-stored files. A copy on your desktop will not be found.
  2. Open a new, blank presentation. Then open the Copilot pane.
  3. Paste the prompt and reference the file. Type / to attach it by name, or name it in the prompt exactly as it is saved.
  4. Check the references, not just the slides. Open the summary alongside the deck and confirm the four findings and the open questions came from the document — and that nothing was added.

Grounded generation

Create a presentation from the Project Northstar Consumer Research Summary. Use the four headline findings as the slide outline, and format the messaging & the language at a Marketing Director audience. Add a slide at the end covering only the open questions listed in the document. Do not add questions that are not in it.
Notice what the prompt is doing. It sets the outline (the four headline findings), the audience (Marketing Director), and a hard boundary on the final slide (only the open questions in the document, and no others). That last clause is the interesting one — it is a constraint, not a request.

Reflection: The document lists exactly three open questions. Did your final slide contain three — or did a plausible fourth appear? Grounding is a claim you should verify, not assume.

PowerPoint · Scenario 2

Template-based creation.

Same source, same audience, same outline — but now Copilot has a template to work from. Move from generic output to a polished, on-brand asset.

What to expect: Move from generic outputs to polished, on-brand assets.
  1. Save both files to OneDrive or SharePoint. Copilot needs to reach the template as well as the source document.
  2. Start a new presentation and open Copilot. Start a fresh conversation so scenario 1 does not colour the result.
  3. Paste the prompt, referencing both files. The summary is the content; the template is the style guide.
  4. Put the two decks side by side. Identical content brief, materially different artifact. That gap is the point of the scenario.

Template-based creation

Create a presentation from the Project Northstar Consumer Research Summary while also using the attached template as a style guide for layouts, style, graphics, color scheme, themes and other relevant design components. Use the four headline findings as the slide outline, and format the messaging & language at a Marketing Director audience. Add a slide at the end covering only the open questions listed in the document. Do not add questions that are not in it.
Keep this deck. Scenario 4 runs Skills against the artifact you create here, and it is the natural comparison point when scenario 3 restyles your scenario 1 output.

Reflection: The Zava template carries 36 layouts. Did Copilot reach for the right ones — section headers, large-number, quote — or default to title-and-bullets in brand colours? On-brand and well-designed are not the same achievement.

PowerPoint · Scenario 3

Brand Kits — what, why, how, who.

A Brand Kit holds your organization's design system so Copilot can restyle an existing deck to brand, rather than you rebuilding it slide by slide.

What to expect: What it holds, why they matter, how they are created, who owns it — then a guided tour of an existing Brand Kit, applied live to an unpolished deck.
What

Your brand's typography, colour palette, logo variants, and imagery treatment, captured once as a reusable definition Copilot can apply.

Why

Styling stops depending on who happened to build the deck. The same brand decisions land on every slide, every time.

How

Built from assets you already own — an approved template, a brand style guide, an existing on-brand deck — then published for others to use.

Who

Owned by brand or marketing operations, not by each deck author. One owner, one source of truth, one place to update it.

FilesUse your unpolished deck from scenario 1Zava Corporate Template
  1. Open the deck from scenario 1. The generic one, before the template was involved — that contrast is what makes the restyle legible.
  2. Confirm which Brand Kit you have available. The lab demonstrates the Zava kit; in your own tenant, use the kit your brand team publishes.
  3. Run the prompt. Watch the restyle land across every slide rather than only the one you are looking at.
  4. Audit the result. Check the slides that were hardest to style — tables, charts, and anything with an image behind text.

Apply the Brand Kit

Modify and redesign this presentation by applying the Zava brand kit to this presentation. Restyle every slides in this deck to match the style guides, themes, colors, fonts, layout, logos, graphics, etc. from the brand kit.
Adapting this to your own work: replace “the Zava brand kit” with the name of the kit published in your tenant. If your organization has not created one yet, that is the takeaway from this scenario — the question to bring back is who owns our brand kit, not how do I style this deck.

Reflection: A Brand Kit changes who does brand enforcement. If restyling is one prompt, what is the reviewer for?

PowerPoint · Scenario 4

PowerPoint Skills.

Skills are reusable instructions you save once and run on demand — the standards you apply to every deck, encoded so they no longer depend on you remembering to apply them.

What to expect: What Skills are, how they are created, why they matter, where they live, plus tips and tricks — seen live against the artifact from scenario 2.
FilesUse your on-brand deck from scenario 2
This scenario is demonstrated live. The Prompt Guide contains no fixed prompt for it — and deliberately so. In the other seven scenarios you paste a prompt; here, the prompt is the artifact you build. Follow along and build one against your own standards.
What

Reusable, instruction-based capabilities that give Copilot domain expertise, workflows, and task-specific guidance — selected from the Copilot pane in PowerPoint.

Why

The check you do inconsistently becomes the check that runs every time. Consistency stops being a discipline problem.

Where

Custom Skills are authored as SKILL.md files stored in OneDrive, then toggled on or off in the Copilot pane — so the instruction is shareable, not trapped in one person's chat history.

Tips & tricks

  • Encode the check you repeat, not the one you did once. If you have never run it twice, it is a prompt, not a Skill.
  • Define what “done” looks like. A Skill with vague success criteria produces vague edits, and you will not notice until a customer does.
  • Keep the scope to a single job. Narrow Skills compose well; one Skill that tries to do everything fails in ways that are hard to diagnose.
  • Test it against a deck you know is wrong. If it does not catch the problem you planted, the instruction is not specific enough yet.
  • Name it for the outcome, so a colleague who did not write it knows when to reach for it.

Engagement moment: Name one review step you perform on every deck and never write down. That is your first Skill.

Outlook · Scenario 1

Inbox prioritization.

You define what matters. Copilot flags it as it arrives — and shows you the reasoning behind each flag.

What to expect: You define what to prioritize — Copilot flags what matters as it arrives and shows its reasoning.
FilesNone — this runs against your own mailbox
  1. Open the prioritization settings for Copilot in Outlook. Find where you state your own criteria.
  2. Enter your instructions. Use the example below as the shape, but replace the specifics with people and topics that are genuinely yours.
  3. Read the reasoning on a flagged message, not just the flag. The explanation is where you find out whether your criteria said what you meant.
  4. Correct the criteria, not the individual flags. If something was wrongly prioritized, the instruction is what needs editing.

Prioritization instructions

Treat anything from my manager or from [agency name] as high priority
Prioritize messages that include campaign launch dates or media buy approvals
Replace the bracket before you run this. Put in the agency, partner, or account team you actually work with. Prioritization has value precisely because it is yours — generic criteria produce generic flags, and a flag you do not trust is worse than no flag.

Reflection: Read the reasoning on one flagged message. Would you have accepted that explanation from a chief of staff? If not, the criteria need work — not the feature.

Outlook · Scenario 2

Govern your calendar.

State your working rules once, then ask for time instead of hunting for it.

What to expect: State your working rules once, then ask for time instead of hunting for it.
FilesNone — this runs against your own calendar
  1. Open your Copilot calendar preferences or instructions in Outlook.
  2. Add the standing rules below. Adjust the subject-line keywords to ones your organization actually uses.
  3. Then stop searching for time. Ask for it, using the second prompt.
  4. Check what the rules did after a day or two. Do that before adding more — standing rules act while you are not watching.

Calendar instructions

Automatically delete canceled meetings from my calendar.
Automatically accept meetings with "Customer Briefing" in the subject if my calendar is free.
Automatically follow meetings with "Office Hours" in the subject.
Automatically decline meetings that conflict with an existing event on my calendar.

Ask for time, don't hunt for it

Find me an hour of focus time every day next week, in the morning if possible
One of these four rules is stronger than the others. “Automatically decline meetings that conflict with an existing event” will decline on your behalf, without you seeing the invitation first — including the escalation that legitimately should have displaced what was already booked. Start with the rules you would comfortably defend to your team, and add that one once you have watched the others behave.

Reflection: Which of these four rules describes a decision you were already making by hand every week?

Outlook · Scenario 3

De-clutter the messy inbox.

Copilot-assisted analysis and guidance for organizing your inbox. Let AI automate the outcomes; you steer the goals.

What to expect: Copilot-assisted analysis and guidance for inbox organization — let AI automate the outcomes, we steer the goals.
FilesNone — this runs against your own mailbox
  1. Ask for a structure before you build one. Run the first prompt and read the proposal against how you actually work.
  2. Constrain the proposal. Note that the prompt states a preference — shallow, one sub-folder at most. Say what you want, or you will get someone else's filing system.
  3. Then automate one outcome. The second prompt creates a folder and a rule that routes into it.

Propose a folder structure

Look at my recent emails and suggest a folder structure that would organize it. I don't really like overly nested folder structures and would rather keep it at a folder or 1 sub-folder level max

Create a folder, then a rule that fills it

First, create a folder titled "Scheduled Prompt Runs". After the folder is created, create a rule that moves messages with "Your scheduled prompt is complete" in the Subject line into that newly created folder
The second prompt is sequenced on purpose. The folder must exist before a rule can target it, so the prompt says first and after explicitly rather than asking for both at once. It is a small thing that quietly determines whether the request succeeds.
This connects directly to scenario 4. “Your scheduled prompt is complete” is the subject line your morning triage brief will arrive under. You are building the filing before you build the thing being filed — so the assistant improves your inbox instead of adding to it.

Reflection: Copilot proposed the structure; you approved it. Which of those two is the part that actually needed a human?

Outlook · Scenario 4

Build your executive triage assistant.

A collaborative build — making Copilot work on your behalf, so a crisp update arrives on schedule, every morning.

What to expect: A collaborative exercise to show how we make Copilot work on our behalf — a crisp update delivered on schedule, each AM.
FilesNone — this reads across your own mail, chats, invitations, and tasks
  1. Run it manually first. Never schedule a prompt you have not read the output of. Run it once, now, and judge the result.
  2. Tune the priority list. Add the people, customers, and commitments specific to your role; remove the categories that produce noise for you.
  3. Then schedule it. Have it run each morning, so it is waiting before your first meeting rather than after it.
  4. Let scenario 3's rule file it. The completed run lands under “Your scheduled prompt is complete” and routes straight into the folder you already created.

Executive triage assistant — morning brief

Act as my executive morning triage assistant. Review my Outlook emails, Teams chats, meeting invitations, and Microsoft To Do/Planner tasks from yesterday afternoon through now.

Prioritize:
- Items received after business hours yesterday that may require my attention today.
- Messages, emails, meeting invites, or tasks that have not received a response from me.
- Requests, action items, approvals, customer commitments, blockers, escalations, and follow-ups assigned to me or implied as my responsibility.
- Any outstanding communications from my manager, leadership, customers, account teams, or frequent collaborators.
- Calendar events occurring today that require preparation, pre-reads, deliverables, or follow-up actions.
- Items marked important, urgent, time-sensitive, or with approaching deadlines.

End with a Top 5 Priorities for Today ranked by urgency and business impact.
Read what this prompt is actually doing. It sets a role, a defined source set, a time window, six ranked priority categories, and a fixed closing format. Every one of those is a decision you would otherwise make yourself at 7am, badly, before coffee. That is the whole argument for encoding it once.

Reflection: Compare the Top 5 to what you actually did that day. Where they differ, the interesting question is which list was right.

Section 11

Q&A

Open floor — and then the part that decides whether any of this survives contact with next week.

Today

Set your prioritization criteria and your calendar rules. Both take under five minutes and both start working immediately.

This week

Run the triage assistant manually for three days. Tune it. Only then schedule it.

This month

Find out who owns your Brand Kit. If the answer is nobody, that is the most valuable thing you leave this lab with.

Bring back the friction

The scenario that did not work on your content is more useful to discuss than the one that did. Bring it to office hours.

Keep the prompt guide

Every prompt from this lab is in one document. Adapt the brackets to your brands, agencies, and customers — that is where the value is.

A closing note on verification: every grounded scenario here produces output that looks sourced. Scenario 1 exists partly to make that point — the prompt fences the last slide to three open questions, and checking whether you got three is a thirty-second habit worth keeping.
Section 1 of 11

Microsoft 365 Copilot enablement lab — PowerPoint and Outlook. All lab data is fictional and created for Microsoft 365 Copilot demonstration purposes only; Zava and Project Northstar do not represent any real company, person, research programme, or financial result. Feature availability varies by licence, tenant configuration, and release channel — confirm what is enabled for you before relying on any scenario.