After creating Azure Arc vmware resource bridge its status is stuck on WaitingforHeartbeat

Ian O'Connor 0 Reputation points
2025-03-12T17:44:01.8266667+00:00

The vmware resource bridge was succesfully created on both vcenter and Azure using the helper script. However its status is waitingforheartbeat once created and it does not go to the ready status. Networking appears to be okay and traffic is leaving the server. Reviewing logs I am not able to find any error in creation of the resource bridge and it appears to be functional to some degree.

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

1 answer

Sort by: Most helpful
  1. Madugula Jahnavi 495 Reputation points Microsoft External Staff Moderator
    2025-03-25T16:08:49.07+00:00

    Its status is waitingforheartbeat once created and it does not go to the ready status:

    The issue occurs when the correct connection has not been established between VMware and Azure.

    In this scenario, firstly you can check the appliance logs with the help of "az arcappliance logs" CLI command and the same is detailed in MS Doc here.

    Also, verify the bridge Status in vCenter to know the status of the connectivity. Refer MS Doc for the similar information.

    Run the az arcappliance show command from your management machine or check the version of your Arc resource bridge Azure resource and ensure the status is Running.

    Check the Azure ARC configuration once again and make sure everything has met the conditions properly.

    Hope this helps!

    If the answer was helpful, please click on Accept Answer and upvote it. If you still have queries, please click on Comment.


Your answer

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