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 a Application with API Data.Read access to the Log Analytics API
Reader permissions granted to the application from the Logs Analytics Workspace
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.
Configuration
Settings
Setting
Type
Required
Description
Tenant ID
string
true
The tenant ID of the Azure AD application
Subscription ID
string
false
The subscription ID of the Azure subscription
Resource Group Name
string
false
The name of the resource group
Resource URI
string
false
The URI of the resource
Resource Provider
string
false
The provider of the resource
Correlation ID
string
false
The correlation ID of the log
API Rate Limit
object
No
Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See API Rate Limiting for the field format, limits, and how to choose a value.
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.