Azure Arc Server Onboarding fails at 80% mark

Harald Haschtschek 1 Reputation point


we try to onbard a Server to Azure Arc using private link scopes. Everything works fine during the connect till the 80% mark, after that we get the following error:
ERROR Errur during Onboarding. Answer Status Request error: Error occurred during heart beat, Details: Non-Successful http response received Error="Error response from agent"

The Server shows up under Arc Servers in Azure but is not connected. Running the Arc troubleshooting Solutions in Azure hasn't had any positve effects and searching for the error also hasn't brought back any usefull information.

Deleting the Server in Azure and then trying to connect again gives the same error; adding --verbose to the connect command gives me also no more insight on how to
troubleshoot the problem

Anyone experienced this error before ?


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

2 answers

Sort by: Most helpful
  1. Marwa Abouawad 281 Reputation points Microsoft Employee

    Hi @ HaraldHaschtschek-5111

    Welcome to Microsoft Q & A community Forum!

    Actually we haven’t experienced an error like that before. It would be best if you please filed a support case so we can collect logs from the system.

    0 comments No comments

  2. Harald Haschtschek 1 Reputation point


    We opened a support case with Micosoft and the solution to the problem is to update the azcmagent to the latest vesion 1.24. Our problem was that one of the private
    endpoints could not be reached; the customer also used a proxy server and we had to use additional agent configs like:
    azcmagent config set proxy.url "<proxyserverurl>"
    azcmagent config set proxy.bypass "Arc"

    azcmagent check -l germanywestcentral --enable-pls-check showed that all endpoints are reachable but one could not be reached which was a bug in the 1.23 Version of the agent.

    Under for the 1.24 version you can see that there is a fix for:

    Fixed a bug with proxy bypass feature that caused the agent to incorrectly use the proxy server for bypassed URLs