Microsoft Copilot Notebooks - Simply Explained

Welcome to the M365 FM podcast, where we explore the people, ideas and technologies shaping the future of work. Why copilot feels random until you give it a home. Most people use copilot like a search box and then wonder why the answers feel random. You have ten files about one project, and the chat window has no idea which of them matter. The fix isn't a better prompt. It's giving copilot a smaller world to work in. Welcome to the M365 FM podcast, where we explore the people, ideas and technologies shaping the future of work. Today, we're looking at copilot notebooks, the part of copilot that answers from the files you choose. By the end, you'll know how to start one, what it does well, and the limits that surprise almost every beginner. Picture a project you have on your plate right now. There's a written brief, two sets of meeting notes, a budget sheet, and a slide deck a colleague built last quarter. You open copilot, you ask it to pull the main risks together, and the answer comes back smooth and confident. The trouble is that it was drawing on whatever it could see across your whole account. It had no idea that your five files were the only ones that mattered. That gap between what you meant and what copilot actually used is the whole problem. The tool isn't bad at writing, and it isn't short on knowledge. A general chat simply has no sense of your projects borders. When you ask a question, it searches wide because wide is the only thing it knows how to do. Now here's where it gets interesting. The answer isn't a longer prompt or a clever way of phrasing the request. It's a place where you decide before you type a single word which sources copilot is allowed to read for this one job. That small decision is what stops the guessing. Microsoft calls that place a copilot notebook. And once you see how it works, the random feeling tends to fade. I'll be honest with you because this channel is built on that. A notebook isn't magic, and it comes with real limits that catch new users off guard. One of those limits trips up almost everyone in their first week, and I'll show you exactly how to dodge it before we finish this episode. What a copilot notebook actually is. A copilot notebook is a workspace inside copilot where you gather the sources for one project. So copilot answers from those sources and nothing else. That's the whole idea. In one line, Microsoft describes it as an AI powered workspace that brings together the content that matters most to your task, and that phrasing is worth taking. Literally. grounded is one of those words that gets used a lot and explained rarely. A grounded answer is tied to the material you supplied, rather than pulled from the open web or from some other corner of your account. If you add the project brief and the budget sheet, then a question about cost gets answered from the budget sheet you chose. It won't pull from a template someone else wrote years ago. The workflow itself is short enough to hold in your head. You create a notebook, you add references, you ask your questions, and you get answers that come from those references. Only Microsoft is direct about the boundary here. Inside a notebook, copilot doesn't reach into your whole OneDrive, your email, your teams chats, or the web. It uses, the references you added and nothing beyond them, which means you stay in control of what copilot can see and what it can't. The difference between a notebook and a normal chat is a bit like the difference between asking a well-read colleague a question in the hallway and sitting them down at a table in the hallway. They answer from memory and reach for whatever comes to mind at the table. With the five documents spread out in front of them, they answer from the paper you handed over. Here's a small example of what that looks like in practice. Say you're planning a product launch. You drop in the launch brief, the pricing sheet, and the last three sets of meeting notes. Then you ask what changed in the pricing over the past month? Copilot answers from the pricing sheet you added. So the reply is about your launch and not about pricing in general. So a notebook isn't a new app to learn from scratch, and it isn't a replacement for chat either. It's a scoped space for the work that deserves more than a one off question, and the scope is the feature rather than a limitation. That scope is what makes the answers feel like they're about your project instead of about everything at once. Which raises the practical question if a notebook is just a workspace holding your files, how do you actually build one? How do you set one up in a few minutes? You'll find notebooks inside the Microsoft Copilot app at m365 dot cloud dot Microsoft. Look in the left navigation, and if it isn't there, open the app launcher at the top and select notebooks from the list. The same notebook also opens in OneNote, and that detail matters more than it sounds. It means you can move between a lighter view in the copilot app and a fuller workspace view in OneNote without losing your place. Creating one is really a naming exercise, followed by a gathering exercise. You give the notebook a name and then you add references. You can search for a file by name, filter the suggestions by files or meetings or emails or sites, or upload something from your computer. You can also browse your OneDrive or simply drag the files straight into the workspace. The kinds of things you can add cover most of what a normal project throws at you. Word documents, PowerPoint decks, Excel sheets, and PDFs all work. You can also add copilot pages, loop items, and OneNote pages. You can even point the notebook at a specific web page, so copilot grounds its answers on that page as well. That range matters because it means you rarely have to convert or re-upload anything the notebook reads, the documents you already work with in the formats you already keep them in. Now the access question, because this is the part that stops people before they even start using copilot notebooks, requires a Microsoft Copilot or copilot chat license, and the account also needs a SharePoint or OneDrive plan to create a notebook. If you're on a Microsoft three hundred sixty five Personal Family Premium or Pro Plan notebooks is included there, too. Your IT team usually handles the license side, so if the notebooks option is missing from your screen, that's the first thing worth checking with them. I want to calm one worry before it takes hold. This isn't a server. You have to stand up and it isn't a database you have to configure. There's nothing to install and no code to write. You're pointing at files that already live in your Microsoft three. Sixty five world and letting copilot read them together in one place. That simplicity is the whole point, and it's also why the next part matters so much. The quality of everything that comes out of a notebook depends on what you put in, so it's worth knowing what the tool is good at, what it does. Well, once your files are in, the first thing a notebook does well is pull things together. You can ask it to summarize a set of documents. Find the main themes across your meeting notes or surface the decisions buried deep inside a long thread of files. The answer comes back shaped by your material, so it reads like a summary of your project rather than a generic overview of the topic. The second thing is drafting. Because the notebook already holds the raw material, you can ask for a first version of a proposal, a one page brief, or a short report. Copilot builds it from the files you supplied. That takes care of the slow part of the job, which is usually staring at a blank page and trying to remember where every fact came from. The third thing is plain question answering, and Microsoft's own example shows it well. You ask which licensing options are mentioned in these documents, and the reply is drawn from the documents you chose. In a normal chat. That question would send copilot hunting across your whole account in a notebook. It stays inside the fence you built. There's one more detail that changes how you work over time. The references in a notebook stay live. If a file on SharePoint gets updated by a colleague, copilot reads the latest version rather than a copy you added last month, you're not maintaining duplicates and you're not chasing people for the newest spreadsheet. The notebook points at the real file and the real file keeps moving. That's a lot of value for a few minutes of setup, which is why the small settings we look at next punch above their weight. The small settings that change everything. Every notebook can carry its own set of instructions. These are standing rules. You write once, and they shape how copilot answers inside that notebook. You might tell it to give the answer in one line first, and then add the detail, or to keep the language plain, or to name which file each fact came from. It's a small box to fill in, and it changes the feel of every answer that follows. A useful way to think about instructions is that they're the notebook's job description. Without them, copilot guesses at the right tone and the right level of detail. With them, you stop repeating yourself in every prompt because the notebook already knows how you want to be talked to. There's also a helpful nudge right at the start. Copilot suggests relevant files based on the Notebook's title or theme. So if you name the notebook, well, the right documents tend to surface on their own. That turns the blank workspace moment into a shortlist you can react to. Instead of a search, you have to run from scratch. Then there's the feature people tend to fall in love with. You can generate an audio overview of a notebook, which is a spoken summary you can listen to while you walk, drive, or make coffee. Microsoft treats it as a way to catch up on your own material when you're away from a screen, and it's handy when a colleague shares a notebook with you, it gives you the gist before a meeting without reading a thing. One honest note about that feature audio overviews are currently limited to a set of languages, including English, Spanish, French, German, Portuguese, Italian, Japanese, and Chinese. If your material is in another language, that particular feature may not help you yet, so the settings and the extras make a good notebook better before you build your whole week around one, though, you should know where it lives and whether it's safe to trust with real work, where your notebooks live and how they fit. Microsoft three hundred sixty five A notebook lives in a personal SharePoint container that belongs to the person who created it. From there, it follows that person's life cycle inside the organization. In plain terms, the notebook has an owner. It lives inside your Microsoft three hundred sixty five world, and it isn't floating somewhere outside your company's reach. Permissions behave the way you'd hope. Copilot respects the access that already exists on the files you reference, so adding a document to a notebook doesn't hand anyone new access to that document. The notebook doesn't open a fresh door into your tenant. It works with the doors that are already there and stays inside them. It's also worth placing this in the bigger picture because the product names blur together fast. Copilot notebooks is part of the Microsoft three. Sixty five Copilot experience alongside Copilot chat and Copilot pages, and it now opens inside OneNote two. If you've heard about loop and wondered whether you need it. You don't need to learn it. Lupe isn't required for a notebook, which is one less thing on your plate. Then there's the Azure question. Since this channel promises to connect those dots for someone getting started, you don't touch Azure to use copilot notebooks and you don't configure anything in it. The AI runs on Microsoft's cloud and your content stays inside your Microsoft three hundred sixty five world, which is exactly why your existing permissions and compliance settings still apply. Azure is where a lot of the underlying plumbing lives, but it isn't a step you take. There's one trust point worth leaving you with before we reach the warnings, Microsoft states that Copilot Notebooks doesn't use your data to train the large language model that matters when you're deciding whether to put real project files into a notebook. And it's a fair question to ask of any AI tool you adopt with the trust covered, let's talk about the places where notebook will surprise you in both directions. The limits and the mistakes to avoid. The first limit is about pictures and numbers. You can't create charts, graphs, or images directly inside a notebook. It's a workspace for reading, reasoning, and writing, not a place to build a visual dashboard if your task is turning raw data into a chart, that work happens in the app that owns the chart, not inside the notebook. The second limit is the one that catches almost everyone, and it's the one I promised you at the start. Copilot can use up to three hundred files in a notebook to answer your questions. When you point a notebook at a whole SharePoint folder or site, it doesn't read every single file in there. It selects up to three hundred files that look most relevant to your specific prompt. That means the one contract you actually need might not be the one it chooses. The fix is simple, and it's the habit I'd build from day one. If a file has to be part of the answer, add that file to the notebook directly instead of trusting a shared folder to surface it. Adding the specific file is what guarantees it's in play. A shared folder is a convenience, and convenience isn't the same thing as certainty. A good way to think about the limit is that a notebook rewards curation over dumping. Five files you chose on purpose will be three hundred you never looked at, because the answer can only be as good as the material copilot can actually see. The third limit is about cleanup, and this is the one that stings. Deleting a notebook or a page is currently permanent and it can't be undone. A recycle bin for notebooks is in development, and a recycle bin for pages is coming sooner. As things stand today, though, deleting is a one way door. Treat clean up with the same care you'd give to emptying a folder you never checked. Then there's sharing, which holds its own surprise when you share a notebook, you're not only sharing the notebook, you can also be giving the people you invited access to the files inside it. On top of that, read only members aren't supported yet, so anyone you invite gets editing, access, and groups can't be added as members at all for a solo project. That's fine for a sensitive one. Think carefully before you invite. The last limit is the most important because it's easy to forget when the answers sound confident. Microsoft's own guidance says these answers may not always be accurate, and it tells you to check important facts before acting on them. Grounding makes an answer relevant and relevant isn't the same as correct. Use the notebook as a fast, well read assistant and keep your own judgment in the loop. One more practical note some features are still rolling out, so a friend in another company may see buttons you don't have yet or the other way around. If something from this episode is missing on your screen, that's usually the reason. Notebooks, OneNote, and pages in one breath with the limits in hand. The question of which tool to use gets much easier to answer. A copilot notebook is for one project with a pile of sources and a long list of questions. OneNote is for everyday notes, quick capture, drawing, and the long term pile of things you want to keep. Both can live in the same Microsoft three hundred sixty five account, and they aren't competing for the same job. Copilot pages are a different shape. Again, a page is the editable canvas you build from a single copilot. Answer something you can refine and share as one clean output. A notebook is where you gather many sources so you can ask many questions. One is about keeping an answer and the other is about working through a project. Pick the one that matches the shape of the job, and you'll rarely reach for the wrong tool. If you want a rule of thumb, here's the one I use many sources and one project means a notebook. While one good answer you want to keep and share means a page. Everything else stays in OneNote exactly as it did before. There's one more comparison worth clearing up because it comes up constantly. A notebook is not the same tool as an agent. An agent is something you build point at content and then mostly use as it was designed. A notebook is a living space that grows as your project grows, and you keep adding files and refining it over time. One is fairly static and the other keeps changing with the work. That clarity is the whole point of this episode. You don't need to master five tools. You need to know which one fits the job in front of you. The short version and one question for you. Here's the short version. A copilot notebook is a scoped workspace inside copilot, where you add the files for one project, and copilot answers from those files and nothing else. You set one up by naming it and adding references, and you sharpen it with a few instructions. From there, you get summaries, drafts, and answers that stay tied to your own material. It's excellent for research and writing, and it has honest limits around charts. The three hundred file ceiling sharing and permanent deletion. So here's my question for you. If you looked back at the last project you finished, which three files would you have handed copilot first, and what would you have asked it to do with them if this made the topic feel less intimidating? Subscribe to M365 FM to master the tools and the mindset shaping the future of work.