---
title: "Microsoft XDR"
slug: "microsoft-xdr"
updated: 2025-03-17T17:30:26Z
published: 2025-03-17T17:30:26Z
canonical: "docs.databee.buzz/microsoft-xdr"
---

> ## 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 XDR

Microsoft Defender XDR natively coordinates detection, prevention, investigation, and response across endpoints, identities, email, and applications to provide integrated protection against sophisticated attacks. For detailed information, refer to [Microsoft’s official documentation](https://www.microsoft.com/en-in/security/business/siem-and-xdr/microsoft-defender-xdr).

**Integration Method:** API

**Tables:** Detection Finding (2004), File System Activity (1001), Memory Activity (1004), Module Activity (1005), Scheduled Job Activity(1006), Process Activity(1007), Network Activity (4001), DNS Activity (4003), Device Config State (5002), Peripheral Device Query (5014), Application Lifecycle (6002), Scan Activity (6007), Device Inventory Info (5001), Authentication (3002), Device Config State Change (5019), Email Activity (4009), Incident Finding (2005), Email URL Activity (4012), Group Management (3006), Account Change (3001), Email File Activity (4011).

The integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| Alert Info | Contains information about security alerts generated by Microsoft Defender, including details like alert ID, severity, category, and detection source. |
| Alert Evidence | Provides evidence associated with security alerts, such as file names, URLs, IP addresses, and other entities related to the alert. |
| Device File | Logs file system activities on devices, including creation, modification, and deletion of files. |
| Identity Directory | Captures events related to directory services, such as changes to user accounts, groups, and directory configurations. |
| Identity Logon | Records user logon activities, including successful and failed authentication attempts across devices and applications. |
| Identity Query | Tracks queries made to identity systems, like directory lookups and authentication requests. |
| Device Info | Provides detailed information about devices, including operating system, hardware specifications, and security posture. |
| Device Network | Logs network activities on devices, such as inbound and outbound connections, including details like IP addresses and ports. |
| Device Image Load | Records events when executable images (like DLLs) are loaded into a process on a device. |
| Device Process | Captures information about processes that are started or terminated on devices, including command-line details. |
| Device Network Info | Provides information about network configurations on devices, such as IP addresses, MAC addresses, and DNS settings. |
| Device Logon | Records logon and logoff activities on devices, including user accounts and session durations. |
| Device File Certificate Info | Contains details about digital certificates associated with files on devices, aiding in assessing file authenticity. |
| Email Attachment Info | Provides information about email attachments, including file names, types, and hashes. |
| URL Click | Logs events when users click on URLs, capturing details like the clicked URL, user, and device information. |
| Email Post Delivery | Contains information about actions taken on email messages after they have been delivered, such as moves to junk or deletion. |
| Email | Provides details about email messages processed by the system, including sender, recipient, subject, and filtering actions taken. |
| Email URL Info | Contains information about URLs found in emails and attachments, including the full URL and its domain. |
| Device Registry | Logs creation and modification of registry entries on devices, providing insights into changes in system configurations. |

This integration supports the following versions.

| Microsoft Graph API Version | beta |
| --- | --- |

> [!NOTE]
> **Note:**
> 
> Microsoft XDR is a continuously updated cloud service. As for this document preparation, the latest release was in January 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-xdr#create-an-application)
  2. [Add endpoint access](/user-manual/docs/microsoft-xdr#add-endpoint-access)
  3. [Create the client secret](/user-manual/docs/microsoft-xdr#creating-the-client-secret)
2. Create [Microsoft XDR data feed](/user-manual/docs/microsoft-xdr#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](/docs/microsoft-xdr#client_secrets) |
| Token URL(<application_id>) | Directory (Tenant) ID |

## Azure 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-xdr-mar2025-image-yzxeeddm.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%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/image-1742205206057.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
4. On the “Register an application” window:

![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-yh8jj8gj.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%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-xdr-mar2025-image-fty6hj3o.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%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-xdr-mar2025-image-aj91woew.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
3. On “Request API permissions” window, Click on **Microsoft APIs** then on **Microsoft Graph**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-at1var5w.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
4. The following permissions need to be granted for the endpoint to function properly:

| **Event** | **Type** | **Permission** |
| --- | --- | --- |
| All Events | Application | ThreatHunting.Read.All |

From the ‘ThreatHunting’ dropdown, select **ThreatHunting.Read.All**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-ynywzyvk.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
5. Click the **Add permissions** button after selecting all required permissions. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-73dtls8j.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
6. On the “API permissions” page, click **Grant Admin Consent** **for <tenant>**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-y5yj3po1.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
7. Click the **Yes** button on the consent confirmation. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-poyr5f76.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
8. 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-xdr-mar2025-image-hvu2qvn8.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)

### 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-xdr-mar2025-image-oz28u5xg.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
3. Click **New client secret**. Then “Add a client secret” window appears. ![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-3hn8ru87.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
4. On “Add a client secret” window:

![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-vyybj3dz.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%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-xdr-mar2025-image-7p9f75gd.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)

## 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-xdr-mar2025-image-uob30h94.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
2. Search for **Microsoft XDR** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-ppok0zgs.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%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-xdr-mar2025-image-i1iyqf8q.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-m8cvluya.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
5. In the configuration page, enter the following:

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-xdr-mar2025-image-zwbdkan9.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A32%3A19Z&se=2026-10-30T12%3A32%3A19Z&sr=c&sp=r&sig=NvYYLmBuUzxRx9kYUt%2FkNcs%2FmbuzOU5HQC%2BaLKGFHnA%3D)
  - Authorization Method: OAuth2
  - Client Key: paste the Application (Client) ID generated earlier in the Azure portal.
  - Client Secret: paste the [Client Secret](/docs/microsoft-xdr#client_secrets) value generated earlier in the Azure portal.
  - Token URL: replace <application_id> with your Directory (Tenant) ID.
6. Click **Submit**.

## 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."}}