How to Clear Microsoft Copilot Memory

To clear Microsoft Copilot’s saved memory, open the memory management controls for your signed-in account and delete individual entries or the full saved list. Turning off a memory switch is not the same as deleting saved entries, and conversation history needs separate attention. fenbs keeps only the project context you deliberately record, independently of what you remove from Copilot.

Choose the outcome before clicking: correct one old preference, remove all saved memories, or stop earlier information from influencing future conversations. Then confirm whether you are in the consumer app or a Microsoft 365 work or school experience. Their menus and related controls differ.

How do you delete memories in the personal Copilot app?

1. Sign in to Microsoft Copilot with the personal Microsoft account you intend to change.
2. Open Settings, then Personalization.
3. Choose Manage beside Saved memories.
4. Delete the unwanted entry, or choose Delete all memories to clear the saved list.

These are the controls in Microsoft’s privacy guidance for individuals↗ (opens in a new tab). Review the displayed list afterward. To prevent future saving, use the separate Saved memories toggle; switching it off does not automatically remove entries already saved.

For one inaccurate preference, a targeted deletion is easier to verify than clearing everything. Read the full entry first so you know what you are removing. If the same statement appears in a prompt you use repeatedly, correct that prompt too. Otherwise, a later conversation can receive the old detail again.

How do you remove saved memories in a work account?

1. Sign in to Copilot Chat with the intended Microsoft 365 account.
2. Open Settings and more, then Chat settings and Personalization.
3. Open Manage saved memories on the Saved memories tile.
4. Delete the individual memory, or choose Delete all memories for the full saved list.

Microsoft’s saved-memory management guide↗ (opens in a new tab) documents this path. Again, turning Saved memories off and deleting existing memories are separate actions. Check the signed-in account before repeating these steps in another browser or app.

If you cannot find the controls, capture the menu labels and account type for the person helping you. Do not treat a missing control as evidence that the account has no stored information. For ongoing enablement and account differences, use Copilot memory settings; this guide focuses on removal.

What if the information also came from earlier chats?

A saved entry is only one possible source. Microsoft’s Copilot Chat history guidance↗ (opens in a new tab) documents turning off Chat history under Personalization to remove chat-derived inferences. A work account may label it Chat history & work insights. Follow the linked guidance for the deletion period and the effect of re-enabling it before that period ends.

Delete an unwanted conversation separately when you also want it removed from visible history. In the consumer app, Microsoft’s conversation history guide↗ (opens in a new tab) describes each conversation’s Delete action and the Microsoft-account dashboard option for deleting all activity history. Use the account-specific instructions rather than applying a workplace portal path to a personal account.

For work or school activity history, Microsoft provides a separate deletion process↗ (opens in a new tab) in My Account under Data and Privacy, Data options, and Copilot activity history. That request concerns activity history. It does not remove content already saved in a file, such as a revised document.

Work information also needs care at its source. Removing personalization is not a request to delete an email or document. If an underlying work record is wrong, use the organization’s normal process to correct it. Microsoft’s personalization explanation↗ (opens in a new tab) explains how saved memories and other personalization sources fit together.

How can you check the result without teaching the detail again?

Begin with the management screen, not a question that repeats the information. If you ask “Did you forget that my old project is called Cedar?”, you have just supplied the project name in the current message. An answer using Cedar would not prove a deletion failure.

1. Reopen the relevant management list and confirm the entry is absent.
2. Check that any separate history or personalization action you intended was also completed.
3. Start a fresh appropriate conversation without including the old detail in your question.
4. If the detail returns, review the other sources available to that session before drawing a conclusion.

Keep the difference between an interface check and a full data deletion clear. Seeing an empty list establishes what the interface displays. It does not independently verify every retention process. If you need help with an account-specific deletion result, give Microsoft support the account type and exact control used without sending unnecessary private conversation contents.

The Copilot and ChatGPT comparison covers the broader assistant choice. These Microsoft steps also do not clear GitHub Copilot memory, which belongs to the separate development product.

Which work facts should you preserve deliberately?

Before a broad cleanup, decide which current work outcomes still belong in your maintained project record. Keep the approved answer and next action, not a copy of everything you are trying to remove. For example, you might preserve that a design was approved while leaving out the personal discussion that preceded it.

• The project goal and active tasks that still need work.
• Decisions people have made, with their scope and reason.
• What was actually checked and the result of those checks.
• The next action, open question, or approval needed.

Review the content before recording it elsewhere. Moving an unnecessary detail into another tool defeats the purpose of removing it. The general agent memory explanation helps distinguish personalization from a deliberate record, while fenbs shows how project context is kept with tasks and decisions.

How to retain chosen project context with fenbs

1. Create a free account, free for one person with no credit card, and add your project.
2. Add the current task and manually write only the work facts you need to keep.
3. Record a person’s approved decisions in Decisions and rules, leaving unresolved choices open.
4. Use Integrations to connect a supported assistant over MCP, a standard way for an AI app to use an outside tool. Ask it to read context first and save progress before stopping.

fenbs is not the right fit if your goal is to erase Microsoft-held data or change Copilot settings. It does not connect to consumer Microsoft Copilot. It gives deliberately retained work a separate home; Microsoft’s own controls handle deletion in Microsoft’s products.

After cleanup, maintain a smaller record: current decisions, useful sources, and a clear next step. Review it when the work changes instead of rebuilding a transcript collection. The AI memory hub covers other ways to keep context correct and inspectable.