M365 Copilot — Pages · When to Use Them (and When Not To)

At a glance — when to use Pages

What it is A named, persistent document created from a Copilot Chat response. Shareable. Editable by collaborators in real time. Does not update automatically when source data changes.

What it is not A notebook. A source of truth. A live dashboard. A replacement for Word. Copilot answers in a Page are a snapshot of one moment — they do not stay current on their own.

The one rule If someone reading this Page 10 days from now would be misled by stale information, use Word or Loop instead. If they need a snapshot of what Copilot produced today, a Page is the right tool.

Scenario	Pages?	Why
Share a Copilot briefing with someone who lacks your chat context	Use	Clean shareable snapshot, no access to your chat required
Collaborate on a Copilot-drafted document with your team	Use	Real-time co-editing, instant share link, lightweight
Create a first draft to promote to a formal Word document	Use	Pages convert directly to Word — good starting point
Track live project status that updates each reporting period	Avoid	Pages do not update automatically — use Notebooks or Loop
Replace a SharePoint knowledge base or team wiki	Avoid	No structured navigation, limited version control, wrong tool
Formal document requiring an approval workflow	Avoid	Convert to Word first — Pages lack change tracking and sign-off workflows
Ongoing reference document updated by multiple people over weeks	Consider Loop	Loop components embed across Teams, Outlook, and OneNote and sync everywhere

What Pages are — and what they are not

Pages are

A persistent copy of a Copilot response you can return to
Shareable with anyone in your org (view or edit access)
Editable by you and collaborators in real time
Convertible to a Word document in one click
Embeddable in Teams, Outlook, OneNote, and Loop
Versioned — history available since October 2025
Visible to unlicensed colleagues (they can edit, not create)

Pages are not

Automatically updated when the underlying data changes
Grounded in references — they hold text, not connections
A replacement for Copilot Notebooks (no reference pinning)
Shareable with external or guest users via direct link
Exportable to PowerPoint (export removed — verify current status in your tenant)
Searchable via SharePoint or Teams search in the same way as Word files
A formal document management tool

How to create a Page — 3 steps

Run a Copilot prompt

Ask Copilot anything in Copilot Chat. Wait for the response to complete.

Click the pencil icon

Click the pencil icon below the response. The Page opens alongside chat for immediate refinement. Rename it by clicking the title.

Click Share → copy the link or enter names. Recipients need a Microsoft 365 account. No Copilot licence required to view or edit.

Pages vs Word vs Loop — choose the right tool

Tool	Best for	Updates	Formal use?	Licence
Pages	Quick share of a Copilot output, lightweight team iteration	Manual — you ask Copilot to refresh	No — convert to Word first	Create: Copilot add-on. View/edit: OneDrive only
Word	Formal documents, reports, contracts, anything with an approval lifecycle	Manual edits, tracked changes	Yes — full change tracking, version history, PDF export	Standard M365 licence
Loop	Living content that needs to appear and stay current across Teams, Outlook, OneNote simultaneously	Real-time everywhere it's embedded	No — designed for collaborative tracking, not formal output	Standard M365 licence

When Pages work well

Four scenarios where Pages save time

Sharing a Copilot output without sharing your chat

All roles

You ran a Copilot prompt that produced something useful — a summary, a briefing, a comparison. A Page lets you share the result with colleagues who were not in the chat and do not have the same Copilot context. Recipients see a clean document, not a raw chat transcript.

Example: Copilot produces a competitive landscape summary. Convert to a Page, share the link with the bid team. They can read and annotate it without needing access to your Copilot chat or licence.

Collaborative iteration on a draft

Manager · EA · Team Lead · Bid Manager

Pages support real-time co-editing. If you need two or three people to refine a Copilot-generated draft — a meeting agenda, a draft communication, an outline — a Page is faster than emailing a Word document back and forth. Edits sync immediately for all editors.

Example: Copilot drafts a change communication for a programme update. Share as a Page with the comms lead and HR rep. All three refine it in parallel before promoting to a final Word document.

Meeting prep briefing — shared before the meeting

