How to Delete Copilot Chat History: Staff and Admin Steps

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Delete Copilot Chat History: Staff and Admin Steps.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Delete Copilot Chat History: Staff and Admin Steps.

Staff delete one Copilot chat from the Chats list in Copilot Chat (More, then Delete) and wipe all their Copilot activity at My Account, Data and Privacy, Data options, Copilot activity history. Admins work in Microsoft Purview instead: retention policies delete Copilot interactions on a schedule, and an eDiscovery search plus a purge request removes specific items.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Deleting is not the end of it. A retention policy or hold can keep a searchable copy for months, saved memories survive when the chat that created them is deleted, and anything Copilot helped write into a saved document stays in that document. The steps below cover each of those, plus what to do when someone leaves.

How do staff delete one Copilot chat or their whole history?

Staff delete a single Copilot conversation from the Chats list in Copilot Chat by selecting More next to its title and choosing Delete, and they delete all Copilot activity from the My Account portal.

Delete one conversation

  1. Go to Copilot Chat and sign in with your work account.
  2. Find the Chats list in the left-side navigation and select the conversation.
  3. Next to the chat's title, select More (…). The menu offers Rename, Move to notebook and Delete.
  4. Select Delete. Microsoft describes this as deleting the conversation from your chat history.

Delete all Copilot activity history

  1. Sign in to the My Account portal (myaccount.microsoft.com) with your work or school account.
  2. Go to My Account, then Data and Privacy, then Data options, and open the Copilot activity history section.
  3. Select Delete.
  4. In the Delete Copilot activity history dialog, tick the Microsoft Copilot checkbox.
  5. Select Delete to send the request to Microsoft.

Microsoft's delete your Copilot activity history page adds three details staff should know. The delete is a request and can take some time to complete. An app that is open when you delete may keep showing old history until you close and reopen it. And the option covers every app at once: Excel, Forms, Loop, OneNote, Outlook, Planner, PowerPoint, Teams, Whiteboard, Word and Copilot Chat. You cannot clear Word but keep Teams.

Staff who also use Copilot with a personal Microsoft account manage that history separately, in the Copilot activity history section of the personal privacy dashboard (account.microsoft.com/privacy), where they can export a CSV file or choose Delete all activity history. Your business's controls in this tutorial are built around work accounts, which is one more reason to require work accounts for work.

What does deleting Copilot history not remove?

Deleting Copilot history does not remove content saved into files, saved memories, copies kept by a retention policy or hold, or custom instructions. Each of those needs its own step, and some need an admin.

What survives the deleteWhyWho removes it, and how
Text Copilot helped write into a saved Word, Excel or PowerPoint fileMicrosoft says saved changes are not removed when history is deletedThe file's owner edits or deletes the file
Saved memoriesDeleting a chat does not delete memories generated from itThe user, under Personalisation, Saved memories; or an admin through eDiscovery
Details inferred from chat historyKept separately from the chatsCleared within seven days once every chat that mentioned them is deleted, or 30 days after Chat history is switched off
Copies under a retention policy, litigation hold or eDiscovery holdRetained copies sit in a hidden mailbox folder and stay searchableKept until the policy period ends; an admin can purge specific items after lifting the hold
Custom instructionsStored with memories; not discoverable in eDiscovery yetThe user, in Settings, Personalisation
Web search queries Copilot sent to BingSearchable in eDiscovery as part of Copilot activityAn admin, through eDiscovery

When the chat is gone but the words are not

An illustrative slip from a veterinary practice: a receptionist asked Copilot in Outlook to draft a reply to an upset client, pasted in the client's full complaint with their address, then deleted the Copilot chat once the reply was sent. The chat was gone, but the draft reply, sitting in the Sent folder with the address quoted back, was an ordinary email and untouched by any Copilot deletion. So was the complaint summary she had saved into a Word file for the practice manager. Deleting Copilot history cleans up the conversation with Copilot, not the places its output travelled to, so the clean-up list always includes sent emails, saved files and anything copied into other systems.

