Microsoft has quietly rolled out a significant eDiscovery enhancement: full-text indexing of Loop components and Copilot Pages within Purview review sets, along with HTML export support. The update, which reached general availability in June 2026, closes a critical gap for legal and compliance teams grappling with collaborative content across Microsoft 365.

What’s Changing in Purview eDiscovery?

The update, tracked under Microsoft 365 Roadmap ID 561492 and updated on July 13, 2026, introduces two concrete changes to the eDiscovery workflow.

Full-content indexing for Loop and Copilot Pages in review sets. When you add Loop components or Copilot-generated pages to an eDiscovery review set, the system now indexes the textual content inside those items. That means keyword searches run against the review set will hit on text within those collaborative artifacts—not just on metadata like file names or stored paths. Previously, reviewers could wind up with partial results, forced to examine each item individually to see if it contained responsive language. Now, the index works at a granular level, making the review set searchable in a way that should dramatically speed up early case assessment and relevance filtering.

HTML export from search. The second change is that when you export Loop and Copilot Pages from a search, the system now includes an HTML format option. Instead of a raw JSON dump or a format that strips away layout, reviewers and outside counsel can receive a web-native representation. That matters for several reasons: HTML preserves visual structure, links, and often embedded contexts better than a flat text export. It’s also easier to feed into many third-party review platforms and can reduce the need for manual reformatting. Administrators should still validate the output against internal preservation and production standards—Microsoft’s documentation doesn’t guarantee that every embedded object, comment, or permission hint survives the export—but the option is a meaningful step toward more practical handling of these modern file types.

Both capabilities are server-side, available through the web-based Purview compliance portal. No Windows client update is required, and the feature is live across all standard Microsoft 365 clouds: worldwide multi-tenant, GCC, GCC High, and Department of Defense environments.

For eDiscovery managers, the indexing improvement is not a minor tweak—it’s a direct answer to a growing pain point. Organizations that allow Loop and Copilot Pages in their tenant are building knowledge inside a new category of document. Those pages can be shared, co-authored, and embedded across Teams chats, Outlook emails, and Word documents. In litigation or an investigation, they might contain key admissions, decisions, or data points. If the eDiscovery tool treats them as opaque blobs, a crucial thread could be missed.

By indexing the full page content, Purview makes sure a keyword search for "project falcon" or "price adjustment" will catch a relevant Copilot page even if the item’s title or path is generic. That parity with traditional Office documents—Word files, Excel sheets, PowerPoint decks—was overdue.

The HTML export is equally practical. Many legal-review workflows rely on standardized formats to load documents into relativity, Nuix, or other review tools. Raw exports often require conversion scripts. HTML, by contrast, can be rendered directly in a browser, shared with opposing counsel in a more readable format, and archived without losing the basic presentation layer. For courtroom exhibits or internal audit reports, a clear visual export can be the difference between a confusing artifact and a persuasive piece of evidence.

One caution: the feature is explicitly about indexing inside a review set, not about expanding the original search query capabilities. Administrators still use the same KQL syntax and conditions to locate items during the collection phase. The new indexing only activates after the items are added to a review set. So, you won’t see new search operators or a Copilot-specific content filter. It’s a back-end refinement that improves downstream analysis.

How We Got Here: Collaborative Content Outpacing Governance

Loop components first appeared in late 2021, promising real-time collaboration blocks that could roam across Microsoft 365 apps. Copilot Pages, emerging from Microsoft’s AI assistant, added a new twist: AI-generated drafts and summaries that users could share and edit like any other document. By 2025, both were deeply woven into the fabric of Teams, Outlook, and the Office web apps.

Meanwhile, eDiscovery tooling lagged. Purview’s handling of modern content has been a work in progress. Early support for Teams messages required mapping chat transcripts to Exchange mailboxes; later updates brought better handling of meeting recordings and transcripts. Loop and Copilot content, however, lacked the same level of integration. The structured, component-based nature of Loop pages meant that traditional parsers often missed the text inside. Administrators could find the pages and add them to review sets, but the content remained unsearchable—a situation that grew riskier as adoption climbed.

Microsoft’s roadmap had signaled this update for months. The roadmap entry lists a general availability date of June 2026, indicating a deliberate, phased rollout rather than a rushed patch. The feature’s alignment with the government cloud environments also suggests it passed thorough security and compliance checks.

What Administrators Should Do Right Now

The capability is live, but it won’t automatically fix every review set. Here’s a practical checklist for eDiscovery administrators:

  1. Confirm availability in your tenant. Sign in to the Microsoft Purview compliance portal with an eDiscovery Administrator or eDiscovery Manager role. Create a test case, add known Loop and Copilot Pages to a review set, and run a few keyword queries. If the feature is active, you should see hits inside the page content.
  2. Re-add older review sets if necessary. Indexing applies to newly added items; existing review sets may need a re-upload or a “refresh” action to trigger re-indexing. Test this on a non-critical case first.
  3. Validate HTML exports. Perform a search that returns Loop or Copilot items, choose the HTML export option, and inspect the file in a browser and in your legal-review platform. Check that formatting, embedded images, and links render correctly. Document any gaps for your compliance team.
  4. Update internal eDiscovery playbooks. Your standard operating procedures should now reflect that Loop and Copilot content is searchable within review sets. Train reviewers to treat these items like any other document when crafting keyword searches.
  5. Monitor for additional governance settings. At present, this is a purely search-related enhancement. There are no new retention labels, sensitivity labels, or auto-classification changes for Loop/Copilot content. Stay tuned to the Microsoft 365 Roadmap for future governance capabilities.

No admin interface changes are required, and there are no PowerShell cmdlets to run. The update is effectively transparent to the user, but testing is essential because the rendering of complex loops (tables, polls, task lists) inside the exported HTML could vary.

What to Watch Next

Microsoft hasn’t announced a sequel to this feature, but the trajectory is clear. As Copilot continues to generate more business content—emails, reports, meeting summaries—that material will inevitably surface in legal disputes. Expect the company to eventually extend similar indexing and export capabilities to Copilot-generated emails and Teams chat summaries, and possibly to offer more granular metadata about the AI’s role in content creation (e.g., “85% AI-generated”). For now, this Purview eDiscovery update brings two critical capabilities to the table, and for legal teams mired in collaborative content, it’s a welcome—if overdue—improvement.