Mind Maps for Mitigate threats using Microsoft Defender for Cloud

Regardless of whether you are using auto provisioning or manual provisioning, the initial installation of the agent on on-premises devices generally requires some form of manual intervention. Here's a brief breakdown:

Manual Provisioning: You manually install and configure the agent on each device. This involves individual effort for each installation.
Auto Provisioning: You set up a system to automate the deployment and configuration of agents. This can involve scripting or using configuration management tools to deploy the agent, but the initial setup of the automation framework might still require some manual steps.

Generate and Run PowerShell Script: To onboard an on-premises server to Azure Arc, you need to generate a PowerShell script. This script is then executed on the on-premises server to establish a connection with Azure Arc.

Install Log Analytics Agent: To enable log analytics and protection, you must install the Log Analytics agent on the on-premises server. You’ll need to configure the agent with the Workspace ID and Primary Key from your Azure Log Analytics workspace. This setup allows the server to send data back to Azure Arc for monitoring and analytics.

Manual Provisioning: You manually execute the script and install the agent yourself. This means you handle both the execution of the script and the installation of the agent manually, including configuring any necessary parameters.
Auto Provisioning: You execute the script, but the agent installation process is automated. The script handles the installation and configuration of the agent, including the automatic setup of the relevant workspace ID and primary key, reducing the need for manual intervention in these steps.