Metrics: Missing platform metrics for multiple VMs in UK South region — ongoing issue

Question

Metrics: Missing platform metrics for multiple VMs in UK South region — ongoing issue

Tosin Adeyemo 0

Problem description

I am experiencing an issue where platform metrics such as Percentage CPU, VmAvailabilityMetric, and Available Memory Percentage for multiple virtual machines in the UK South region have stopped being reported since 01:11 UTC on 29/09/2026. The affected metrics show no data, and this problem has persisted since then.

Environment

Azure Monitor metrics for Azure virtual machines (Microsoft.Compute/virtualMachines) in UK South.

What I've already tried

I reviewed guidance for missing metrics, including allowing time for data propagation, widening the time range, and confirming that the metrics are supported for the resources. I also used Get-AzMetric at 5-minute granularity to inspect the affected VMs, checked metric history across multiple VMs, and compared with VMs in other subscriptions. The metrics were present up to 01:11 UTC, then mostly null, with occasional isolated data points later. The affected VMs remain healthy and in a running state, and the metric values that do appear indicate VM availability, suggesting a metrics delivery issue rather than VM problems.

Current status

I am seeking assistance to understand the root cause of this metrics ingestion issue, confirm if it's regional Azure Monitor service disruption, and guidance on next steps for resolution.

Venkatanaidu Madamanchi 85 Reputation points Microsoft External Staff Moderator

2026-09-29T17:23:11.13+00:00
Hello @Tosin Adeyemo

Thanks for reaching out to Microsoft Support Team and Thank you for providing the detailed information and the troubleshooting steps you have already performed.

Based on the information shared, the behavior observed across multiple virtual machines suggests that the issue is unlikely to be related to the individual VM health or configuration. Since the affected VMs remain in a running state, the VmAvailabilityMetric occasionally reports successful values, and the metrics were consistently available until approximately 01:11 UTC on 29/09/2026 before becoming predominantly null, this points more towards a potential Azure Monitor metrics collection, ingestion, or delivery issue rather than a problem with the virtual machines themselves.

To further validate the scope of the issue, we recommend the following:

Verify whether the missing metrics behavior is affecting all subscriptions and resource groups within the UK South region or only a subset of resources.

Review the Azure Service Health dashboard for any active advisories or incidents related to Azure Monitor, Azure Metrics, or the UK South region.

Compare metric availability for similar virtual machines deployed in other Azure regions to determine whether the behavior is isolated to UK South.

Continue monitoring the affected metrics for any backfill activity, as temporary telemetry ingestion issues can sometimes result in delayed metric publication.

If available, validate VM health using alternative monitoring sources such as Azure Monitor Logs, VM Insights, Guest OS performance counters, or Log Analytics data to confirm that the VMs themselves remain healthy.

Given that:

Multiple VMs are affected simultaneously.

The issue started at approximately the same timestamp (01:11 UTC).

VM availability remains unaffected.

Occasional metric data points are still being received.

Similar behavior is observed across multiple resources.

There is a possibility of a backend Azure Monitor metrics ingestion or regional service issue impacting the publication of platform metrics in the UK South region.

We apologize for the inconvenience caused. We understand the impact this may have on your monitoring and alerting workflows and will continue to investigate the issue from the Azure platform side to determine whether a service degradation or telemetry ingestion issue exists within the region.

Please let us know if you observe any recovery of metric data or if additional VMs become affected, as this information will help us refine the investigation.

Regards.

Venkat.M
Venkatanaidu Madamanchi 85 Reputation points Microsoft External Staff Moderator

2026-10-01T01:11:53.6466667+00:00

Hello @Tosin Adeyemo

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

1 answer

Your answer

Venkatanaidu Madamanchi 85 Reputation points Microsoft External Staff Moderator

2026-10-01T01:11:53.6466667+00:00

Hello @Tosin Adeyemo

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Answer 1

This appears to be an Azure Monitor regional metrics ingestion issue rather than a VM health problem, as multiple VMs in UK South stopped reporting metrics at approximately the same time.

Recommended actions:

Check Azure Service Health for any UK South/Azure Monitor incidents.
Open a Microsoft Azure support ticket under Monitoring → Metrics with the affected VM resource IDs and the exact timestamp (29/09/2026 01:11 UTC).
Continue monitoring the VMs through VM/OS-level monitoring until platform metrics resume.

Since the VMs remain healthy and the issue affects multiple resources simultaneously, Microsoft Support will need to confirm the backend ingestion status and regional impact.