Issue with Change Tracking and Inventory

GarethBeaumont-8270 0

I think I have found a bug in Azure Arc for Change Tracking and Inventory

When you view Windows Services (for example) of an Arc-enabled machine the services are all displayed as expected

However, when you try to drill into that service to view all machines where that service is you are returned with an empty result set.

After troubleshooting, I have captured the KQL sent by the browser to return the result set and have worked out what is going on.

The query does a JOIN on the ConfigurationData and Heartbeat tables ON the Computer field

The issue arises because ConfigurationData stores the machine name as onboarded into Arc. Heartbeat contains the FQDN of the computer. So if the machine is onboarded using only the hostname (as per default Azure Arc onboarding behaviour mentioned in point 4 in the below article) then you will see this issue

https://learn.microsoft.com/en-us/azure/azure-arc/servers/manage-agent?tabs=windows#renaming-an-azure-arc-enabled-server-resource

If the query used _ResourceId instead then this would not be an issue

I have a support call raised but I wanted to raise it here as well for visibility of the issue.

I don't want to have to onboard all of our devices again using the FQDN as that is just madness through bad coding. I am trying to present Arc to the business and this is a key feature we need for audit and investigations.

Feel free to reach out if you need specifics

Rahul Podila 1,730 Reputation points Microsoft Vendor

2025-02-13T07:49:46.48+00:00

Hi @GarethBeaumont-8270

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

ConfigurationData uses the machine’s hostname, while Heartbeat uses the Fully Qualified Domain Name (FQDN). When the system tries to match the two, it can’t find a match if the machine was onboarded with just the hostname instead of the full FQDN. That’s why you're seeing an empty result when trying to view all machines running a particular service.

We recommend joining the two tables using the _ResourceId, which is a unique identifier for each machine. The _ResourceId doesn’t depend on whether the machine was onboarded with a hostname or FQDN, so it will help the system match up the data correctly and return the proper results.

If you’re comfortable with KQL, you can adjust the query to join using _ResourceId instead of the Computer field. Otherwise, you can continue working with Microsoft support to ask for a fix that would use _ResourceId for the join.

If you any concerns, please go through this link: -

https://learn.microsoft.com/en-us/azure/azure-arc/servers/manage-agent?tabs=windows#renaming-an-azure-arc-enabled-server-resource

If you have any further queries, do let us know

If the answer is helpful, please click "Upvote it"
GarethBeaumont-8270 0 Reputation points

2025-02-13T09:29:50.0766667+00:00

I know all of that... you are just repeating everything I have already said.

I already have the workaround of using _ResourcesID as I already mentioned about using it instead.

The issue is that when you try to use the Azure Arc browser console through the Change Tracking and Inventory Center, the console itself uses the wrong query and returns no results.

Share via

Issue with Change Tracking and Inventory

Your answer