1. Resources
  2. Detection rules
  3. eDiscovery Search and Export Used for Collection

eDiscovery Search and Export Used for Collection detection rules

An attacker who holds, or grants themselves, Microsoft Purview eDiscovery permissions searches mailboxes, OneDrive, SharePoint and Teams across the tenant and exports the results. The audit log records each step.

Platform
Microsoft 365
Severity
High
Log source
Microsoft 365 unified audit log (Microsoft Purview)
Last updated
Rule formats
Sigmaand queries for: Splunk
What an attacker needs
An account in the eDiscovery Manager role group, or one that can manage Microsoft Purview role groups and adds itself to it.
Impact
A copy of mail and files from across the tenant, taken through a supported feature without signing in to any mailbox or site.
Response
Remove the account from the eDiscovery role groups, revoke its sessions, and work out from the query and data sources what was exported.
Mitigation
Keep the eDiscovery Manager role group small and reviewed, and add people to it for a case instead of leaving administrators in it.
Operations
CaseAddedPurviewSearchAddedCaseMembersUpdatedPurviewSearchExportJobSubmittedReviewSetExportJobSubmittedAdminMailAccessGrantPermissionsAsyncCreateRBACRoleGroupDefinitionUpdateRBACRoleGroupDefinition

How the attack works

Microsoft Purview eDiscovery exists so that legal and compliance staff can find and hand over content for an investigation. A search can cover Exchange mailboxes, OneDrive accounts, SharePoint sites, Microsoft Teams, Microsoft 365 Groups and Viva Engage, and an export copies the matching items to a storage location provided by Microsoft, from where they are downloaded. The same feature, in the hands of an attacker, is a search engine over the whole tenant with a download button.

Access is governed by role groups in the Microsoft Purview portal. The primary one is eDiscovery Manager, whose members can search content locations and preview and export the results. An eDiscovery Manager sees only the cases they created, and an eDiscovery Administrator, a subgroup of the same role group, has wider access. An attacker with an account that can manage Purview role groups adds an account to the role group first. An attacker who takes over an account that is already a member needs no change at all. Membership of eDiscovery Manager also carries, by default, the Preview role of Microsoft Defender for Office 365, which lets the account open or download single messages in Threat Explorer, and Microsoft records each of those as AdminMailAccess.

The unified audit log records the whole sequence. GrantPermissionsAsync is written when user assignments are added to a role group, and CreateRBACRoleGroupDefinition and UpdateRBACRoleGroupDefinition when a role group is created or changed. CaseAdded and PurviewSearchAdded record a new case and a new search, CaseMembersUpdated a change of who can work in a case, and PurviewSearchExportJobSubmitted and ReviewSetExportJobSubmitted an export. The rules on this page read these operations by name. They convert for Splunk only: Microsoft Sentinel's Microsoft 365 connector collects Exchange, SharePoint and Teams records and not the Purview ones, and the library has no documented QRadar source for them, so the page shows those two SIEMs as not available.

What an attacker needs

  • An account in the eDiscovery Manager role group, or in another role group that holds the search and export roles.
  • Or an account that can manage role groups in the Microsoft Purview portal and adds itself, or an account it controls, to such a role group.

Impact

A copy of whatever the search matched, across mailboxes, OneDrive, SharePoint and Teams, taken through a supported Microsoft feature and without signing in to any of the mailboxes or sites. The content owners see nothing. The export leaves the tenant as a download.

Detection rules

eDiscovery Case or Search Created, or Case Members Updated

Detects the steps that come before an eDiscovery export in Microsoft Purview. Microsoft's audit log activities list "Created eDiscovery case" (CaseAdded), "Added Purview search" (PurviewSearchAdded: a new search was created, with the case name, case ID and search name) and "Updated case members" (CaseMembersUpdated: case membership was updated, and a member of a case can perform case-related tasks). These are ordinary work for an eDiscovery team and are rated low. They matter when the account is not one of the people who run investigations, and as the lead-up to an export. The account is in UserId. Microsoft Sentinel and QRadar have no documented source for Microsoft Purview records, so this rule converts for Splunk only.

LevelLowStatusExperimentalLog sourceMicrosoft 365 unified audit log (Microsoft Purview)
title: eDiscovery Case or Search Created, or Case Members Updated
id: 7ad5f8bd-75c7-4c6e-a1b2-8687b699b5c3
status: experimental
description: >-
  Detects the steps that come before an eDiscovery export in Microsoft
  Purview. Microsoft's audit log activities list "Created eDiscovery case"
  (CaseAdded), "Added Purview search" (PurviewSearchAdded: a new search was
  created, with the case name, case ID and search name) and "Updated case
  members" (CaseMembersUpdated: case membership was updated, and a member of
  a case can perform case-related tasks). These are ordinary work for an
  eDiscovery team and are rated low. They matter when the account is not one
  of the people who run investigations, and as the lead-up to an export. The
  account is in UserId. Microsoft Sentinel and QRadar have no documented
  source for Microsoft Purview records, so this rule converts for Splunk
  only.
