Copilot in PowerPoint: speaker notes and translation

Building slides gets the headlines, but the two Copilot in PowerPoint features people actually end up using every week are quieter: generating speaker notes for a deck someone else built, and translating a presentation for an audience in another language. Both are shipped, both work, and both have failure modes that are worth knowing before you present in front of a customer.

Speaker notes

Ask Copilot to "add speaker notes to this presentation" (or per slide, "write speaker notes for this slide") and it drafts talking points into the Notes pane, slide by slide. It reads the slide content, title, and — when there's enough context — the surrounding slides, and produces a short spoken-word script.

What it does well:

• Expands terse bullets into full sentences you could actually say. For a deck that's six words per slide, this is the difference between reading the slide aloud and presenting it.
• Bridges between slides. Copilot tends to add "having looked at X, let's turn to Y" transitions, which are exactly the connective tissue people forget when rehearsing.
• Rescues inherited decks. The most common real-world use: someone hands you their deck the night before and you need to know what each slide is for. Copilot's notes are a plausible reconstruction.

What it does badly:

• It invents specifics. If a slide says "Q3 results" with a chart, the notes may assert a narrative about the numbers that isn't what the chart shows. Any slide with data needs the notes checked against the data.
• It's generic on dense slides. A slide with a complex diagram gets notes that describe the diagram's shape, not its meaning.
• Tone is corporate-neutral. Fine for internal reviews; flat for a keynote. Ask for "conversational" or "for a technical audience" and you'll get closer, but you still need to make it yours.

Practical tip: generate notes before rehearsing, then rewrite the ones for the three slides that matter. Don't try to make Copilot write the whole talk.

The narrative angle

Copilot can also produce a summary of a deck ("summarise this presentation"), which is often the faster route to understanding an inherited file than notes are, and it can help reorganise — "add a section header before slide 8," "which slides are redundant?" The second question is more useful than it sounds: Copilot is decent at spotting two slides that make the same point. What it can't do is understand your audience's politics, so "cut this to ten slides" produces a shorter deck, not a better one.

Translating a presentation

The translate feature ("translate this presentation to German") produces a new copy of the deck in the target language — it doesn't overwrite the original, which is the right design. Slide text, titles, notes, and most text in shapes are translated; the layouts, images, and theme are preserved.

This replaces a workflow that used to involve copying every text box into a translation tool or buying a plug-in, and for internal decks and first drafts it's a straightforward win. The honest caveats:

Length changes break layouts. German runs roughly a third longer than English; Finnish longer still; Chinese often much shorter. A slide that was tight in English overflows its placeholder in German. Copilot doesn't reflow the design, so expect a pass through every slide fixing text that spills. Templates with generous placeholder sizes cope better.

Text in images isn't translated. Screenshots, diagrams exported as pictures, and charts pasted as images stay in the source language. Native PowerPoint charts translate their titles and labels; embedded pictures don't.

Terminology drift. Product names, internal jargon, and legal phrases get translated when they shouldn't be, or translated inconsistently across slides. For a customer-facing deck, a native-speaker review is not optional — it's a five-minute job that catches the "Microsoft Teams" that became "Microsoft Equipes."

SmartArt and grouped objects are the usual casualties — some text inside them may be missed or translated but not resized. Check them specifically.

Compared to the older Review → Translate feature (which handles one selection at a time), the Copilot version is whole-deck and far faster. Compared to a professional translation, it's a draft.

Sensitivity labels and generated copies

When Copilot creates the translated copy, it's a new file and it inherits the sensitivity label of the source, as with any Copilot-generated document in Microsoft 365. What it doesn't inherit is the file's location: the copy lands in the user's OneDrive or wherever they save it, not automatically alongside the original in the project's SharePoint library. Users translating a Confidential deck should be told to save the copy in the same governed location — otherwise you end up with governed originals and ungoverned translations.

Neither feature sends content anywhere unusual; both run through the standard Microsoft 365 Copilot service with the same data boundaries as the rest of the product.

Availability

Speaker-notes generation and deck summarisation are on Windows, Mac, and the web. Whole-deck translation rolled out to Windows and the web first; if a platform is missing it, the Review → Translate fallback still exists. Everything here requires a Microsoft 365 Copilot licence; the free Copilot Chat surface doesn't operate inside PowerPoint.

What to tell users

Two lines cover it: speaker notes are a draft, check any slide with numbers; translations are a draft, have a native speaker skim it and fix the overflow. With that expectation set, both features save real hours every week — which is more than can be said for a lot of generative-AI features.