Four coworkers smile as they collaborate around a monitor displaying a colorful project-planning dashboard.
Microsoft plans to give Copilot Workspaces a memory. Roadmap entry 580869 is titled "Copilot Workspaces – Updated workspace memory." It says Work IQ will let Copilot keep useful context from how you work in a workspace, so later sessions don't start from nothing. If you have ever pasted the same project background into Copilot for the fourth time this week, this is the problem Microsoft says it is addressing.

The roadmap lists the feature as in development. Its dates are targets, and Microsoft can still change them.

Four coworkers smile as they collaborate around a monitor displaying a colorful project-planning dashboard. What the roadmap entry says​

According to the Microsoft 365 roadmap listing:

  • Feature: Microsoft Copilot (Microsoft 365): Copilot Workspaces – Updated workspace memory
  • Roadmap ID: 580869
  • Status: In development
  • Platforms: Desktop and Web
  • Cloud: Worldwide (Standard Multi-Tenant)
  • Preview target: November 2026
  • General availability target: December 2026

Microsoft describes the feature as Copilot using Work IQ to retain context from how a user works in a workspace. The goal is responses that are more relevant, consistent and personalized. The listing names three kinds of saved memory:

  1. Workspace details, meaning the background of the project or workstream
  2. Working preferences, meaning how you like the work done
  3. Recurring instructions, meaning the directions you would otherwise repeat every session

Microsoft says this should cut down on repeated setup and help users pick up work across workspace sessions.

The listing leaves a lot out. It gives no exact rollout day, no license requirement, no admin control, no retention period and no steps for viewing or editing what Copilot remembers. Keep that in mind when reading coverage that sounds more complete.

Section summary: Microsoft has announced the feature, but it hasn't shipped and its controls haven't been documented. Preview is targeted for November 2026 and GA for December 2026 on web and desktop.

First, what is a Copilot Workspace?​

Many readers may know this feature by its old name. Microsoft's support documentation says Copilot Notebooks is now Copilot Workspaces. A workspace is a shared place where a team keeps project files and information together and works with Copilot on an ongoing workstream.

Microsoft says the new version is built for teams first:

  • Several people can work across different documents at the same time.
  • Live cursors show what teammates are working on.
  • The team works with Copilot from shared context.

Microsoft separates Workspaces from Copilot Projects. Projects are for your own work and hold your chats, tasks, files and results. Workspaces are for group work. You can use both, and Microsoft says that as changes roll out you'll be able to move a file or other item from a project into a workspace to share it.

For existing users, Microsoft's support page says:

  • Existing notebooks become workspaces automatically, with their content intact.
  • A notebook that was already shared stays shared. Otherwise the workspace stays private.
  • No Notebooks features are being removed, and users don't need to move anything.
  • The phased rollout was due to start in late October 2026, with timing varying by organization.
  • The new collaborative experience appears first in the Microsoft Copilot app and will reach Copilot Workspaces in OneNote later.

There is a naming trap here. Microsoft also uses "workspaces" for an agent infrastructure layer in the Work IQ APIs. When it announced those APIs, Microsoft said Work IQ digital workspaces are within the Microsoft 365 tenant boundary, and store data, files, memory, progress, and intermediate outputs as agents reason through work. That describes the scratch space long-running agents use, not the team product that used to be Notebooks. Roadmap item 580869 is about the user-facing Copilot Workspaces. Don't assume the developer storage details apply to it.

Section summary: Workspaces is the renamed and more collaborative Notebooks. The memory update gives that shared project space a way to remember context between sessions.

Where Work IQ comes in​

Work IQ is Microsoft's name for the intelligence layer underneath Copilot. In a Microsoft 365 Blog post published for Ignite 2026, Microsoft said Work IQ grounds Copilot responses in a user's emails, meetings, chats, files and colleagues. It also said memory carries across sessions, so Copilot and custom agents built on Work IQ don't start over when the user switches tasks.

