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.

Integration Method: API

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

This integration supports the following events.

This integration supports the following versions.

Note:

Azure Activity is a continuously updated cloud service. As for this document preparation, the latest release was in March 2025.

Prerequisites

• The user should have access to the Azure 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 with required permissions to fetch the data. 

2. Create Azure Activity data 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(<tenant_id>)	Directory (Tenant) ID
   Subscription ID (subscriptionId)	Subscription ID

Azure Configuration

Create an application

1. Log on to Azure portal with an account that has the Global Administrator role.

2. In the search bar, search for App registrations and select it. 

   
   

3. On the “Register an application” window:

   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. 

   

5. Login on to Azure portal with an account that has the Global Administrator role. In the search bar check for Subscriptions and select it.

   

6. Select the Subscription name as shown below.

   

7. On the Overview page, copy the Subscription ID for later use. 

   

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.

   

3. On “Request API permissions” window, click on Microsoft APIs then on Microsoft Graph.
    

4. Click on Application permissions.

   

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

   
   

6. In the search bar check for Subscriptions and select it.

   

7. Assign the Reader Role to the Subscription. Click on Access Control and select Add.

   • Permission Name: Reader

   • Type: RBAC

   • Scope: Subscription

   

8. Under Role select the Reader and Select members to be added.

   

   

   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.  
     

3. Click New client secret. Then “Add a client secret” window appears.  
    
   

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.

   
   

   Note:

   The user needs to re-create the client secret when it expires.

5. Copy the Value fields for later use. 
    

   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.
    

2. Search for the Azure Activity and click it as shown below.
    

3. Click on the API Ingest option for collection method.
    
   

4. Enter feed contact information and click Next.
    
   

5. In the configuration page, confirm the following:

   • Client Key: paste the Application (Client) ID generated previously.

   • Client Secret: paste the Client Secret generated previously.

   • Token URL: replace <tenant_id> placeholder with your Directory (Tenant) ID.

   • 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 1^st 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.