Copilot in PowerPoint: Designer and brand templates

The most common complaint about Copilot in PowerPoint isn't the content — it's that the slides look like a stock-photo fever dream in colours nobody approved. That's not a bug in Copilot; it's Copilot doing exactly what you'd expect with no brand guidance. The fix is understanding three things that decide what a generated deck looks like: Designer, the template you start from, and the organisation asset library. Get those right and Copilot produces decks the comms team can live with.

The three layers

Designer is the older, non-Copilot feature (now surfaced as Design Ideas) that proposes layouts for a slide based on its content. It's a layout engine: it picks arrangements, cropping, icon placement, and — crucially — it respects the theme of the current file. Copilot uses Designer-style layout logic when it builds slides, so a deck's theme is the single biggest lever on how Copilot output looks.

The template you start from is what Copilot inherits. Open a blank presentation and ask Copilot to create a deck, and you'll get Microsoft's default theme plus whatever Designer decides. Open your corporate template first, then ask, and Copilot generates slides using your layouts, fonts, colours, and logo placement. This is the single most under-communicated fact about Copilot in PowerPoint: start from the template, then prompt.

The organisation asset library — a SharePoint library designated through the Add-SPOOrgAssetsLibrary PowerShell cmdlet — is how the corporate template shows up in the Organization tab of PowerPoint's start screen and how Copilot can offer it when a user asks to create a presentation. It also holds approved images that Copilot and Designer can pull from instead of stock photography. If you've never set one up, this is where to begin; the organization assets library docs cover the cmdlets and the CDN prerequisite.

Making the template Copilot-friendly

Copilot doesn't just use your template; it interrogates it. It chooses which slide layouts to use for a title slide, a section header, a two-column comparison, a bulleted list, an image-plus-text slide. A template built with a complete, well-named set of layouts in the slide master produces good output. A template that's really one blank layout with a logo pasted on every slide produces bad output, because Copilot has nothing to choose from.

Practical checklist for the template owner:

• Every layout in the master has the right placeholders (title, content, picture, footer) — Copilot places content into placeholders, not free-floating text boxes.
• Layouts are named sensibly ("Two content," "Picture with caption") rather than "Custom Layout 7."
• Theme fonts and colours are set at the theme level, not applied slide by slide, so generated slides inherit them.
• Include a handful of image-heavy layouts; Copilot likes to use images and will pull from stock if you give it no on-brand alternative.
• Keep one corporate template that people actually start from, published to the asset library. Ten variants means Copilot decks in ten styles.

Microsoft has been steadily improving how well Copilot honours "branded templates," and there's a dedicated support page on it, but the feature only works with a template that's structurally sound. Test with the actual template before rolling it out.

The "Create presentation from file" path

Users can point Copilot at a Word document or PDF (via a file reference in the prompt) and get a deck built from it. Two things determine quality: the structure of the source document — headings become sections, paragraphs become bullets — and again, the template open at the time. A well-structured Word doc plus the corporate template gives a first draft that's genuinely usable. A wall-of-text Word doc plus a blank file gives twelve slides of overflow bullets.

When the source is large, Copilot summarises aggressively. It's a starting point that saves the blank-page problem, not a finished deck, and someone who understands the material needs to check that the summary didn't lose the point.

Designer settings and admin controls

Designer (Design Ideas) itself can be turned off — per user via PowerPoint options, and at tenant scale via the Cloud Policy service (the Office cloud policy settings for "Turn off Design Ideas"). Some organisations disable it because it pulls stock images and icons from Microsoft's online content library, which brand teams dislike and which counts as connected experiences. Note the trade-off: disabling connected content also removes some of what makes Copilot's layouts look polished. The better path is usually to leave Designer on and give it an on-brand image library to prefer.

Copilot in PowerPoint honours the usual Microsoft 365 Copilot boundaries — it only reads files the user can access, and sensitivity labels carry across when a deck is created from a labelled document. There's no separate PowerPoint-specific data policy to configure.

What still goes wrong

• Image choice. Even with an asset library, Copilot sometimes picks a stock image over yours. Users need to know they can swap an image without breaking the layout.
• Layout drift on edit. Ask Copilot to add a slide to a deck mid-way and it may pick a layout that doesn't match its neighbours. A quick Reset Slide fixes it.
• Colour "improvements." Occasionally Copilot applies a Designer variant that shifts accent colours. If brand fidelity is non-negotiable, lock the theme colours and tell users to reject variants.
• Not every layout gets used. Copilot has favourites; some of your carefully built layouts will never appear. That's fine.

The one-line rollout message

"Open the company template first. Then ask Copilot." Put that in the adoption materials, put the template in the organisation asset library, and most of the "Copilot makes ugly slides" tickets go away. The remaining ones are about content, which is a different guide.