# Azure Monitor previews container-level advanced platform metrics > Azure Storage is the first service to expose paid advanced metrics, adding per-container blob capacity and object-count signals. Canonical URL: https://www.devobs.io/news/news-azure-monitor-advanced-platform-metrics-preview/ By: Samira Haddad Published: 2026-09-06T11:58:54.639Z Updated: 2026-09-06T11:58:54.639Z Event date: 2026-07-15 Section: Infrastructure Azure Monitor introduced advanced platform metrics in public preview on July 15. The [Observability announcement](https://techcommunity.microsoft.com/blog/azureobservabilityblog/public-preview-advanced-platform-metrics-in-azure-monitor/4536983) says Azure Storage is the first supported resource, with Container Blob Capacity and Container Blob Count available across public Azure regions. Teams enable the paid capability per storage account and can query, chart, split, and alert on it through existing metrics experiences. ## Account totals gain container context An account-level capacity curve can show growth without identifying the workload responsible. Container dimensions expose which backup, log, staging, or application container contributes to that change. That can shorten cost attribution and runaway-growth investigations without a custom inventory pipeline. The preview is deliberately narrow: two storage metrics, container granularity, and a subset of Azure resources beginning with Storage. It should not be described as universal high-cardinality telemetry for every Azure service. ## Control dimensions and cost Enable the feature on a nonproduction or representative account first. Verify that every expected container appears and understand naming patterns before constructing dashboards. Create alerts around meaningful growth rates or capacity thresholds; a raw blob count often needs workload context to be actionable. Because Microsoft describes advanced platform metrics as paid during preview, estimate sample volume and assign a budget owner. Limit access to container names if they reveal tenant or application structure. Compare values with storage inventory or billing exports over the same time window. Document which decisions use these metrics and how operators respond when data is delayed or missing. Keep account-level alerts for broad service health. The finer signal should help locate a change, while logs and application telemetry explain why it happened. ## Source references -