---
title: "Azure VDI User Session"
slug: "azure-vdi-user-session"
updated: 2025-11-03T17:26:39Z
published: 2025-11-03T17:26:39Z
canonical: "docs.databee.buzz/azure-vdi-user-session"
---

> ## 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 VDI User Session

Azure Virtual Desktop Infrastructure (VDI) delivers simplified management, multi-session Windows 10 and optimizations for Microsoft 365 Apps for enterprise. For detailed information refer to the [Azure VDI official documentation](https://learn.microsoft.com/en-us/azure/virtual-desktop/).

**Integration Method:** API

**Tables**: Authentication (3002)

This integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| User Session | Captures user session activity within Azure Virtual Desktop environments, including session initiation, active state, user identity, and associated host pool details |

The *Azure User Session* feed supports the following versions.

| Azure Activity API version | 2025-04-01, 2024-04-03 |
| --- | --- |

> [!NOTE]
> **Note:**
> 
> Azure VDI is a continuously updated cloud service. As for this document preparation, the latest release was in [March 2025](https://azure.microsoft.com/en-us/updates).

Refer to these related feeds which provide different information regarding Azure VDI:

- [Azure VDI Applications](/user-manual/docs/azure-vdi-application)
- [Azure VDI Workspace](/user-manual/docs/azure-vdi-workspace)

## Prerequisites

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

## Configuration Overview

1. [Create an application](/user-manual/docs/azure-vdi-user-session#create-an-application) with required permissions to fetch the data.
2. Create [Azure VDI User Session data feed](/user-manual/docs/azure-vdi-user-session#databee-configuration) in the DataBee console with the below parameters.

| **DataBee Parameter** | **Azure Parameter** |
| --- | --- |
| Client Key | [Application (client ID)](/docs/azure-vdi-user-session#clientid) |
| Client Secret | Client secret Value |
| Token URL(<tenant_id>) | [Directory (Tenant) ID](/docs/azure-vdi-user-session#tenantid) |

## Azure Configuration

### Create an application

1. Log on to [Azure](https://portal.azure.com/) portal 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/azure-vdi-user-session-image-yd8qrr4y.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
3. On the “Register an application” window:

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-f8zngddv.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
  1. Under ‘Name’, enter your Application Name then click on **Register** to create the application.
4. 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-vdi-user-session-image-79msjdb0.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
5. Login on to [Azure](https://portal.azure.com/) portal with an account that has the **Global Administrator** privilege. In the search bar, check for **subscriptions** and select it.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-r262aku1.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
6. Select the Subscription name as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/image-1762160133284.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
7. On the **Overview** page, copy the **Subscription ID** for later use.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-ywaujwup.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
8. In the search bar, check for **Resource groups** and select it.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-qyq79mgn.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
9. In the “Resource groups” page, copy the **Resource Group name** for later use.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-y89w8opj.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)

### Add Endpoint Access

Once the application is created, three 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/azure-vdi-user-session-image-bhmfw6jg.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%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-vdi-user-session-image-xav147wc.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
4. Click on **Application permissions**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-syep1x0z.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
5. The following permissions need to be granted for the endpoint to function properly:

| **Event** | **Permission Name** | **Type** |
| --- | --- | --- |
| User Session | AccessReview.Read.All AuditLog.Read.All | Application |

> [!NOTE]
> **Note:**
> 
> In case of using other data sources such as Azure VDI Application and Azure VDI Workspace parallelly with the current data source, the permissions would be the same.

![A screenshot of a computer screen AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-2pdif17y.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)

### Subscription and Role Assignment

1. In the search bar, check for **subscriptions** and select it.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/image-1762160372114.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
2. Assign the Reader Role to the Subscription. Click on **Access control (IAM)** and select **Add**.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-m023mv80.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
  - **Permission Name:** Reader
  - **Type:** RBAC
  - **Scope:** Subscription
3. Under **Role**, select the **Reader** and **select member** to be added.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-mpkq7lhs.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
4. In the selected role Reader, **select member** to be added.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-5lkittzv.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)

> [!NOTE]
> **Action:**
> 
> Grant the Reader role to the Subscription for the App Registration to enable read-only access to subscription-level resources.

### Create the Client Secret

The final step in 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/azure-vdi-user-session-image-d1fi8sgv.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%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-vdi-user-session-image-8heet0ae.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
4. On “Add a client secret” window:

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-8yh8agtt.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%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 the **Value** fields for later use. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-kwrcav3z.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)

This completes the setup for Azure Activity API integration.

# 

## DataBee Configuration

1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-4r0giho3.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
2. Search for the **Azure VDI** **User Session** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-3n8rrevx.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
3. Click on the **API Ingest** option for collection method. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-74fgp5tx.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
4. Enter feed contact information and add the configurations as mentioned in step 5.
5. In the configuration page, confirm the following:

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-vdi-user-session-image-gptx4wn7.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A54Z&se=2026-10-30T13%3A22%3A54Z&sr=c&sp=r&sig=Vjr6izVJbwmrJS3bpDCHr8WUsE5KfutPS8%2FkzjyW0CY%3D)
  - **Authorization Method: OAuth2**
  - **Client Key:** Paste the [Client ID](/docs/azure-vdi-user-session#clientid) generated previously
  - **Client Secret:** Paste the Client Secret generated previously
  - **Token URL**: Replace <tenant_id> placeholder with your [Directory (Tenant) ID](/docs/azure-vdi-user-session#tenantid)
  - **Event Types**: Preselected for all the event types that integration pulls.
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.

#