You can use the search feature to search for and delete email messages from all mailboxes in your organization. This process can help you find and remove potentially harmful or high-risk email, such as: Messages that contain dangerous attachments or viruses Phishing messages Messages that contain sensitive data However, the eDiscovery purge process isn't intended for general mailbox management ...
Summary: Learn how to search for and purge messages from Exchange Server 2016 and Exchange Server 2019 mailboxes.
If the purge data operation is started successfully, this action returns a 202 Accepted response code. The response also contains a Location header, which contains the location of the Purge data operation that was created to commit the purge. To check the status of the purge data operation, make a GET request to the location URL.
You can refer to: Search for and delete email messages in your organization | Microsoft Learn Using PowerShell to purge: The portal doesn't have a "Delete" or "Purge" button for search results in eDiscovery cases. Purging (removing emails from mailboxes) requires PowerShell or Microsoft Graph API (for advanced eDiscovery Premium cases). This is a common point of confusion, many admins expect a ...
Try running the purge on a smaller batch (e.g., filter by folder or date). If it still fails after several attempts, opening a Microsoft support case might be the best path — this could be infra-side.
Purging the queue causes Message Queuing to set the queue modification flag, which affects the LastModifyTime property. Messages that are purged from the queue are lost; they are not sent to the dead-letter queue or the journal queue. The following table shows whether this method is available in various Workgroup modes.