Can't See Compliance Search Results in Purview Portal When Search Is Initiated via PowerShell

Hi all,

I've run into an issue where compliance searches initiated via PowerShell don't show up in the Microsoft Purview portal, even though the same user account (mine) is used to authenticate both in PowerShell and in the browser.

Here's what I know:

• If I create and run a compliance search via the Purview portal, everything works as expected — I can view results, statistics, process manager, export options, etc.

If I run a very similar search via PowerShell, the script completes successfully (or at least appears to). The search shows as "Completed", and a preview action is started. I see no errors.

However, I can't see the search or its results anywhere in the Purview portal. It's as if it never happened — nothing shows under "Statistics" or "Process Manager", even though it has an Identity and ExchangeLocations defined.

I initially assumed the PowerShell search wasn’t running properly, but we’ve seen enough evidence (status logs, search metadata, etc.) that suggests it does complete and processes mailboxes — even when it hits problematic ones.

This leads me to suspect there might be a permission or visibility issue, where PowerShell-initiated searches aren’t linked to my portal view, even though I'm signed in as the same user in both places.

I’ve tried:

Confirming I’m in the eDiscovery Manager role group (though my PowerShell modules struggled to validate this cleanly),

Using different authenticated accounts,

Reviewing job metadata via PowerShell, though it's difficult to get consistent info due to module inconsistencies.

I'm essentially looking for any advice on:

Why I can’t see my PowerShell-initiated compliance searches in the portal.

Whether there's a permissions nuance or ownership linkage I'm missing.

Or if anyone has seen this behavior and found a workaround or explanation.

Thanks in advance — any pointers would be massively appreciated.Hi all,

I've run into an issue where compliance searches initiated via PowerShell don't show up in the Microsoft Purview portal, even though the same user account (mine) is used to authenticate both in PowerShell and in the browser.

Here's what I know:

If I create and run a compliance search via the Purview portal, everything works as expected — I can view results, statistics, process manager, export options, etc.

If I run a very similar search via PowerShell, the script completes successfully (or at least appears to). The search shows as "Completed", and a preview action is started. I see no errors.

However, I can't see the search or its results anywhere in the Purview portal. It's as if it never happened — nothing shows under "Statistics" or "Process Manager", even though it has an Identity and ExchangeLocations defined.

I initially assumed the PowerShell search wasn’t running properly, but we’ve seen enough evidence (status logs, search metadata, etc.) that suggests it does complete and processes mailboxes — even when it hits problematic ones.

This leads me to suspect there might be a permission or visibility issue, where PowerShell-initiated searches aren’t linked to my portal view, even though I'm signed in as the same user in both places.

I’ve tried:

Confirming I’m in the eDiscovery Manager role group (though my PowerShell modules struggled to validate this cleanly),

Using different authenticated accounts,

Reviewing job metadata via PowerShell, though it's difficult to get consistent info due to module inconsistencies.

I'm essentially looking for any advice on:

Why I can’t see my PowerShell-initiated compliance searches in the portal.

Whether there's a permissions nuance or ownership linkage I'm missing.

1. Or if anyone has seen this behaviour and found a workaround or explanation.

Thanks in advance — any pointers would be massively appreciated.