On the **Ready to Install** page, review your choices, and then click **Install**.ġ.
On the **Microsoft Update** page, optionally select **Use Microsoft Update when I check for updates (recommended)**, then click **Next**.ġ. If you use a proxy server instead of an Log Analytics Gateway, add the information for your proxy server and if required, authentication credentials (not required for the Log Analytics Gateway), then click **Next** twice.ġ. Specify the fully qualified domain name (FQDN) or the IP address and port of the Log Analytics Gateway. If you do not use any of the above, click **Next** and go to **step 12**.ġ. If you are currently installing the agent on the data collection machine and using an Log Analytics Gateway deployment scenario, or if your company requires access through a proxy server, click the **Advanced** button to provide **HTTP proxy** configuration. Select **Azure Commercial** or if you are using an Azure US Government cloud select **Azure US Government** from the **Azure Cloud** drop down menu and click **OK**.ġ. (Hint: Click the copy button then paste in the corresponding **Agent Setup** field). On the **Overview, Settings Dashboard** page, click **Connected Sources**, and then copy and paste the **Workspace ID** and **Workspace Key (Primary Key)** from the log analytics portal.
On the Agent Setup Options page, choose the Connect the agent to Azure Log Analytics (OMS) option.On the Destination Folder page, change or keep the default installation folder and then click Next.On the License Terms page, read the license and then click I Agree.
Refer to the Microsoft Monitoring Agent Upgrade section in this document when you are performing an upgrade of the Monitoring Agent for SCOM. The next steps apply to installations where no monitoring client was installed for SCOM. The upgrade for SCOM agent does not include any of the configuration steps below.* If a monitoring client was installed for System Center Operations Manager (SCOM), the setup only offers to Upgrade the agent, preserving existing settings.
If Log Analytics Gateway scenario is being deployed, then install and configure the MMA on the gateway first. On the designated data collection machine and Log Analytics Gateway (if using) complete the following steps. Agent Resourceĭownload and install the Microsoft Monitoring Agent (MMA) setup file from Azure Log Analytics For complete and up to date information on the networking requirements for the MMA as well as networking requirements for Azure Government or other sovereign Azure Log Analytics services, see the article HERE. The information below list the proxy and firewall configuration information required for the Linux and Windows agent to communicate with Log Analytics within the Azure commercial cloud.
It must also be installed on the Log Analytics Gateway if deploying that scenario.įor detailed information about the Microsoft Monitoring Agent including system requirements, network firewall configuration requirements, TLS 1.2 requirements, download, and installation instructions, see the Agent Windows article. The Microsoft Monitoring Agent must be installed and configured on the data collection machine.