In the admin center there is a build " e.g. October 2025" of the agent, but that build is already auto-updated under the hood. This is confusing because others get a newer build, e.g. December 2025 based on the deployment.
In the end, they are both on the same updated/latest version because of auto-update, but the portal still shows a different build description. Actually it's showing the deployment build version/description.
Hello, and thank your for your idea.
The agent version number shown in the Analytics UI, when looking at individual agent, reflects the running version of the Agent that it reports itself to be. This is different from the installed version of the Agent, which is a deployment-time version that got installed - executing version is updated via auto-update mechanism in the Agent. The deployment version stays the same (unless and if newer MSI/PKG is run over the existing one on device), and we intentionally do not include that in the software listing as that would be confusing if only looking at that and trying to determine what version of the Agent is actually running.
The purpose of the information in the portal is to show if the Agent is up-to-date wrt. to what is actually running on the device, regardless of what got installed originally. This allows seeing if there are some devices that have issues auto-updating itself.