---
id: copilot-copilot-pages
lang: en
track: copilot
title: "What are Copilot Pages?"
seoTitle: "Copilot Pages: keep and share answers"
description: "Turn a Copilot chat answer into a Page you can keep, edit and co-edit live with colleagues, and learn when a Page is the right home for Copilot output."
part: getting-started
partTitle: "Getting started with Copilot"
partOrder: 2
order: 4
level: Beginner
durationMinutes: 3
outcome: "Use Pages to turn Copilot output into something you and others can keep working on."
summary: "A Page turns a Copilot chat answer into a document you can keep, edit, and, unlike a normal chat reply, co-edit live with colleagues."
draft: false
updated: "2026-10-14"
furtherReading:
  - title: "How Microsoft 365 Copilot Pages works"
    url: "https://support.microsoft.com/en-us/topic/how-microsoft-365-copilot-pages-works-d155bd99-c3cc-4ef8-8da4-c0a92bfce29b"
    note: "How Pages are stored, shared and kept."
  - title: "Get started with Copilot Pages"
    url: "https://support.microsoft.com/en-us/microsoft-365-copilot/get-started-with-microsoft-365-copilot-pages"
    note: "Step by step: create your first Page from a Copilot answer."
  - title: "Frequently asked questions about Microsoft 365 Copilot Pages"
    url: "https://support.microsoft.com/en-us/topic/frequently-asked-questions-about-microsoft-365-copilot-pages-aaffb2d7-cbd7-4b57-a69a-69a29bd03685"
    note: "Microsoft's answers to common questions about Pages."
  - title: "View or restore an earlier version of your Microsoft 365 Copilot Page"
    url: "https://support.microsoft.com/en-us/Microsoft-365-Copilot/view-or-restore-an-earlier-version-of-your-microsoft-365-copilot-page"
    note: "How to use a Page's version history."
keywords:
  - Copilot Pages
  - Microsoft 365 Copilot Pages
  - co-edit Copilot output
  - save a Copilot answer
  - Copilot Page version history
  - collaborate with Copilot
quiz:
  intro: "Four quick questions. Ace them all and the next lesson unlocks."
  passScore: 4
  questions:
    - q: "What's the core difference between a normal Copilot Chat reply and a Page?"
      options:
        - "A Page is just a longer chat reply"
        - "A Page is a persistent, editable document; a chat reply scrolls away as the conversation continues"
        - "A Page can be read but not edited"
      answer: 1
      explain: "A Page is a persistent, editable document; a chat reply scrolls away as the conversation continues."
    - q: "What can multiple people do on the same Copilot Page at once?"
      options:
        - "Only view it, while one person edits"
        - "Each work on their own private copy"
        - "Nothing, because a Page can't be shared"
        - "Co-edit it live, the same way as a shared Word or OneNote document"
      answer: 3
      explain: "Co-edit it live, the same way as a shared Word or OneNote document, and keep chatting with Copilot from inside it."
    - q: "Which of these is worth sending to a Page rather than leaving in chat?"
      options:
        - "A proposal you build up across several chats"
        - "A one-off answer you only needed right now"
        - "Nothing, since chat answers can't be added to a Page"
      answer: 0
      explain: "Any answer you'll keep, edit further, or share with others: a draft report, meeting brief, or a proposal built up across several chats. A one-off answer can stay in the chat."
    - q: "If an edit to a Page goes wrong, what's the best way to get the earlier version back?"
      options:
        - "Rebuild it from memory"
        - "Ask Copilot to start a new Page from scratch"
        - "Open the Page's version history and restore an earlier version"
        - "Nothing, because edits on a Page are permanent"
      answer: 2
      explain: "Open the Page's version history and restore an earlier version, instead of rebuilding it from memory."
  pass:
    badge: "Perfect score"
    title: "You can make Copilot work stick."
    body: "Full marks. You know when to send an answer to a Page, how to co-edit it, and how to restore an earlier version. Next up: giving Copilot context, so its answers fit your role and your work."
  retry: "Check the marked answers and give it another go. You've got this."
---

> **Level:** Beginner · **Reading time:** ~3 min
>
> **What you'll be able to do:** use Pages to turn Copilot output into something you and others can keep working on.

## The problem Pages solves

A normal Copilot Chat reply is just that: a reply. Scroll up enough and it's gone from view; ask a follow-up and the original answer doesn't move with you. A Page takes a chat response out of that scrolling conversation and puts it on its own persistent canvas: a real, editable document that stays put, that you can shape further, and that doesn't get buried under the next question you ask.

## What you can build in a Page

Anything that started as a chat answer but deserves to become a document: a draft report, a meeting brief, a project plan, a set of collected notes pulled together from several chat responses, a first pass at a policy or one-pager. It's also where a piece of work that grows over several sessions belongs: a proposal you add to across a few days of chats with Copilot, rather than one single answer, is exactly the kind of thing a Page is built to hold. If you'd otherwise copy-paste a Copilot answer into Word to keep working on it, that's exactly the moment to send it to a Page instead.

A concrete case: say a colleague asks Copilot in Teams to draft talking points for Thursday's client call. The moment more than one person needs to read or edit that draft, it's a candidate for a Page, since anyone in the meeting can add their own point directly onto the same document instead of emailing edits back and forth.

## Multiplayer: the part Claude doesn't do

This is where Pages genuinely differ from Claude's Artifacts. A Page isn't just yours to keep. You can share it with colleagues and co-edit it together in real time, the same way you'd co-edit a Word or OneNote document. Everyone sees the same Page, can add to it, and can keep chatting with Copilot from inside it to extend or revise the content. If a piece of work is genuinely a team effort, like building a proposal together or drafting shared meeting notes, a Page is built for that in a way a private chat reply isn't.

