---
title: "Microsoft Defender Office365 E-Discovery Cases"
slug: "ms-defender-for-o365-e-discovery-cases"
updated: 2025-03-25T14:33:20Z
published: 2025-03-25T14:33:20Z
canonical: "docs.databee.buzz/ms-defender-for-o365-e-discovery-cases"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Defender Office365 E-Discovery Cases

Microsoft Defender for Office 365 E-Discovery Cases is a comprehensive tool designed to assist organizations in managing, identifying, and securing data during legal investigations or compliance reviews. It streamlines the process of searching, collecting, and preserving relevant email and file content from Office 365 environments. For detailed information, please refer to the [Microsoft’s official documentation](https://learn.microsoft.com/en-us/graph/api/resources/security-ediscoverycase?view=graph-rest-1.0).

**Integration Method:** API

**Tables:** Incident Finding (2005)

The integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| Cases | Allows organizations to automate eDiscovery workflows, integrate with existing tools, and build repeatable processes for legal needs, investigations, and regulatory requests, focusing on Microsoft 365 data |

This integration supports the following versions.

| Microsoft Graph API Version | v1 |
| --- | --- |

> [!NOTE]
> **Note:**
> 
> Microsoft Defender Office365 E-Discovery Cases API version doesn’t follow a traditional versioning system. Instead, it is a continuously updated cloud service. As for this document preparation, the latest release was in [**March 2025**](https://learn.microsoft.com/en-us/defender-office-365/defender-for-office-365-whats-new#march-2025)**.**

## Prerequisites

- The user should have access to the [Azure portal](https://portal.azure.com/) with an account that has the Global Administrator privileges.
- The user should have access to the DataBee console.

## Configuration Overview

1. Create an application with required permissions to fetch the data.
  1. [Create an application](/user-manual/docs/microsoft-defender-office365-e-discovery-cases#create-an-application)
  2. [Add endpoint access](/user-manual/docs/microsoft-defender-office365-e-discovery-cases#add-endpoint-access)
  3. [Create the client secret](/user-manual/docs/microsoft-defender-office365-e-discovery-cases#creating-the-client-secret)
2. Create [Microsoft Defender for Office365 E-Discovery data feed](/user-manual/docs/microsoft-defender-office365-e-discovery-cases#databee-configuration) in the DataBee console with the required Client credentials.

| **DataBee Feed Parameter** | **Azure Parameter** |
| --- | --- |
| Client Key | Application (client) ID |
| Client Secret | Client Secret Value |
| Token URL(<tenant_id>) | Directory (Tenant) ID |
| Username | Username |
| Password | Password |

> [!NOTE]
> **Note:**
> 
> Username and Password mentioned above are the user credentials used for logging in.

## Microsoft Defender Office365 Configuration

### Create an application

1. Log on to [Azure portal](https://portal.azure.com/) with an account that has the Global Administrator privileges.
2. In the search bar, search for **App registrations** and select it. ![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-a7k2qzlf.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
3. On the “App registrations” page, select **New registration,** then **“**Register an application” window will appear. ![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-tb8k76yo.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
4. On the “Register an application” window:

![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-fzu4evf1.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
  1. Under ‘Name’ enter your Application Name then click on **Register** to create the application.
5. On the app **Overview** page, copy the **Application (client) ID** and **Directory (tenant) ID** for later use. ![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-didg4gnp.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)

### Add Endpoint Access

Once the application is created, one permission to the Graph API is needed. This section details how to configure and add permission to the required endpoints.

#### Add Permissions

From the Azure Active Directory portal:

1. Select the application registered in the previous step.
2. Under **Manage,** click **API permissions** and then click **Add a permission,** the “Request API permissions” window will appear. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-iex2mp7m.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
3. On “Request API permissions” window, click on **Microsoft APIs** then on **Microsoft Graph**. ![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-mv4crfkc.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
4. The following permissions need to be granted for the endpoint to function properly:

| **Event** | **Type** | **Permission** |
| --- | --- | --- |
| Cases | Application | eDiscovery.Read.All |
5. From the ‘eDiscovery’ dropdown, select **eDiscovery.Read.All**

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-jmmjr8i4.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
6. Click the **Add permissions** button after selecting all required permissions. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-wh6a3bxb.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
7. On the “API permissions” page, click **Grant Admin Consent** **for <tenant>**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-y2sl5i5n.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
8. Click the **Yes** button on the consent confirmation. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-2x0313y9.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
9. The necessary permissions have now been added for the endpoints. After this step, the permissions should include these minimum required permissions shown. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-3e2wa9ft.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)

> [!NOTE]
> **Note:**
> 
> If you found any difficulties while configuring. You can refer to [Microsoft's official documentation](https://learn.microsoft.com/en-us/office/office-365-management-api/get-started-with-office-365-management-apis).

### Creating the Client Secret

The final step to accessing the APIs is creating a Client Secret. To create it from the Azure Portal:

1. Select the application created above.
2. Under **Manage**, click **Certificates & secrets**, and then **Client secrets**. ![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-ksyak74g.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
3. Click on **New client secret**.

![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-0i3mdzxb.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
4. On “Add a client secret” window:

![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-cr8fgjex.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)

> [!NOTE]
> **Note**:
> 
> The user needs to re-create the client secret when it expires.
  1. Enter a ‘Description’ for this client secret and select the desired expiry period from the ‘Expires’ drop-list.
  2. Then click on **Add** to create the client secret.
5. Copy **Client secrets** **Value** field for later use. ![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-nvdx93pf.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)

> [!NOTE]
> **Note:**
> 
> The API restricts data retrieval to the last 7 days. Older data cannot be fetched.

## DataBee Configuration

1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-0fn8u98i.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
2. Search for **Microsoft Defender for Office365 E-Discovery Cases** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-j0q3spii.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
3. Click on the **API Ingest** option for collection method. ![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-qzh3n7l9.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-965guqci.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
5. In the configuration page, enter the following:

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-office365-e-discovery-cases-docs-standards-image-aoayiaem.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A53Z&se=2026-10-30T13%3A22%3A53Z&sr=c&sp=r&sig=hi8x026yOFr3xwf2d2VlRTVxo6fdLQzIjXiwUHmrNMo%3D)
  - Authorization Method: OAuth2
  - Client Key: paste the [Application (Client) I](/user-manual/docs/microsoft-defender-office365-e-discovery-cases#create-an-application)D generated earlier in the Azure portal.
  - Client Secret: paste the [Client Secret](/user-manual/docs/microsoft-defender-office365-e-discovery-cases#creating-the-client-secret) value generated earlier in the Azure portal.
  - Token URL: replace <tenant_id> with your [Directory (Tenant) ID.](/user-manual/docs/microsoft-defender-office365-e-discovery-cases#create-an-application)
  - Username: paste [username](/user-manual/docs/microsoft-defender-office365-e-discovery-cases#configuration-overview) Credentials.
  - Password: paste [password](/user-manual/docs/microsoft-defender-office365-e-discovery-cases#configuration-overview) Credentials.
6. Click **Submit**.

> [!NOTE]
> **Note:**
> 
> The URL for the API endpoint that you use is based on the type of Microsoft 365 or Office 365 subscription plan for your organization. Here, we have used the URL for **Microsoft Graph global service**. You can change the URL as per subscription plan for your organization. Below are the list of URLs as per the subscription plans.
> 
> Microsoft Graph global service:[](https://manage.office.com/)[https://graph.microsoft.com](https://graph.microsoft.com)
> 
> Microsoft Graph for US Government L4:[](https://manage-gcc.office.com/)[https://graph.microsoft.us](https://graph.microsoft.us)
> 
> Microsoft Graph for US Government L5 (DOD):[](https://manage.office365.us/)[https://dod-graph.microsoft.us](https://dod-graph.microsoft.us)
> 
> Microsoft Graph China operated by 21Vianet:[](https://manage.protection.apps.mil/)[https://microsoftgraph.chinacloudapi.cn](https://microsoftgraph.chinacloudapi.cn)

## Troubleshooting Tips

- If you encounter an **Invalid client** or **Unauthorized client** error, it may be due to incorrect credentials. Please double-check that the client key, client secret, and Tenant ID are entered correctly. Since the client secret is only visible upon creation, you may need to regenerate it. To avoid any issues, consider pasting it into a text editor to ensure there are no extra spaces or unexpected characters before reconfiguring the DataBee feed.
- If you receive an **Unauthorized** error, it may be because the client ID and client secret belong to different applications. Kindly verify that you are using credentials from the same application to resolve the issue.
- If we encounter response code **401**, it is likely due to missing permissions. Ensure that all required permissions are correctly granted as per the steps outlined above.
  - For example: {"error":{"code":"AF10001","message":"The permission set () sent in the request does not include the expected permission."}}