Azure Arc: Connectivity Issue on Azure Local VM — Resource Already Exists Error

Problem description

I am experiencing connectivity issues with an Azure Local VM that is Azure Arc-enabled. The VM appears as 'Enabled (disconnected)' in Azure, despite all in-guest services like himds, gcarcservice, and extensionservice running, and connectivity checks passing. When attempting to reconnect the Arc agent using 'azcmagent connect', I receive an error code AZCM0044 indicating that a resource with the same name already exists. I understand that this VM is an Azure Local-backed machine, not a standalone Arc server. I am concerned that the existing Azure resource conflict prevents reconnection without risking deletion of the VM itself. I need guidance on how to safely resolve this resource conflict and restore connectivity.

Environment

Azure Arc enabled servers; Resource type: Machine - Azure Arc (Azure Local); Hosting model: VM on Azure Local; Region: West Europe; In-guest services: himds, gcarcservice, extensionservice; Connectivity validation: successful

What I've already tried

I have checked that in-guest services are running and ran 'azcmagent check', which reports success. I attempted to run 'azcmagent connect' to re-establish the Arc connection, but it failed with AZCM0044 because a resource with the same name already exists. I also reviewed guidance on disconnecting and reconnecting Arc agents, but I did not delete or modify existing Azure resources due to concerns about deleting the VM.

Current status

The VM still appears as 'Enabled (disconnected)' in Azure, and reconnection attempts are failing with resource conflicts. I seek advice on how to resolve the resource name conflict without risking deletion of the VM, and how to properly rebind the Arc agent to the existing Azure Local-managed machine object.