Microsoft Learn's Copilot Studio documentation divides Work IQ into three layers: Data, Memory and Inference. It describes Memory as a persistent understanding of how people and teams work. That page covers agents in Copilot Studio, so it confirms the general idea but tells us nothing about how memory inside Workspaces will be configured or controlled.

Microsoft's Inside Track team describes the same idea from its own internal deployment. It names the ability to retain persistent memory of each employee's role, responsibilities, and work context as an important part of Work IQ.

The roadmap item applies that memory to a particular container. Instead of a general memory of you across all of Copilot, this is context tied to a specific workspace. For a team running a product launch, a client engagement or a quarterly close, that could mean less time re-briefing Copilot and more time on the work.

The open questions​

Microsoft hasn't answered several questions that matter to both users and admins:

  • Who sees workspace memory? Workspaces are shared, but the roadmap describes memory built from how you work. It doesn't say whether one member's preferences shape answers for the rest of the team. Don't assume they do, and don't assume they don't.
  • Can users view, edit or delete it? Nothing in the entry describes a way to manage memory.
  • How long does it last? No retention period is listed.
  • What admin controls apply? Microsoft's Workspaces support page says core Microsoft 365 security, compliance and governance controls still apply. That statement covers the Notebooks-to-Workspaces transition, not this memory feature specifically.

Recent roadmap activity shows why these questions matter. In a separate roadmap item, ID 578869, Microsoft plans a December 2026 Work IQ MCP feature letting authorized agents read users' Copilot memories, subject to admin policy and personalization settings. WindowsForum's coverage of that item noted that a new admin policy controls access to memory through Work IQ MCP in the Microsoft 365 admin center and is enabled by default. That is a different feature from workspace memory. Still, it shows Copilot memory is becoming something other services can draw on, which makes it a governance topic.

Some third-party explainers say Work IQ personal memory is private to the user by default. Microsoft hasn't published an equivalent statement for workspace memory, so treat those claims as unconfirmed for this feature.

What admins and users can do now​

For IT admins:

  1. Watch Message Center. Microsoft directs admins there for organization-specific Workspaces rollout timing. Expect any memory-specific notice to appear there too.
  2. Treat November and December as targets. The status is "in development," and the roadmap page itself says all information is subject to change.
  3. Revisit your Copilot memory and personalization policies. Workspace memory adds another place where context persists. Note how memory is already handled in your tenant before this feature arrives.
  4. Brief the people who own sensitive workspaces. Until Microsoft documents how workspace memory is shared, workspaces for HR, legal or deal work deserve extra attention during preview.

For end users:

  • Office Watch's practical advice on Work IQ is to review your Copilot Memory settings in the Microsoft 365 Copilot app and understand what it can remember about you. That is good advice before any memory feature expands.
  • When the preview reaches you, test it with harmless instructions first, such as a formatting preference or a recurring summary style. Check that Copilot applies them before you rely on it for anything that matters.

Analysis: a useful convenience that needs clear controls​

On the user side, this is a sensible upgrade. Re-establishing context is one of the most tedious parts of working with AI assistants. A workspace that remembers that "this client wants British spelling, the budget figures live in the Q3 tracker, and summaries go in bullet form" saves real time, and the time adds up across a team.

The risk is in the details Microsoft hasn't published. Memory that is invisible or hard to edit can turn into stale assumptions. If Copilot keeps applying an instruction from three sprints ago, convenience becomes confusion. In a shared workspace, the line between "my preferences" and "the team's context" needs to be clearly drawn and visible to the people using it. Microsoft's broader Work IQ messaging stresses permissions and governance, which is encouraging. What's still missing is documentation specific to Workspaces: what gets stored, who can see it, and how to clear it.

Until that documentation appears, treat the feature as a promising preview to try in low-risk workspaces before rolling it out widely.

 

References

  1. Microsoft Copilot (Microsoft 365): Copilot Workspaces - Updated workspace memory Microsoft 365 Roadmap 2026-11-17T18:36:41.967573Z
  2. Announcing the new Work IQ APIs microsoft.com
  3. What's new in Work IQ at Ignite 2026: agents that get work done | Microsoft Community Hub techcommunity.microsoft.com