Copilot Pages and Notebooks: Collaborative AI Workspaces
Introduction to Copilot Pages and Notebooks, the collaborative spaces for working with AI-generated content alongside your team.
Overview
Copilot responses are valuable, but what happens after you get an answer? How do you share it with your team? How do you build on it? How do you keep that work instead of losing it when you close the app?
That’s where Copilot Pages and Notebooks come in. These collaborative features let you turn Copilot conversations into persistent, shareable workspaces that integrate AI assistance with team collaboration.
What You’ll Learn
- What Are Pages: Shareable, editable AI-generated documents
- What Are Notebooks: Deeper thinking workspaces for complex work
- When to Use Each: Pages for outputs, Notebooks for process
- Getting Started: How to create and share Pages and Notebooks
Script
Hook
You ask Copilot a great question. It gives you a useful answer. But then what? How do you share it with your team? How do you build on it? How do you keep that work instead of losing it when you close the app?
That’s where Copilot Pages and Notebooks come in.
What Are Copilot Pages?
Let’s start with Pages. Pages are shareable, editable AI-generated documents.
Here’s how they work. After Copilot answers a question, click “Create Page.” The response becomes a persistent document. You can edit it like a Word doc.
Then you share it with your team. Send the link via Teams, email, or SharePoint. Collaborators can view and edit. Everyone sees the same content.
Think of Pages as turning Copilot conversations into collaborative documents. Instead of copying and pasting into Word, you create a Page and share it.
Example use cases: turn meeting notes into action items to share, create a research summary for the team, draft policy language collaboratively, build a shared knowledge base.
In government environments, Pages respect M365 permissions. You control who can see and edit them, just like any M365 file.
What Are Copilot Notebooks?
Now Notebooks. Notebooks are deeper thinking workspaces designed for complex, multi-turn work.
They give you more space to prompt and refine. They’re better for exploratory work. They keep the full conversation thread so you can see how you got to the final answer.
Use Notebooks when you need multiple iterations on a draft, when you’re exploring a complex problem, or when you want to save the entire back-and-forth with Copilot.
Notebooks are like having a whiteboard session with Copilot. You’re not just asking one question — you’re working through a problem together.
Example use cases: drafting a complex policy document with multiple revisions, exploring different approaches to a project plan, researching and synthesizing information on a new topic.
You access Notebooks in the M365 Copilot app. Create a new Notebook or continue from existing work.
Pages vs Notebooks: When to Use Each
So when do you use Pages versus Notebooks?
Use Pages when you have a Copilot response you want to share, when you need lightweight collaboration, when you want something quick and shareable.
Use Notebooks when you need deep, iterative work, when you’re working on something complex over time, when you want to save the full conversation history.
Pages are for outputs. Notebooks are for process. If you’re sharing a result, use Pages. If you’re working through a problem, use Notebooks.
Getting Started
Here’s how to get started. Both features require a Microsoft 365 Copilot license.
Start by creating a Page from your next Copilot response. Just click “Create Page” and see how it works.
Try Notebooks for your next complex project. Open the M365 Copilot app and create a new Notebook.
These features make Copilot more than a Q&A tool. They make it a collaborative workspace. Start using them, and you’ll see how AI work integrates with team work.
Sources & References
- Use Copilot Pages for Deeper Collaboration — Official guide to Copilot Pages
- Microsoft 365 Copilot Overview — Overview of collaborative features in M365 Copilot
- Copilot Adoption Resources — Adoption guidance for collaborative Copilot features