---
title: "Azure AD"
slug: "azure-ad"
updated: 2026-04-27T13:30:47Z
published: 2026-04-27T13:30:47Z
canonical: "docs.databee.buzz/azure-ad"
---

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

# Azure AD

Azure AD is a cloud-based identity and access management service that employees can use to access external resources. For detailed information, please refer to [Microsoft’s official documentation](https://www.microsoft.com/en-in/security/business/identity-access/microsoft-entra-id).

**Integration Method:** API

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

This integration supports the following types of events.

| Event | Description |
| --- | --- |
| Users | Retrieve a list of user objects. |
| Users by groups | Retrieve users by provided groups |

This integration supports the following versions.

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

> [!NOTE]
> Note:
> 
> Azure AD is a continuously updated cloud service. As for this document preparation, the latest release was in November 2025.

## Prerequisites

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

## Configuration Overview

1. Create an application with required permissions to fetch the data.
2. Create [Azure AD data feed](/user-manual/docs/azure-ad#databee-configuration) 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(<tenant_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 role.
2. In the search bar, search for **App registrations** and select it. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-feb-2025-image-wmn8rdpp.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
3. On the “App registrations” page, select **New registration**, “Register an application” window will appear. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-feb-2025-image-ziq3mjpr.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%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/azure-ad-feb-2025-image-27gyv2qt.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%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/azure-ad-feb-2025-image-ivqg6h9u.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)

### Add Endpoint Access

Once the application is created, three permissions should be provided in order 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/azure-ad-feb-2025-image-9i1hbc7o.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%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/azure-ad-feb-2025-image-0961kcfr.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
4. Click on **Application permissions**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-feb-2025-image-5tcqhatp.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
5. The following permissions need to be granted for the endpoint to function properly:

| Event | Type | Permission |
| --- | --- | --- |
| Users | Application | User.Read.All AuditLog.Read.All |
| Groups | Application | GroupMember.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/azure-ad-feb-2025-image-boshr307.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aad1.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aad2.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)

1. Click the **Add permissions** button after selecting all required permissions.
2. On the **API permissions** page, click **Grant Admin Consent** **for <tenant>**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/ADpermissions.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
3. Click the **Yes** button on the consent confirmation. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/AD2.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
4. 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/AD3.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)

### Create the Client Secret

The final step to access 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/azure-ad-feb-2025-image-fbrmls2p.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
3. Click **New client secret**. Then “Add a client secret” window appears. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-feb-2025-image-d51ebqaz.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%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/azure-ad-feb-2025-image-fuvtrqgs.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)

> [!NOTE]
> Note:
> 
> The user needs to re-create the client secret when it expires.
5. Copy the **Value** field for later use. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-feb-2025-image-ubllksaq.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%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/azure-ad-feb-2025-image-30am1rlh.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
2. Search for the **Azure AD** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aad1(1).png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
3. Click on the **API Ingest** option for collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-feb-2025-image-or2pk56i.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/AAD3.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
5. In the configuration page, confirm the following:

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/AAD4(1).png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A20%3A12Z&se=2026-10-30T13%3A20%3A12Z&sr=c&sp=r&sig=nKBbDYn6tbFIqJrcIYGnkQDI9Sd6%2BdUULPx3h1966mk%3D)
  - API Base URL: this is the base URL that DataBee will interact with.
  - Authorization Method: OAuth2
  - Client Key: paste the Application (Client) ID generated earlier
  - Client Secret: paste the Client Secret Value generated earlier in the Azure portal.
  - Token URL: replace <tenant_id> placeholder with your Directory (Tenant) ID.
  - Event Types: Preselected for all the event types. Please choose one.
    - There are two event types: Users and Users By Groups
      - Select **Users,** to fetch all users.
      - Select **Users by groups,** to limit fetching users by groups.
    - **Include SignIn Activity:** Enable this option to fetch sign-in activity of the user.

> [!WARNING]
> IMPORTANT:
> 
> 1. If the User by Groups event is selected, enter a comma seperated group names in the Group Names text box. A max of 15
> 
> group names per feed is allowed
> 2. If Include Signin Activity is checked, then AuditLog.Read.All permission **must** be granted
6. Click on **Test Connection** to verify the credentials are valid.
7. Click **Submit**.

> [!NOTE]
> Note
> 
> If the connection test fails, the **Submit** button will remain disabled. Onboarding will not proceed until the issue is resolved and the connection test is successful.

## 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 **403** response code this might be possibly due to missing permissions. Ensure that all the required permissions are granted correctly as per the above-mentioned steps.