Quickstart: Connect your non-Azure machines to Microsoft Defender for Cloud
Defender for Cloud can monitor the security posture of your non-Azure computers, but first you need to connect them to Azure.
You can connect your non-Azure computers in any of the following ways:
- Using Azure Arc-enabled servers (recommended)
- From Defender for Cloud's pages in the Azure portal (Getting started and Inventory)
Each of these is described on this page.
If you're connecting machines from other cloud providers, see Connect your AWS accounts or Connect your GCP projects. Defender for Cloud's multicloud connectors for AWS and GCP transparently handles the Azure Arc deployment for you.
Add non-Azure machines with Azure Arc
The preferred way of adding your non-Azure machines to Microsoft Defender for Cloud is with Azure Arc-enabled servers.
A machine with Azure Arc-enabled servers becomes an Azure resource and - when you've installed the Log Analytics agent on it - appears in Defender for Cloud with recommendations like your other Azure resources.
In addition, Azure Arc-enabled servers provides enhanced capabilities such as the option to enable guest configuration policies on the machine, simplify deployment with other Azure services, and more. For an overview of the benefits, see Supported cloud operations.
Defender for Cloud's auto-deploy tools for deploying the Log Analytics agent works with machines running Azure Arc however this capability is currently in preview . When you've connected your machines using Azure Arc, use the relevant Defender for Cloud recommendation to deploy the agent and benefit from the full range of protections offered by Defender for Cloud:
Learn more about Azure Arc-enabled servers.
To deploy Azure Arc:
- For one machine, follow the instructions in Quickstart: Connect hybrid machines with Azure Arc-enabled servers.
- To connect multiple machines at scale to Azure Arc-enabled servers, see Connect hybrid machines to Azure at scale
Add non-Azure machines from the Azure portal
From Defender for Cloud's menu, open the Getting started page.
Select the Get started tab.
Below Add non-Azure servers, select Configure .
You can also open add machines from the inventory page's Add non-Azure servers button.
A list of your Log Analytics workspaces is shown. The list includes, if applicable, the default workspace created for you by Defender for Cloud when automatic provisioning was enabled. Select this workspace or another workspace you want to use.
You can add computers to an existing workspace or create a new workspace.
Optionally, to create a new workspace, select Create new workspace.
From the list of workspaces, select Add Servers for the relevant workspace.
The Agents management page appears.
From here, choose the relevant procedure below depending on the type of machines you're onboarding:
Onboard your Linux machines
To add Linux machines, you need the WGET command from the Agents management page.
From the Agents management page, copy the WGET command into Notepad. Save this file to a location that can be accessible from your Linux computer.
On your Linux computer, open the file with the WGET command. Select the entire content and copy and paste it into a terminal console.
When the installation completes, you can validate that the
omsagentis installed by running the
pgrepcommand. The command will return the
The logs for the Agent can be found at:
/var/opt/microsoft/omsagent/\<workspace id>/log/. It might take up to 30 minutes for the new Linux machine to appear in Defender for Cloud.
Onboard your Windows machines
To add Windows machines, you need the information on the Agents management page and to download the appropriate agent file (32/64-bit).
- Select the Download Windows Agent link applicable to your computer processor type to download the setup file.
- From the Agents management page, copy the Workspace ID and Primary Key into Notepad.
- Copy the downloaded setup file to the target computer and run it.
- Follow the installation wizard (Next, I Agree, Next, Next).
- On the Azure Log Analytics page, paste the Workspace ID and Workspace Key (Primary Key) that you copied into Notepad.
- If the computer should report to a Log Analytics workspace in Azure Government cloud, select Azure US Government from the Azure Cloud dropdown list.
- If the computer needs to communicate through a proxy server to the Log Analytics service, select Advanced and provide the URL and port number of the proxy server.
- When you've entered all of the configuration settings, select Next.
- From the Ready to Install page, review the settings to be applied and select Install.
- On the Configuration completed 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.
For further information on installing and configuring the agent, see Connect Windows machines.
Congratulations! Now you can see your Azure and non-Azure machines together in one place. Open the asset inventory page and filter to the relevant resource types. These icons distinguish the types:
Azure Arc-enabled server
This page showed you how to add your non-Azure machines to Microsoft Defender for Cloud. To monitor their status, use the inventory tools as explained in the following page: