Microsoft Purview has two tools for this job. Petri contributor Michael Reinders compares them and boils the difference down to a rule of thumb: Audit shows what happened, and eDiscovery finds the content involved. The rule holds up. Microsoft's documentation adds several caveats that decide whether an investigation succeeds or stalls, and those are covered below.
Audit vs. eDiscovery at a glance
Reinders suggests picking the tool from the question being asked:
| Investigation question | Start with |
|---|---|
| Who deleted a Teams message, and when? | Purview Audit |
| Who changed mailbox permissions? | Purview Audit |
| Who downloaded a SharePoint document? | Purview Audit |
| Who removed someone from a Team? | Purview Audit |
| What did the conversation contain? | eDiscovery |
| Find emails discussing a project | eDiscovery |
| Locate documents or Teams conversations relevant to a matter | eDiscovery |
| Preserve content relevant to an investigation | eDiscovery |
Treat this as a shorthand. It isn't a complete description of either product. Audit won't give you message text. eDiscovery isn't required for every activity question. Real investigations often move from one tool to the other.
What Purview Audit does
Audit records activity. When a user or admin performs an audited action, the system writes a record to the audit log. Microsoft retired all classic eDiscovery experiences on August 31, 2025, but the Audit workflow in the Purview portal is separate from that change.
Practical points from Microsoft's documentation:
- Auditing must be on. Audit log search is turned on by default for Microsoft 365 and Office 365 enterprise organizations, and you can verify the setting in Exchange Online PowerShell with
Get-AdminAuditLogConfig | Format-List UnifiedAuditLogIngestionEnabled. Run it there and not in Security & Compliance PowerShell, where the property always shows False. - Teams data only exists from the point auditing was enabled. Microsoft's Teams audit page says audit data is only available from the point at which you turn on auditing.
- Roles matter. To search the log you need the Audit Logs or View-Only Audit Logs role.
- There is a lag. For core services such as Exchange, SharePoint, OneDrive and Teams, records typically appear 60 to 90 minutes after the event. Microsoft doesn't commit to a specific time.
- Search criteria. The portal lets you filter by date and time range (UTC), users, activities, record types, workloads, and file, folder or site. The maximum range is 180 days.
- Export limits. Export supports up to 50,000 rows for Audit (Standard) and up to 1,000,000 rows for Audit (Premium).
A caveat on "who did it"
Audit doesn't always name the real actor. When Teams membership changes through Microsoft Entra ID, the Microsoft 365 admin portal or the Microsoft 365 Groups Graph API, Microsoft says the Teams audit entries show an existing team owner as the initiator. They don't show the person who actually made the change. In those cases Microsoft advises checking the Entra ID or Microsoft 365 Group audit logs. This matters for an "who removed someone from the Team?" question, so confirm the actor before it goes into an HR file.
How long audit records last
Audit history has a limit, and an old investigation may run into it. Microsoft's current figures:
- Non-E5 users and guests: 180 days. The Audit (Standard) default changed from 90 to 180 days. Records generated before October 17, 2023 stay at 90 days. Records generated on or after that date get 180.
- E5 users (Office 365 E5, Microsoft 365 E5, Purview Suite, or the E5 eDiscovery and Audit add-on): Audit (Premium) keeps Exchange, SharePoint, OneDrive and Microsoft Entra records for one year by default. Other activity types are kept for 180 days unless a retention policy changes that.
- Longer retention: custom audit retention policies can retain records for up to 10 years. The user who generated the record needs the matching licence. Ten years also requires the 10-year audit log retention add-on on top of E5.
Retention follows the licence of the user who generated the record. If that user lacks the licence a policy calls for, the record falls back to the default for that user's licence. Microsoft also notes that licence or policy changes don't update items already committed. Check the licensing and policy configuration before you promise HR a timeline.
What eDiscovery does
eDiscovery searches stored content: email, chats, files and group conversations. The Petri piece lists Exchange Online, Teams, SharePoint, OneDrive, Microsoft 365 Groups and Viva Engage as searchable locations.
The classic tools are gone
Older guides still describe three separate tools. That retirement includes classic Content Search, classic eDiscovery (Standard), and classic eDiscovery (Premium). Microsoft's legacy page says the older guidance now applies only to organizations hosted by 21Vianet in China. One third-party write-up notes that every search now runs inside a case in the Microsoft Purview portal. That is a practical reason to create a case first, as Reinders recommends. Tiering has moved to licensing, so Standard and Premium now describe licensed feature sets rather than separate menus.
Searching Teams: pick the right mailbox
"Search Teams" is not a single target. Microsoft's eDiscovery documentation says channel conversations are associated with the team's mailbox. Chat-list conversations (1 x N chats) are associated with the mailboxes of the participating users. Your locations must match the type of conversation. Otherwise you may run a clean-looking search that finds nothing.
Deleted doesn't always mean gone
Microsoft's Teams retention documentation says deleted messages can remain discoverable when a hold applies. It describes the mechanism:
- Teams chat and channel data is copied into hidden mailbox folders that eDiscovery tools can search.
- Permanent deletion from the SubstrateHolds folder is suspended while a Teams retention policy, Litigation Hold, delay hold or eDiscovery hold affects the mailbox.
- While the mailbox is under a hold, deleted Teams messages are no longer visible in the Teams app but stay discoverable in eDiscovery.
- When a user deletes a message under a retention policy, the message doesn't go into the SubstrateHolds folder for 21 days. After that it stays for at least 1 day, and a timer job that typically runs every 1 to 7 days handles permanent deletion.
Microsoft's guidance is to verify compliance requirements with eDiscovery tools, not by looking at what the Teams app shows. Don't promise HR the message can be recovered. Whether it can depends on retention policies, holds and whether the content has been permanently purged.
Permissions and case access
Investigation access needs deliberate setup. Under Microsoft's role model:
- eDiscovery Manager members can search, preview and export, and they create and manage cases. Managers can only access the cases they create.
- eDiscovery Administrators can see and access all cases. Microsoft advises limiting how many people hold this role because they can reach sensitive results.
- Only an eDiscovery Administrator can remove members from a case. That includes cases the manager created.
- Custom roles let you split duties. Compliance Search, Preview, Export, Hold and Review are separate roles.
- Adding or removing a role from a role group automatically removes that role group from any case it belongs to. Re-check membership after changing roles.
A case supports least-privilege access, but it doesn't enforce it on its own. Role and membership configuration does.
A working sequence for the Teams scenario
This follows Reinders's workflow, with the caveats added.
- Confirm auditing was on and the event is within retention. Check the ingestion setting and the relevant user's licence.
- Search the audit log. In the Purview portal, open Audit and filter by time range, user and Teams activities. Keep the scope tight.
- Verify the actor. For membership changes made outside Teams, check the Entra or Microsoft 365 Group audit logs.
- Open or create an eDiscovery case. Make sure only the intended investigators are members.
- Build a targeted search. Use the users, approximate time, keywords and locations you learned from Audit. For chats, search participants' mailboxes. For channel posts, search the team's mailbox.
- Check holds and retention before concluding anything is lost. If content must be preserved, use an eDiscovery hold within the approved scope.
- Follow your organization's HR and legal procedures. Don't widen the search beyond what was authorized.
What to make of it
The Petri article's strength is the scoping discipline. Starting with Audit narrows the eDiscovery search, which saves time and limits how much content investigators see. Two details deserve more weight than the source gives them. One is that retention windows and licensing can close the audit trail before you start. The other is that Teams storage decides where a content search must look.
Reinders writes from the administrator's point of view, and the piece is general guidance. It doesn't tell you what your tenant is licensed for. Verify retention settings and role assignments in your own environment, because those differ between organizations.
Bottom line
- Use Audit for who did what, and when. Check retention and the licence of the user who generated the record.
- Use eDiscovery for what was said or stored. Target the right mailboxes and work inside a case.
- Use both when you need a timeline and the underlying content, with Audit first to scope the search.
- Don't assume a deleted message is gone or recoverable until you've checked holds and retention.
References
- Microsoft Purview Audit vs. eDiscovery: Which Tool Should IT Administrators Use? Petri IT Knowledgebase · 2026-11-19T15:00:19+00:00
- Search the audit log for events in Microsoft Teams | Microsoft Learn learn.microsoft.com
- Search the audit log | Microsoft Learn learn.microsoft.com