-Export Parameter Retired for New-ComplianceSearchAction – Seeking Alternatives

Open Discussions
1

Hi all,

I wanted to open a discussion regarding the retirement of the -Export parameter for the New-ComplianceSearchAction cmdlet. As of May 26th, 2025, this parameter is no longer available. Attempting to run a command like:

New-ComplianceSearchAction -SearchName $user.SearchName -Export -Format FxStream

now results in the following error:

New-ComplianceSearchAction: |Microsoft.Exchange.Management.Tasks.ComplianceJobTaskException|Unable to execute the task. Reason: On May 26th 2025, the -Export parameter will no longer be available. See https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084 to learn more.

Background:

Before this change, our workflow relied on -Export to automatically download user mailboxes (PST) and SharePoint/OneDrive content as part of eDiscovery searches:

# Create the compliance search
$params = @{
    Name               = $user.SearchName
    Case               = $casename
    Description        = $description
    ExchangeLocation   = $user.EmailAddress
    SharePointLocation = $user.SharePointLocation
}
New-ComplianceSearch @params

# Export the results
New-ComplianceSearchAction -SearchName $user.SearchName -Export -Format FxStream

With the parameter gone, it’s unclear how to automate the export of search results, especially at scale.

Graph API consideration:

I’ve looked into Graph API workflows for eDiscovery, but:

  • The APIs currently only work with eDiscovery (Premium) cases, which we do not have licensed.

  • Microsoft is retiring eDiscovery Premium on August 31st, 2025, making it a short-term or impractical solution.

  • I’m not yet familiar enough with Graph API to implement this reliably.

My questions for the community:

  1. How are others handling automated mailbox + SharePoint/OneDrive exports now that -Export is retired?

  2. Are there alternative cmdlets, scripts, or supported workflows that allow programmatic eDiscovery exports without relying on eDiscovery Premium?

  3. Any tips for migrating existing automation away from New-ComplianceSearchAction -Export?

We’re looking for practical, production-ready alternatives that don’t require licenses for soon-to-be-retired features. Any input, experiences, or guidance would be greatly appreciated.

2

@vasil-michev pinging you. No pressure :blush:
And I thought Harm Veenstra was a member here too.

And Andrew Pla? I don’t know your guys’ handles… :grin:

3

I have not had a chance to look further into this…Very busy at work! As of now I’m using the Purview web GUI.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.