The retained-copy row surprises people most. Microsoft's retention documentation is blunt about it: messages visible in your AI apps are not an accurate reflection of whether they are retained or permanently deleted. A chat that has vanished from a staff member's screen can still turn up in an admin's search.

How do staff clear Copilot memory as well as chats?

Staff clear Copilot memory under Settings and more, Chat settings, Personalisation, where Manage saved memories deletes memories singly or all at once and the Chat history toggle clears inferred details after 30 days.

  1. In Copilot Chat, select Settings and more (…) at the top right.
  2. Select Chat settings, then Personalisation.
  3. Find the Saved memories tile and select Manage saved memories.
  4. Delete individual memories with the trash icon, or select Delete all memories.
  5. To stop Copilot using past chats at all, turn off the Chat history toggle (on work accounts it may read Chat history & work insights). Inferences from previous chats are deleted after 30 days; switching the toggle back on within those 30 days restores them.

Turning the Saved memories toggle off is not the same as deleting: Microsoft says it stops new memories but leaves existing ones in place until they are deleted. For a fuller comparison of what each assistant keeps, see what ChatGPT, Claude, Gemini and Copilot remember at work.

Admins have a tenant-wide switch too. Microsoft documents an Enhanced personalisation control, on by default and set through Microsoft Graph, that turns memory off for users. Two limits matter: switching it off stops Copilot applying saved memories but does not delete them, and Microsoft says admins cannot restrict what type of information goes into memory. Memory actions also do not generate audit log entries in Purview.

Can admins delete a user's Copilot history?

Admins can delete a user's Copilot prompts and responses by creating an eDiscovery case, searching for the Copilot activity, then sending a purge request through Microsoft Graph Explorer. Holds and retention policies on that mailbox must be lifted first.

Microsoft stores every Copilot prompt and response in a hidden folder of the user's Exchange mailbox, which is why the admin route runs through eDiscovery. The documented workflow, from Microsoft's search for and delete AI application data page:

  1. Check permissions. Creating the case and search needs membership of the eDiscovery Manager role group. Deleting needs the Search And Purge role, which the Data Investigator role group has by default.
  2. Create an eDiscovery case in the Microsoft Purview portal.
  3. Create a search using the item class condition with the Copilot activity option, scoped to the user's mailbox, plus a date range or keywords so it returns only what you mean to delete.
  4. Review the results. The purge deletes everything the search returns, so check a sample first.
  5. Remove holds and retention policies from the affected mailbox, and write down which ones, because otherwise the data is retained anyway.
  6. Purge. In Graph Explorer, signed in with the Search And Purge role, find the case ID and search ID, then send the purgeData request for that search.
  7. Reapply the holds and retention policies once you have confirmed the deletion.

Three limits shape how long this takes. Microsoft caps removal at 10 items per mailbox at a time, because the feature is designed as an incident-response tool rather than a bulk cleaner. The user receives no notification that anything was deleted. And purged items move to the hidden SubstrateHolds folder for at least one day before a timer job, which typically runs every one to seven days, deletes them permanently.

The same route reaches memories. Saved and inferred memories are discoverable in eDiscovery under the IPM.Contact item class (the same class as ordinary contacts, so filter carefully), and admins can purge them with Graph Explorer. Deleting a conversation through Purview does not delete the related memory, so search for both.

How do retention policies control how long Copilot chats are kept?

A Purview retention policy with the Microsoft Copilot experiences location keeps Copilot prompts and responses for a set period, deletes them after a set period, or both, regardless of what staff delete on screen.

The path in the Microsoft Purview portal is Solutions, then Data Lifecycle Management, then Policies, then Retention policies, then New retention policy. Name the policy, choose Static (adaptive scopes need extra licences and set-up), select the Microsoft Copilot experiences location, then decide whether to retain content, delete it, or both. Note that the name, scope type and most retention settings cannot be changed after saving; only the retention period can.

The timings are slower than most people expect. Microsoft's retention page explains that a background job typically takes one to seven days to act, expired items then sit in SubstrateHolds for at least a day, and a second job run deletes them. Its own example shows a delete-only policy set to one day taking up to 16 days to remove a message permanently.

