Copilot Memories: What “Will Not Be Deleted” Means
A notice about memories surviving a deletion usually describes the scope of that action. Check saved memories, chat history, and retention separately.
Updated 5 min read
If a Copilot notice says memories created will not be deleted, read it as a warning about what that particular action leaves behind. It does not establish that memories are impossible to delete; you need to identify the product, the action, and the separate memory controls.
Deleting a conversation, disabling personalization, and deleting a saved memory answer different questions. Tools like fenbs let you record a deliberate policy for the work context you choose to retain, but they cannot perform or verify a deletion inside Microsoft’s systems.
What exactly does the notice apply to?
Read the complete dialog before interpreting one sentence. Identify whether you are deleting a chat, clearing activity history, turning off a toggle, or removing saved memories. The object named beside the action matters more than a broad expectation that “delete” clears everything associated with an account.
The exact phrase alone is insufficient to identify a universal Copilot policy. If it appears while deleting a conversation, it warns that the conversation action does not cover memories. If it appears beside a setting, check the explanation for that setting instead of assuming the same consequence.
For example, clearing a hypothetical planning chat may meet your goal of removing that thread from the visible list. Removing a preference extracted from it is a second goal. Name both goals before choosing the controls, so the result is something you can check.
Write down the app, account type, action, and notice wording if you need support. Do not include the private memory itself in a screenshot or support message unless the support process requires it and you have checked how that information will be handled.
Which information might have separate controls?
| Record | What you are checking | What not to infer |
|---|---|---|
| Saved memory | An extracted preference or fact in the memory management view. | Deleting its source conversation necessarily removes the entry. |
| Chat or activity history | The prompts and responses available in the account’s history controls. | Clearing that view proves every retained copy is gone. |
| Personalization from past work | Whether applicable history or work-insight controls remain enabled. | An empty saved-memory list explains every answer. |
| Saved documents | Files containing outputs you deliberately kept. | A chat deletion also edits those files. |
Think of the table as a checklist, not a claim that every product uses all four records. A personal account and an organization’s account can expose different controls. GitHub Copilot is a separate coding product; Microsoft Copilot app settings do not manage its memory.
Keep the project’s storage policy explicit with fenbs Decisions and rules: what may be retained, where it belongs, and who approves changes to that policy.
How do you check the personal Microsoft Copilot app?
For the updated personal app, Microsoft’s privacy controls (opens in a new tab) separate Saved memories from chat history. Open Settings, Personalization, and Manage beside Saved memories to inspect or delete entries. Turning the memory toggle off does not automatically delete entries already saved.
Use the actual delete control when removal is your goal. Turning off a feature and clearing its existing contents are separate actions in this interface. Reopen the management view afterward so you can check what the product now displays.
For broader history cleanup, follow Microsoft’s personal account activity-history guide (opens in a new tab). Choose the relevant Copilot activity category in the privacy dashboard and read the confirmation. Do not assume you cleared every category because one list is empty.
What changes with a work or school account?
For Copilot Chat using a Microsoft 365 account, the saved-memory guide (opens in a new tab) routes you through Settings and more, Chat settings, Personalization, and Manage saved memories. Its delete controls are separate from the switch that stops memory saving.
Microsoft’s personalization guidance (opens in a new tab) also distinguishes saved memories from history inferences and work insights. Removing a saved entry may therefore be only part of the review. Follow the relevant history controls and consult your organization’s administrator when work content is involved.
Avoid promising a colleague that their information has been erased based only on what disappeared from your screen. Ask the administrator which retention policy applies and what a user’s deletion request changes. Keep an ordinary cleanup request separate from a formal organizational records process.
If you were investigating ignored written instructions rather than removal, our Copilot instructions troubleshooting guide covers that separate behavior. Changing an instruction is not a substitute for using deletion controls.
How can you verify the result without overclaiming?
- Confirm that you are still signed in to the intended account and product.
- Reopen the saved-memory management view and check whether the selected entry remains.
- Check the separate conversation or activity-history view if you also requested history deletion.
- Read the help page for the action’s processing and retention behavior. Keep any confirmation or request status the service provides.
- If the display and documentation disagree, contact Microsoft support or your administrator with the action, time, and account type, without unnecessary private content.
For work and school accounts, Microsoft says an activity-history deletion request (opens in a new tab) can take time to complete, and an open app may continue to display previous activity until reopened. The same page explains that content already saved in files remains.
A conversational test can help identify a continuing problem, but it cannot certify deletion. If you repeat the supposedly removed fact in the test question, you have supplied it again. Ask a neutral question in a fresh conversation if you test behavior at all, and judge the settings and request status separately.
Choose what the next assistant should retain
Use fenbs to record a person-approved policy for saved work context, such as keeping project decisions while excluding private client details. Rules appear first when a connected assistant reads the project context. Save the policy and the outcome of a review without copying the information you intended to remove.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account and add a project for the work you deliberately want to preserve.
- Record the person’s decision about what belongs in shared context. Give the rule a clear scope and reason rather than a vague instruction to remember everything.
- Add only approved, necessary project facts as AI context notes. Keep a task for reviewing outdated context if more checks remain.
- Connect a supported assistant through Integrations, ask it to read the rules before work, and save progress with the review’s remaining steps.
fenbs does not connect to the consumer Microsoft Copilot app or delete its memories. It is not the right fit for erasing Microsoft account data. Use it when you want an explicit work record across supported assistants, and remember that anything you deliberately copy there becomes another record to manage.
For the separate coding product, GitHub Copilot agent troubleshooting addresses execution problems. For more on keeping context under deliberate control, explore the AI memory hub.