<figure class="lesson-svg" aria-labelledby="copilot-pages-t">
<svg viewBox="0 0 640 266" width="100%" height="auto" role="img" aria-labelledby="copilot-pages-t copilot-pages-d" xmlns="http://www.w3.org/2000/svg" font-family="Inter, system-ui, sans-serif"><title id="copilot-pages-t">A chat answer vs. a Page</title><desc id="copilot-pages-d">Two panels. Left, a chat answer: lives in the conversation, scrolls away as you keep chatting, good for quick answers. Right, a Page: a persistent, editable canvas with Edit, Share and Live controls -- keep it, edit it, co-edit it live.</desc><text x="0" y="26" fill="var(--ink,#1F2328)" text-anchor="start" style="font-size:20px;font-weight:800;">A chat answer vs. a Page</text><rect x="0" y="40" width="295.0" height="200" rx="12" ry="12" fill="#fff" stroke="var(--line,#E7E9EC)" stroke-width="1.5"></rect><text x="20" y="68" fill="var(--med-gray,#5B6169)" text-anchor="start" style="font-size:15px;font-weight:800;">A chat answer</text><rect x="20" y="82" width="255.0" height="60" rx="10" ry="10" fill="#F5F6F7"></rect><rect x="34" y="96" width="147.89999999999998" height="7" rx="3.5" ry="3.5" fill="var(--line,#E7E9EC)"></rect><rect x="34" y="112" width="183.6" height="7" rx="3.5" ry="3.5" fill="var(--line,#E7E9EC)"></rect><rect x="34" y="128" width="107.1" height="7" rx="3.5" ry="3.5" fill="var(--line,#E7E9EC)"></rect><text x="20" y="168" fill="var(--med-gray,#5B6169)" text-anchor="start" style="font-size:12.5px;font-weight:normal;">Lives in the conversation.</text><text x="20" y="188" fill="var(--med-gray,#5B6169)" text-anchor="start" style="font-size:12.5px;font-weight:700;">Scrolls away as you keep chatting.</text><rect x="345.0" y="40" width="295.0" height="200" rx="12" ry="12" fill="var(--part-tint,#FDF4E8)" stroke="var(--part,#EA9A3E)" stroke-width="2"></rect><text x="365.0" y="68" fill="var(--part-ink,#B4770F)" text-anchor="start" style="font-size:15px;font-weight:800;">A Page</text><rect x="365.0" y="82" width="255.0" height="60" rx="10" ry="10" fill="#fff" stroke="var(--part,#EA9A3E)" stroke-width="1.5"></rect><rect x="377.0" y="101.0" width="37.6" height="22" rx="11" ry="11" fill="none" stroke="var(--part,#EA9A3E)" stroke-width="1.3"></rect><text x="395.8" y="116.0" fill="var(--part-ink,#B4770F)" text-anchor="middle" style="font-size:10.5px;font-weight:700;">Edit</text><rect x="422.6" y="101.0" width="44.0" height="22" rx="11" ry="11" fill="none" stroke="var(--part,#EA9A3E)" stroke-width="1.3"></rect><text x="444.6" y="116.0" fill="var(--part-ink,#B4770F)" text-anchor="middle" style="font-size:10.5px;font-weight:700;">Share</text><rect x="474.6" y="101.0" width="37.6" height="22" rx="11" ry="11" fill="none" stroke="var(--part,#EA9A3E)" stroke-width="1.3"></rect><text x="493.40000000000003" y="116.0" fill="var(--part-ink,#B4770F)" text-anchor="middle" style="font-size:10.5px;font-weight:700;">Live</text><text x="365.0" y="168" fill="var(--med-gray,#5B6169)" text-anchor="start" style="font-size:12.5px;font-weight:normal;">A persistent, editable canvas.</text><text x="365.0" y="188" fill="var(--med-gray,#5B6169)" text-anchor="start" style="font-size:12.5px;font-weight:700;">Keep it, edit it, co-edit it live.</text><text x="320.0" y="145.0" fill="var(--part,#EA9A3E)" text-anchor="middle" style="font-size:15px;font-weight:800;">vs</text></svg>
</figure>

## How to create one, and edit it afterwards

After Copilot gives you a response worth keeping, look for the option to add it to a Page (in Copilot Chat, this shows up alongside the response). That opens the canvas with the response already in it. From there you're not limited to asking Copilot for changes: you can edit the text directly on the Page, the way you'd edit any document, or keep chatting with Copilot to extend or rework it. Pages also keep a version history, so if an edit, yours or a colleague's, goes the wrong way, you can open an earlier version and restore it rather than reconstructing it from memory. That history is also useful for more than fixing mistakes: it's how you check what a colleague actually changed, the same way Word's own version history lets you see who edited what and when, rather than just noticing a document looks different with no record of why.

## When to reach for a Page

If you'll edit it, keep it, or work on it with someone else, send it to a Page. If it's a one-off answer you just needed right now, leave it in the chat. When in doubt, ask yourself whether you'd otherwise be tempted to paste the answer into a Word doc just to keep it safe; if the answer is yes, send it to a Page instead and save yourself the copy-paste.

## Try it

Ask Copilot Chat to draft a short pre-meeting brief for an upcoming meeting. Add the response to a Page, edit it directly (tighten a paragraph, add a questions section), then share the Page with a colleague and see their edits appear. Open the version history afterwards and see your first draft still sitting there.

## Key terms

[Copilot Pages](/glossary#copilot-pages), [Multiplayer collaboration](/glossary#copilot-pages), [Version history](/glossary#version-history), [Copilot](/glossary#copilot)
