Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Microsoft Monitoring Agent must be installed and configured on the data collection machine. It must also be installed on the Log Analytics Gateway if deploying that scenario.
For 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 following information lists the proxy and firewall configuration information required for the Linux and Windows agent to communicate with Log Analytics within the Azure commercial cloud. 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 Log Analytics agent overview - 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 |
Download and install the Microsoft Monitoring Agent (MMA) setup file from Azure Log Analytics
On the designated data collection machine and Log Analytics Gateway (if using) complete the following steps. If Log Analytics Gateway scenario is being deployed, then install and configure the MMA on the gateway first.
Note
If the collection machine does not have an internet connection, perform the first 3 steps from an internet connected machine.
In the Azure portal, go to Log Analytics, select your workspace and select the Advanced Settings Icon.
Select Connected Sources, and then select Windows Servers.
Select the Download Windows Agent link that is applicable to your computer processor type to download the setup file. If the agent is downloaded on another machine, copy the Setup file over to the data collection machine or Log Analytics Gateway server.
Note
If a monitoring client was installed for System Center Operations Manager (SCOM), the setup only offers to Upgrade the agent, preserving existing settings. The upgrade for SCOM agent does not include any of the configuration steps following.
The next steps apply to installations where no monitoring client was installed for SCOM. Refer to the Microsoft Monitoring Agent Upgrade section in this document when you are performing an upgrade of the Monitoring Agent for SCOM.
Run Setup to install the agent.
On the Welcome page, select Next.
On the License Terms page, read the license and then select I Agree.
On the Destination Folder page, change or keep the default installation folder and then select Next.
On the Agent Setup Options page, choose Connect the agent to Azure Log Analytics (OMS). Select Next.
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. (Hint: Select the copy button then paste in the corresponding Agent Setup box). 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 select OK.
If you are currently installing the agent on the data collection machine and using a Log Analytics Gateway deployment scenario, or if your company requires access through a proxy server, Select Advanced to provide HTTP proxy configuration. If you do not use any of these, select Next and go to step 12.
Specify the fully qualified domain name (FQDN) or the IP address and port of the Log Analytics Gateway. If you use a proxy server instead of a Log Analytics Gateway, add the information for your proxy server and, if required, authentication credentials (not required for the Log Analytics Gateway), then select Next twice.
On the Microsoft Update page, optionally select Use Microsoft Update when I check for updates (recommended), then select Next.
On the Ready to Install page, review your choices, and then select Install.
On the Microsoft Monitoring Agent configuration completes successfully page, select Finish.
When complete, the Microsoft Monitoring Agent appears in Control Panel. You can review your configuration there and verify that the agent is connected to Azure Log Analytics. When connected to Log Analytics, the agent displays a message stating: The Microsoft Monitoring Agent has successfully connected to the log analytics service.
Note
If you have been installing the Microsoft Monitoring Agent on the Log Analytics Gateway, you need to repeat the listed installation steps for the data collection machine.
After setting up the data collection machine, continue getting started with On-demand Assessments by selecting the Configure Microsoft On-demand Assessments article in the Table of Contents.
Microsoft Monitoring Agent Upgrade
If a monitoring agent is already installed, the Microsoft Monitoring Agent setup will only display the upgrade command. The upgrade will keep the existing configuration and adds a new command to configure a Log Analytics workspace.
Follow the steps to perform an upgrade and configure the agent for the Log Analytics Workspace.
Run Setup to install the agent.
On the Welcome page, select Next.
On the License Terms page, read the license and then select I Agree.
On the begin Upgrade page, select Upgrade.
On the Completion page, select Finish.
Once the agent installation completes, go to the Control Panel.
Select Microsoft Monitoring Agent.
If the Log Analytics Gateway scenario is chosen or a Proxy server is in place go to the Proxy Settings tab. When this scenario is not used go to Step 9.
Select Use a proxy server and specify the fully qualified domain name (FQDN) or the IP address and port of the Log Analytics Gateway. If you use a proxy server instead of a Log Analytics Gateway, add the information for your proxy server and if required, authentication credentials (not required for the Log Analytics Gateway), then Select Apply.
Select the Azure Log Analytics (OMS) tab and select Add.
Copy and paste the Workspace ID and Workspace Key (Primary Key) from the log analytics portal. (Tip: Select the copy button then paste in the corresponding Agent Setup field). 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 select OK.
An exclamation mark will be visible in the Workspaces pane. Select Apply. This will stop and start the agent, and the Workspaces pane should look like the following example after a few seconds.
Select OK to finish.
Select OK to finish the Microsoft Monitoring Agent upgrade for Log Analytics.
After setting up the data collection machine, continue getting started with On-demand Assessments by selecting the Configure Microsoft On-demand Assessments article in the Table of Contents.