AI Tools Academy
Microsoft Copilot 0/20

Phase 2 · Microsoft Copilot · Level 2 · Practitioner

Copilot in PowerPoint: build a deck from a document

Walkthrough · 11 minLast checked against the live product: 14 July 2026

30-second recall from earlier lessons
An AI assistant gives you a confident, well-written answer with a specific statistic and a link to a source. You need the figure for a board paper. What's the wisest next step?
A colleague pastes a signed client contract into their free, personal ChatGPT account to get a quick summary. What's the core problem?

By the end, you'll be able to…

  • Generate a first-draft deck from an existing Word or PDF document with Copilot
  • Refine the draft (add, remove, reorganise and reword slides) in plain English
  • Review a generated deck critically before it goes anywhere near an audience

Why it matters

Building slides from scratch is slow, and it's the task Copilot in PowerPoint speeds up most: hand it a document and it returns a structured draft deck with headings, bullets, images and speaker notes. But a generated deck is a starting point, not a finished one. This lesson shows you how to produce the draft and, just as much, how to refine and sanity-check it so what you present is actually yours.

What Copilot in PowerPoint is for

Copilot in PowerPoint turns a document into a draft deck and then helps you shape it. Like the other in-app Copilots, it lives on the ribbon and generally needs a Microsoft 365 Copilot licence. No Copilot button usually means no licence rather than a fault. Its headline trick is Create presentation from file: point it at a document and it builds slides (a title, sensible sections, bulleted content, relevant images and even speaker notes) in one go. It can also generate from a plain prompt, add individual slides, reorganise, and rewrite slide text.

The mental model to hold: Copilot is fast at the scaffolding (structure, layout, first-pass wording) and weak at judgement about what your specific audience needs to hear. So you let it do the scaffolding and you supply the judgement. A deck that goes out unreviewed is the classic misuse.

A quick reassurance on access: if you don't see Copilot in PowerPoint, it's licensing, not you. The free Copilot Chat route from Level 1 still works, so you can keep building the skill even without the in-app buttons.

The worked example: a deck from the Fernway brief

Maya has Priya's customer-feedback project brief in Word and needs a short deck to present the plan at the ops sync. Rather than start from an empty slide, she generates from the file.

To do this: open PowerPoint to a blank presentation, select Copilot on the ribbon, and type "Create presentation from file", then pick the document. One thing to know up front: creating a presentation from a file generally works from Word documents or PDFs, not spreadsheets, so a Word brief is exactly the right input.

Generate a deck from a documentCopilot
Create a presentation from /fernway-project-brief for a 10-minute update to the operations team. Around 8 slides: the problem, the objective, what's changing, the deliverables, the timeline, and how we'll measure success. Keep the tone plain and practical.

Why this works: It names the source file, the audience and the length, so Copilot builds a focused deck rather than a sprawling one. Telling it who's watching and how many slides keeps the draft close to what you actually need to present.

In a minute or so you have a full draft: a title slide, a slide per section, bullets pulled from the brief, some stock imagery, and speaker notes underneath. That's twenty minutes of structuring done. But it is a draft: the bullets may over-compress a point, the images may be generic, and the emphasis may not match what your audience cares about. Refining is the real work, and it's where Copilot keeps helping.

Refining the draft

You don't restart to fix a generated deck. You steer it, slide by slide, in plain language, exactly as you'd iterate on any AI draft.

Reshape the deckCopilot
Add a slide near the start covering the risk that the process gets dropped, and how we'll keep it lightweight. Remove the generic stock photo on the timeline slide. And the objective slide has too much text, so cut it to three short bullets.

Why this works: Concrete, specific instructions (add a named slide, cut clutter, tighten a busy slide to a number of bullets) steer the existing deck rather than regenerating it, so you keep what already works. Vague 'improve this' loses the good parts.

Other refinements worth knowing: ask Copilot to rewrite a single slide's text to a punchier tone, to add speaker notes to a slide that's missing them, to reorganise the running order, or to summarise the deck back to you so you can sense-check the flow. If your organisation has a template or brand, Copilot can also help keep the deck on-brand rather than using its default look.

Tighten one slide and add a talk trackCopilot
On the 'measuring success' slide, cut the bullets to the three key measures only, and write speaker notes I can talk to for about 45 seconds explaining why each one matters.

Why this works: It scopes the request to a single slide and asks for both tighter bullets and speaker notes, so the slide is presentable and you know what to say over it. Asking for notes separately keeps the slide itself clean.

Sanity-check the flowCopilot
Read this deck as an audience member seeing it cold. Does the story flow logically? Point out any slide that's confusing, out of order, or missing something the audience would need, but don't change the slides.

Why this works: Asking Copilot to critique the narrative arc rather than rewrite it surfaces gaps and weak transitions you can then fix yourself, keeping you the author of the story.

The review that matters

Before a generated deck leaves your hands, do three checks. Facts: every number, date and name on the slides should trace back to the source document. Copilot can round, merge or drift. On the Fernway deck, confirm the two-working-day acknowledgement target and the week-by-week timeline survived intact. Emphasis: does the deck stress what your audience cares about, or what happened to be prominent in the source? Ownership: does it sound like you, or like a generic AI deck? A few minutes here is the difference between "Copilot helped me build this" and "Copilot embarrassed me in a meeting".

Try it now

Common mistakes

  • Presenting the first draft. A generated deck is scaffolding. The value is in the refining and checking; skipping straight to "present" is where people get caught out.
  • Feeding it the wrong file type. Create-from-file generally wants a Word document or PDF, not a spreadsheet. If you want a deck from Excel data, summarise the findings into a document first.
  • Letting Copilot pick the emphasis. It stresses what's prominent in the source, which may not be what your audience needs. You decide the emphasis; Copilot arranges it.
  • Keeping the generic images. Default AI imagery reads as exactly that. Swap in real or on-brand visuals for anything that matters.
  • Over-trusting the slide text. Bullets are compressed by definition, and compression is where Copilot can distort or invent a detail. A number that reads cleanly on a slide is still worth tracing back to the source. A confident bullet is not a checked fact; verify anything load-bearing before it's on screen in front of people.

Keeping current

The generation and refinement features move quickly, and "create from file" limits (which file types, how many slides) change. The durable habit is unchanged: generate the scaffold, refine slide by slide, and fact-check before presenting. On licensing: during 2026 Microsoft moved the in-app Copilot features inside Word, Excel, PowerPoint and OneNote behind a full Microsoft 365 Copilot licence; the free Copilot Chat continues, and Copilot in Outlook remains available. For current steps see Microsoft's Create a new presentation with Copilot in PowerPoint and Frequently asked questions about Copilot in PowerPoint. Accurate as of 14 July 2026.