Log Analytics agent overview

This article provides a detailed overview of the Log Analytics agent and the agent's system and network requirements and deployment methods.


The Log Analytics agent is on a deprecation path and won't be supported after August 31, 2024. Any new data centers brought online after January 1 2024 will not support the Log Analytics agent. If you use the Log Analytics agent to ingest data to Azure Monitor, migrate to the new Azure Monitor agent prior to that date.

You might also see the Log Analytics agent referred to as Microsoft Monitoring Agent (MMA).

Primary scenarios

Use the Log Analytics agent if you need to:

Limitations of the Log Analytics agent:

  • Can't send data to Azure Monitor Metrics, Azure Storage, or Azure Event Hubs.
  • Difficult to configure unique monitoring definitions for individual agents.
  • Difficult to manage at scale because each virtual machine has a unique configuration.

Comparison to other agents

For a comparison between the Log Analytics and other agents in Azure Monitor, see Overview of Azure Monitor agents.

Supported operating systems

For a list of the Windows and Linux operating system versions that are supported by the Log Analytics agent, see Supported operating systems.

Installation options

This section explains how to install the Log Analytics agent on different types of virtual machines and connect the machines to Azure Monitor.


The legacy Log Analytics agent will be deprecated by August 2024. After this date, Microsoft will no longer provide any support for the Log Analytics agent. Migrate to Azure Monitor agent before August 2024 to continue ingesting data.


Cloning a machine with the Log Analytics Agent already configured is not supported. If the agent is already associated with a workspace, cloning won't work for "golden images."

Azure virtual machine

Windows virtual machine on-premises or in another cloud

Linux virtual machine on-premises or in another cloud

  • Use Azure Arc-enabled servers to deploy and manage the Log Analytics VM extension. Review the deployment options to understand the different deployment methods available for the extension on machines registered with Azure Arc-enabled servers.
  • Manually install the agent calling a wrapper-script hosted on GitHub.
  • Integrate System Center Operations Manager with Azure Monitor to forward collected data from Windows computers reporting to a management group.

Data collected

The following table lists the types of data you can configure a Log Analytics workspace to collect from all connected agents.

Data Source Description
Windows Event logs Information sent to the Windows event logging system
Syslog Information sent to the Linux event logging system
Performance Numerical values measuring performance of different aspects of operating system and workloads
IIS logs Usage information for IIS websites running on the guest operating system
Custom logs Events from text files on both Windows and Linux computers

Other services

The agent for Linux and Windows isn't only for connecting to Azure Monitor. Other services such as Microsoft Defender for Cloud and Microsoft Sentinel rely on the agent and its connected Log Analytics workspace. The agent also supports Azure Automation to host the Hybrid Runbook Worker role and other services such as Change Tracking, Update Management, and Microsoft Defender for Cloud. For more information about the Hybrid Runbook Worker role, see Azure Automation Hybrid Runbook Worker.

Workspace and management group limitations

For details on connecting an agent to an Operations Manager management group, see Configure agent to report to an Operations Manager management group.

  • Windows agents can connect to up to four workspaces, even if they're connected to a System Center Operations Manager management group.
  • The Linux agent doesn't support multi-homing and can only connect to a single workspace or management group.

Security limitations

The Windows and Linux agents support the FIPS 140 standard, but other types of hardening might not be supported.

TLS protocol

To ensure the security of data in transit to Azure Monitor logs, we strongly encourage you to configure the agent to use at least Transport Layer Security (TLS) 1.2. Older versions of TLS/Secure Sockets Layer (SSL) have been found to be vulnerable. Although they still currently work to allow backward compatibility, they are not recommended. For more information, see Sending data securely using TLS.

Network requirements

The agent for Linux and Windows communicates outbound to the Azure Monitor service over TCP port 443. If the machine connects through a firewall or proxy server to communicate over the internet, review the following requirements to understand the network configuration required. If your IT security policies do not allow computers on the network to connect to the internet, set up a Log Analytics gateway and configure the agent to connect through the gateway to Azure Monitor. The agent can then receive configuration information and send data collected.

Diagram that shows Log Analytics agent communication.

The following table lists the proxy and firewall configuration information required for the Linux and Windows agents to communicate with Azure Monitor logs.

Firewall requirements

Agent Resource Ports Direction Bypass HTTPS inspection
*.ods.opinsights.azure.com Port 443 Outbound Yes
*.oms.opinsights.azure.com Port 443 Outbound Yes
*.blob.core.windows.net Port 443 Outbound Yes
*.azure-automation.net Port 443 Outbound Yes

For firewall information required for Azure Government, see Azure Government management.


If your firewall is doing CNAME inspections, you need to configure it to allow all domains in the CNAME.

If you plan to use the Azure Automation Hybrid Runbook Worker to connect to and register with the Automation service to use runbooks or management features in your environment, it must have access to the port number and the URLs described in Configure your network for the Hybrid Runbook Worker.

Proxy configuration

The Windows and Linux agent supports communicating either through a proxy server or Log Analytics gateway to Azure Monitor by using the HTTPS protocol. Both anonymous and basic authentication (username/password) are supported.

For the Windows agent connected directly to the service, the proxy configuration is specified during installation or after deployment from Control Panel or with PowerShell. Log Analytics Agent (MMA) doesn't use the system proxy settings. As a result, the user has to pass the proxy setting while installing MMA. These settings will be stored under MMA configuration (registry) on the virtual machine.

For the Linux agent, the proxy server is specified during installation or after installation by modifying the proxy.conf configuration file. The Linux agent proxy configuration value has the following syntax:


Property Description
Protocol https
user Optional username for proxy authentication
password Optional password for proxy authentication
proxyhost Address or FQDN of the proxy server/Log Analytics gateway
port Optional port number for the proxy server/Log Analytics gateway

For example: https://user01:password@proxy01.contoso.com:30443


If you use special characters such as "@" in your password, you'll receive a proxy connection error because the value is parsed incorrectly. To work around this issue, encode the password in the URL by using a tool like URLDecode.

Next steps

  • Review data sources to understand the data sources available to collect data from your Windows or Linux system.
  • Learn about log queries to analyze the data collected from data sources and solutions.
  • Learn about monitoring solutions that add functionality to Azure Monitor and also collect data into the Log Analytics workspace.