Microsoft Purview eDiscovery Adds Loop/Copilot Page Indexing and HTML Export

Microsoft has marked a Microsoft Purview eDiscovery update for Loop and Copilot Pages as launched, adding full page-content indexing to review sets and HTML export support from search. The company’s Microsoft 365 Roadmap lists the feature under ID 561492, with general availability dated June 2026 and a July 13 update to the entry.

Illustration of a secure legal document management system with search, cloud storage, and shield protection.Better search coverage for collaborative content​

The important change is that Loop and Copilot Pages content can now be fully indexed for keyword searching inside eDiscovery review sets. For legal, compliance, and investigation teams, that should reduce the gap between finding an item and seeing the relevant text contained within a collaborative page.
Loop components and Copilot-generated pages do not behave exactly like traditional Office documents. Their content can be shared, edited, and embedded across Microsoft 365 experiences, which makes reliable collection and review especially important when a case involves modern collaboration tools rather than just Exchange mailboxes and SharePoint files.
Microsoft’s roadmap wording is specific: this is indexing for keyword search within review sets. It is not a broad announcement of new Purview search syntax, new case-management controls, or a change to retention policy behavior. Administrators should treat it as an eDiscovery workflow enhancement rather than a platform-wide Copilot data-governance overhaul.

HTML joins search exports​

The second change is HTML format support when exporting Loop and Copilot Pages from search. That gives reviewers and downstream counsel a more web-native representation of collected material, potentially making page content easier to inspect outside the Purview interface than a less structured export format.
HTML exports can also matter where review tooling or legal-production processes preserve page layout and linked presentation more effectively in browser-readable files. Organizations should still validate exported output against their own evidentiary, preservation, and production requirements; Microsoft’s roadmap entry does not specify how every embedded object, component, revision, or permission context is represented in the exported file.

Availability and admin impact​

According to Microsoft, the capability is generally available in the worldwide multi-tenant cloud as well as GCC, GCC High, and Department of Defense environments. It is listed as a web-based Microsoft Purview feature, so there is no Windows client update to deploy.
This is a relatively quiet but useful improvement for organizations already using Purview eDiscovery and permitting Loop or Copilot Pages in their tenant. The immediate task for eDiscovery administrators is to test representative Loop and Copilot Page content in an active or test case: confirm keyword hits appear in review sets, then verify that exported HTML meets internal review and legal-hold workflows.
The feature should now be available through Purview’s eDiscovery workflow in the listed Microsoft 365 cloud environments.

References​

  1. Primary source: Microsoft 365 Roadmap
    Published: 2026-07-13T23:07:14.8221961Z
 

Back
Top