How to Use Copilot in PowerPoint: A Complete Guide

To use Copilot in PowerPoint, open a presentation, select Copilot, and describe the slide or content you want. Give it a specific audience, purpose, key points, and preferred tone, then review the result and refine it with follow-up instructions. Copilot can add a slide from a natural-language description, while its Rewrite tools can adjust existing text. The useful mindset is simple: treat Copilot as a drafting partner, not the final editor.

This guide is for beginners, busy professionals, students, and teams that want a repeatable process for creating and improving presentations without giving up editorial control.

Before you start

First, confirm that Copilot is available in your version of PowerPoint. If it does not appear, Microsoft says it may not be included in your Microsoft 365 subscription or may be unavailable because of your organization’s settings. Copilot also needs an internet connection and works with .ppt and .pptx files. Check Microsoft’s Copilot in PowerPoint FAQ before troubleshooting the presentation itself.

Prepare four things before prompting:

• The presentation’s goal: inform, persuade, teach, report, or propose.
• The audience: executives, customers, classmates, new employees, or another defined group.
• The essential material: facts, conclusions, examples, and required terminology.
• The desired output: one slide, a draft deck, a rewrite, or a clearer visual structure.

For example, “Create a slide about quarterly results” gives little direction. “Create an executive-summary slide for department leaders, using three takeaways and a neutral tone” defines both the reader and the job.

How to add a slide with Copilot

Microsoft’s documented workflow is straightforward: in PowerPoint, select the Copilot icon, then type a description of the slide in the prompt box. Microsoft also notes that more detail generally produces better results.

Use this sequence:

1. Open the presentation in which you want the new slide.
2. Select the Copilot icon.
3. Describe the slide’s purpose, audience, content, and tone.
4. Submit the prompt and inspect the draft.
5. Correct the content, wording, order, and visual hierarchy before presenting it.

A practical prompt formula is:

Create a [type of slide] for [audience] about [topic]. Include [key points]. Use a [tone] tone and organize the content as [structure].

Examples:

• “Create an opening slide for new employees that introduces our onboarding plan and previews three stages: setup, training, and first-month goals.”
• “Create a comparison slide for project sponsors showing Option A and Option B across cost, implementation effort, and expected impact. Keep the language concise and neutral.”
• “Create a conclusion slide for a classroom presentation on renewable energy. Summarize three takeaways and end with one discussion question.”

These are adaptable instructions rather than magic phrases. Replace every bracketed idea with details from your real assignment.

Build better prompts in two passes

Trying to include every requirement in the first prompt can make the instruction hard to inspect. A two-pass method is often easier.

In the first pass, establish the content: “Create a recommendation slide for a leadership meeting. Compare the two proposed launch dates and include the main dependency for each.” In the second pass, shape the delivery: “Shorten each option to two bullets, keep the language neutral, and end with the decision the group needs to make.”

This separates questions of substance from questions of presentation. If the first draft misses an essential idea, fix the content before spending time on tone or formatting. If the ideas are right but the slide is crowded, keep the substance and change only the structure.

Useful follow-up prompts describe the change, not merely the feeling:

• Instead of “Make it better,” try “Replace the introduction with one sentence that states the recommendation.”
• Instead of “This is too long,” try “Keep the three findings, but limit each explanation to one short bullet.”
• Instead of “Make it more visual,” try “Organize these four milestones as a chronological sequence with a short label for each stage.”
• Instead of “Try again,” explain which content must stay and which part must change.

Keep each revision narrow enough to evaluate. When you change audience, tone, structure, and subject at the same time, it becomes difficult to tell why the new version improved or declined.

Create a presentation that stays visually consistent

Copilot can assist with creating presentations and editing slides, but a consistent starting structure matters. If your organization uses a standard PowerPoint template, Microsoft recommends opening that file first. Copilot can then use its existing layouts while retaining the presentation’s theme and design. See Microsoft’s guidance on creating a presentation with Copilot.

This makes the workflow especially useful for recurring formats such as project updates, training decks, proposals, lesson summaries, and internal briefings. Start with the approved template, ask for content that fits a specific slide purpose, and check that the result uses the right layout.

Do not ask for an entire polished presentation in one vague sentence. Break the work into stages: outline the story, draft the main slides, add supporting material, and then refine the wording. That makes weak assumptions easier to spot.

Edit and refine Copilot’s output

The first draft is a starting point. Check every slide for factual accuracy, relevance, repetition, reading order, and fit with the audience. Remove details that do not advance the presentation’s goal.

For selected slide text, Copilot’s Rewrite feature can rephrase content based on length, tone, and style. Its documented options include Custom prompt, Auto-rewrite, Condense, Make professional, and Visualize as a list. Microsoft explains these choices in its PowerPoint Rewrite guide.

