Duplicate entry in Azure Arc - Machines

Larry Skeen 40 Reputation points
2025-11-25T20:36:51.58+00:00

I onboarded a Linux server, rf-ms-chkpntlog, to the wrong resource group, rf-monitor-syslog.

I then deleted the resource group and onboarded the server again to the correct resource group, RefuelSEIM.

I now have 2 entries for the same server. 1 with the correct resource group and 1 with the wrong resource group.

When I click the incorrect machine, it says Resource Group not found.

I have tried to delete the resource via CLI, but the resource group is gone.

It has been over 24 hours to allow sync, but the double entry is still there. How do I clean up the stale entry?

Azure Arc
Azure Arc
A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
0 comments No comments
{count} votes

Answer accepted by question author
  1. Siva shunmugam Nadessin 3,025 Reputation points Microsoft External Staff Moderator
    2025-11-26T00:21:30.1466667+00:00

    Hello Larry Skeen,

    It looks like you're experiencing an issue with duplicate entries for your Linux server in Azure Arc after onboarding it multiple times. Here’s a step-by-step approach you can try to clean up the stale entry:

    1. Verify Machines in Azure Portal: Go to the Azure Portal and navigate to the Azure Arc section. Check if you can identify both entries for the server (rf-ms-chkpntlog): one in the correct resource group and the other in the deleted resource group.
    2. Force Refresh: Sometimes, the sync might take a bit longer. To refresh the state, you can try running the following command in Azure CLI to see if this helps:
    3. az connectedmachine show --resource-group RefuelSEIM --name rf-ms-chkpntlog
    4. Use Azure CLI to Delete the Stale Entry: Since you mentioned you've tried using the CLI without success, ensure you're using the correct command format. You can run:
    5. az connectedmachine delete --resource-group rf-monitor-syslog --name rf-ms-chkpntlog

    Note: Ensure the resource group name in the command matches exactly where the stale entry is shown.

    1. Check for Dependencies: If the stale entry fails to delete, check if there are any dependencies or locks applied on that resource that might prevent deletion.
    2. Contact Microsoft Support: If none of these steps work, it might be best to reach out to Azure Support directly for further assistance. They can help resolve issues related to orphaned entries in the Azure Arc service.

    Hope this helps you clean up the duplicate entry! If you need any more assistance or if these steps don’t resolve the issue, feel free to ask.

    Relevant Documentation Links:

    Let me know if you need more information!

     


Answer accepted by question author
  1. Q&A Assist
    2025-11-25T20:37:00.36+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To clean up the stale entry for the Linux server in Azure Arc, you will need to manually delete the resource representation from Azure. Since the resource group for the incorrect entry has already been deleted, you can follow these steps:

    1. Delete the Stale Resource Representation: Navigate to the Azure portal and search for the specific Azure Arc resource that represents the stale entry. You may need to look under the Azure Arc section or search for the machine name directly.
    2. Use Azure CLI: If you prefer using the CLI, you can attempt to delete the resource directly by using the Azure CLI commands. You can use the following command to delete the specific resource:
         az connectedmachine delete --resource-group <YourResourceGroup> --name <YourMachineName>
      
      Replace <YourResourceGroup> with the name of the resource group where the correct entry is located and <YourMachineName> with the name of the machine you want to delete.
    3. Wait for Sync: After deleting the stale entry, it may take some time for the changes to reflect across the Azure portal. Ensure that you allow sufficient time for the synchronization to complete.

    If the stale entry still persists after these steps, consider reaching out to Azure support for further assistance.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.