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.
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.