Content reviewed: 13 October 2026
Deleting a chat, retaining its content and retaining an audit record are different operations. A legal or security team investigating a Copilot answer needs more than a history screenshot. It must check interaction content, audit metadata, applicable policies and, where necessary, the source document version.
The traces an interaction creates
The prompt and response are interaction content. For retention they are stored in a hidden area of the user’s Exchange Online mailbox that ordinary Outlook does not expose. An audit record instead captures the event: user, time, workload and references to files, sites or resources used by Copilot. A file uploaded to Copilot Chat can live in the user’s OneDrive; Copilot Pages can live in a user-owned SharePoint Embedded container. A single question can therefore have different lifecycles for conversation text, audit metadata, upload and output artifact. Microsoft primary documentation.
Deleted chat and the retained copy
For compliance, prompts and responses are stored in a hidden area of the user’s Exchange mailbox. Ordinary Outlook does not expose it; eDiscovery verifies the content. Deleting the visible conversation therefore does not confirm permanent removal. Microsoft describes storage and retention processing.
However, not every deletion immediately follows the same SubstrateHolds path. Documentation distinguishes retain-and-delete, retain-only and delete-only policies. In the first mode, deleting chat before expiry moves the message to the hidden folder and preserves it until retention ends. The other modes have different paths and outcomes.
The Exchange timer job typically processes items in a 1–7-day cycle. An item remains in SubstrateHolds for at least one day before further processing. Microsoft’s example shows that delete-only after one day can take up to sixteen days before permanent deletion. This describes possible processing timing, not a guaranteed deadline or a rule for every policy. Another policy for the same location, Litigation Hold, delay hold or eDiscovery hold can suspend removal.
| Mode | What to track | Do not assume |
|---|---|---|
| Retain and delete | Preservation until expiry followed by deletion | User deletion ends preservation |
| Retain only | The preservation duty; later behaviour also depends on removal from the app | A message left in the app disappears automatically at expiry |
| Delete only | Deletion under the configured period and backend processing | The period also protects against earlier user deletion |
Separate retention locations
New policies have separate Microsoft Copilot experiences, Enterprise AI apps and Other AI apps locations. Do not rely on the old Teams chats and Copilot interactions name when designing a new policy. Other supported AI applications may require a collection policy with capture content; selecting a location does not collect from every tool. The Enterprise group also includes Microsoft Foundry, while consumer Copilot belongs to Other AI apps. Check the current groups and collection requirements for the actual application.
| Trace | Question | Control |
|---|---|---|
| Prompt and response | What did the user ask and receive? | Purview retention and eDiscovery |
| Audit event | Who, when, where and which resources? | Purview Audit |
| Referenced content | Which document version grounded the answer? | SharePoint/OneDrive, labels and eDiscovery |
| Uploaded file | What was supplied directly to chat? | OneDrive retention and DLP |
| Output artifact | What was created or shared next? | Policies of the destination workload |
Copilot Pages are .page files collected from their storage location. Selecting the user’s OneDrive alone does not include their Pages in SharePoint Embedded. Add that container as a separate data source; administration identifies it as the Loop application, without a separate Copilot Pages filter. Microsoft collection instructions.
What Audit Standard includes
The AI auditing guide includes Microsoft applications in Audit Standard when organisational auditing is enabled. These Microsoft events do not need separate AI pay-as-you-go billing. Records identify an interaction and can include AccessedResources and Messages. Messages contains identifiers and prompt/response flags, not automatically the entire conversation text. Fields available vary by scenario.
Audit Standard now retains records for 180 days by default. Audit Premium does not automatically give every Copilot event one year: the one-year default applies to specified workloads; other records default to 180 days unless a suitable audit-log retention policy is used. Check policy, workload and user licensing for longer retention. Audit Premium defaults differ from prompt-content retention.
Auditing other AI applications
Auditing non-Microsoft AI interactions can require enabling pay-as-you-go. The current guide specifies 180 days and charging by ingested events. Some ConnectedAIAppInteraction scenarios are included, but that category name alone does not establish the billing model for every record. Microsoft distinguishes Microsoft and non-Microsoft apps. Separate content collection, audit events, billing configuration and subsequent retention; letting staff use a service does not replace these controls.
eDiscovery and licensing
eDiscovery Standard covers cases, search, hold and export; Premium adds review-set processing, analysis and further legal workflows. These are not one generic “Purview licence”. For example, the current service description lists basic Copilot interaction search, hold and export for Microsoft 365 E3 with Copilot, but not Premium search for Copilot interactions in that combination. E5 with Copilot includes the premium option. Compare the exact feature row, rather than the presence of a portal menu.
The same source lists E3/E5 with Copilot and selected E3 add-on combinations for Copilot interaction retention policies. Adaptive scope and preservation of the exact referenced version have separate higher prerequisites. General Business Premium retention rights do not establish every Copilot control. When using eDiscovery Premium, both the person whose data is analysed and the administrator performing the analysis require the appropriate licence; roles and licences are separate requirements.
Finding interactions and memory
For a controlled test, select the user mailbox, time window and a unique harmless phrase. The current query builder offers Item class and Copilot activity, which also includes other supported AI activity. For a narrower case, select the item class from the following table. The item-class and search guide does not define one universal class for all AI data.
| Content | Documented class |
|---|---|
| Microsoft Copilot interactions | `IPM.SkypeTeams.Message.Copilot.*` |
| Copilot Chat | `IPM.SkypeTeams.Message.Copilot.BizChat` |
| Memory and personalisation | `IPM.Contact` |
Deleting a conversation through Purview or eDiscovery does not delete associated Copilot memory. Memory uses IPM.Contact and matches contacts in the condition builder. A narrow query for Copilot messages may miss it. Conversely, a Contacts result does not prove that every matching contact is Copilot memory. Review content and origin before selecting items; searching is not a reason to delete contacts broadly. Microsoft explicitly documents this distinction.
Incident search and purge have different permissions: eDiscovery Manager supports the case and search, while removal separately requires Search And Purge. The incident-deletion guide specifies ten items per mailbox in one step. That is not a limit on the whole search or a tool for managing the complete retention lifecycle. Holds first require an approved legal process; removing them is not a routine response to an empty search.
Which file version is preserved?
With correctly configured cloud-attachment and Copilot-reference auto-labelling, a retention label applies to a file copy in the Preservation Hold library, not the live original. The copy is typically created within an hour. Editing and sharing again creates another version; sharing an unchanged file again can update the labelled date. Microsoft therefore recommends starting retention at labelling. The cloud-attachment mechanism belongs in both the design and the test.
A new reference to a file in an already archived SharePoint site is an exception: the cloud-attachment auto-apply policy does not preserve it that way. Copies preserved before archiving remain subject to their policy. An audit link, ordinary version history or a chat licence alone therefore does not prove preservation of the required historical version. Check the archived-site limitation before using archive storage as evidence.
Permissions when the question was asked
Copilot can use only content the user is authorized to access. Encrypted material additionally requires VIEW and EXTRACT rights; sensitivity labels and Azure Rights Management are enforced during grounding and generation. Current permission, however, does not prove the historic state. The user might have had access when asking and lost it later. Investigations should correlate audit, sign-in, sharing changes, file version and interaction content. A screenshot of an answer is not sufficient evidence. Microsoft primary documentation.
Sensitive information in prompts
Users put names, contract context, customer information and incident details into prompts. Governance must define lawful purpose, retention duration, investigator access and data-subject processes. Minimization does not always mean the shortest deletion policy; deleting too quickly can destroy evidence required for an incident or dispute. Indefinite retention increases the stock of sensitive text. The decision should follow a records schedule and risk assessment rather than a technical default.
| Scenario | Priority | Typical design |
|---|---|---|
| Routine productivity | Minimization and operational need | Defined period from the records schedule |
| Regulated activity | Evidence of decisions | Longer retention and explicit scope |
| Litigation or investigation | Prevent relevant deletion | eDiscovery hold for affected custodians |
| Security incident | Correlate source and event | Audit plus preserved content and versions |
| External AI service | Collection and lawful purpose | Separate policy, billing and privacy assessment |
Who may search and export?
Audit and eDiscovery can expose highly sensitive material, so do not give every administrator a global compliance role. Separate Audit Reader, case-based eDiscovery access, export approval and oversight of investigators. Record the reason for a search and scope cases to necessary custodians and dates. Teams should also understand that audit schemas evolve: fields such as Messages, jailbreak detection and DLP evaluation flags are metadata whose availability depends on workload and scenario. Microsoft primary documentation.
Test a controlled prompt
- 01
Create a controlled interaction
Use a unique phrase and versioned document without real sensitive data
- 02
Record the visible state
Capture time, app, account, source and expected answer
- 03
Find the audit event
Verify user, workload, operation and references
- 04
Find content in eDiscovery
Search the phrase and verify prompt and response
- 05
Check other traces
Check memory and other item classes too; a messages-only query does not cover every AI trace.
- 06
Delete the visible chat
Confirm compliance results still follow the retention policy
- 07
Change the source document
Check whether the relevant historic version remains discoverable
- 08
Document timing and licensing
Put timer jobs and roles in the runbook; do not call delay data loss
Before deployment
The Copilot approval pack should contain a trace map, retention decision record, roles and separation of duties, an eDiscovery test, legal-hold procedure, DLP and sensitivity-label baseline, oversharing remediation and user guidance. Add an incident contact for prompt-related events and a regular review of new AI locations in Purview. The product changes faster than many records schedules, so an owner should verify locations, supported workloads and licensing at least quarterly.
What the decision must record
Record which traces you preserve, for how long, in which system and who may search or export. For each control, document licensing, policy scope and the controlled test result. Assign an incident case owner and a process for holds. An interface deletion date, answer screenshot or licence alone does not establish this evidence.
Frequently asked questions
Does a prompt disappear from eDiscovery when the user deletes the chat?
Not necessarily. Retention or hold can preserve the copy in hidden storage for eDiscovery according to policy and processing time.
Is Microsoft 365 Copilot included in Audit Standard?
Yes. Microsoft AI applications are included when organizational auditing is enabled.
Does the audit log contain the complete prompt and response text?
Audit captures interaction metadata. Use retention and eDiscovery for content, holds and export.
Is 30 days the correct retention period?
There is no universal number. Derive it from records schedules, legal obligations, incident response and data minimization.
Does deleting a conversation also remove Copilot memory?
No. Microsoft says the associated memory is not removed by that deletion. In eDiscovery it has item class IPM.Contact and needs separate assessment.
Does Audit Premium retain every Copilot event for a year?
Not automatically. The one-year default is limited to specified workloads. Check the appropriate audit-log retention policy and licensing for other records.








