vs Copilot
Microsoft's own admin documentation is unusually specific about Copilot memory: what it stores, where it is kept, what deletes it, and which controls do not reach it. Read together, those details explain most of the confusion about why Copilot seems to forget.
Microsoft says it does, with a caveat printed at the top of its own admin guide: "Copilot personalization and memory are in preview and subject to change." That page, last updated September 2, 2026, is the closest thing to a published contract for the feature, and it is written for tenant administrators rather than for the person wondering why their Copilot forgot a project name.
The guide describes three distinct things under one word. There are saved memories, which you create deliberately. There are "details inferred from chat history," which Copilot derives on its own. And there are custom instructions, which are standing preferences. Microsoft groups all three as "memories" and says Copilot memory is available to Copilot Chat users "with and without a Microsoft Copilot license."
The most useful sentence for anyone debugging a forgetful Copilot is about the inferred layer: "Details from the chat history are dynamic. Copilot might update or discard older details as it learns what's most helpful to retain." Discarding is documented behavior, not a malfunction. If the thing you expected Copilot to remember was inferred rather than saved, Microsoft reserves the right to let it go.
In your mailbox. Microsoft states it plainly: "Memories, which include saved memories, details inferred from chat history and custom instructions, are stored in the user's Exchange mailbox in a hidden folder." The stated consequence is that memories "follow the same security and compliance policies as other mailbox data," and the page names Customer Lockbox and encryption at rest as examples.
That storage choice has a practical edge for administrators. The same page explains that memory is discoverable through eDiscovery and Microsoft Graph Explorer by searching the item class IPM.Contact, and notes that a user's ordinary contacts share that item class — so an export of everything in it returns the Copilot memory inside a CopilotMemory folder alongside actual contacts.
It also creates a gap worth knowing about before you rely on the feature. Microsoft writes that memory and personalization actions "don't generate audit log entries in Purview." Memory is discoverable after the fact, but the act of storing or applying it is not logged.
This is where most of the surprise lives. Microsoft says saved memories "are retained until the end-user explicitly deletes the saved memory in Settings > Personalization," and then adds the sentence that catches people out: "Deleting a chat doesn't delete saved memories that were generated from that chat." Clearing your history is not clearing your memory.
Turning the feature off is likewise not an erase. If the admin-level or user-level control is switched off, Microsoft says Copilot "is stopped from applying" custom instructions and saved memories, "but doesn't remove" them. The inferred layer behaves differently: with the control off, "all details from chat history are deleted after 30 days." Three kinds of memory, three different outcomes from the same switch.
The one deletion path that does cascade runs through the chats themselves. Microsoft says that if a user deletes every chat where a piece of information was originally shared or referenced, "then all traces of that information are deleted from the Chat History details within seven days" — which only reaches the inferred layer, not anything you saved on purpose.
Enhanced personalization, the tenant control that allows Copilot memory to be used, is on by default. Microsoft is explicit that no action is needed to enable it: "No action is required to turn on Copilot memory; you only need to turn off Copilot memory for end-users or the tenant if desired." Where the control is switched off, end users see the personalization toggles disabled and, in Microsoft's words, "can't turn on these settings."
Two admin expectations do not hold. Retention is the first: "Retention policies and retention labels configured in Purview by organization admins don't apply to Copilot memory," and Microsoft gives the concrete example that a delete-after-three-months policy on Copilot Chat interactions does not delete the memories. The page states there are no admin controls to enforce retention rules specifically for Copilot memory.
Content scoping is the second. Asked whether a tenant admin can restrict what information is added to memory, Microsoft answers: "No, admins can't restrict what type of information is added to Copilot memory." Custom instructions are also called out as not yet discoverable in eDiscovery or Content Search, though a user can export them manually from their own personalization settings.
Before debugging behavior, confirm the feature is present. Memory has been rolling out gradually, and on Microsoft's own Q&A a user asked in January 2026 why the memory feature was not in their Copilot or Copilot 365. The answer from Microsoft staff the following month was blunt about the remedy: "there's no way to install or force-enable it—it will appear automatically in your settings once your account is included in the rollout."
That same answer set expectations about scope, describing the feature as remembering things primarily when you explicitly ask it to, or inferring interests from activity, rather than being full conversational memory that automatically carries everything across sessions. The toggle is reached from the profile icon under settings, named "Personalization and memory" on consumer Copilot and "Enhanced Personalization" in Microsoft 365 Copilot.
The naming is its own obstacle. Consumer Copilot, Microsoft 365 Copilot, Copilot in Windows, and GitHub Copilot are separate products that share a word, and a support answer written for one does not necessarily describe another. When you search for why Copilot forgot something, the first step is establishing which Copilot you were using.
Fostera centers continuity on a named Soul rather than on a thread or a mailbox. Soul and project memory is selective, and it is meant to be read: retained entries are listed individually in a memory browser where you can inspect, edit, and delete them. Retrieval is relevance-based and can still miss a detail, which is why Custom Rules exist as an explicit home for durable voice, canon, or working preferences instead of leaving them to be inferred and later discarded.
The distinction that matters against Copilot's model is who decides what persists. Fostera does not infer a memory layer that it may quietly prune, and deleting is deleting rather than pausing. Projects group related chats, files, instructions, and project-scoped memories under the same Soul, and a structured JSON export of your account data is available from settings if you want a copy before changing anything.
Fostera also routes automatically among eligible engines, with manual selection available as a Premium feature, so a Soul's retained context does not have to be rebuilt when the engine behind a reply changes. Connected provider terms vary, and memory deletion cleanup may take up to 30 days. Choose Copilot when your work already lives in Microsoft 365 and you want memory governed by the same mailbox controls as the rest of your tenant. Choose Fostera when you want to see the memory, edit it, and keep it when you change models.
| Feature | Fostera | Copilot |
|---|---|---|
| Feature status | Memory is a shipped, core part of every Soul | Personalization and memory documented as in preview and subject to change |
| Where memory is stored | Soul and project memory you can open and read | A hidden folder in the user's Exchange mailbox |
| Memory visibility | Memory browser with individually editable entries | Saved memories listed in personalization settings; inferred details may be updated or discarded |
| Turning it off | Deleting a memory removes it | Switching the control off stops memories being applied but does not remove them |
| Deleting your chats | Memory is managed independently of transcripts | Deleting a chat does not delete saved memories generated from it |
| Model portability | Fostera routes automatically among eligible engines, and manual selection is a Premium feature | Microsoft's models inside Microsoft's own products |
| Age policy | Fostera is SFW for ages 13+, with confirmed guardian consent required for ages 13–17 | Governed by the Microsoft account terms that apply to you |
AI with persistent memory
How selective long-term memory works
Why Copilot forgets you
Which Copilot surface dropped your context
ChatGPT memory vs Fostera
Memory summaries and project boundaries
Claude memory vs Fostera
Chat search and project memory compared
Which AI model should I use
Match the engine to the work
Researcher Soul
Keep sources and decisions connected
Fostera privacy and providers
Which providers may process a request
Bring prior AI context
Start a Soul from an existing export
Does Copilot remember previous conversations?
Microsoft documents a memory feature covering saved memories, details inferred from chat history, and custom instructions, and describes it as in preview and subject to change. The inferred layer is explicitly dynamic: Microsoft says Copilot might update or discard older details as it learns what is most helpful to retain.
Where does Microsoft store Copilot memory?
In the user's Exchange mailbox, in a hidden folder. Microsoft says memories therefore follow the same security and compliance policies as other mailbox data, naming Customer Lockbox and encryption at rest, and that memory is discoverable through eDiscovery by searching the item class IPM.Contact.
Does deleting a Copilot chat delete what it remembered?
Not for saved memories. Microsoft states that deleting a chat does not delete saved memories generated from that chat, and that saved memories are retained until the user explicitly deletes them in personalization settings. Deleting every chat where a detail appeared removes it from the inferred chat-history layer within seven days.
Can my administrator control what Copilot remembers?
Only partly. Microsoft says admins cannot restrict what type of information is added to Copilot memory, and that Purview retention policies and labels do not apply to it. Admins can turn the enhanced personalization control off for a tenant, and can search, export, and delete memory data through eDiscovery and Microsoft Graph Explorer.
Why do I not have Copilot memory yet?
It has been rolling out in stages. On Microsoft's Q&A, staff answering a January 2026 question said there is no way to install or force-enable the feature and that it appears automatically once an account is included in the rollout. The setting is found from the profile icon under settings when it arrives.
Is Microsoft 365 Copilot memory the same as consumer Copilot memory?
They are different surfaces with differently named controls. Microsoft 365 Copilot uses an Enhanced Personalization control, while consumer Copilot exposes a personalization and memory toggle. Copilot in Windows and GitHub Copilot are separate products again, so a support answer about one does not necessarily describe another.
Further reading: Microsoft Learn: Manage Copilot personalization and memory
Continue with context
Start with one project. Or one companion. Either way, your Soul takes it from there and remembers the rest.
Start with one projectFree to start · No credit card required
Necessary cookies power sign-in and core settings. If you allow, optional cookies support product analytics, enhanced preferences, and personalized marketing. Read our Cookie Policy or Privacy Policy.