Skip to content

Commit 0af8c27

Browse files
authored
Merge pull request #50459 from MicrosoftDocs/NEW-purview-understand-ediscovery
New purview understand ediscovery
2 parents e94908c + a7683ee commit 0af8c27

15 files changed

+406
-0
lines changed
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.purview-ediscovery-understand.compare-classic-new-ediscovery
3+
title: Compare the classic and new eDiscovery experiences
4+
metadata:
5+
title: Compare the classic and new eDiscovery experiences
6+
description: "Compare the classic and new eDiscovery experiences"
7+
ms.date: 05/15/2025
8+
author: wwlpublish
9+
ms.author: riswinto
10+
ms.topic: unit
11+
azureSandbox: false
12+
labModal: false
13+
durationInMinutes: 6
14+
content: |
15+
[!include[](includes/compare-classic-new-ediscovery.md)]
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
Microsoft has updated how eDiscovery works in Microsoft Purview. If you're familiar with the older experience in the Microsoft Purview compliance portal, you'll notice several changes in the new one. Some workflows have been updated or consolidated, while others have been removed entirely.
2+
3+
## Why there are two eDiscovery experiences
4+
5+
During the transition from the Microsoft Purview compliance portal to the new portal, Microsoft introduced an updated experience for managing eDiscovery cases, searches, and review sets. For a limited time, you can still use the classic experience, but the new experience is the supported path going forward.
6+
7+
Many of the same concepts still apply, but the layout, terminology, and feature availability are different.
8+
9+
## What's different in the new experience?
10+
11+
Here are some of the most important differences between the classic and new eDiscovery experiences:
12+
13+
- **Advanced indexing runs automatically**: In the classic experience, advanced indexing had to be triggered manually to reprocess partially indexed content before you could search it. In the new experience, advanced indexing happens automatically when you run a search, add items to a review set, or export results. There's no need to initiate it separately.
14+
15+
- **Search statistics have replaced collections**: The classic experience used collections to estimate the size and scope of potentially relevant content. In the new experience, search statistics provide similar insights. You can still analyze the scope of results and preview items, but you're no longer limited to fixed, immutable collections. Searches can be updated or rerun at any time.
16+
17+
- **Content search is built into eDiscovery**: Previously, Content search was a separate feature from eDiscovery. In the new experience, content search is available by default in a system-generated eDiscovery case. Members of the eDiscovery Manager or Administrator role groups can access it directly. You can also manage holds and review sets within this case, depending on your subscription.
18+
19+
- **Cases are now the central organizing unit**: In the classic experience, custodians played a more prominent role in organizing cases. The new experience centers everything around the case itself. You still assign custodians and add data sources, but those actions all happen within the context of the case.
20+
21+
- **Exporting content is faster and more consistent**: The export process has been streamlined. It now provides faster performance, clearer reports, and consistent options for both standard and premium features. Exporting from either a review set or a search now follows the same unified process.
22+
23+
- **Jobs are now called processes**: In the classic experience, tasks and activities were grouped as jobs. The new experience uses the term processes instead. These provide more visibility and reporting for long-running tasks like indexing, exporting, or adding content to a review set.
24+
25+
## Feature availability based on licensing
26+
27+
In the new eDiscovery experience, standard and premium capabilities are part of the same unified interface. Your organization's license determines which features are available, but there's no longer a need to switch between separate tools. What you can do within a case depends on your permissions and subscription level.
28+
29+
Use the table to understand which capabilities are available based on your license:
30+
31+
| Capability | Standard | Premium |
32+
|-----|-----|-----|
33+
| Search for content |||
34+
| Keyword queries and search conditions |||
35+
| Search statistics |||
36+
| Export search results |||
37+
| Role-based permissions |||
38+
| Case management |||
39+
| Place content locations on hold |||
40+
| Advanced indexing | ||
41+
| Review sets | ||
42+
| Cloud attachments and SharePoint versions | ||
43+
| Optical character recognition (OCR) | ||
44+
| Conversation threading | ||
45+
| Review set filtering | ||
46+
| Tagging | ||
47+
| Analytics (email threading, near-duplicate) | ||
48+
| Computed document metadata | ||
49+
| Reporting for long-running processes | ||
50+
51+
## Temporary access to the classic experience
52+
53+
You can still use the classic eDiscovery experience in the Microsoft Purview portal if your organization relies on specific features that haven't yet migrated. These include:
54+
55+
- Sending and tracking legal hold notifications
56+
- Associating custodians with reusable data sources
57+
- Importing non-Microsoft 365 data into a review set
58+
- Remediating multiple processing errors in bulk
59+
60+
These features will be available only for a limited time and are scheduled to retire after August 2025.
61+
62+
The new eDiscovery experience in Microsoft Purview simplifies how organizations manage searches, holds, and review sets across Microsoft 365. While many core features are still available, the updated interface improves performance and reduces the number of manual steps required. By understanding how the two experiences differ and what features your license includes, you can take full advantage of the latest tools and prepare for the retirement of the older interface.
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
Legal investigations, regulatory requests, and internal reviews often require more than just finding documents. Organizations need a consistent, defensible process for identifying, preserving, reviewing, and producing electronically stored information (ESI). Without the right tools in place, responding to these requests can be slow, inconsistent, or incomplete, putting the organization at risk.
2+
3+
Microsoft Purview provides eDiscovery tools that help legal, compliance, and security teams manage this process end to end. With support for role-based access control, content search, legal holds, review sets, and advanced analytics, organizations can respond to investigations with confidence and consistency.
4+
5+
Learn the core concepts behind eDiscovery in Microsoft Purview, including:
6+
7+
- How the eDiscovery process works and why it matters
8+
- What changed in the new eDiscovery experience
9+
- How Microsoft Purview supports each stage of the eDiscovery lifecycle
10+
- Who has access to eDiscovery and how permissions are assigned
11+
12+
## Learning objectives
13+
14+
By the end of this module, you'll be able to:
15+
16+
- Explain what eDiscovery is and when to use it
17+
- Compare the classic and new eDiscovery experiences in Microsoft Purview
18+
- Describe each step of the eDiscovery lifecycle
19+
- Identify which roles and permissions are required to use eDiscovery features
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
Investigations require more than improvised searches. Organizations need tools that support a defensible eDiscovery process across Microsoft 365 services. Microsoft Purview provides those tools through a modern eDiscovery experience designed to help teams work efficiently while maintaining compliance.
2+
3+
Microsoft Purview supports the full eDiscovery lifecycle, from identifying and preserving content to reviewing and exporting it. The updated experience introduces key improvements over the classic one, and feature availability depends on licensing. Access is managed through permissions that limit sensitive case data to authorized users.
4+
5+
Understanding how eDiscovery works in Microsoft Purview helps organizations handle investigations with more control and less guesswork. With the right tools and permissions in place, teams can move quickly to preserve data, manage access, and deliver results that meet legal and regulatory expectations while minimizing disruption to daily operations.
6+
7+
## References
8+
9+
- [Learn about eDiscovery](/purview/edisc?azure-portal=true)
10+
- [Learn about the eDiscovery workflow](/purview/edisc-workflow?azure-portal=true)
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
eDiscovery in Microsoft Purview follows a structured workflow designed to help legal, compliance, and security teams find and manage content relevant to an investigation. This process ensures that electronically stored information (ESI) is identified, preserved, and reviewed in a consistent and defensible way.
2+
3+
Here's a high-level overview of the eDiscovery workflow:
4+
5+
:::image type="content" source="../media/ediscovery-workflow.png" alt-text="Diagram illustrating the eDiscovery workflow from trigger event to case creation, search, holds, and review actions in Microsoft Purview." lightbox="../media/ediscovery-workflow.png":::
6+
7+
## Step 1: Start with a trigger event
8+
9+
Every eDiscovery case begins with a trigger event. This event could be a legal request, a regulatory inquiry, or an alert from another Microsoft Purview solution, like Insider Risk Management. Trigger events indicate that something needs deeper investigation, which prompts the creation of a new case.
10+
11+
## Step 2: Create and manage the case
12+
13+
A case brings together everything related to the investigation. It consolidates the searches, review sets, and any applied holds used throughout the lifecycle. You can also assign people to the case to control who has access. Microsoft Purview also supports integration with Insider Risk Management so you can escalate directly from a risk case to eDiscovery.
14+
15+
## Step 3: Search and evaluate content
16+
17+
With the case created, the next step is to run searches to find relevant content. You can search across Exchange, SharePoint, OneDrive, and Teams using keywords or other filters. Search statistics help refine results, and you can preview content to make sure you're capturing what matters. If needed, you can revise or rerun queries to adjust your results as the case develops.
18+
19+
## Step 4: Take action on search results
20+
21+
Once results are in, you have a few paths depending on the goals of the investigation:
22+
23+
- **Export content** if it's ready to be shared with legal or external reviewers.
24+
- **Add content to a review set** if you need to organize, filter, or analyze it further.
25+
- **Place a hold** on relevant content to preserve it during the investigation.
26+
27+
A **legal hold** prevents content from being deleted or altered, even if retention policies or user actions would normally allow it. Holds can apply to entire content locations, like a mailbox or SharePoint site, or to specific items returned by a query. They help maintain the integrity of evidence while a case is ongoing.
28+
29+
## Step 5: Review and take action
30+
31+
Review sets are where deeper analysis happens. The investigation team can search within a review set, apply filters, tag items, redact sensitive information, or export selected content. You can also run analytics to reduce the volume of data and help prioritize what gets reviewed first.
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
Access to eDiscovery tools in Microsoft Purview isn't granted by default. Because eDiscovery involves access to sensitive content, permissions must be explicitly granted to ensure that only authorized individuals can create cases, run searches, place holds, and export data.
2+
3+
## Who typically uses eDiscovery?
4+
5+
eDiscovery is often used by legal teams, compliance officers, and security personnel. Depending on how responsibilities are structured in your organization, tasks might be split across different roles:
6+
7+
- **eDiscovery Admins** configure the overall setup, assign permissions, and manage global settings.
8+
- **eDiscovery Managers** create and manage cases, run searches, and review content.
9+
10+
Other teams, such as HR or external counsel, might be added to specific cases with limited access based on the scope of the investigation.
11+
12+
## How are permissions assigned?
13+
14+
Access to eDiscovery features is controlled through **role-based access control (RBAC)** in the Microsoft Purview portal. To perform tasks in eDiscovery, users need to be added to a built-in role group such as **eDiscovery Manager** or **Administrator**, or a custom role group with the right permissions.
15+
16+
Permissions are scoped by case. Even if someone has access to the eDiscovery tools, they can't see a specific case unless they're added to it.
17+
18+
This approach helps organizations ensure that investigations are handled securely, with access limited to only users who need it.
Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
When an organization needs to respond to a legal investigation or regulatory request, it's not enough to hand over random emails or files. Instead, there's a structured legal process for finding, preserving, reviewing, and producing that information in a way that's defensible. This process is called **eDiscovery**, short for **electronic discovery**.
2+
3+
## eDiscovery as a legal and investigative process
4+
5+
eDiscovery is a process used to identify, collect, and produce electronically stored information (ESI) during legal proceedings, internal investigations, audits, or regulatory reviews. This could include emails, chat messages, documents, or anything else stored digitally that's relevant to a case.
6+
7+
There are generally five stages to the eDiscovery process:
8+
9+
1. **Identification**: Locate potentially relevant information.
10+
1. **Preservation**: Make sure the content isn't deleted or altered.
11+
1. **Collection**: Gather the content for analysis.
12+
1. **Review**: Filter, tag, or redact content before sharing it.
13+
1. **Export/Production**: Prepare the content for legal teams or regulatory authorities.
14+
15+
While many people think of eDiscovery as something only legal teams handle, that's not always the case. Security teams, compliance officers, and HR professionals also rely on eDiscovery tools to conduct internal investigations and respond to incidents.
16+
17+
## eDiscovery in Microsoft 365
18+
19+
Microsoft 365 includes a built-in set of tools that help organizations manage each step of the eDiscovery process. These tools are available through **Microsoft Purview**, the compliance and risk management portal for Microsoft 365.
20+
21+
When you use Microsoft Purview for eDiscovery, you can:
22+
23+
- Create and manage eDiscovery **cases**
24+
- Assign **custodians** and place their content on legal hold
25+
- Run targeted **searches** across mailboxes, Teams messages, OneDrive files, and more
26+
- Analyze results in **review sets**
27+
- Export content or even **purge** sensitive items if needed
28+
29+
All of these actions are tracked for auditing purposes and can be restricted based on role-based access controls.
30+
31+
## Use Microsoft Purview for an investigation
32+
33+
Here's a typical example of how someone might use eDiscovery in Microsoft Purview:
34+
35+
Let's say your organization is investigating whether confidential project files were leaked to a competitor. The legal and security teams need to find out:
36+
37+
- Who had access to those files?
38+
- Were they shared externally?
39+
- What was said about them in email or Teams?
40+
41+
In Microsoft Purview, they would:
42+
43+
- Create an **eDiscovery case** to contain all activity related to the investigation.
44+
- Add specific employees as **custodians** and apply a **legal hold** to preserve their data.
45+
- Use the **Search** feature to look across Exchange, SharePoint, OneDrive, and Teams for references to the project.
46+
- Add matching results to a **review set**, where they can tag and filter the data.
47+
- Take appropriate action, such as exporting the results for legal review or purging externally shared content if a data leak is confirmed.
48+
49+
## How Microsoft Purview supports eDiscovery
50+
51+
Microsoft Purview helps organizations take a structured and defensible approach to handling sensitive or legally relevant data. It integrates with Microsoft 365 services like Exchange, SharePoint, OneDrive, Teams, and Microsoft Defender to centralize the eDiscovery process. Instead of relying on manual collection or disconnected searches, Purview allows each step to be tracked, governed, and carried out consistently.
52+
53+
Understanding eDiscovery as both a legal process and a practical workflow helps clarify how Microsoft Purview fits into investigations and compliance tasks. These tools support legal, compliance, security, and HR teams as they work to identify, preserve, and review content in response to investigations or legal obligations.
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
### YamlMime:Module
2+
uid: learn.wwl.purview-ediscovery-understand
3+
metadata:
4+
title: Understand Microsoft Purview eDiscovery
5+
description: "Understand Microsoft Purview eDiscovery."
6+
ms.date: 05/15/2025
7+
author: wwlpublish
8+
ms.author: riswinto
9+
ms.topic: module
10+
ms.service: purview
11+
hidden: false
12+
title: Understand Microsoft Purview eDiscovery
13+
summary: Discover how Microsoft Purview supports a defensible eDiscovery process across Microsoft 365 services. Review how organizations can manage investigations by preserving content, running searches, analyzing results, and controlling access through role-based permissions.
14+
abstract: |
15+
After completing this module, you'll be able to:
16+
- Describe the purpose and stages of the eDiscovery process.
17+
- Compare the classic and new eDiscovery experiences in Microsoft Purview.
18+
- Explain how Microsoft 365 licensing affects feature availability in eDiscovery.
19+
- Identify how permissions are used to control access to sensitive case data.
20+
prerequisites: |
21+
- General understanding of Microsoft 365 services and user roles.
22+
- Familiarity with organizational compliance or investigation workflows.
23+
iconUrl: /training/achievements/generic-badge.svg
24+
levels:
25+
- intermediate
26+
roles:
27+
- auditor
28+
- administrator
29+
products:
30+
- microsoft-purview
31+
- m365
32+
subjects:
33+
- information-protection-governance
34+
- security
35+
- compliance
36+
units:
37+
- learn.wwl.purview-ediscovery-understand.introduction
38+
- learn.wwl.purview-ediscovery-understand.understand-ediscovery
39+
- learn.wwl.purview-ediscovery-understand.compare-classic-new-ediscovery
40+
- learn.wwl.purview-ediscovery-understand.understand-ediscovery-lifecycle
41+
- learn.wwl.purview-ediscovery-understand.understand-ediscovery-permissions
42+
- learn.wwl.purview-ediscovery-understand.knowledge-check
43+
- learn.wwl.purview-ediscovery-understand.summary
44+
45+
badge:
46+
uid: learn.wwl.purview-ediscovery-understand.badge
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.purview-ediscovery-understand.introduction
3+
title: Introduction
4+
metadata:
5+
title: Introduction
6+
description: "Introduction"
7+
ms.date: 05/15/2025
8+
author: wwlpublish
9+
ms.author: riswinto
10+
ms.topic: unit
11+
azureSandbox: false
12+
labModal: false
13+
durationInMinutes: 1
14+
content: |
15+
[!include[](includes/introduction.md)]

0 commit comments

Comments
 (0)