Microsoft Azure Activity Logs
Ingests Azure control plane logs from the Monitor API to track admin activity across services.
Sync Type: Incremental
Requirements
Before setting up the Microsoft Azure Activity Logs input, you need to:
- Have a Microsoft Account with an active Azure Subscription
- Create an app registration with a client secret
- Assign the application the Reader or Monitoring Reader role on the subscription
The input reads the subscription's Activity Log through Azure Resource Manager. No Log Analytics workspace is involved.
Details
The Microsoft Azure Activity Logs input allows you to collect and ingest activity logs from the Azure Monitor API. On the first sync it starts from the time the input is enabled — there is no historical backfill, so only events occurring after the input is enabled are ingested. Subsequent syncs are incremental and fetch data from the last successful sync time forward.
Delivery delay
Azure Activity Log entries are not queryable the instant an event occurs. Azure documents that an entry becomes available for analysis and alerting within 3 to 20 minutes of the event occurring. To avoid skipping events that are published late, this input holds its cursor back by a fixed buffer and only queries events that are at least 20 minutes old.
As a result, activity logs are ingested with an approximate 20-minute delay from when the event occurred. This is expected behavior and ensures late-published events are not missed. Right after the input is first enabled it may take up to ~20 minutes before the first records arrive.
Filters
You can set at most one of Resource Group Name, Resource URI, Resource Provider and Correlation ID. Azure rejects a request that combines more than one of them.
Configuration
Settings
| Setting | Type | Required | Default | Description |
|---|---|---|---|---|
tenant_id | string | Yes | - | The tenant ID of the Entra ID directory associated with your Azure subscription. |
subscription_id | string | Yes | - | The subscription ID of the Azure subscription |
resource_group_name | string | No | - | The name of the resource group |
resource_uri | string | No | - | The URI of the resource |
resource_provider | string | No | - | The provider of the resource |
correlation_id | string | No | - | The correlation ID of the log |
use_synthetic_data | bool | No | false | Generate synthetic data for testing, instead of connecting to a real data source. Defaults to an hourly cron schedule for cron-based inputs. |
rate_limit | object | No | - | Maximum outbound source-API request rate. A blank or zero value falls back to the connector's default rate-limiting behavior. Maximum 10 requests per second. See API Rate Limiting for the field format. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
client_id | secret | Yes | The client ID of the Entra ID application |
client_secret | secret | Yes | The client secret of the Entra ID application |
Setting up API Access
- Registering a new application
- Open the App Registration page in the Azure portal.
- Select New Registration
- Add a name to the new registration
- Click Register
- Save the applications
Application (client) IDandDirectory (tenant) ID - Select Certificates and Secrets
- Click link next to Client credentials
- In "Client secrets" click "New client secret"
- Add a name and expiration to the new secret
- Save the client secret value
- Assign the application a role on the subscription
- Navigate to Subscriptions and select the subscription
- Click "Access control (IAM)" on the left menu
- Select "Add Role Assignment" from the "+ Add" menu
- Select the
ReaderorMonitoring Readerrole and click Next - Click "Select members"
- Search for the new application name and click Select
- Click "Review + assign"
- Confirm by clicking "Review + assign"
Related Articles
Sample Record
Code
Sync frequency
By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. See Input Sync Frequency for details.
Community transforms
The Monad Transforms Repository has ready-made transforms for this input. Import one into your organization, then add it to a pipeline after this input.
| Format | Transform |
|---|---|
| OCSF v1.9.0 | Microsoft Azure Activity Logs to OCSF v1.9.0 |
| ECS v9.5.0 | Microsoft Azure Activity Logs to ECS v9.5.0 |
| CEF | Microsoft Azure Activity Logs to CEF |
CEF transforms emit an intermediate record; add the CEF Serializer transform after one to produce the CEF:0 string.