Choose the refinement that matches the problem:

If a result is irrelevant, do not keep regenerating the same vague request. Identify the specific failure and correct it: “Keep the slide focused on customer onboarding, remove pricing, and use only the three milestones I provided.” A targeted correction gives Copilot a clearer boundary.

Review every slide with the same checklist

A repeatable review is more reliable than judging whether a slide simply “looks good.” Work from meaning to appearance:

1. Purpose: Can you state in one sentence what this slide should accomplish?
2. Accuracy: Are names, dates, figures, labels, and conclusions correct?
3. Relevance: Does every element help the audience understand the main point?
4. Hierarchy: Is the most important message visible before supporting detail?
5. Clarity: Can unfamiliar terms be replaced or briefly explained?
6. Consistency: Does the slide match the deck’s terminology, tone, and visual system?
7. Delivery: Can a speaker present it without reading every word aloud?

For example, a project-status slide may contain correct information yet still fail if the decision required from leaders is buried at the bottom. Move the decision to the title or opening line, keep only the evidence that supports it, and shift background detail to speaker notes or a supporting slide.

Read the full deck after reviewing individual slides. A sequence can repeat the same idea even when each slide works on its own. Check whether the presentation moves logically from context to evidence, implications, and action.

Best practices for individuals and teams

Strong Copilot workflows depend more on preparation and review than on elaborate prompt wording.

• Give one slide one clear job. A slide that tries to explain, compare, recommend, and conclude at once will usually feel crowded.
• Name the audience. A technical team and a prospective customer need different context and vocabulary.
• Supply the required points. Do not assume the tool knows the facts or priorities unique to your project.
• Ask for structure. Specify a timeline, comparison, three takeaways, or another useful format.
• Review claims and numbers. Compare the draft with the materials your team trusts.
• Edit for presentation delivery. Slides should support the speaker rather than reproduce a full document.
• Use an approved template for shared work. This gives collaborators a common visual starting point.
• Assign a final owner. One person should verify accuracy, tone, accessibility, and consistency before distribution.

For team workflows, agree on a small prompt brief before drafting: audience, goal, source material, terminology, and reviewer. Save successful prompt patterns with the project template so coworkers can reuse the structure without copying outdated content.

Use a clear team handoff

AI-assisted drafting should not blur responsibility. At handoff, tell the reviewer what Copilot helped draft, which source material was used, and which points still need subject-matter confirmation. This lets the reviewer focus on risk rather than guessing how the slide was assembled.

A simple handoff note can include:

• The deck’s audience and intended decision.
• The approved source documents or data used for review.
• Slides that contain time-sensitive or sensitive information.
• Terms, claims, or visuals that need specialist approval.
• The name of the person responsible for final sign-off.

When several people edit the same deck, agree on terminology before generating slides. If one person prompts for “customers,” another for “users,” and a third for “accounts,” the presentation may imply distinctions that nobody intended. A short shared glossary keeps both manual and AI-assisted edits aligned.

Check readability and accessibility

Before sharing, inspect the presentation as an audience member would encounter it. Use descriptive slide titles, keep reading order logical, avoid communicating meaning through color alone, and make sure text remains legible at presentation distance. Add meaningful descriptions for informative visuals according to your organization’s accessibility process, and avoid adding decorative detail that competes with the message.

Do not assume generated structure is automatically accessible. A list may be clearer than a paragraph, but only if its order makes sense. A chart may compress information, but only if labels and the takeaway are understandable. Review contrast, font size, object order, and visual descriptions in PowerPoint with the same care you give the wording.

For a remote meeting, test the deck in the actual viewing conditions. Content that looks comfortable on a large monitor may be difficult to read in a shared window. For an in-person presentation, preview the slides at a distance and shorten anything that depends on close reading.

Common mistakes to avoid

The most common mistake is accepting generated content without judgment. A polished sentence can still be irrelevant, unsupported, or wrong for the audience. Verify important details and rewrite anything you could not confidently explain aloud.

Other pitfalls include asking for “a professional deck” without defining professional, mixing several audiences in one prompt, packing too much text onto each slide, and changing the visual direction midway through a shared deck. Clear constraints prevent more rework than repeated regeneration.

Also avoid treating visual consistency as proof of accuracy. Theme, layout, and fluent language improve readability, but they do not validate the underlying message.

Frequently asked questions

Put the workflow into practice

Start with one low-risk slide. Write a prompt that names the audience, goal, key points, tone, and structure. Generate the draft, verify its content, and make one focused revision. Once that process feels reliable, apply it to a complete deck using your approved template and review checklist.

If you want to build broader confidence with guided AI learning, explore Coursiv AI lessons. The next practical step is still yours: choose a real presentation, draft one specific prompt, and improve the result with deliberate editing.