Every Microsoft 365 tenant that has deployed Microsoft Loop or Copilot Pages is now operating under a discovery obligation that did not exist in practical terms six months ago. As of July 13, 2026, Microsoft confirmed general availability of full-text indexing and HTML-export support for Loop components and Copilot Pages within Microsoft Purview eDiscovery (Premium) (Roadmap ID 561492). Previously, these cloud-native .loop and .page files could be located and added to review sets, but their content was entirely unsearchable — a gap that exposed organizations to the risk of incomplete productions without any visible warning sign. That gap is now closed, but closing it created new obligations that most legal hold systems are not yet designed to meet.
The stakes are straightforward. Courts and regulators have already begun treating artificial-intelligence prompts and outputs as discoverable electronically stored information ("ESI"). Copilot Pages — the persistent, co-authored workspaces generated through Microsoft 365 Copilot interactions — sit squarely within that category. The moment full-text indexing reached general availability, those artifacts became subject to the same preservation, collection, and production standards that govern a Word document or an Outlook email. For in-house counsel, litigation support teams, and outside litigators managing M365-heavy clients, the implications are immediate and demand action. This article examines the technical change Microsoft has implemented, identifies the discovery risks it surfaces, and provides practical guidance for updating ESI frameworks to account for this new class of collaborative artifact.
What Changed, and Why It Matters
Microsoft Loop is a collaborative productivity application that stores content as portable, modular components — essentially live, embedded documents that can appear simultaneously in Teams, Outlook, and dedicated Loop workspaces. Copilot Pages are a related artifact: persistent workspaces in which Microsoft 365 Copilot assembles, drafts, and co-authors content alongside human users. Both file types are stored in SharePoint-based cloud infrastructure and carry .loop or .page extensions.
Before the July 2026 update, Purview eDiscovery could identify these files and include them in a review set, but keyword searches did not reach their contents. A custodian's Loop workspace might contain highly relevant negotiation notes, project timelines, or Copilot-generated legal summaries — none of which would surface in a standard keyword search. The risk was compounded by the fact that most eDiscovery practitioners had no reliable way to know what they were missing. The file existed in the collection; its substance was invisible.
The general availability release resolves the search problem. Full-text indexing now treats the content of .loop and .page files on equal footing with traditional Office documents. HTML-export support means those files can be rendered and produced in a reviewable format. These are meaningful improvements. They also carry a corollary: organizations that have not updated their litigation hold and ESI inventory protocols to capture Loop workspaces and Copilot Pages are now, in effect, running a deficient preservation program.
The Modern Attachment Problem, Revisited
The closest analogy in recent eDiscovery history is the cloud-linked-file problem that emerged as organizations migrated from email attachments to Google Drive and SharePoint hyperlinks. Email-centric collection workflows captured the link but not the document — producing an incomplete record that opposing counsel could challenge under Federal Rule of Civil Procedure 34 as a deficient production. Courts and practitioners spent several years reconciling hold protocols, collection tools, and production standards to account for that shift.
Loop and Copilot Pages represent the same structural disruption at a higher level of complexity. A single Copilot Page can reflect the collaborative work product of multiple custodians, persist across project lifecycles, and contain AI-generated summaries of information that may itself be relevant. The content is not siloed in any one custodian's mailbox or OneDrive folder; it lives in a shared workspace that traditional custodian-centric collection may never reach. Metadata is not merely a technical curiosity in this context; it is evidence — documenting who contributed, when, and in what sequence.
There is an additional configuration risk specific to this rollout: the HTML conversion setting in Purview eDiscovery is off by default. Organizations that fail to enable it before collecting Loop or Copilot Page content will produce files that are opaque and unsearchable — precisely the format that opposing counsel can challenge as functionally incomplete, even if technically collected.
Practical Guidance for Counsel and Legal Operations Teams
In-house counsel, litigation support directors, and outside counsel advising M365 tenants should take the following steps without delay.
1. Audit your ESI inventory for Loop and Copilot Page coverage. Most ESI maps and data-source inventories were built before Loop reached enterprise scale. Review whether Loop workspaces and Copilot Pages appear as named data sources, identify the SharePoint sites and user accounts where they reside, and document custodian access.
2. Update litigation hold notices and legal hold system configurations. Standard litigation hold language referencing "emails, documents, and SharePoint files" does not self-evidently capture .loop and .page artifacts. Revise hold templates to name these file types explicitly, and confirm that your hold management platform can issue and track preservation for Loop workspaces at the workspace and component level.
3. Enable HTML conversion in Purview eDiscovery before the next collection. Because the setting is off by default, your team must actively configure it. Producing Loop or Copilot Page content without HTML conversion enabled risks a production that opposing counsel can characterize as rendering the material inaccessible — a challenge that invites sanctions motions and re-production demands.
4. Train custodians to preserve Loop workspaces as potential evidence. Custodians who understand email preservation obligations frequently do not extend the same instinct to collaborative workspaces. Targeted training should explain that Copilot Pages — including AI-generated drafts, summaries, and co-authored content — are subject to the same hold obligations as any other business record.
5. Incorporate Loop and Copilot Page review into your meet-and-confer protocol. Federal Rule of Civil Procedure 26(f) conferences should address the format and scope of Loop and Copilot Page production, including agreement on HTML conversion, metadata fields, and whether Copilot-generated content within a page will be distinguished from human-authored content. Raising these issues early reduces the risk of costly disputes at the production stage.
Conclusion
In conclusion, the general availability of full-text indexing for Microsoft Loop components and Copilot Pages is not merely a product update; it is a discovery inflection point. The technical barrier that previously limited these artifacts to locate-only collection is gone. What remains is the organizational and procedural work of ensuring that legal hold frameworks, ESI inventories, and production protocols have caught up with the reality of how M365 tenants actually create and store information. There is no one-size-fits-all approach to updating these frameworks — the right configuration will depend on the organization's Loop adoption level, litigation profile, and existing Purview deployment. What is clear is that treating Loop and Copilot Pages as an edge case is no longer defensible. As AI-assisted collaboration becomes the default mode of enterprise work product creation, the courts and the rules that govern discovery will follow the evidence wherever it lives.