Copilot Notebooks: a second brain per project.
Sometimes you don't want Copilot searching everything — you want it thinking inside a specific pile: this project's files, this client's history, this course's materials. That's Notebooks: a workspace where the AI is grounded in sources you chose.
Notebooks can now take web links as reference sources, per Microsoft’s Copilot release notes (web version; roadmap ID 516040). Paste a link when you add a reference, and Copilot can draw on that page alongside your files. Rollout can vary by tenant, so check that the option appears for you. The “chosen sources” rule still applies: add only pages you would trust as evidence.
Microsoft announced Copilot Workspaces at Ignite and calls it “the evolution of Copilot Notebooks”: the same grounded-in-chosen-sources idea, made multiplayer. People and agents share one space — an agent drafts a section, you comment, an agent picks the comment up — and the collaboration carries into Teams. It is available in Frontier (Microsoft’s early-access program) for now, so most tenants still see Notebooks as described below. Microsoft hasn’t said what happens to existing Notebooks; the habits in this lesson carry over either way. Source: Microsoft’s Ignite Copilot post.
01 What a Notebook is (and isn't)
A Copilot Notebook is a workspace where you gather specific sources — documents, spreadsheets, pages, links — and every question you ask is answered from those sources. It's the difference between asking a librarian to search the whole library versus handing a sharp assistant one banker's box and saying "master this." Regular Copilot chat is breadth; a Notebook is controlled depth. (If you've used ChatGPT's Projects, the mental model is close — this is the M365-native version of the same idea; our Projects lesson covers that side.)
02 What deserves a Notebook
- A live deal or project: the proposal, the contract drafts, the pricing sheet, the requirements doc — then ask "what did we promise?" with confidence about where answers come from.
- A recurring client: everything Halverson, one box. Every future question about them starts grounded.
- A body of reference: your safety manuals, the employee handbook, this year's vendor contracts — the pile people ask YOU about.
- Learning something: the course PDFs, your notes — quiz yourself against sources that can't drift.
03 Working a Notebook well
Question about anything you might have → chat (whole-tenant search). Question that must be answered from exactly these documents → Notebook. When the answer's provenance matters — contracts, compliance, commitments — provenance is the feature.
04 Keep it honest
A Notebook inherits its sources' flaws: outdated pricing sheet in, confidently outdated answers out. Refresh sources when reality changes, and date-stamp anything volatile. The one-line audit habit — "which of these sources is most likely stale?" — is worth running monthly on any Notebook you rely on.
Build one Notebook for your messiest active project. Six sources, opening audit, one contradiction hunt. Twenty minutes to a project brain.
Open Copilot →This week's challenge
Run one real week of project questions through the project's Notebook instead of memory, chat, or colleague interrupts. Note every 'sources don't cover it' answer — that list is your project's actual documentation debt, found the cheap way.