---
title: "Microsoft Defender for Identity"
slug: "microsoft-defender-for-identity"
updated: 2025-03-24T16:33:06Z
published: 2025-03-24T16:33:06Z
canonical: "docs.databee.buzz/microsoft-defender-for-identity"
---

> ## 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 for Identity

Microsoft Defender for Identity is a cloud-based security solution that provides identity monitoring across your organization. Defender for Identity is fully integrated with Microsoft Defender XDR, and leverages signals from both on-premises Active Directory and cloud identities to help you better identify, detect, and investigate advanced threats directed at your organization. For detailed information, please refer to the [Microsoft’s official documentation](https://www.microsoft.com/en-in/security/business/siem-and-xdr/microsoft-defender-for-identity).

**Integration Method:** API

**Tables**: User Inventory Info (5003)

This integration supports the following type of events.

| **Event** | **Description** |
| --- | --- |
| Users | Retrieve a list of user objects. |

This integration supports the following versions.

| Microsoft Graph API version | v1.0 |
| --- | --- |

> [!NOTE]
> **Note:**
> 
> Microsoft Defender for Identity 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-for-identity/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 privilege.
- The user should have access to the DataBee console.

## Configuration Overview

1. Create an application with required permissions to fetch the data.
2. Create [Microsoft Defender for Identity Data](/user-manual/docs/microsoft-defender-for-identity#databee-configuration) Feed in the DataBee console with the required Client credentials.

| **DataBee Parameter** | **Azure Parameter** |
| --- | --- |
| Client Key | Application (Client) ID |
| Client Secret | Client Secret Value |
| 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 privilege.
2. In the search bar, search for **App Registrations** and select it. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-qnm78bok.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
3. On the “App registrations” page, click **New registration.** The “Register an application” window will open. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-qusgmyeu.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
4. On the “Register an application” window:
  1. Under ‘Name’**,** enter your Application Name then click on **Register** to create the application. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-x15rt8ox.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
5. On the app **Overview** page, copy the **Application (client) ID** and **Directory (tenant) ID** for later use. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-u97h3mdq.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)

### Add Endpoint Access

Once the application is created, two permissions should be provided to fetch data. The appropriate permissions for the application are needed to access these endpoints. The following section details how to configure and add permissions 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-for-identity-mar2025-image-sy5aw7yk.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%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-defender-for-identity-mar2025-image-xywjnjmp.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
4. Click on **Application Permissions.** ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-bkww3sy5.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
5. The following permissions need to be granted for the endpoint to function properly:

| **Event** | **Type** | **Permission** |
| --- | --- | --- |
| Users | Application | AuditLog.Read.All |
| Users | Application | User.Read.All |
6. In the Select permissions search bar, enter the permissions shown above, and check the box to include them. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-8iokf76r.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
7. Click the **Add permissions** button after selecting all required permissions. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-qr7txm7v.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
8. On the “API permissions” page, click **Grant Admin Consent** **for <tenant>**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-3v2x1ely.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
9. Click the **Yes** button on the consent confirmation. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-m63iv450.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
10. The necessary permissions have now been added for the endpoints. After this step, the permissions should include at least the minimum required permissions shown in the screenshot below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-b7swv0lk.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)

### Create 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**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-8p5ivpty.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
3. Click **New client secret**. Then “Add a client secret” window appears. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-9yab39hu.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
4. On “**Add a client secret**” window:
  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. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-omarj2mt.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)

> [!NOTE]
> **Note**:
> 
> The user needs to re-create the client secret when it expires.
5. Copy the ‘Value’ fields for later use. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-dtk1jbxs.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)

## DataBee Configuration

1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-ik6y5w2y.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
2. Search for the **Microsoft Defender for Identity** and click it as shown below.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-jgf9f62t.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
3. Click on the **API Ingest** option for collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-1jxc5b8q.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-0spvlmip.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
5. In the configuration page, confirm the following:
  - Authorization Method: OAuth2
  - API Base URL: this is the base URL that DataBee will interact with.
  - Client Key: paste the [**Client ID**](/user-manual/docs/microsoft-defender-for-identity#create-an-application) generated earlier in the Azure portal.
  - Client Secret: paste the [**Client Secret**](/user-manual/docs/microsoft-defender-for-identity#create-the-client-secret) value generated earlier in the Azure portal.
  - Token URL: replace <application_id> with your **Directory (Tenant) ID**.
  - Event Types: preselected for all the event types that integration pulls.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-identity-mar2025-image-uw65d9s0.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A53Z&se=2026-11-15T01%3A04%3A53Z&sr=c&sp=r&sig=poJ6hBvv3bSCokARZd7vBbzxCpv3IGo%2Bl4SyGfpO9%2Fo%3D)
6. Click **Submit**.

## Troubleshooting Tips

- If you are facing an **invalid client** or **unauthorized client** error this might be possibly due to incorrect credentials. Ensure the client key, client secret and Tenant ID are pasted correctly. Since you cannot view the client secret after the 1st time, re-create it, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed.
- If you are facing response code – **403** this might be possibly due to missing permissions. Ensure that all the required permissions are granted correctly as per the above-mentioned steps.