---
title: "Azure metrics: Grafana Alloy | Grafana Labs"
description: "Collect Azure metrics 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 metrics Alloy architecture: Alloy pulls from Azure Monitor across subscriptions, pushes to Grafana Cloud Metrics](cp-olly-viz-azure-metrics-alloy-light.svg "Azure metrics Alloy architecture: Alloy pulls from Azure Monitor across subscriptions, pushes to Grafana Cloud Metrics")

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

Deploy Alloy once, for example as a container in Azure Container Instances or a pod in AKS. It collects metrics from across all your subscriptions. Alloy can authenticate with an Azure managed identity, so there are no service principal credentials to rotate. Its processing pipeline lets you filter, relabel, and aggregate metrics before they’re stored.

## Considerations

- Multiple subscriptions from one Alloy deployment
- Managed identity support, so no keys to rotate
- Full processing pipeline for filtering, relabeling, and aggregation
- Correlation with other telemetry sources
- Alloy infrastructure to deploy, maintain, and update
- Learning curve

## When to use

- Multi-subscription environments
- Want managed identity
- Combining Azure with other clouds

## Documentation

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