---
title: "Azure metric delays | Grafana Cloud documentation"
description: "Understand why Azure Monitor metrics in Grafana Cloud may appear delayed or show lower values than the Azure portal, and how to work around these delays."
---

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

# Azure metric delays

When you monitor Azure resources with Grafana Cloud, metric values can differ from what the Azure portal shows for the same time period. This discrepancy is expected behavior caused by how Azure Monitor publishes and aggregates metric data.

## How Azure metric collection works

Grafana Cloud collects Azure metrics by polling the Azure Monitor API on a regular schedule. Telemetry data is not instantly made available to Azure Monitor.

When Grafana Cloud queries Azure Monitor for a recent time window, Azure may not have received or finished aggregating all raw data points in that time window. Depending on when the query runs, not all telemetry data for the time window may have been available to Azure Monitor, which would cause values ingested into Grafana Cloud to differ from their final aggregated value as seen in Azure Monitor.

Refer to [Chart shows unexpected drop in values](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/metrics-troubleshoot#chart-shows-unexpected-drop-in-values) in Microsoft Azure documentation for more information.

## Further reading

- [Supported metrics with Azure Monitor](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/metrics-supported) in the Azure documentation
- [Azure Monitor data collection basics](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/data-collection) in the Azure documentation
- [Troubleshoot metrics collection](/docs/grafana-cloud/monitor-infrastructure/monitor-cloud-provider/azure/troubleshoot/)