Manager · Executive · EA · Programme Lead

Ask Copilot to generate a pre-meeting briefing, convert to a Page, and share with attendees in the calendar invite. Attendees can view and add context before the meeting. The Page becomes the shared pre-read rather than an email attachment.

Example: Copilot drafts a steering committee pre-read from the project status documents in your chat. Send the Page link in the meeting invite. Attendees can comment before the call.

First draft that promotes to Word

All roles producing formal documents

Use Pages as a fast drafting surface, then convert to Word when the content needs a formal lifecycle. Click the Create button in the Page → Document. The Word file opens with your content ready for tracked changes, review, and approval workflows.

Example: Copilot drafts a lessons-learned summary from meeting notes. Refine it in the Page with two colleagues, then promote to Word for the formal project close-out report.

When Pages create problems

Four patterns that generate stale data, confusion, or trust issues

Using a Page as a live status report

The stale data problem

A Page is a snapshot of what Copilot produced at one point in time. When someone reads it two weeks later, nothing has changed — not because the project is on track, but because Pages do not update themselves. People reading a shared Page assume the content is current. On a fast-moving project, a two-week-old Copilot status summary shared as a Page is actively misleading.

Use instead: Copilot Notebooks for ongoing project document analysis. Run a fresh Copilot prompt each reporting period rather than refreshing the Page manually.

Treating a Page as a source of truth or knowledge base

Wrong tool for persistent knowledge

Pages are not indexed in SharePoint search the same way Word or PDF documents are. They have limited metadata, no structured navigation, and no connection to the Copilot reasoning that generated them. Teams that store reference information in Pages — procedures, decisions, standards — find it becomes invisible over time. No one knows it exists, no one can find it, and no one trusts whether it is still valid.

Use instead: SharePoint pages or a Teams Wiki for team knowledge. Word documents in SharePoint for procedures and reference documents. Copilot Notebooks for document-grounded research that needs to be requeried.

Confusing Pages with Notebooks

No grounding, no memory

Pages and Notebooks look similar and live in the same sidebar. They do different things. A Page holds text. A Notebook holds references and answers queries against them. Sharing a Page does not give the recipient the ability to query the underlying documents. Asking Copilot a question in a Page does not ground the answer in any pinned files — it draws on whatever Copilot can access from your general M365 data, not a curated reference set.

Use instead: Copilot Notebooks when you need persistent, reference-grounded queries. Pin the relevant documents once; query them repeatedly. Share the Notebook rather than a Page for collaborative research.

Putting a Page into a formal approval workflow

Wrong format for governed documents

Pages have version history but lack the tracked changes, comment resolution, and sign-off mechanisms that formal document approval requires. If a document needs a named reviewer, a change log, a final approved version, or a PDF for distribution, a Page is the wrong format. Pages are designed for informal iteration, not formal governance. All invited members also receive editing access — there is no read-only sharing for internal users, which creates risk in a review context.

Use instead: Convert the Page to Word (Create → Document) before entering any review or approval process. The Word file retains your content and adds the full document lifecycle tooling.

Five rules for using Pages without creating problems

01
Date every Page you share. Add the creation date to the title or first line. Readers then know whether the content is current without having to ask.
02
Add a staleness note on any Page that might be reread later. One line at the top: "Generated [date]. Reflects data available at that time. Do not treat as current status." Thirty seconds of work prevents real confusion.
03
Promote to Word before any formal review. Convert via Create → Document before sending anything that requires tracked changes, sign-off, or PDF distribution.
04
Do not share a Page as a notebook substitute. If the recipient needs to query the underlying documents, share a Copilot Notebook instead. A Page contains text; a Notebook contains references.
05
Delete Pages you no longer need. Pages accumulate in your SharePoint Embedded container. Stale Pages shared with no expiry become someone else's source of truth six months later.
06
Pages live in the creator's storage — not a shared location. A Page you create is stored in your SharePoint Embedded container. If you leave the organisation or lose your licence, anyone with a shared link may lose access to that Page. For anything shared with a team long-term, export to Word and save it to a shared SharePoint site.