---
title: "Azure logs: Grafana Alloy | Grafana Labs"
description: "Collect Azure logs using Grafana Alloy for flexibility."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## How it works

[Azure logs Alloy architecture: Azure Monitor to Event Hub with Kafka endpoint, Alloy pulls logs and pushes to Grafana Cloud Logs](cp-olly-viz-azure-logs-alloy-light.svg "Azure logs Alloy architecture: Azure Monitor to Event Hub with Kafka endpoint, Alloy pulls logs and pushes to Grafana Cloud Logs")

**Complexity:** Flexible | **Infrastructure:** VM, ACI, or AKS | **Latency:** Configurable

Azure Monitor streams log data to an Event Hubs namespace with a Kafka endpoint. Alloy pulls the logs using the Kafka protocol and forwards them to Grafana Cloud Logs. Its pipeline can parse, filter, relabel, and enrich logs first. If you already deployed Alloy for metrics, the same deployment can collect logs.

## Considerations

- Event Hub ingestion over the Kafka protocol
- Full processing pipeline for parsing, filtering, and enrichment
- Managed identity authentication
- One deployment for both metrics and logs
- Alloy infrastructure to deploy, maintain, and update
- Event Hub setup required

## When to use

- Complex processing needs
- Event Hub log sources
- Combined metrics + logs collection

## Documentation

View the [Azure Alloy logs](/docs/grafana-cloud/monitor-infrastructure/monitor-cloud-provider/azure/config-azure-logs-alloy/) documentation.