Azure Resource Graph: Intermittent incomplete VM inventory results — Investigation and clarification needed

Problem description

I am experiencing occasional cases where the Azure Resource Graph query returns an incomplete list of virtual machines, omitting some that still exist. This occurs rarely but consistently enough to impact my inventory workflows.

Environment

Azure Resource Graph service, resource type: Microsoft.Compute/virtualMachines, region: Central US.

What I've already tried

I compared the results from affected scans with known-good baselines, validated that the missing VMs still exist in ARM and the Azure portal, and reviewed activity logs. I also checked the query parameters and pagination behavior, but the issue persists intermittently.

Current status

I am seeking clarification on whether this behavior indicates a transient backend issue with Azure Resource Graph, and I would like guidance on any additional diagnostic steps or data I should collect to assist in further investigation.