Create a PowerPoint from One Work File, and Check It Before You Present

The Problem We Are Solving

If you have ever given Copilot a carefully written report and received a deck that looks finished but quietly misses the point, this is the awkward bit: generating slides is easy; trusting them is not.

Here, grounded simply means Copilot starts from a work file you choose rather than from a broad topic prompt. Your job is to control the source, shape the outline and check every important claim before you present it.

This is a current practical companion to Richard Harbridge's original post and session, Unlocking AI and mastering Microsoft Copilot. The original water-quality-report example is still useful, but the dependable workflow is narrower than an "agent pipeline": one approved file, one draft deck and one deliberate human review.

The Short Answer

For one report-to-deck job, you do not need to build a Copilot Studio agent.

Use PowerPoint's presentation-creation experience with a referenced file if that option is available in your tenant. Review and refine the outline before generating slides. Then check the finished deck against the source before sharing it.

Microsoft's current documentation reflects a staged product rollout. It describes creating a presentation from a referenced file, but the latest Agent Mode instructions also say that file references in Agent Mode are still coming soon. Menus can therefore differ by licence, tenant configuration, update channel and rollout stage.

The practical rule is simple:

Before You Start

Use this five-minute check before a live demo:

• Sign in with the work or school account that will run the demonstration.
• Confirm that Copilot is visible in PowerPoint. Microsoft says the experience varies by licence and tenant configuration.
• Confirm that the presenter can open the source file with the same account.
• If the source is a Word document, use Word heading styles to make its structure clear. Microsoft says this helps Copilot understand how to divide the content into slides.
• If the organisation has a PowerPoint template, start with it. A useful template contains real layouts and placeholders, not just brand colours.
• For Word sources, Microsoft currently says Copilot works best with documents smaller than 24 MB. Treat that as guidance, not a guaranteed failure threshold.
• Check that the source is appropriate for the presentation's intended audience. Access to the report does not remove your responsibility to review what appears in the new deck.

Create the First Draft

1. Prepare one source file

For the cleanest test, use one approved report with:

• a descriptive title
• clear Heading 1 and Heading 2 sections
• labelled tables and charts
• a short conclusion or recommendation section
• no obsolete appendix material that you do not want promoted into slides

One file makes it easier to see whether the generated deck reflects the source. It also makes errors easier to trace.

2. Start from the right PowerPoint file

Open a new presentation or your organisation's approved template before invoking Copilot.

If the template is little more than a blank theme, expect more manual layout work. Microsoft says Copilot gets stronger brand guidance from representative sample slides, layouts, placeholders and theme settings.

3. Choose the file-reference path when it is available

Open Copilot in PowerPoint and look for Reference file or Create a presentation from a file.

Select the report through the file picker. You must have access to the file you reference.

Microsoft currently notes that file-based creation does not accept additional context in the same prompt. Let Copilot produce or propose the initial outline, then refine that outline in the conversation.

If the file-reference option is not present, stop and label the limitation honestly. A topic-based deck can still be useful, but it is not proof that PowerPoint created slides from the chosen report.

4. Refine the outline before creating slides

Do not accept the first outline simply because it looks tidy. Use a follow-up like this:

Then check:

• Does the sequence match the decision the audience needs to make?
• Are the report's main findings present?
• Have warnings, uncertainty or inconvenient findings disappeared?
• Has Copilot promoted a minor detail into the headline?
• Is anything in the outline absent from the source?

Only ask Copilot to create the slides when the outline passes those checks.

5. Generate, then edit

Once the slides exist, use Copilot for bounded edits such as reorganising sections, adding a missing topic or shortening text. Keep the source report open beside the deck.

Copilot has produced a draft, not an approved presentation.

What Good Output Looks Like

A useful first draft should pass these tests:

Final Review Checklist

Before anyone presents or sends the deck:

• Compare every number, date and named claim with the source file.
• Restore any caveat or uncertainty that disappeared during summarisation.
• Remove unsupported claims, even when they sound plausible.
• Check that titles do not overstate what the report proves.
• Review charts, units, legends and time periods.
• Replace generic or unsuitable images.
• Check speaker notes for any AI-generated image source information.
• Confirm the template and layouts are genuinely on-brand.
• Confirm the sensitivity label and sharing settings are appropriate.
• Ask someone who understands the report to approve the final version.

If the Demo Does Not Behave as Expected

Copilot is missing: Ask the Microsoft 365 administrator to check the assigned licence, organisational settings, connected-experience privacy settings and Office updates.

The report is missing from the picker: Confirm the presenter can open it with the same work account and has permission to use it.

The file-reference option is missing: Do not improvise an "agent workflow" and claim it is equivalent. Show a clearly labelled topic-based presentation demonstration, or postpone the grounded demo until the feature is available in that tenant.

The slides are generic: Improve the Word document's heading structure, begin with a stronger organisation template and refine the outline before generating slides.

Important material is missing: Add the missing topic through a bounded follow-up, then verify the new slide directly against the report.

Do You Need an Agent?

Not for this one-file presentation workflow.

A SharePoint or Copilot Studio agent can be useful when people need repeated question-and-answer access to a larger, controlled knowledge set. That is a separate job. Building an agent does not by itself make PowerPoint's file-reference control appear, and the original draft did not demonstrate an end-to-end connection between its custom agent and the generated deck.

Start with direct file grounding. Consider an agent only when the ongoing knowledge-access problem justifies one.

Evidence Notes

Microsoft's documentation supports these parts of the workflow:

• PowerPoint can create a draft presentation from a prompt or a referenced file when the relevant feature is available.
• Copilot can produce an outline that the user refines before slide generation.
• Word heading styles help Copilot understand source structure.
• Organisation templates and representative layouts can improve brand consistency.
• The user must have access to a referenced file.
• Microsoft explicitly says AI-generated presentation content should be reviewed and edited by a person.

The documentation does not prove that every tenant has the same controls today, that a generated deck is factually complete, that it is safe to share, or that it will meet your organisation's brand and governance standards without review.

Use Microsoft documentation to trust the product mechanics. Use the checklist above to decide whether the actual deck is ready.