Hi @Bart,
Thank you for your patient.
Welcome to the Microsoft Q&A Platform.
We understand from your query that you are experiencing an issue is related to the resource name of the VMs. When you connect a VM to Azure Arc, the Connected Machine agent uses the VM's name as the default resource name. If that name is already taken, the agent will create a number to it to make a unique name.
Here we noticed that VMs deployed from Azure to HCI are listed as "Machine - Azure Arc (Azure Stack HCI)" while manually connected VMs are listed as "Machine - Azure Arc". This might indicate a resource type mismatch. Verify that the Azure Arc resource type is correctly set for the problematic VMs.
- Disconnect the VMs that are not connecting to Azure Arc by using the
azcmagent disconnect
command. This will remove them from Azure Arc. - Change the hostname of the VMs that aren't connecting to a unique name.
- Then, reconnect the VMs to Azure Arc using the
azcmagent connect
command. This time, the Connected Machine agent can use the new hostname as the resource name and connect the VMs to Azure Arc.
Verify guest management is enabled in the Azure portal. Check the VM properties in the Azure portal to ensure that the VM is correctly listed under Azure Arc and shows as connected. https://learn.microsoft.com/en-us/azure-stack/hci/manage/manage-arc-virtual-machines#verify-guest-management-is-enabled-in-the-azure-portal
If you have any further queries, do let us know.