If Copilot Keeps Pulling the Wrong Information, You Need a Notebook

In session after session across dozens of workshops, I asked the same question: “How many of you have used Copilot Notebooks?”

Almost no hands went up. Ever.

That surprised me at first. Notebooks are one of the most practically useful things in Copilot, especially for people who work with a fixed set of reference material. But they’re tucked away enough that most users never find them on their own. By the time I started front-loading Notebooks into every session, the reaction was consistently the same: people wished they’d known about it earlier.

What regular Copilot chat actually does

When you open Copilot chat and type a question, Copilot looks across your Microsoft 365 environment for relevant content. That includes emails, SharePoint files, Teams messages, documents you have open, and documents other people have shared with you. It synthesizes what it finds and responds.

This is powerful for broad questions. If you want to know what your team has been discussing about a topic across channels, Copilot chat is a good tool for that.

The problem shows up when you want Copilot to work from a specific set of content. You paste a document and ask questions about it. You think it’s answering from the document. But Copilot may be blending the document with related emails, a similar SharePoint file from six months ago, or a Teams thread on the same topic. The answer sounds right. The source might not be what you intended.

This is the failure mode Notebooks exist to solve.

What a Notebook actually is

A Notebook is a bounded workspace. You load content into it — documents, notes, URLs, plain text — and Copilot works exclusively from what you’ve put in. It doesn’t wander into your email. It doesn’t pull from SharePoint. It stays inside the Notebook.

That constraint is the entire value. When you need Copilot to be a specialist on one specific thing rather than a generalist across your whole environment, a Notebook gives you that.

I use Notebooks for any work that involves returning to the same reference material repeatedly. Project documentation that needs to be queried from multiple angles. A long report that needs to be summarized, then explored, then cross-referenced. Onboarding materials for a new client. Content that doesn’t change much but that you need Copilot to know deeply.

When to use a Notebook vs regular chat

Regular Copilot chat is better for: broad questions across your organization, finding information that’s spread across multiple places, quick one-off queries where source breadth is fine.

Notebooks are better for: anything where source accuracy matters, research or analysis work on a defined document set, recurring work where you load the same content and query it in different ways over time, and cases where you’ve had Copilot pull the wrong source and it’s become a frustration.

The practical test: if you’d want to hand a specific set of documents to a smart assistant and say “work only from these,” use a Notebook.

Setting one up

Creating a Notebook is straightforward. In Copilot, look for the Notebooks option (it’s in the left sidebar in Microsoft 365 Copilot). You give it a name, load in your content, and then interact with it exactly like regular Copilot chat — except Copilot stays inside what you’ve given it.

You can paste text directly, upload documents, or add links. The Notebook holds the content and persists between sessions, so you can return to it tomorrow and pick up where you left off without reloading everything.

One thing worth knowing: Notebooks have a content limit. For most working documents this isn’t a constraint, but for very large document sets you’ll want to be selective about what you include.

The audio overview feature

Once you have a Notebook loaded, there’s a bonus feature worth knowing about: audio overview.

Audio overview generates a conversational summary of the Notebook content in podcast format. Two synthesized voices discuss the material, cover the key points, and surface the main themes. It’s roughly 10 to 15 minutes for a reasonably sized document set.

It sounds gimmicky. In practice, it’s genuinely useful for getting oriented in a new body of content, especially lengthy reports or documents you need to understand quickly without reading every page. I started mentioning it toward the end of Notebook sections in workshops and people lit up. It’s the kind of feature that doesn’t feel useful in the abstract but immediately makes sense once you hear it.

The practical takeaway

If you’ve been frustrated by Copilot pulling information from places you didn’t intend, Notebooks are the fix. They’re not a workaround. They’re the right tool for the job when source accuracy matters more than source breadth.

Load your content in, work from it, and Copilot stays where you put it.

This is the kind of thing I cover in Copilot adoption workshops — practical features that change how people actually work, not just feature walkthroughs. See how I work with teams →