Microsoft Copilot Notebooks: The Memory Layer That Could End AI Amnesia, Coming June 2026

Microsoft is adding a persistent memory layer to its web-based Copilot app via redesigned Notebooks, previewing in June 2026 and going live in July. The feature lets users collect chats, files, and outputs in project-specific containers, allowing Copilot to ground future answers in prior context—finally addressing the “amnesia problem” of AI assistants. For admins, it raises urgent governance questions around retention, permissions, and sensitive data, while users gain a friction-free way to maintain continuity across complex, multi-session work.

Microsoft plans to roll out a redesigned Copilot Notebooks experience in the Microsoft 365 Copilot web app, with preview available in June 2026 and general availability in July 2026. The feature, tracked under Roadmap ID 562662, turns ephemeral AI conversations into persistent workspaces—allowing Copilot to remember project context across sessions.

What’s Actually Changing

The update brings a dedicated Notebooks pane to the web-based Microsoft 365 Copilot app (formerly known as the Office app). Instead of starting every chat from scratch, users can now create a Notebook—a container that collects related conversations, generated outputs, uploaded files, and reference links. Copilot then uses that accumulated material to ground future responses, reducing the need to re-explain background, goals, or constraints.

This isn’t a standalone app. It lives inside the Microsoft 365 Copilot hub, which already aggregates chat, search, agents, and Copilot Pages. The new Notebooks surface is designed for quick continuity: a lightweight project bucket that stays attached to the tasks at hand. Microsoft is careful to distinguish it from the richer, section-and-page-based Copilot Notebooks already available in OneNote, which target more structured, long-term research.

According to Microsoft’s support documentation, a Notebook in the Copilot app lets you “gather related chats, Copilot outputs, and references in one place so Copilot can ground its responses in that accumulated context.” That grounding mechanism is the breakthrough—it means the AI can pull from your prior work without needing explicit prompts to “remember X.”

What It Means for You

Everyday Users and Power Users

If you’re juggling multiple projects—say, a quarterly budget, a client proposal, and an internal policy draft—you can now give each one its own Notebook. No more copy-pasting the same background brief every morning. Copilot already knows the tone, the files you’ve reviewed, and the open questions you flagged last week. The payoff is immediate: faster, more coherent assistance that feels like a colleague, not a very forgetful intern.

IT Administrators and Governance Teams

Persistent context is also persistent responsibility. A Notebook can accumulate sensitive documents, strategic decisions, and draft deliverables—turning it into a business record that needs retention schedules, access controls, and eDiscovery coverage. Because Notebooks rely on SharePoint or OneDrive storage in commercial tenants, they inherit Microsoft 365’s existing permission model. But that doesn’t automatically apply sensitivity labels or data loss prevention policies. Admins should treat Notebooks like any collaborative workspace: map them to your information architecture before users start dumping confidential material inside.

Developers and Power Automate Builders

The roadmap entry doesn’t mention APIs or connectors, but Notebooks will likely become a component of Microsoft’s agent platform. If a Notebook can hold project context, a custom agent could one day read that context to automate workflows. For now, assume no direct developer hooks, but watch for future Graph API endpoints.

How We Got Here

Microsoft’s AI journey started with sprinkling Copilot buttons into Word, Excel, and Teams. The first generation was all about access: put a chat box everywhere and let users ask questions. But the “amnesia problem” quickly surfaced—every interaction was a clean slate, forcing workers to rebuild context repeatedly.

The company began stitching together a memory fabric. Copilot Pages (2024) made generated content shareable and editable. OneNote’s Copilot Notebooks (2025) introduced a deliberate, binder-like space for project material. Now the redesigned Copilot app Notebooks pull that idea into the primary AI entry point. It’s part of a broader shift from prompting to place: making AI-assisted work durable, not disposable.

What to Do Right Now

For Users:
- Start thinking in Notebooks. For recurring projects or frequent workflows, create a dedicated container as soon as the feature hits your tenant.
- Verify grounded answers. Better context reduces hallucinations but doesn’t eliminate them—always review output that affects decisions.

For Admins:
- Check licensing. Notebooks require Microsoft 365 Copilot or Copilot Chat licenses, with commercial plans needing the appropriate service plans enabled.
- Prepare governance guidance by July 2026. Classify what belongs in a Notebook (short-term ideation vs. regulated records), set retention policies, and update acceptable use policies to cover AI-generated content in persistent workspaces.
- Communicate the staggered rollout. Preview starts June 2026, GA in July, but not all tenants will see the feature simultaneously. Help desks should expect interface inconsistencies across users.

Outlook

Notebooks represent Microsoft’s bet that enterprise AI’s next frontier isn’t smarter models—it’s better memory. If users can inspect and trust the context Copilot is using, the tool could graduate from a sidebar curiosity to a project command center. But if the context becomes a black box, adoption will stall. The biggest test arrives later this year: whether the Notebooks experience can survive the messiness of daily work without becoming just another information silo.