references:
  - https://learn.microsoft.com/en-us/purview/audit-log-activities
  - https://learn.microsoft.com/en-us/purview/edisc-ref-audit-log
  - https://attack.mitre.org/techniques/T1213/
author: Forestall
date: 2026-11-18
tags:
  - attack.collection
  - attack.t1213
logsource:
  product: m365
  service: purview
detection:
  selection:
    Operation:
      - CaseAdded
      - PurviewSearchAdded
      - CaseMembersUpdated
  condition: selection
falsepositives:
  - The eDiscovery team opening cases and building searches, which is their daily work. List their accounts and alert on everybody else.
level: low

False positives

  • The eDiscovery team opening cases and building searches, which is their daily work. List their accounts and alert on everybody else.

eDiscovery Export Submitted From a Search or a Review Set

Detects the start of an eDiscovery export in Microsoft Purview. Microsoft's audit log activities list "Submitted purview search export job" (PurviewSearchExportJobSubmitted: the user triggered an export process from a search) and "Submitted review set export job" (ReviewSetExportJobSubmitted: exported documents from a review set). An export copies the items that match a search out of mailboxes, OneDrive, SharePoint and Teams for download. The search record includes the search name, the data sources, the query values and the export name as detailed properties, so read them in the event. The account is in UserId. Microsoft Sentinel and QRadar have no documented source for Microsoft Purview records, so this rule converts for Splunk only.

LevelMediumStatusExperimentalLog sourceMicrosoft 365 unified audit log (Microsoft Purview)
title: eDiscovery Export Submitted From a Search or a Review Set
id: ed278c57-a4e6-4e4a-a3fe-9dc1a7b32ae4
status: experimental
description: >-
  Detects the start of an eDiscovery export in Microsoft Purview. Microsoft's
  audit log activities list "Submitted purview search export job"
  (PurviewSearchExportJobSubmitted: the user triggered an export process from
  a search) and "Submitted review set export job" (ReviewSetExportJobSubmitted:
  exported documents from a review set). An export copies the items that
  match a search out of mailboxes, OneDrive, SharePoint and Teams for
  download. The search record includes the search name, the data sources, the
  query values and the export name as detailed properties, so read them in
  the event. The account is in UserId. Microsoft Sentinel and QRadar have no
  documented source for Microsoft Purview records, so this rule converts for
  Splunk only.
references:
  - https://learn.microsoft.com/en-us/purview/audit-log-activities
  - https://learn.microsoft.com/en-us/purview/edisc-ref-audit-log
  - https://learn.microsoft.com/en-us/purview/edisc-permissions
  - https://attack.mitre.org/techniques/T1213/
author: Forestall
date: 2026-11-18
tags:
  - attack.collection
  - attack.t1213
logsource:
  product: m365
  service: purview
detection:
  selection:
    Operation:
      - PurviewSearchExportJobSubmitted
      - ReviewSetExportJobSubmitted
  condition: selection
falsepositives:
  - Legal, compliance and investigation staff who export content for a matter. Exports are rare and made by a few people, so match each one to a case the legal team knows and list the usual accounts.
level: medium

False positives

  • Legal, compliance and investigation staff who export content for a matter. Exports are rare and made by a few people, so match each one to a case the legal team knows and list the usual accounts.

Email Previewed or Downloaded by an Administrator in Microsoft Defender

Detects the audit activity AdminMailAccess. Microsoft documents that audit log entries are generated when admins preview or download email messages in Threat Explorer and Real-time detections of Microsoft Defender for Office 365, and that these actions need the Preview role, which by default is assigned only to the Data Investigator and eDiscovery Manager role groups. An account in those role groups can therefore read the content of any message in a cloud mailbox through the security portal, without an eDiscovery search, and the owner of the mailbox is not told. The account is in UserId. Like the other rules of this page, it converts for Splunk only, because Microsoft Sentinel and QRadar have no documented source for these records here. Confirm in your own data which workload your tenant writes the record under before relying on the Splunk macro.

