Microsoft 365 Copilot generates distinct types of data: prompts, responses, memories, Pages, and more. The table below provides a consolidated view of where each data type resides, the item class used to identify it, and the recommended strategy for collecting it.
Copilot Data Collection Reference Table
|
Data Type |
Storage Location |
Item Class |
Collection Strategy |
|
Copilot Prompts (user questions sent to M365 Copilot) |
Exchange Online: Hidden folder in the user's mailbox. Compliance copies stored similar to Teams chats, but with unique item classes. |
IPM.SkypeTeams.Message.Copilot.<AppName> (e.g., .Word, .Excel, .Outlook, .BizChat). Additional AI-related classes may also apply: IPM.SkypeTeams.Message.ConnectedAIApp*, IPM.SkypeTeams.Message.CloudAIApp*, IPM.SkypeTeams.Message.TeamCopilot*, IPM.SkypeTeams.TeamCopilot* |
1. Add the user's Exchange mailbox as a data source to the search. 2. In the condition builder you can optionally filter the search to only return Copilot prompts by adding a condition of "Item class contains any of Copilot activity". This automatically applies all relevant M365 Copilot item classes as a condition of the search. 3. Add any further additional conditions such as date range or keywords to narrow results as required. You can also use the Item Class condition to exclude M365 Copilot interactions from your collections when targeting a user’s mailbox. Notes: · Additional item classes may be added. The item class condition will be updated accordingly. |
|
Copilot Responses (AI-generated answers) |
Exchange Online: The same hidden folder in the user's mailbox as prompts. |
The same IPM.SkypeTeams.Message.Copilot.<AppName> pattern as prompts |
The same collection strategy used for prompts. |
|
Copilot Memories (personalized saved information Copilot "remembers") |
Exchange Online: Hidden CopilotMemory subfolder within the user's mailbox contacts. Stored as contact entries separate from prompts and responses. |
IPM.Contact Each memory item appears as a contact card within Exchange, which is distinct from the message-based item classes used for prompts/responses. |
1. Add the user's Exchange mailbox as a data source to the search. 2. In the condition builder you can optionally filter the search to only return Contacts by adding a condition of "Item class contains any of Contacts".
Notes: · Copilot memories will not be preserved under a legal hold or retention policy. · This will return both Copilot memories stored in contacts as well as traditional contacts from the user’s Exchange mailbox.
|
|
Copilot Pages (AI-generated, user-editable documents) |
SharePoint Online: Stored in a user-owned SharePoint embedded container (shared with Loop workspace content and Copilot Notebooks). File format is .page.
Not stored in the user's mailbox. |
N/A
These are SharePoint files (not Exchange items), so no item class applies. Identify them in search results by the .page file extension.
|
1. Add the custodian’s SharePoint embedded site URL as a data source to the search. Alternatively, tenant-wide searches of all SPO sites will include all SharePoint Embedded containers 2. Optionally use the condition builder with conditions such as date range, keywords or file type to further filter results returned |
|
Facilitator agent interactions in a Team meeting chat |
Exchange Online: Hidden folder in all meeting attendees’ mailboxes. Compliance copies stored as Teams chats |
IPM.SkypeTeams.Message |
1. Add the user's Exchange mailbox as a data source to the search. 2. In the condition builder you can optionally filter the search to only return Copilot prompts by adding a condition of "Item class contains any of Instant messages". 3. Add any further additional conditions such as date range or keywords to narrow results as required. |
|
Facilitator agent meeting notes (loop) |
SharePoint Online: Facilitator meeting notes are stored as a .loop file in a OneDrive folder titled Meetings of the user who initiated Facilitator in Teams |
N/A
These are SharePoint files (not Exchange items), so no item class applies. Identify them in search results by the .loop file extension.
|
1. Add the user's OneDrive URL as a data source to the search. 2. In the condition builder you can optionally filter the search to only return loop files by adding a condition of "File type equals any of loop". 3. Add any further additional conditions such as date range or keywords to narrow results as required. Notes: · With eDiscovery premium enabled cases you can follow the standard workflow for collecting Team meeting messages and select to include cloud attachments in your collection. This will automatically pull into the export or review set any Facilitator agent meeting notes. |
|
Facilitator created word/loop documents |
SharePoint Online: When the facilitator agent is asked to create a word or loop document during a meeting they are stored in the requesters OneDrive in a folder called |
N/A
These are SharePoint files (not Exchange items), so no item class applies. Identify them in search results by the .loop file extension.
|
1. Add the user's OneDrive URL as a data source to the search. 2. In the condition builder you can optionally filter the search to only return loop and doc files by adding a condition of "File type equals any of loop, docx". 3. Add any further additional conditions such as date range or keywords to narrow results as required. Notes: · With eDiscovery premium enabled cases you can follow the standard workflow for collecting Team meeting messages and select to include cloud attachments in your collection. This will automatically pull into the export or review set any Facilitator generated loop or word documents. |
|
Facilitator generated and assigned tasks |
Exchange Online: When the facilitator agent creates and assigns a task to an individual, it is created as a to-do item in the assigned individual's Exchange Mailbox |
IPM.Task
|
1. Add the user's Exchange mailbox as a data source to the search. 2. In the condition builder you can optionally filter the search to only return Tasks by adding a condition of "Item class contains any of Tasks". 3. Add any further additional conditions such as date range or keywords to narrow results as required. |
Application-Specific Item Classes for Prompts & Responses
For more granular filtering by Copilot application, the following item class values can be used in KQL queries:
|
Application Context |
Item Class Value |
|
Microsoft Copilot Chat (BizChat / Teams) |
IPM.SkypeTeams.Message.Copilot.BizChat |
|
Copilot in Excel |
IPM.SkypeTeams.Message.Copilot.Excel |
|
Copilot in Loop |
IPM.SkypeTeams.Message.Copilot.Loop |
|
Copilot in Outlook |
IPM.SkypeTeams.Message.Copilot.Outlook |
|
Copilot in PowerPoint |
IPM.SkypeTeams.Message.Copilot.PowerPoint |
|
Copilot in Teams |
IPM.SkypeTeams.Message.Copilot.Teams |
|
Copilot in Whiteboard |
IPM.SkypeTeams.Message.Copilot.Whiteboard |
|
Copilot in Word |
IPM.SkypeTeams.Message.Copilot.Word |
To target all Copilot applications at once, use the wildcard query ItemClass:IPM.SkypeTeams.Message.Copilot.*.
For a wider list of AI data sources, see the following link:
https://learn.microsoft.com/en-us/purview/edisc-search-copilot-data#data-sources-for-ai-data
Important Notes for eDiscovery Practitioners
Excluding Copilot Data from Broader Searches
Because Copilot prompts and responses reside in the same Exchange mailbox as emails and Teams chats, they will appear in broad mailbox searches unless explicitly filtered out. To exclude Copilot items, use the condition "Item Class Contains none of Copilot activity" in the condition builder, or add (-ItemClass:IPM.SkypeTeams.Message.Copilot.*) in KQL.
Some eDiscovery managers run separate searches, one for Copilot data and one for other communications, to keep collections distinct.
Copilot Memories: Retention & Hold Limitations
Purview retention policies and eDiscovery holds do not currently apply to Copilot memory items. Memory items remain until a user deletes them or an admin explicitly removes them via eDiscovery or Graph API. Additionally, deleting a Copilot prompt and response does not delete any memory derived from that conversation. Memories must be removed separately if required.
Copilot Pages: Do Not Treat Like Prompts/Responses
Copilot Pages are not stored in Exchange mailboxes. Searching only a custodian’s mailbox will not return Copilot Pages. Treat Copilot Pages the same way as you do for SharePoint content in your existing eDiscovery workflow.
For collections, keyword searches will generate hits on text content within the .page file if either the SharePoint Embedded URL is included in the search or the search is a tenant-wide search of all SharePoint sites
Be aware that full-text search within .page files in Purview eDiscovery review sets is not currently available. Instead you can use filters such as Subject/Title or Native File Type to locate Copilot Pages in your review set and review the content.
When an eDiscovery hold is placed on a custodian’s mailbox, it does not automatically extend to the SharePoint Embedded site where the Copilot Pages are stored. Instead, ensure the hold policy includes the URL for the user-owned SharePoint Embedded site that contains the Copilot Page(s) that must be preserved.
Audit Logs vs. eDiscovery for Copilot Content
Audit logs record that a Copilot interaction occurred (time, user, workload context) but do not include the actual prompt or response text. To retrieve the substance of Copilot interactions, use Purview eDiscovery searches against the mailbox.
Copilot Prompts and Responses: HTML Transcription
Copilot prompts and responses are stored as individual messages within the user’s mailbox. When collecting Copilot interactions, enabling the “Organize conversations into HTML transcripts” premium option will convert these individual messages into HTML transcripts making for easier review and linkage between the user’s original prompt and the Copilot responses.
Copilot Prompts and Responses: Contextual prompts and responses
When using the Keywords condition as part of your collection in eDiscovery, it will only return items that match the keywords included in the query. This means that you may only return a part of the Copilot interaction. If using keywords in your collection query you can enable the “Include full conversation for Copilot, Teams and Viva Engage messages” premium option. This will include in the export or review set any prompts or responses from the Copilot interaction within a 12-hour window before and after each responsive item. This means that you are able to see the full context of the prompt or response that was responsive to search.
Collecting Referenced Documents (Cloud Attachments)
Copilot responses may reference or summarize SharePoint/OneDrive files. When collecting Copilot interactions, enabling the "Access links (cloud attachments) in messages" premium option will additionally collect the files referenced in the prompt or response and include them in the export package.
This provides full evidentiary context but can significantly increase export size and processing time so consider if collecting these artifacts are relevant to the investigation. If so, look to use additional conditions such as date to effectively manage volumes or reduce the number of custodians in the collection.
Facilitator agent in Microsoft Teams Meetings
The Facilitator agent in Microsoft Teams is an AI-powered assistant (included with Microsoft 365 Copilot) that enhances meeting productivity by generating real-time notes, summarizing key decisions, and managing action items. It acts as an active participant, allowing for collaborative editing of notes and answering chat questions during calls.
As the Facilitator works within the context of Microsoft Teams meetings (scheduled private meetings only) your existing workflows for collecting Microsoft Teams meetings chat should be used. In addition, enabling the "Access links (cloud attachments) in messages" premium setting will automatically collect any meeting note (loop) or loop or word documents created by the Facilitator agent.
Copilot Retention Reference Table
|
Data Type |
Microsoft Purview Retention Policy Location/Scope |
|
Copilot prompts and responses |
Microsoft Copilot experiences |
|
Copilot Memories (personalized saved information Copilot "remembers") |
Not supported |
|
Copilot Pages (AI-generated, user-editable documents) |
SharePoint classic and communications sites (Static Scopes only) |
|
Facilitator interactions in a Team meeting |
Teams chats |
|
Facilitator meeting notes (loop) |
OneDrive Accounts |
|
Facilitator created word/loop documents |
OneDrive Accounts |
|
Facilitator generated and assigned tasks |
Exchange mailboxes (Tasks with end dates only) |