Copilot Pages vs Notebooks: Choose the Right Place for Work
Copilot Pages are collaborative documents built from Copilot responses. Copilot Notebooks ground Copilot on specific source documents you add. Here is what each does, when to use both and what belongs elsewhere.
Updated 5 min read
Copilot Pages and Copilot Notebooks are two different Microsoft Copilot features that solve different problems. Pages are a canvas where you turn Copilot responses into a collaborative, editable document that colleagues can read and update. Notebooks are a research tool where you add specific source documents and ask Copilot questions grounded on those sources. Understanding the difference prevents you from trying to make one tool do the job of the other.
Neither Pages nor Notebooks are designed to carry decisions, rules and project progress forward into future sessions. fenbs stores those things outside any one Microsoft tool, so connected AI apps can continue the work from the right point regardless of which Copilot feature produced it.
| Copilot Pages | Copilot Notebooks | |
|---|---|---|
| What it is | A collaborative document you build from Copilot responses | A research session grounded on documents you add |
| Primary use | Create shareable, editable documents with colleagues | Ask Copilot questions about specific files you upload |
| Who adds the content | Copilot generates it; people edit and add to it | Copilot answers from the sources you provide |
| Grounding | General Copilot knowledge plus what you add to the Page | Strictly the documents you add to the Notebook |
| Collaboration | Multiple people can edit the Page in real time | Sessions are personal; not designed for co-editing |
| Output type | A persistent, editable document at a shareable URL | A research conversation with cited answers |
| Best for | Drafting a report, briefing or plan with the team | Reviewing contracts, analyzing a set of documents |
| fenbs | Keeps decisions and progress that outlive any Copilot session or Page | Keeps decisions and progress that outlive any research session |
What Copilot Pages do
Copilot Pages are editable documents you create directly from a Copilot chat. When Copilot gives you a response, you can push it to a Page — a blank canvas that works like a Microsoft Loop component. You can then add to it, rearrange it, share it with colleagues and ask Copilot for more content to include.
Because Pages use Loop components, they embed in other Microsoft 365 apps — Teams, Word, Outlook. A Page updated in one place updates everywhere it appears. This makes Pages useful for a briefing note, a project overview or a plan that multiple people need to read and edit together.
Pages do not ground Copilot on a specific set of documents by default. Copilot answers from its general knowledge, the content already in the Page and your Microsoft 365 content it has been granted access to. If you need answers from a specific file, you need a Copilot Notebook.
What Copilot Notebooks do
Copilot Notebooks let you add a set of source documents — PDFs, Word files and other supported types — and then ask Copilot questions that are answered specifically from those sources. The answers cite the source and the section. This is useful when you need to work with a specific set of files rather than general knowledge.
Notebooks are personal research sessions. They are not designed for real-time collaboration — you add the sources and ask the questions yourself. The output is a researched answer to your question, not a shareable document. To share findings from a Notebook, you would copy the key conclusions into a Page or a document.
For more on Notebooks alongside other AI research tools, see copilot notebooks vs chatgpt projects and gemini notebook.
When to use both together
A useful workflow: use a Notebook to research a specific question from documents — reviewing supplier contracts, analyzing a regulation or comparing product specifications. Then move the key findings into a Page where you and colleagues can build a recommendation or a plan on top of the research.
The Notebook does the source-grounded analysis. The Page becomes the collaborative document where the findings are turned into action. This uses each tool for what it does best rather than trying to stretch one to cover both jobs.
Keep decisions beyond the Page or Notebook
When a research session or a collaborative Page produces a real decision — an approved approach, a confirmed rule, a clear next step — record it in fenbs as a Decisions and rules entry. The next assistant reads it regardless of which Copilot feature produced it, so the decision survives when the session closes. Create a free account to try it.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
What neither tool is built to do
Neither Pages nor Notebooks track project progress across sessions. A Page captures what was written; it does not tell the next person what was decided, what is still open or where to start. A Notebook answers questions from sources; it does not remember the conclusions you reached last week.
Both tools also live inside Microsoft's ecosystem. If a colleague uses Claude, ChatGPT or a different AI app, they cannot connect to a Copilot Page or Notebook directly. For shared project context that any connected AI can read, that context needs a tool designed for it.
For how Notebooks compare to other AI research tools, see copilot notebooks vs chatgpt projects. For the broader Microsoft Copilot ecosystem, microsoft copilot agents covers connected agent capabilities.
Choosing between Pages, Notebooks and other tools
- You need to draft a report or plan with colleagues, with Copilot adding content: use Pages.
- You need to analyze a specific set of documents and get cited answers: use Notebooks.
- You need to write your own notes alongside AI assistance: use OneNote with Copilot.
- You need decisions, rules and project progress that any AI app can read across sessions: use fenbs.
How to do this with fenbs
- Create a free account and add a project for the work that your Pages and Notebooks support.
- Use Copilot Notebooks for targeted document research and Copilot Pages for collaborative output.
- When a session produces a decision, add it to fenbs as a Decisions and rules entry with the person who decided and the date.
- Add the Page URL as a Links and listings entry so the shareable document is findable from the project.
- Connect your preferred AI app from /integrations. Ask it to read the project context at the start of each session so it starts from the current decisions and next steps.
fenbs does not connect to Copilot Pages or Copilot Notebooks directly. It stores the decisions and progress you choose to record there, available to any connected AI app through MCP.