--- title: "Microsoft Purview eDiscovery Change and Reveal Hold Classic Transition to Graph APIs" slug: "microsoft-purview-ediscovery-change-and-reveal-hold-classic-transition-to-graph-apis" updated: 2026-03-13T17:10:07Z published: 2026-03-13T17:10:07Z canonical: "docs.revealdata.com/microsoft-purview-ediscovery-change-and-reveal-hold-classic-transition-to-graph-apis" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.revealdata.com/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft Purview eDiscovery Change and Reveal Hold Classic Transition to Graph APIs Microsoft has announced that as of **March 23, 2026**, eDiscovery cases and searches created using PowerShell cmdlets, will no longer automatically synchronize with or appear in the Microsoft Purview eDiscovery UX. This affects only the *UX visibility* of PowerShell-created objects—not their functionality. Reveal Hold Classic historically relied on Microsoft’s PowerShell APIs for creating preservation cases and holds. To ensure continuity and alignment with Microsoft’s long-term roadmap, we have already been transitioning Classic to the Microsoft Graph API for relevant actions. ### What this means for Reveal Hold Classic customers Preservation functionality remains fully supported and operational. Cases or holds created using PowerShell may no longer display in the Purview user interface. Compliance, auditability, and preservation integrity will *not* be affected. ### **Our path forward for Reveal Hold Classic** Our transition toward Graph-based operations will continue, ensuring long-term compatibility with Microsoft’s platform direction. Reveal Hold Classic continues to support compliant, defensible preservation, and this Microsoft change does not affect the ability to meet regulatory or legal obligations.