What it does

Copilot Notebooks let you gather a defined set of sources — files, pages, links, meeting notes — into one notebook and have Copilot reason over just that grounded set. It's scoped, project-style context rather than the whole Graph.

Key facts

• You control the sources. Copilot answers from the notebook's contents, which cuts noise and improves relevance.
• Sources can include documents, links and other M365 content you already have access to.
• It's aimed at recurring work on a fixed body of material — a bid, a project, a research theme.
• Part of the Microsoft 365 Copilot experience, so it rides existing licensing and permissions.

When to use / skip

Use it when you keep coming back to the same pile of documents and want answers grounded only in those. Skip it for broad, tenant-wide questions where you actually want Copilot to range across everything.

Configuration decisions

• How you guide users on what's a sensible notebook scope versus dumping everything in.
• Nothing bespoke at admin level beyond the usual Copilot licensing and data governance.

Gotchas

• Answer quality is only as good as the sources you added — a thin or off-topic notebook gives thin answers.
• Users confuse it with Copilot Chat and expect it to know things outside the notebook. It won't, by design.
• Permissions still apply per source; adding a link doesn't grant anyone access they didn't have.

Consultant notes

• This is the feature power users love once they get it — the scoping is the point, not a limitation.
• It maps neatly onto consulting and bid work: one notebook per engagement. Pitch it that way.
• Curation discipline matters. The teams that keep notebooks tidy get far more out of them than those that hoard sources.

---

Worth revisiting after the next release wave.