Policy choiceA chat the user deletesA chat the user never deletes
Retain 1 year, then deleteHidden from the user at once; kept and searchable until a year from creation, then removed within about two weeksVisible to the user for a year, then removed within about two weeks
Delete after 90 days (delete-only)Removed within about two weeks of deletionRemoved within about two weeks after day 90
Retain foreverHidden from the user; kept indefinitely and still searchableKept indefinitely

Any other retention policy for the same location, a litigation hold, a delay hold or an eDiscovery hold suspends permanent deletion. When two rules disagree, keeping wins over deleting.

A date for your diary: older policies used a combined location called Teams chats and Copilot interactions. Microsoft says that from 15 January 2027, Purview will treat those policies as Teams-only, and Copilot interactions, both old and new, will no longer be retained or deleted by them. If your Copilot rules live in one of those policies, create a new policy with the Microsoft Copilot experiences location before that date.

How long to keep Copilot chats is a business decision, and the useful test is what the chats feed into. Three illustrative choices: a care agency whose coordinators draft care-plan summaries with Copilot might keep chats for as long as it keeps those drafts, so it can show how a record was written if a complaint arrives; an optician that only uses Copilot for emails and rotas might pick 90 days, because the finished records live in its practice system; a music school using Copilot for lesson ideas might choose a delete-only policy at 30 days. Where records carry legal minimums, ask your adviser for the period rather than guessing.

Check the licence before you rely on a Copilot retention policy. Microsoft's Purview service description lists Microsoft 365 E3 or E5 with Microsoft 365 Copilot as the licences that give user rights for retention policies covering Copilot interactions, while Business Premium appears in its list for organisation-wide retention policies in general. If you are on a Business plan, ask your Microsoft partner to confirm what your licences cover. Audit (Standard) for Copilot interactions is listed for Business Basic, Standard and Premium, and those audit logs are generated only when Copilot is licensed and in use.

A care agency's medication-list mistake, cleaned up in eight days

Here is the whole process with illustrative numbers. A home-care agency has 12 office staff on Microsoft 365, six of them with Copilot licences. Last spring the owner set a retention policy on the Microsoft Copilot experiences location: retain for one year, then delete.

On a Monday at 10 am, a care coordinator pastes a client's medication list, doctor's details and a relative's phone number into Copilot Chat to draft a care-plan summary. The chat runs to 14 prompts and 14 responses: 28 items. The office manager spots it at 10:40 am. What happens next:

  1. 10:45 am, the coordinator deletes the chat from the Chats list and opens Manage saved memories, where Copilot has saved one memory naming the client. She deletes it. Time: five minutes.
  2. 10:50 am, the coordinator opens the care-plan document Copilot helped draft. The summary belongs there, but the relative's phone number does not, so she removes it and saves.
  3. 11:00 am, the owner, who holds the eDiscovery Manager role and the Search And Purge role, creates a case and a search: Copilot activity, the coordinator's mailbox, that Monday's date, the client's surname as a keyword. The search returns 28 items.
  4. 11:30 am, the owner excludes the coordinator's mailbox from the one-year retention policy and notes the change on the incident log. Without this, the one-year policy would keep every item.
  5. 11:45 am, the purge. At 10 items per mailbox per run, 28 items need three purge requests: 10, 10 and 8, rerunning the search between each to confirm what is left.
  6. Days 2 to 8, the items sit in SubstrateHolds for at least a day, then the timer job deletes them permanently. A final search on day 9 returns nothing, and the owner reapplies the retention policy to the mailbox.

The quick sum: about two and a half hours of the owner's time the first time (permissions, case, search, purges, log), 15 minutes of the coordinator's, and up to eight days before the items are gone for good. The second incident takes under an hour because the roles and the saved search already exist.

The agency keeps a simple deletion log for each incident: date, mailbox, search name, item count, purge runs, the policy excluded and the date it was reapplied.

If keeping that log, or checking the item counts in a spreadsheet, is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.

The rule that prevents the next one is better than any purge: decide what staff must never paste into an AI tool at all. What an aged-care AI policy should cover and what staff must not paste has wording a care business can adapt.