LevelMediumStatusExperimentalLog sourceMicrosoft 365 unified audit log (Microsoft Purview)
title: Email Previewed or Downloaded by an Administrator in Microsoft Defender
id: 823a1c1a-f513-4fc9-acb8-590dd52c5293
status: experimental
description: >-
  Detects the audit activity AdminMailAccess. Microsoft documents that audit
  log entries are generated when admins preview or download email messages
  in Threat Explorer and Real-time detections of Microsoft Defender for
  Office 365, and that these actions need the Preview role, which by default
  is assigned only to the Data Investigator and eDiscovery Manager role
  groups. An account in those role groups can therefore read the content of
  any message in a cloud mailbox through the security portal, without an
  eDiscovery search, and the owner of the mailbox is not told. The account
  is in UserId. Like the other rules of this page, it converts for Splunk
  only, because Microsoft Sentinel and QRadar have no documented source for
  these records here. Confirm in your own data which workload your tenant
  writes the record under before relying on the Splunk macro.
references:
  - https://learn.microsoft.com/en-us/defender-office-365/threat-explorer-real-time-detections-about
  - https://learn.microsoft.com/en-us/defender-office-365/mdo-email-entity-page
  - https://learn.microsoft.com/en-us/purview/edisc-permissions
  - https://attack.mitre.org/techniques/T1213/
author: Forestall
date: 2026-11-18
tags:
  - attack.collection
  - attack.t1213
  - attack.t1114.002
logsource:
  product: m365
  service: purview
detection:
  selection:
    Operation: AdminMailAccess
  condition: selection
falsepositives:
  - Security analysts who preview or download a reported or suspicious message during an investigation, which is the purpose of the feature. Match each event to an incident or an alert, and alert on accounts outside the security team.
level: medium

False positives

  • Security analysts who preview or download a reported or suspicious message during an investigation, which is the purpose of the feature. Match each event to an incident or an alert, and alert on accounts outside the security team.

Microsoft Purview Role Group Assignment Added or Role Group Changed

Detects changes to role groups in the Microsoft Purview portal. Microsoft's audit log activities list "Add user assignments to role group" (GrantPermissionsAsync: user assignments to an RBAC role group are added), "Create RBAC role group definition" (CreateRBACRoleGroupDefinition) and "Update RBAC role group definition" (UpdateRBACRoleGroupDefinition). Role groups such as eDiscovery Manager decide who can search and export content across the tenant, so an assignment is the step that gives an account that power. The Management Activity API schema documents that the record holds the role group and the member in PreExecutionMessage. That field has no mapping here, so the rule fires for every role group and the event has to be read to see which one. The account that made the change is in UserId. Microsoft Sentinel and QRadar have no documented source for Microsoft Purview records, so this rule converts for Splunk only.

LevelMediumStatusExperimentalLog sourceMicrosoft 365 unified audit log (Microsoft Purview)
title: Microsoft Purview Role Group Assignment Added or Role Group Changed
id: 9d2f3d9f-d85d-4265-89e8-e2e3bacbf8f7
status: experimental
description: >-
  Detects changes to role groups in the Microsoft Purview portal. Microsoft's
  audit log activities list "Add user assignments to role group"
  (GrantPermissionsAsync: user assignments to an RBAC role group are added),
  "Create RBAC role group definition" (CreateRBACRoleGroupDefinition) and
  "Update RBAC role group definition" (UpdateRBACRoleGroupDefinition). Role
  groups such as eDiscovery Manager decide who can search and export content
  across the tenant, so an assignment is the step that gives an account that
  power. The Management Activity API schema documents that the record holds
  the role group and the member in PreExecutionMessage. That field has no
  mapping here, so the rule fires for every role group and the event has to
  be read to see which one. The account that made the change is in UserId.
  Microsoft Sentinel and QRadar have no documented source for Microsoft
  Purview records, so this rule converts for Splunk only.
references:
  - https://learn.microsoft.com/en-us/purview/audit-log-activities
  - https://learn.microsoft.com/en-us/office/office-365-management-api/office-365-management-activity-api-schema
  - https://learn.microsoft.com/en-us/purview/edisc-permissions
  - https://attack.mitre.org/techniques/T1098/003/
author: Forestall
date: 2026-11-18
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098.003
logsource:
  product: m365
  service: purview
detection:
  selection:
    Operation:
      - GrantPermissionsAsync
      - CreateRBACRoleGroupDefinition
      - UpdateRBACRoleGroupDefinition
  condition: selection
falsepositives:
  - Compliance and security administrators who add staff to role groups, for example a new member of the legal team or a new analyst. Confirm the assignment with the owner of the role group.
level: medium

False positives

  • Compliance and security administrators who add staff to role groups, for example a new member of the legal team or a new analyst. Confirm the assignment with the owner of the role group.

Detection logic

Patterns that need more than one event, a baseline or knowledge of your own environment. Each is a hypothesis to build and tune in your SIEM, not a ready rule.

Role group assignment followed by a search and an export by the same account

