Skip to content

Commit 5e41402

Browse files
authored
Update network-requirements.md
Can you please see if this statement can be elaborated. Field engineers depending on their research sequence if they land up on this page it seems so that this note is making a contradictory statement to what is listed here. https://learn.microsoft.com/en-us/azure/sentinel/best-practices-data#on-premises-windows-log-collection Row - Servers do not connect to the internet Use the Log Analytics gateway Configuring a proxy to your agent requires extra firewall rules to allow the Gateway to work. Note : If outbound connectivity is restricted by your firewall or proxy server, make sure the URLs and Service Tags listed below are not blocked.
1 parent 591cda5 commit 5e41402

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-arc/servers/includes/network-requirements.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ The Azure Connected Machine agent for Linux and Windows communicates outbound se
1313
To further secure your network connectivity to Azure Arc, instead of using public networks and proxy servers, you can implement an [Azure Arc Private Link Scope](../private-link-security.md) .
1414

1515
> [!NOTE]
16-
> Azure Arc-enabled servers does not support using a [Log Analytics gateway](../../../azure-monitor/agents/gateway.md) as a proxy for the Connected Machine agent.
16+
> Azure Arc-enabled servers does not support using a [Log Analytics gateway](../../../azure-monitor/agents/gateway.md) as a proxy for the Connected Machine agent.If outbound connectivity is restricted by your firewall or proxy server, make sure the URLs and Service Tags listed below are not blocked.At the same time AMA agent supports Log Analytics gateway.
1717
1818
If outbound connectivity is restricted by your firewall or proxy server, make sure the URLs and Service Tags listed below are not blocked.
1919

0 commit comments

Comments
 (0)