What should happen to Copilot history when someone leaves?

A leaver's Copilot history sits in a hidden folder of their mailbox, so it follows your mailbox decision: keep it, convert it to shared, or delete the account, which starts a 30-day restore window.

Microsoft's guidance for deleting a user covers the mailbox and OneDrive side; add the Copilot items to it. A filled-in leaver checklist for the care agency's departing coordinator (illustrative):

Leaver: Care coordinator   Last day: Friday 4 December   Owner of checklist: office manager

[x] 1. Decide on Copilot history: keep for 1 year under the Copilot retention
       policy (care-plan drafting may matter in a complaint). No purge needed.
[x] 2. Ask the leaver to copy any Copilot output the team still needs into
       documents in the shared care-plans folder before the last day.
[x] 3. Check Saved memories with the leaver and delete any that name clients.
[x] 4. Email: give the new coordinator access, which converts the mailbox to a
       shared mailbox (no licence needed). Don't delete that account later.
[x] 5. OneDrive: move files to the shared folder within 30 days.
[x] 6. Copilot licence: reassign to the new coordinator rather than remove it,
       because an annual commitment cannot be reduced mid-term.
[ ] 7. If the account is deleted later: 30 days to restore; mailbox content
       under a retention policy moves to an inactive mailbox and stays
       searchable for the policy period.
[x] 8. Record on the leaver file: where the history is kept and until when.

Each line comes from Microsoft's own behaviour. Giving another user access to a deleted user's email converts the mailbox to a shared mailbox, and Microsoft says not to delete an account that has been converted to a shared mailbox or set up for forwarding. After deletion there are 30 days to restore the account. OneDrive files should be moved within the OneDrive retention period, 30 days by default. Licences bought on an annual plan cannot be removed from the subscription until the commitment ends, so reassigning the Copilot seat is usually the cheaper move. And Microsoft's retention documentation says that when an account is deleted, Copilot messages subject to retention are stored in an inactive mailbox, still covered by the policy and available to eDiscovery.

The wider offboarding job, including AI tools outside Microsoft 365, is covered in the staff offboarding checklist for AI tools and shared accounts, and the ownership question behind it in who owns AI chat history when an employee leaves.

How do you check that a Copilot deletion really worked?

Checking a Copilot deletion means rerunning the same eDiscovery search until it returns nothing, because purged items stay searchable in a hidden folder until Microsoft's timer job removes them, which typically takes days.

The screen a staff member sees is not the test. Microsoft says deleted items in the SubstrateHolds folder remain searchable until they are permanently deleted, so a search the same afternoon will still find them, and that is expected rather than a failure. Here is the care agency's check sheet, filled in (illustrative):

WhenCheckResult
Monday, after each purgeGraph Explorer responseGreen banner saying the request was accepted, three times
Monday, 1 pmRerun the saved search28 items still found: in SubstrateHolds, as expected
WednesdayRerun the saved search28 items still found; the timer job has not run yet
Following Tuesday (day 9)Rerun the saved search0 items; retention policy reapplied to the mailbox
Day 9Retention policies page, the policy's statusNo Error shown in the distribution status
Day 9Coordinator closes and reopens Copilot; checks Chats and Saved memoriesChat and client memory both gone

If a policy's status shows an error after you reapply it, Microsoft's retention guidance suggests retrying distribution in PowerShell with the RetryDistribution switch; its page lists which of its two retention cmdlets applies to each location. Record the final zero-result search in the incident log; it is your evidence that the clean-up finished, which matters if a client or regulator ever asks what happened to the data.

Which Copilot deletion controls does each role have?

Staff control their own chats, history and memories; admins control retention, purges, memory switches and audit. This table puts every control in one place.

