User with Global Administrator and Compliance Administrator role is unable to export ediscovery result to PST file

NLinAU 20 Reputation points
2023-06-14T01:04:51.66+00:00

Hi,

One of our users has global administrator and compliance administrator permissions.

When running an eDiscovery she's able to get results to show up, but when attempting to export the results the following error comes up:
You don't have export permissions.

A compliance Administrator or a member of the Organization Management role group can assign you a role with export permissions. Only eDiscovery Managers and eDiscovery Administrators have export permissions among the default role groups.

Following has been checked:

User permissions in Azure, confirmed Global Administrator and Compliance Manager roles are assigned.

In Microsoft Purview - Roles & Scopes -> Permissions -> Azure AD Roles - Roles

Here the Global Administrator role and Compliance Administrator role are visible and confirm the users is in these groups.

In Microsoft Purview - Roles & Scopes -> Permissions -> Microsoft Purview Solutions -> Roles

When I select eDiscovery Manager I can see all users with compliance administrator permissions, except this one particular user.

When attempting to manually add the user, I get the following error:

Client Error
Request failed with status code 500

I've attempted to add myself to the eDiscovery Manager role in the same wizard and receive the same error.

My permissions include Global Administrator and Compliance Manager.

Microsoft Exchange Online Management
Microsoft Exchange Online Management
Microsoft Exchange Online: A Microsoft email and calendaring hosted service.Management: The act or process of organizing, handling, directing or controlling something.
4,330 questions
Microsoft Exchange
Microsoft Exchange
Microsoft messaging and collaboration software.
435 questions
0 comments No comments
{count} votes

Accepted answer
  1. Vasil Michev 98,946 Reputation points MVP
    2023-06-14T15:43:58.15+00:00

    By default, even Global admins do not have permissions to perform such actions, as eDiscovery effectively allows access to everyone's data, which is an obvious concern. As an admin, you can add permissions, by using the steps you've detailed above.

    The 500 error is unfortunate, as it doesn't really tell us much. Can you capture the network traffic when performing the request and check the detailed error message therein?

    The UI effectively uses PowerShell to manage said permissions, so you might as well try adding them via PowerShell directly. To do so, connect to the SCC endpoint first: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-scc-powershell?view=exchange-ps

    Once connected, use the following cmdlet:

    Add-RoleGroupMember "eDiscovery Manager" -Member user@domain.com

    Remember that you will also have to add the user to the specific case afterwards. Alternatively, add him as eDiscovery admin instead:

    Add-eDiscoveryCaseAdmin -User user@domain.com

    3 people found this answer helpful.

0 additional answers

Sort by: Most helpful