Lesson 05 · Copilot Mastery Pro ~8 min read 3 workflows

Copilot Pages: the workspace nobody knows about.

Copilot Pages is the Microsoft 365 surface most people haven't touched. It's the place where Copilot output becomes a collaborative document — a hybrid between a chat thread, a doc, and a workspace. Once you understand it, it changes how you handle multi-step work that crosses people and threads.

The mental model

Pages turns Copilot conversations into shared workspaces.

Chat with Copilot is ephemeral — when the conversation closes, the work is gone unless you copied it out. Pages persists it as a collaborative document anyone you share with can extend, edit, or continue the Copilot conversation inside.

Workflow 01 Capture Copilot work into a persistent Page

1

Stop losing Copilot output

Anytime you have a Copilot conversation worth keeping, click "Edit in Pages." The conversation becomes a document with rich formatting and the option to continue.

The prompt that works

When to use thisMulti-step plans, brainstorm sessions worth saving, drafts that need review from teammates, anything where you'd lose context closing the chat tab.

Best use cases

  • Project planning sessions with Copilot
  • Research summaries you want to keep editing
  • Drafts that need collaborative input
  • Anything you'd otherwise paste into a new Word doc
Pages are stored in your OneDrive — they count against your storage quota. Not unlimited, but generous.
Time savings: Re-doing lost Copilot work: never again.

Workflow 02 Co-edit with teammates inside a Page

2

Share, comment, continue together

Share a Page with a colleague. They can add to it, comment, ask Copilot follow-up questions inside the same Page. The AI sees the full thread; everyone stays in sync.

The prompt that works

Common patternUse a Page as a "working doc" for any project where multiple people would otherwise be in conflicting threads of Copilot, each with their own context. Everyone working in the same Page = shared AI context.

Best use cases

  • Cross-functional projects with multiple stakeholders
  • Sales pursuit pages (customer details, proposal drafts, internal notes)
  • Account planning with your team
  • Onboarding documents that evolve with input from many
Permissions follow standard OneDrive sharing — same controls you'd use for any doc. Verify the share scope before adding sensitive context.
Time savings: Async collaboration that used to fragment across DMs and emails: now in one place.

Workflow 03 Use Pages as living, AI-aware briefs

3

The brief that updates itself

Build a Page that's a brief on a topic. Include source data, key questions, current status. Anyone (or you) can ask Copilot inside the Page "what's changed?" or "summarize where we are" and Copilot uses the full Page as context.

The prompt that works

Use case exampleA Page that's an account brief for a customer — past meetings, current deal stage, decision-makers, next steps. Re-open it monthly, ask Copilot for an update, get fresh recommendations based on the full history.

Best use cases

  • Customer account briefs
  • Project status pages
  • Personal weekly review pages
  • Living strategy docs that update over time
Pages can get unwieldy if they grow too long. Best practice: keep a Page focused on one topic; create new Pages for sub-topics that take on their own life.
Time savings: Context-switching tax on recurring work: dropped to near zero.

Final challenge: build one Page that pays off

Pick one recurring topic that drags on you — a customer account, a long-running project, a personal goal you track. Build a Copilot Page for it:

  1. Open Copilot, prompt for the initial structure (e.g., "Set up a brief on the Acme account: history, current status, open items")
  2. Click "Edit in Pages"
  3. Add details that only you know
  4. Share with a teammate if relevant
  5. Re-open it once a week and ask Copilot "summarize what's changed" + "what should I do next"

The Page becomes a permanent thinking partner on that topic.

What you can do now

  • Capture any Copilot conversation into a persistent, editable Page
  • Co-edit with teammates while keeping Copilot in the same context
  • Build account briefs and project pages that improve over time
  • Know when a Page is the right surface vs. when chat or Word is better
Pro+
Up next in Copilot Mastery

Lesson 6 · Copilot Agents: build a custom assistant for your role

Custom agents that know your team's data, your job, your style. Walkthrough builds: a sales follow-up agent, an HR policy agent, a Q&A agent for your knowledge base. See pricing →