Azure Stack HCI Guest management showing disconnected

Hello

Based on the error message: AZCM0044: Resource Already Exists FATAL resource name 'VMName' already exists

This typically indicates that a machine with the same name is already registered in Azure as an Azure Arc–enabled server. When the azcmagent connect command is executed again, it attempts to create a new resource with the same name, which results in this conflict.

Since you already attempted azcmagent disconnect --force-local-only, it is possible that the local agent state was cleared while the existing Azure Arc resource still remains registered in Azure.

1.Please check if the Arc resource exists in the resource group created for Azure Stack HCI infrastructure.

As you mentioned you didn't see delete option from the portal you can also verify it using Azure CLI:

az connectedmachine list --resource-group "HCINODE-<GUID>-Arc-Infra-RG" -o table

If the resource exists, you can delete it using:

az connectedmachine delete --name "VMName" --resource-group "HCINODE-<GUID>-Arc-Infra-RG"

After the resource is deleted, please retry connecting the agent from the VM:

C:\Program Files\AzureConnectedMachineAgent\azcmagent.exe connect --resource-group <ResourceGroup> --tenant-id <TenantID> --location <Region>

Register the machine with a different resource name

Alternatively, you can reconnect the agent using a different resource name:

azcmagent.exe connect `
--resource-group <ResourceGroup> `
--resource-name VMName-v2 `
--location <Region>

This will create a new Azure Arc resource with a different name and avoid the conflict.

To help us further understand the issue, could you please provide the following details:

1. Can you confirm if a resource with the same VM name exists under Azure Arc → Machines in the Azure portal?
2. What is the output of the following command on the affected VM? azcmagent show
3. How many VMs in the cluster are showing Guest Management as disconnected?
   Is the issue affecting all VMs or only a few specific machines?
4. Which version of the Azure Connected Machine Agent is installed on the affected VM?
5. Did the issue start after any recent changes such as Azure Stack HCI updates, cluster upgrades, VM recreation, or node maintenance?

Once we receive the above details, we will review them and assist you further with the next steps.

Hi Jilakara,

Deleting the Resource will definitly delete the VM from Azure Local cluster as when i clicking the VM it pontin the page to clsuterVM i tried by shuting down the vm . so deleting will complex the issue.

1. Can you confirm if a resource with the same VM name exists under Azure Arc → Machines in the Azure portal? Yes its shwoing in Azure Arc
2. What is the output of the following command on the affected VM? azcmagent show
3. How many VMs in the cluster are showing Guest Management as disconnected? Is the issue affecting all VMs or only a few specific machines? Almost all Vm are showing this behaviour. whiever is showing connected if i disconnect that it will give same issue.
4. Which version of the Azure Connected Machine Agent is installed on the affected VM? 1.55.03132.2414 & 1.61.03319.2737 but it doesn mater as issue is on both versions.
5. Did the issue start after any recent changes such as Azure Stack HCI updates, cluster upgrades, VM recreation, or node maintenance? Nope i am trying this first time and seeing this issue.

Hello

Could you please check private message and provide the necessary details