Send Azure logs via Event Hub logs to LogPulse
Azure Activity Log, Entra ID sign-ins and audit, Defender for Cloud alerts, Azure Firewall, WAF, AKS audit and other resource logs from one Event Hub.
Configure → Sources → Cloud. LogPulse reads the Azure Event Hub (Kafka endpoint) itself, without an agent. Events land in the audit, iam, firewall, web, endpoint, kubernetes indexes with source azure and fill the Cloud Audit, Authentication, Alert, Network Activity, Web Access data models.Overview
- Azure Event Hub (Kafka endpoint) to Integration poller
- Integration poller to index=audit
- Integration poller to index=iam
- Integration poller to index=firewall
- Integration poller to index=web
- Integration poller to index=endpoint
- Integration poller to index=kubernetes
LogPulse signs in to Azure logs via Event Hub with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.
What you need
- An Event Hubs namespace on the Standard tier or higher (Kafka endpoint)
- A diagnostic setting per subscription or resource that streams to the hub
- A shared access policy with Listen rights
- In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.
1. Create a credential in Azure logs via Event Hub
| Field in LogPulse | Where you find it |
|---|---|
| Connection string | From a shared access policy with Listen rights, on the namespace or on the hub. Stored encrypted and never shown again. |
| Event hub (optional) | The name of the hub. Not needed when the connection string is from the hub itself (it then ends with EntityPath=…). |
| Consumer group (optional) | A consumer group for LogPulse alone, so it does not take events from another reader. Empty uses "logpulse". |
2. Add the integration in LogPulse
Go to Configure → Sources → Cloud and choose Azure logs via Event Hub. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.
What arrives
| Data source | Index | Source | Sourcetype | What it holds |
|---|---|---|---|---|
| Activity Log | audit | azure | azure:activity | Who created, changed or deleted what in your subscriptions, with role assignments and policy. |
| Entra ID sign-ins | iam | azure | azure:signin | Interactive, non-interactive, service principal and managed identity sign-ins. |
| Entra ID audit | iam | azure | azure:audit | Changes to users, groups, roles, apps and provisioning. |
| Defender for Cloud alerts | audit | azure | azure:defender:alert | Alerts from continuous export for VMs, storage, Key Vault and containers. |
| Azure Firewall | firewall | azure | azure:firewall | Network and application rule hits, NAT, threat intelligence and IDPS. |
| Web application firewall | web | azure | azure:waf | Application Gateway and Front Door WAF. |
| Defender XDR streaming (off by default) | endpoint | azure | ms_defender | Advanced hunting tables streamed to the hub. |
| Application Gateway and Front Door access (off by default) | web | azure | azure:web:access | Every request through your gateways. High volume. |
| AKS audit (off by default) | kubernetes | azure | azure:aks:audit | Kubernetes API audit of your AKS clusters. |
| Other resource logs (off by default) | audit | azure | azure:resource | Key Vault, Storage, SQL, App Service and every other category. |
The index is the kind of data and the source is the product, so detection rules for that kind of data find Azure logs via Event Hub without changes.
Fields and data models
| Data model | What you get |
|---|---|
| Cloud Audit | Activity Log, Entra ID audit, AKS audit and resource logs with user, action, object and src_ip. |
| Authentication | Entra ID sign-ins with the same fields as the Entra ID connector. |
| Alert | Defender for Cloud alerts in the shared alert shape. |
| Network Activity | Azure Firewall with the 5-tuple and allowed or blocked. |
| Web Access | WAF and gateway requests with src_ip, http_method, url, status and http_user_agent. |
Events are mapped to the data models above, with the same field names as other sources of the same kind. See field names.
The original record of Azure logs via Event Hub is kept with each event under raw, so nothing the vendor sent is lost.
3. Check the data
The first events arrive within a few minutes. Check what came in:
earliest=-1h index IN (audit, iam, firewall, web, endpoint, kubernetes) source IN (azure)
| stats count by index, source, sourcetypeThe integration page in LogPulse shows when it last read events and the last error, if any.
Troubleshooting
The connection test names what is wrong. These are the answers you are most likely to see.
| What you see | What to do |
|---|---|
| Azure refused the connection string. | Use the connection string of a shared access policy with Listen rights, on the namespace or on the hub. |
| Name the event hub, or use a connection string of the hub itself (with EntityPath) | Fill in the hub name, or copy the connection string from the hub instead of the namespace. |
| The namespace answered, but has no hub with that name. | Check the hub name. A diagnostic setting without a hub name writes to hubs called insights-logs-<category>. |
| The test passes but no events arrive. | Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Azure logs via Event Hub may also simply have had nothing new. |
Frequently asked questions
- How do I send Azure logs via Event Hub logs to LogPulse?
- Add the Azure logs via Event Hub cloud integration under Configure, Sources, Cloud in LogPulse and fill in Connection string. LogPulse reads the Azure Event Hub (Kafka endpoint) itself, every five minutes by default; there is nothing to install.
- Which permissions does LogPulse need in Azure logs via Event Hub?
- An Event Hubs namespace on the Standard tier or higher (Kafka endpoint). A diagnostic setting per subscription or resource that streams to the hub. A shared access policy with Listen rights. Read access is enough for collecting logs.
- Which index does Azure logs via Event Hub data go to?
- The index is the kind of data: audit, iam, firewall, web, endpoint, kubernetes. The source is the product: azure. Each data source has its own sourcetype, listed on this page.
- Which data models does Azure logs via Event Hub fill?
- Cloud Audit, Authentication, Alert, Network Activity, Web Access. Detection rules and dashboards written for a data model work on Azure logs via Event Hub without changes.
- Why is a data source off by default?
- To keep your daily ingest down until you need it: Defender XDR streaming, Application Gateway and Front Door access, AKS audit, Other resource logs are high volume or of use to fewer teams. Tick the data source in the integration to switch it on.
- Does LogPulse read the whole retention of the Event Hub at the start?
- No. A new consumer group starts at the newest events. Give LogPulse a consumer group of its own, so it does not take events from another reader.