Control 3.3: eDiscovery for Copilot-Generated Content — Verification & Testing
Test cases and evidence collection procedures to validate eDiscovery capabilities for Copilot-generated content and interaction history. All test procedures use the unified eDiscovery experience in the Microsoft Purview portal (Microsoft Purview > eDiscovery > Cases).
Test Cases
Test 1: Copilot Content Discoverability
- Objective: Confirm that Copilot interactions are searchable via the unified eDiscovery search builder
- Steps:
- Have a test user perform several Copilot interactions in different applications (Word, Teams, Outlook).
- Wait 24 hours for content indexing.
- In eDiscovery, create a search using Add condition > Item class / Type > Contains any of > Copilot activity, then add the test user through the supported custodian/participant condition.
- As a KQL fallback after tenant validation, test a documented item-class query such as
itemclass:IPM.SkypeTeams.Message.Copilot.* scoped to the test user's mailbox.
- Review search results for completeness.
- Expected Result: Copilot interactions from the test user are returned in search results with available metadata, using either the condition-builder Copilot activity selection or the documented item-class fallback.
- Evidence: Search results export showing Copilot interaction records with timestamps and content.
Test 2: Custodian Hold Preservation
- Objective: Verify that eDiscovery holds preserve Copilot content from deletion
- Steps:
- Place a test custodian on hold using the Copilot activity condition-builder selection or a documented item-class hold query such as
(itemclass:IPM.SkypeTeams.Message.Copilot.* OR itemclass:IPM.Contact).
- Have the custodian delete a Copilot-generated document.
- Search for the deleted document using eDiscovery.
- Confirm the document is still discoverable in the Recoverable Items folder.
- Expected Result: Deleted Copilot content remains preserved and discoverable under the hold.
- Evidence: Search results showing the preserved document with hold metadata.
Test 3: Cross-Workload Collection
- Objective: Validate that eDiscovery searches capture Copilot content across all M365 workloads
- Steps:
- Create a search targeting Exchange, SharePoint, OneDrive, and Teams custodian locations.
- Filter by Copilot-specific content types using the unified search builder.
- Review search estimates for each workload.
- Commit the results to a review set.
- Expected Result: Copilot content from all targeted workloads appears in the review set.
- Evidence: Search statistics showing items per workload and review set contents.
Test 4: Existing Case Source Verification
- Objective: Confirm that existing cases include the documented Copilot activity and container sources needed for the matter
- Steps:
- Open each active eDiscovery case that may need Copilot content.
- Navigate to Data sources within the case.
- Verify that custodian mailboxes, Copilot activity search conditions, and any in-scope SharePoint, OneDrive, Teams, or SharePoint Embedded container locations are included.
- If missing, add the documented source or condition and confirm inclusion in any active searches or holds.
- Expected Result: All active cases that require Copilot evidence cover the documented Copilot activity and container sources for the matter.
- Evidence: Screenshot of Data sources/search conditions panel for each reviewed case, showing the Copilot activity and container coverage.
Test 5: Export and Production Readiness
- Objective: Confirm Copilot content can be exported in standard litigation formats using the unified portal or Graph APIs
- Steps:
- Select items from the review set containing Copilot content.
- Export using the Purview portal export experience or Microsoft Graph eDiscovery APIs (deprecated PowerShell export cmdlets are no longer supported — see Troubleshooting Issue 6).
- Export in the required format (PST, EML, or native format).
- Verify exported items retain metadata including Copilot attribution.
- Confirm the export load file contains correct field mappings.
- Expected Result: Copilot content exports successfully with preserved metadata and standard load file format.
- Evidence: Export manifest and sample exported items with Copilot metadata intact.
Evidence Collection
| Evidence Item |
Source |
Format |
Retention |
| Search results summary |
Purview eDiscovery |
CSV |
Case duration |
| Hold confirmation |
PowerShell |
Text export |
Case duration |
| Existing case source audit |
Purview portal |
Screenshot |
Ongoing |
| Search statistics |
Purview eDiscovery |
Screenshot |
Case duration |
| Export manifest |
Export tool |
CSV |
Case duration |
Compliance Mapping
| Regulation |
Requirement |
How This Control Helps |
| FRCP Rule 26(b)(1) |
Proportional ESI preservation and production |
Unified search builder enables targeted, proportional discovery of Copilot content |
| FINRA Rule 8210 |
Record production for examinations |
Supports timely production of Copilot interaction records |
| SEC 17a-4(j) |
Record accessibility and production |
Supports requirements for accessible and producible electronic records |
Next Steps