---
title: "Azure Activity"
slug: "azure-activity"
updated: 2025-03-14T17:38:50Z
published: 2025-03-14T17:38:50Z
canonical: "docs.databee.buzz/azure-activity"
---

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

Azure Activity Logs provide a comprehensive record of actions, capturing operations that impact resources, such as creating, updating, or deleting resources. They cover various categories, including administrative actions, service health events, alert triggers, and policy compliance checks. Activity Logs are retained for 90 days.

Common use cases include security auditing, compliance tracking, diagnostics, and setting automated alerts. For more details, refer to [Microsoft’s official documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log-schema).

**Integration Method**: API

**Tables**: Detection Finding (2004), Compliance Finding (2003), Entity Management (3004)

This integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| Administrative | Admin activities that provide information about user or group management |
| Alerts | Detection alerts generated by Azure Activity |
| Policy | Compliance information with reference to the policies |
| Security | Reports Detections/findings for a specified resource |

This integration supports the following versions.

| Azure Activity API version | 2015-04-01 |
| --- | --- |

> [!NOTE]
> Note:
> 
> Azure Activity 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).

## 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.
2. Create [Azure Activity data feed](/user-manual/docs/azure-activity#databee-configuration) in the DataBee console with the required client credentials.

| **DataBee Parameter** | **Azure Parameter** |
| --- | --- |
| Client Key | [Application (client ID)](/docs/azure-activity#clientid) |
| Client Secret | Client secret Value |
| Token URL(<tenant_id>) | [Directory (Tenant) ID](/docs/azure-activity#tenantid) |
| Subscription ID (subscriptionId) | Subscription 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-activity-api-config-v1.0-mar2025-image-4y6hbsn4.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
3. On the “Register an application” window:

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-86a5tn6k.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%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-activity-api-config-v1.0-mar2025-image-ow1gqi20.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
5. Login on to [Azure portal](https://portal.azure.com/) with an account that has the Global Administrator role. In the search bar check for **Subscriptions** and select it.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-7pv6gmn2.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
6. Select the **Subscription name** as shown below.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure_activity_subscription.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
7. On the **Overview** page, copy the **Subscription ID** for later use.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-5jy0us15.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%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-activity-api-config-v1.0-mar2025-image-zdf9kgsx.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%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-activity-api-config-v1.0-mar2025-image-sbl89o5h.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
4. Click on **Application permissions**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-swsro4yt.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
5. The following permissions need to be granted for the endpoint to function properly:

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

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-ee5f22hx.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
6. In the search bar check for **Subscriptions** and select it.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/subscriptions.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
7. Assign the **Reader** Role to the Subscription. Click on **Access Control** and select **Add**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-w4iet30q.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
  - Permission Name: Reader
  - Type: RBAC
  - Scope: Subscription
8. Under **Role** select the **Reader** and **Select members** to be added.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-vui9dh4w.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-8r3skc0a.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)

> [!NOTE]
> Note:
> 
> 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-activity-api-config-v1.0-mar2025-image-gws8kviu.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%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-activity-api-config-v1.0-mar2025-image-bmnboc6i.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
4. On “Add a client secret” window:

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-r7ew6xvx.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%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-activity-api-config-v1.0-mar2025-image-u8q7e8jv.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%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-activity-api-config-v1.0-mar2025-image-yhlwq9ob.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
2. Search for the **Azure Activity** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-fgomsyc6.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%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-activity-api-config-v1.0-mar2025-image-qon5kuuk.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-ptqtqda2.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
5. In the configuration page, confirm the following:

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-activity-api-config-v1.0-mar2025-image-fnbdau1p.png?sv=2026-02-06&spr=https&st=2026-10-27T01%3A01%3A30Z&se=2026-10-27T02%3A01%3A30Z&sr=c&sp=r&sig=AP0WFBeRPEE6kFvHhUm%2F6sPcQaheQAKhRx3y%2BNm6kMM%3D)
  - Client Key: paste the [Application (Client) ID](/docs/azure-activity#clientid) generated previously.
  - Client Secret: paste the Client Secret generated previously.
  - Token URL: replace <tenant_id> placeholder with your [Directory (Tenant) ID](/docs/azure-activity#tenantid).
  - Subscription ID: paste the Subscription ID noted earlier.
  - 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.