Two tools, one job split in half
Claude Design (covered in the Claude track) does prototypes, slides, and one-pagers inside a single canvas tool. Microsoft splits that job across two separate products: Copilot in PowerPoint, which builds and edits the deck itself, and Microsoft Designer, a standalone web app at designer.microsoft.com for generating images and graphics that you then place into the deck, or into Word, Outlook, Teams, or OneNote. Knowing this split matters practically: if you want a full presentation, start in PowerPoint; if you want a single polished image, logo-style graphic, or social post, open Designer directly rather than hunting for an equivalent feature buried inside PowerPoint. The two tools also have different licence footprints and different places they live, so treat this lesson as covering two separate stops rather than one feature with two names.
Building the deck in PowerPoint
There are three ways to start a deck, and one way to improve whatever Copilot drafts.
Building a deck from a prompt
PowerPoint gives you two on-ramps for a prompt-built deck. On the canvas, open the Copilot menu above a slide, choose "Create a presentation about...", and describe the deck you want. Copilot generates a list of proposed topics rather than jumping straight to slides, and you can add, remove, reorder, or regenerate any topic with the pencil button before committing. Only once that topic list looks right do you select Generate slides, which is a deliberately different flow from Claude Design's more continuous canvas, closer to reviewing an outline before the deck itself exists.
The second route runs through Copilot chat: select the Copilot button on the Home tab, choose "Create a presentation," type your description, and send it. This skips the topic-review step and drafts the full deck in one pass, which is faster but gives you less control before the first draft lands.
A real limitation worth planning around: prompt-based creation only supports one output language per deck, so if you need both an English and a Dutch version of the same presentation, you build and prompt each language separately rather than generating once and translating after.
Building a deck from a document
The more reliable starting point for anything with real content already written is "Create presentation from file," reached from the same Copilot button on the Home tab. Point it at a Word document, or a PDF if you have a Microsoft 365 Copilot (work) licence, and Copilot splits it into slides, applies layouts, writes speaker notes, and picks a theme automatically. Two things noticeably improve the result: using Word's built-in heading styles to structure the source document, since that is what Copilot actually reads to decide where one slide ends and the next begins, and keeping images already placed in the document, since those can carry straight over into the deck rather than needing to be re-added.
There are real constraints here too. You cannot add extra instructions in the same prompt when referencing a file, so a request like "build this from my report, but keep it under eight slides and skip the appendix" will not work as one step; you build from the file first, then edit the result. You also need access to and permission to use the file itself, Copilot works best with documents under 24 MB, and output should always be reviewed and edited rather than treated as final, the same "review before you ship" discipline that applies to every generative feature in this track.
Building from a theme or template
If your team already has a branded PowerPoint template, Copilot can draft new content directly into that existing theme rather than starting from a generic one. The real catch: this option replaces the current presentation it is applied to, so save a copy of your template first, build the draft into the copy, and keep the original clean for next time. This option, like full file-based creation, needs a Microsoft 365 Copilot work licence; Copilot Pro gives more limited options here.
Refining what Copilot drafted
A generated deck is a first draft, not a finished one, and refining it uses the same Copilot menu you used to create it. You can ask for a specific slide to be rewritten, request a different tone or length for the speaker notes, or ask Copilot to tighten a slide that has too much text on it. This mirrors the "describe, generate, refine" loop Claude Design uses, just split across more individual commands rather than one continuous conversation with the canvas.
Bringing in Microsoft Designer
Designer is where you go for a graphic Copilot in PowerPoint cannot generate well on its own: a custom hero image for a title slide, a restyled photo, a background removed from an uploaded picture, or a polished one-off graphic like an invitation or social post. It works from a text prompt the same way Copilot does, and it also offers templates and a blank canvas for building something from scratch rather than generating it outright.
Designer is currently a personal-account tool: it runs for Microsoft 365 Personal and Family subscribers, and enterprise accounts are not yet supported, which means a work account cannot reliably assume access to it the way it can assume access to Copilot in PowerPoint. Once you have made something in Designer, bringing it into a slide is a plain copy-and-place: Designer's graphics are built to drop into PowerPoint, Word, Outlook, Teams, and OneNote without any special export step.
Designer also supports editing an uploaded photo rather than only generating something from nothing: restyling it to match a different visual theme, or removing its background to drop a clean subject onto a slide. One line worth holding, though: an edited or generated image should never pass itself off as a real screenshot of a product interface. A restyled or background-removed photo of real people, products, or places is fine; a generated image claiming to show a specific product's actual screen is not, and neither tool should be used to fabricate that kind of fake authenticity.
Where it fits: PowerPoint, Designer, or neither
For most of what this track covers, the decision is simple. A full presentation with real content, even a rough first draft, is PowerPoint's job: start from a prompt if you are working from nothing, or from a file if the content already exists somewhere else. A single image, a branded graphic, or something meant to stand alone outside a deck is Designer's job. Neither tool replaces careful editing afterward: both are explicitly first-draft generators, and the review step is where the actual quality of a shared deck or graphic gets decided, not the generation step.
Feeding it your brand
Neither tool reads your brand guidelines automatically the way a dedicated design system would. For PowerPoint, the practical way to get on-brand output is the template route described above: build Copilot's draft into your existing branded theme rather than a generic one, so fonts, colors, and logo placement come from the template rather than from Copilot's own defaults. For Designer, there is no uploaded brand kit in the current version, since the legacy visual editor that supported brand kits and stock video was retired in October 2025 as part of the app's migration. In practice this means brand consistency for anything Designer-generated is a manual review step, not something either tool enforces for you: check a generated graphic against your actual brand colors and logo usage before it goes into a deck or anywhere external.
A worked example: a client-update deck
Say you need a five-slide update for a client, built from a short internal status report sitting in a Word document. Start with "Create presentation from file," point it at the report, and let Copilot propose the slide breakdown. If the report has clear headings (Progress, Risks, Next steps, Budget, Timeline), Copilot tends to turn each into its own slide reasonably well; if the document is one long block of prose with no heading structure, expect a rougher first pass, since headings are what Copilot actually uses to decide where slides should break.
Once the draft exists, refine slide by slide rather than regenerating the whole deck: ask Copilot to shorten the Risks slide if it reads as a wall of text, or to rewrite the speaker notes on the Next steps slide in a more conversational tone for a live readout. Then switch to Designer for the one visual the deck actually needs that neither the source document nor PowerPoint's own stock art provides well, commonly a title-slide image that signals the client's industry or project theme without using a literal screenshot of anything. Generate a few variations from the same prompt, since Designer typically returns more than one option per request, pick the one that fits, and drop it into the title slide. The whole sequence, document in, Copilot draft, manual refinement, one Designer image, mirrors the same "generate, then edit the parts that matter" workflow that runs through every generative tool in this track, just split across two separate apps instead of handled inside one canvas.
Licensing and cost, briefly
Access to the fuller feature set in both tools tracks the same licence lines already familiar from earlier lessons in this track. "Create presentation from file" with full file-type support, and the template-based build option, both require a Microsoft 365 Copilot licence (the paid work add-on); Copilot Pro gives a more limited version of file-based creation. On-canvas prompt-based creation was still rolling out to Microsoft 365 Insiders as of the most recent documentation, so availability can vary by tenant and update channel even among licensed users. Designer, separately, is currently scoped to Microsoft 365 Personal and Family subscriptions rather than work licences at all, so a Copilot work licence does not automatically grant Designer access, and the two tools' availability should be checked independently rather than assumed to move together.
Staying in control
The same review discipline that applies everywhere else in this track applies here, with one addition specific to visual content: a generated image can look finished and still be subtly wrong in a way text usually isn't, an odd hand, a garbled logo-like shape, a detail that doesn't match reality. Treat every Designer-generated image headed for a client-facing deck as a draft needing a visual once-over, not just a factual one. For PowerPoint drafts, the standard practice from earlier lessons still applies directly: review generated content before sending, since both tools state plainly that their output should be checked and edited rather than shipped as-is.
When to skip both and just write it yourself
Not every deck benefits from starting with a generated draft. A very short, highly structured deck, three slides with a single number on each, say, is often faster to build directly than to prompt, review, and then strip back down. Generation earns its keep on decks with real narrative structure: several sections, a mix of text and visuals, content that already exists somewhere else and just needs reshaping. The same judgment applies to Designer: a quick placeholder rectangle in PowerPoint's own shape tools is sometimes the right call when a generated image would take longer to get right than the slide is worth.
Try it
Pick a short document you already have, a one-page brief, a short report, or a set of notes, and run it through "Create presentation from file" in PowerPoint. Review the slide breakdown it chose, rewrite the one slide that reads worst, and then open Designer separately to generate one title-slide image that matches the deck's topic, to see how the two tools hand off to each other in practice.