Azure Arc endpoint not reachable

Question

We setup Arc a while back and have onboarded a bunch of VMs onsite through a private scope link.

All was working fine until a few days ago a lot of them became disconnected.

Upon checking the agent we now get this:

azcmagent check

INFO Testing connectivity to endpoints that are needed to connect to Azure... This might take a few minutes.

Use Case |Endpoint |Reachable |Private |TLS |Proxy

core |https://agentserviceapi.guestconfiguration.azure.com |true |unknown |TLS 1.3 |set

core |https://gbl.his.arc.azure.com |true |unknown |TLS 1.3 |set

core |https://login.microsoftonline.com |true |unknown |TLS 1.3 |set

core |https://management.azure.com |true |unknown |TLS 1.3 |set

core |https://pas.windows.net |true |unknown |TLS 1.3 |set

core |https://uks.his.arc.azure.com |false |unknown |unknown |set

core |https://uksouth-gas.guestconfiguration.azure.com |true |unknown |TLS 1.3 |set

host uks.his.arc.azure.com

uks.his.arc.azure.com has address 10.100.5.5

If we run the onboard script again:
FATAL required endpoints unavailable: https://uks.his.arc.azure.com (error: Get "https://uks.his.arc.azure.com/connectivitytest": context deadline exceeded (Client.Timeout exceeded while awaiting headers))

azcmagent Logs:

time="2025-01-09T12:27:16Z" level=debug msg="Endpoint properties" error="Get "https://uks.his.arc.azure.com/connectivitytest": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" hostname=uks.his.arc.azure.com ipAddresses= private=unknown proxyStatus=set requiredForPrivateLinkScope=true tls=unknown useCase=core

DNS records all seem fine our end, and the vpn to azure appears to be working as the others connect fine.

Is there a service status page for azure connectors anywhere or something??

I've double checked the settings, and nothing has changed on our end, so I'm not really sure what to do next - can I troubleshoot the endpoint in Azure somehow??

Pete.

Answer 1

Hi @Peter Brigham
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Issue: Azure Arc endpoint not reachable

Solution:
It looks like the connector was just down or in maintenance for some reason - A Day or so later and the agent checks reported it working again.

If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

Answer 2

Hi Peter Brigham

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Check that the virtual machines are running and healthy. You can do this by trying to connect to them using Remote Desktop or SSH.

Use the command azcmagent show to check the status of the Azure Connected Machine Agent and confirm that it is properly installed and functioning.

The azcmagent check command shows that some endpoints, like uks.his.arc.azure.com, are not reachable. This could be due to network problems or firewall settings. Check to see if any changes have been made to the network that might be blocking access to this endpoint.

Since your DNS records appear to be fine, make sure that the DNS settings on your VM are properly configured to resolve Azure endpoints.

If the agent was connected before but is now disconnected, try running this command:

azcmagent connect --location "your_location" --resource-group "your_resource_group" --subscription-id "your_subscription_id"

There isn't a specific status page for Azure connectors, but you can check the Azure status page for any current issues with services in your region.

Check the logs from azcmagent for any error messages that might give you more information about the issue.

Make sure that any VPNs or firewalls allow traffic to Azure endpoints, especially the ones shown in your connectivity test results.

For reference, please review this documentation :-
https://techcommunity.microsoft.com/blog/itopstalkblog/troubleshooting-azure-arc-for-servers---status-offline/1342751
https://learn.microsoft.com/en-us/azure/azure-arc/servers/troubleshoot-agent-onboard
https://learn.microsoft.com/en-us/azure/azure-arc/resource-bridge/troubleshoot-resource-bridge

If you have any further queries, do let us know.

---

If the answer is helpful, please and "Upvote it".