Naveenommi-MSFT
commented
12 months ago @InformTechPro Thanks for your feedback! We will investigate and update as appropriate.
Closed InformTechPro closed 3 months ago
Naveenommi-MSFT
commented
12 months ago @InformTechPro Thanks for your feedback! We will investigate and update as appropriate.
AbbyMSFT
commented
3 months ago Hi @InformTechPro, Thanks for reaching out to us and for your interest in improving our documentation. We see that this issue has been in our backlog for quite a while. We have opened an internal work item to make sure this issue is addressed: https://dev.azure.com/msft-skilling/Content/_workitems/edit/257122.
We are closing this issue but rest assured that this is in our backlog to make sure we get to it!
We need to mention that the Gateway does NOT support Azure Arc due to its requirement for bypass to wild card URLs. The document mentions that "The log analytics gateway supports: ... Windows computers on which either the Azure Monitor Agent .... " The ALA gateway often used in on-premise environment where machines might not have access to the Azure solutions like Network Access Control, etc. But in on-premise environment the Azure Monitor Agent requires Azure Arc agent. Since the Gateway does not support wild card URLs, the Log Analytics Gateway use case is only applicable to those on premise-machines that managed without Azure Arc. Specifically, it could be used with Windows Workstation machines that are connected to Azure AD and do NOT require Arc agent. It would be helpful to mention an alternative proxy when customer needs to connect Azure Arc agent.
Azure Monitor Agent or the legacy Microsoft Monitoring Agent is directly connected to a Log Analytics workspace in Azure Monitor
Connected Machine agent network requirements - Azure Arc | Microsoft Learn Managing the Azure Connected Machine agent - Azure Arc | Microsoft Learn
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.