AMA extension error: failed to get authentication token for workspace ID xxx

sadik karadag 1 Reputation point

Hello everyone,

I'm currently trying to troubleshoot an issue where the monAgentHost.log file shows that there is an issue with retrieving the authentication token for a log analytics workspace? Everything else seem to be working. We also do not see any errors in the connectivity logs.

Bit of background:

This is happening on a machine that is onboarded to Azure Arc through Azure Arc Private Link scope. The private link scope is working as intended and connected machine agent is showing there are no errors. We are also seeing healthy status on Azure Arc server pages.

Then I have installed the Azure Monitor Agent extension using a PowerShell script. The reason we used PowerShell script and not the Azure portal is because we could only this method where you can assign the proxy manually. As seen here :

We have Azure monitor private link scope + data collection endpoint setup to forward the logs through private channels.

This seem to have worked fine as we can see all the connections from AMA are going through the proxy. Proxy server does not show any connectivity failures (all 200 response) and we can see that connections are hitting the private link scope.

However, we are seeing the error in the post title and not sure what causes it. Anyone had a similar issue?

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
2,858 questions
Azure Arc
Azure Arc
A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
337 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Ryan Hill 26,241 Reputation points Microsoft Employee

    @sadik karadag , sorry for the late reply. I couldn't find any reference material mentioning authentication token failures in MonAgentHost.log. Most of everything I discovered was communication errors, which you don't have any. We'll need to work more closely with you to investigate what's going on. Please respond to the private comment above for the next steps.

    0 comments No comments