ControlWhoWhereLimits
Delete one chatStaffCopilot Chat, Chats list, More, DeleteRetained copies may remain
Delete all Copilot activityStaffMy Account, Data and Privacy, Data optionsAll apps at once; takes time
Delete memoriesStaffSettings and more, Chat settings, PersonalisationSeparate from chats
Turn memory off for everyoneAdminEnhanced personalisation control, via Microsoft GraphStops use, does not delete
Keep or delete on a scheduleCompliance adminPurview, Data Lifecycle Management, Retention policiesDays of delay; holds win; check licence
Purge specific itemsAdmin with eDiscovery Manager and Search And PurgePurview eDiscovery plus Graph Explorer10 items per mailbox per run; lift holds first
See that Copilot was usedAdminPurview Audit (Standard)Only when Copilot is licensed and in use

If you want help fitting these controls into how your agency, practice or firm actually runs, I offer one-to-one AI consultations for small businesses.

What should staff be told about deleting Copilot chats?

Staff should be told three things: deleting a chat hides it from them but may not delete the business's copy, some mistakes must be reported rather than quietly deleted, and memories need deleting separately.

Without that note, the natural reaction to pasting the wrong thing is to delete the chat and say nothing, which leaves the retained copy in place and the admin unaware. A short notice that works, filled in for the care agency:

Copilot chats at [agency name]: what deleting does

1. Deleting a chat removes it from your screen. Our retention policy keeps
   a copy of Copilot chats for 1 year, which managers can search if needed.
2. If you paste client health details, addresses or family contacts into
   Copilot by mistake: delete the chat, then tell [office manager] within
   the hour so the business copy can be removed too. Nobody is in trouble
   for reporting it.
3. Copilot can save memories about you and your work. Check them monthly:
   Settings and more > Chat settings > Personalisation > Saved memories.
4. Use your work account for work. Chats in a personal Copilot account are
   outside our control and our retention policy.

Pair the notice with the privacy basics in whether Microsoft 365 Copilot keeps your business data private, so staff understand that the same rules that protect the business also mean their work chats are business records.

Questions about deleting Copilot history at work

Can my employer see my Copilot chats?

Yes, people with the right admin roles can. Microsoft says admins can use Content search or Microsoft Purview to view and manage stored Copilot prompts and responses, and eDiscovery searches can find them in the hidden mailbox folder where they are kept. Deleting a chat yourself does not stop a retention policy or hold keeping a searchable copy, so treat work Copilot chats like work email.

How long does it take for deleted Copilot history to disappear?

Usually days, not seconds. A whole-history delete from My Account sends a request that Microsoft says might take some time, and open apps can keep showing old history until you close them. Behind the scenes, deleted items sit in a hidden folder for at least a day before a job that typically runs every one to seven days removes them, and a retention policy can keep them far longer.

Can I delete Copilot history for just Word or just Teams?

No. Microsoft's deletion option for work accounts covers Copilot activity across every app at once, including Word, Excel, PowerPoint, Outlook, Teams and Copilot Chat; you cannot pick only some apps. To remove a single conversation instead, delete that chat from the Chats list in Copilot Chat using More, then Delete.

Does deleting a Copilot chat delete what Copilot remembers about me?

No. Microsoft says deleting a chat does not delete saved memories that came from it. Remove those under Settings and more, Chat settings, Personalisation, Saved memories. Inferred details from chat history clear within seven days once every chat that mentioned them is deleted, or after 30 days if you turn the Chat history toggle off.

Do Purview retention policies delete Copilot memories too?

No. Microsoft states that retention policies and labels in Purview do not apply to Copilot memory, so a delete-after-three-months policy leaves users' memories in place. Saved memories stay until the user deletes them. Admins can still search for and delete memory items through eDiscovery and Microsoft Graph Explorer, where they appear under the contact item class.

Further reads

Sources: Microsoft Support pages on deleting Copilot activity history, the privacy dashboard for personal accounts, how Copilot Chat history works and managing Copilot memory; Microsoft Learn pages on data, privacy and security for Microsoft Copilot, retention for Copilot and AI apps, creating retention policies, searching for and deleting AI application data in eDiscovery, Copilot personalisation and memory, deleting a user, and the Microsoft Purview service description. All read 22 November 2026.

Rather not work this out alone?

An AI implementation consultation is a one-to-one call with me, not an agency or a sales team. You leave knowing what AI you can use in your business and where to start.

Book a 1:1 call with me