Copilot Notebooks are getting a meaningful upgrade, and this one finally answers the question every Microsoft 365 Copilot user keeps asking: where did all my work go? If you have ever started a project in Copilot, generated a handful of drafts, pulled in a few files, then closed the tab and lost the thread, the new Notebooks experience in the Microsoft 365 Copilot app is built for exactly that pain. Microsoft is turning Copilot from a place where you ask one-off questions into a place where project work actually lives, in a lightweight, persistent workspace that stays in context.
This update is tracked under Microsoft 365 Roadmap ID 562662(opens in new window), and it rolls out to tenants with eligible licenses through June and July 2026.
What Are Copilot Notebooks in the Microsoft 365 Copilot App?
At a basic level, Copilot Notebooks bring three things together in one spot: your Copilot chats, the content Copilot generates for you, and the reference materials you want grounded in your work. Instead of treating every conversation as disposable, the Notebook keeps them connected so you can return tomorrow and pick up where you left off.
The important detail for admins is that this does not replace anything. The Notebooks experience in OneNote stays exactly as it is. The Copilot app simply gains its own Notebooks surface, and the two stay in sync. Content created from a Notebook, including Word documents, PowerPoint presentations, Excel spreadsheets, and Copilot Pages, stays associated with that Notebook so the project record stays whole.
Why Copilot Notebooks Matter for Your Tenant
Most Copilot adoption stalls at the same place: people use it like a smarter search box, ask one question, and move on. They never build a habit around it. Copilot Notebooks change the shape of that habit by giving each project a home. That is a small design choice with a big behavioral payoff, because a persistent workspace is what turns occasional use into daily use.
There is also a governance angle worth calling out. Because Copilot Notebooks run under your existing Microsoft 365 Copilot policies, there is no separate admin toggle and no new permission model to learn. Whatever data boundaries, sensitivity controls, and access rules you already enforce continue to apply. That is the same principle behind Microsoft’s broader enterprise data protection in Microsoft 365 Copilot(opens in new window), where prompts and responses stay inside your tenant’s protection scope.
Copilot Notebooks and OneNote Stay in Sync
This is the part that will generate the most questions, so it is worth being precise. Copilot Notebooks in the Copilot app and Copilot Notebooks in OneNote are kept in sync. You can open a Notebook in either experience and keep working without losing context. The entry point and any existing Notebook data you already have remain in place, so nobody loses content on day one. The catch is purely a naming one: two surfaces, same name, one synced experience. Set expectations early and the confusion evaporates.
How to Use Copilot Notebooks
Once the rollout reaches your tenant, getting started takes only a few steps:
- Sign in to the Microsoft 365 Copilot app on the web at microsoft365.com.
- In the left navigation, select Notebooks to expand the list, then select All notebooks.
- Select New notebook and give it a name that maps to your project.
- Under references, add the chats, files, meeting notes, sites, and links you want Copilot to ground its answers in. You can upload files, pull from OneDrive, or drag and drop.
- Start prompting. Ask Copilot to summarize everything in the Notebook, surface key themes, or draft something new based only on the content you collected.
Because references update as your project evolves, the answers you get stay tied to the materials that matter rather than the whole tenant. Microsoft’s own walkthrough in Get started with Microsoft 365 Copilot Notebooks(opens in new window) covers the reference and sharing options in more depth.
Rollout Schedule
| Phase | Begins | Expected complete |
|---|---|---|
| Public Preview (Worldwide) | mid-June 2026 | early July 2026 |
| General Availability (Worldwide) | early July 2026 | late July 2026 |
According to Microsoft, this should be rolling out around mid-June 2026 for Preview and early July 2026 for General Availability. No admin action is required to enable it, and Microsoft has said it will update the original post with new documentation before rollout.
Licensing for Copilot Notebooks
The license story is simple. Copilot Notebooks in the Microsoft 365 Copilot app are available to users with a Microsoft 365 Copilot (Premium) license. If a user does not hold that license, they will not see the Notebooks surface in the Copilot app. There is no separate add-on or admin entitlement specific to this feature, and the experience is on by default for eligible users once rollout reaches the tenant.
If you are still mapping out who in your organization should hold a Copilot license, this is a good moment to revisit that plan, because Notebooks make the license noticeably more valuable for project-heavy roles.
Admin Tips
A few things to do before the rollout window opens:
- Get ahead of the naming. Send a short internal note clarifying that Notebooks is the workspace name in the Copilot app, and that Notebooks in OneNote remain available and unchanged. This single message will prevent the bulk of the confusion.
- Update your helpdesk article now. Reference Notebooks as the organizing workspace in the Copilot app so support staff are not improvising answers in week one.
- Confirm your Copilot policies are where you want them. Since Copilot Notebooks inherit existing Microsoft 365 Copilot policies, the time to tighten data boundaries is before, not after. If you are tightening Copilot grounding and connectors more broadly, my write-up on federated Copilot connectors for admins(opens in new window) pairs well with this change.
- Watch the adoption signal. Notebooks are a strong nudge toward daily Copilot use, so this is a natural checkpoint to revisit your earlier rollout of Copilot Notebooks features(opens in new window) and measure whether usage is actually moving.
The Paul-Take
Here is my honest read. The feature is good and the strategy behind it is smart. Microsoft knows the biggest threat to Copilot is not a competitor, it is the user who tries it twice and never builds a habit. A persistent project workspace is the right answer to that problem, and Copilot Notebooks deliver it cleanly.
But the rollout is going to test your communication, not your tenant. There is nothing to configure, nothing to approve, nothing to break. The only real risk is two surfaces sharing the name Notebooks and your users not knowing which is which. That is a documentation problem, and documentation problems are the ones IT teams love to skip until the tickets arrive.
So treat this as a comms project, not a technical one. One paragraph to your users before mid June, one updated helpdesk article, and you will have spent fifteen minutes to avoid a week of confused questions. That is the kind of trade I will take every time. Get the messaging out early, and Copilot Notebooks will land as the quiet productivity win it is meant to be.
MVP Reference List
- Microsoft 365 Roadmap ID: 562662(opens in new window)
- Message Center ID: not specified in the source post (add the MC number before publishing if you have it)
- Get started with Microsoft 365 Copilot Notebooks: https://support.microsoft.com/en-us/Microsoft-365-Copilot/get-started-with-microsoft-365-copilot-notebooks(opens in new window)
- Enterprise data protection in Microsoft 365 Copilot: https://learn.microsoft.com/en-us/microsoft-365/copilot/enterprise-data-protection