Detection hypothesisSequence of eventsJoins two logs

Legal staff are members of the eDiscovery role group for months before they export anything. An attacker adds the account, searches and exports in one sitting. A role group assignment followed within days by a search and an export from the newly added account is the full chain.

  1. Unified audit log: GrantPermissionsAsync. Take the member from PreExecutionMessage and the time.
  2. Within 7 days: CaseAdded or PurviewSearchAdded whose UserId is that member.
  3. Then PurviewSearchExportJobSubmitted or ReviewSetExportJobSubmitted with the same UserId.
  4. Alert on the export, and include the query text and the data sources of the search in the alert.

EventsGrantPermissionsAsyncCaseAddedPurviewSearchAddedPurviewSearchExportJobSubmittedReviewSetExportJobSubmitted

LimitsA new member of the legal team who starts work on a case right away looks the same. It does not see an attacker who takes over an account that was a member for a long time. The 7 days are a starting point.

First eDiscovery export by an account, or an export from an unusual address

Detection hypothesisNeeds a baseline

Exports are made by a small, stable group of people from their usual workplaces. An export by an account that never exported before, or from an address that account never used, deserves a question to the legal team.

  1. Build the list of UserId values with PurviewSearchExportJobSubmitted or ReviewSetExportJobSubmitted in the last 180 days, with the ClientIP values of each.
  2. For each new export, check whether the UserId is on the list and whether its ClientIP was seen for it before.
  3. Alert when the account is new, or when the address is new for the account.

EventsPurviewSearchExportJobSubmittedReviewSetExportJobSubmitted

LimitsExports are rare, so the baseline is thin and a new joiner or a person who travels will appear. Microsoft includes the client IP only for the current eDiscovery experience. The 180 days are a starting point.

Triage

  • Read UserId for the account and Operation for the step. For eDiscovery operations Microsoft documents the detailed properties CaseName, ObjectName, QueryText, DataSources and ExportName, which say what was searched, where and under which name.
  • Match the case and the export to a matter the legal or compliance team knows. An export nobody asked for is the finding.
  • Check ClientIP. Microsoft includes the client IP address for activities performed in the current eDiscovery experience. Compare it with the usual addresses of the account.
  • For a role group assignment, read the role group and the member in PreExecutionMessage, and ask who approved it.
  • Look at the days before for the first steps, such as a role group assignment, a new case and a new search by the same account.
  • Review the sign-in of the account, such as device, location and risk level.

Response

Once the attack is confirmed:

  1. Remove the account from the eDiscovery role groups, revoke its sessions and reset its credentials.
  2. Delete the exports and searches that were not authorized, after recording their names, queries and data sources as evidence.
  3. Establish from QueryText and DataSources what the search covered, and treat the matching content as disclosed.
  4. Remove role group assignments and custom role groups that were created for the attack, and review the other members of the eDiscovery role groups.
  5. Tell the legal and privacy teams, because an export of mail and files can carry notification duties.

Mitigation

  • Keep the eDiscovery Manager role group small, name its members, and review it regularly.
  • Do not leave administrators in eDiscovery role groups permanently. Add a person for a case and remove them when it is closed.
  • Limit who can manage role groups in the Microsoft Purview portal, and require phishing-resistant MFA for those accounts and for the eDiscovery staff.
  • Send the unified audit log, including the Purview records, to your SIEM and alert on exports and role group assignments.
  • Agree with the legal team on a simple record of cases, so that an export can be matched to a matter.

Frequently asked questions

Why do these rules convert for Splunk only?

The eDiscovery and role group records are Microsoft Purview records of the unified audit log. The Microsoft 365 connector of Microsoft Sentinel collects Exchange, SharePoint and Teams records, and the library has no documented QRadar source for Purview records. The Splunk Add-on for Microsoft Office 365 reads all audit events of the Management Activity API, so only Splunk gets a query.

Does an eDiscovery export show up in the mailbox or site that was searched?

No. The search and the export run in Microsoft Purview, not in the mailbox or the site, and the owner of the content is not told. The record of it is in the unified audit log, under the eDiscovery activities, with the case, the query and the data sources as detailed properties.

Do the rules cover eDiscovery done with PowerShell?

Not reliably. Microsoft states that the audit log also has a group named eDiscovery cmdlet activities, which returns records from the cmdlet audit log. The rules on this page read the operations of the Microsoft Purview portal that Microsoft lists by name. Check your own audit data for the cmdlet records if your staff or an attacker could use Security and Compliance PowerShell.

Is there a public incident report for this technique?

No public incident report describes this at the audit event level. The page is based on what Microsoft documents about eDiscovery: what the eDiscovery Manager role group can search and export, and which audit operations each step writes.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.