CIS Microsoft Azure Foundations Benchmark v1.4.0/Microsoft Defender for Cloud/33 of 115
2.11Ensure That Auto provisioning of 'Log Analytics agent for Azure VMs' is Set to 'On'
Control family: Microsoft Defender for Cloud
Control description
Enable automatic provisioning of the monitoring agent to collect security data.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
The Log Analytics agent this recommendation names has been retired: Microsoft deprecated it and Defender for Cloud now collects what it needs through agentless scanning, the Defender for Endpoint sensor and, where a plan still needs it, the Azure Monitor Agent, which is provisioned automatically. The intent, that every machine is covered without manual installs, is met by turning on those components.
Before you start
The same on every cloud, before the steps in the tabs.
- Record that the Log Analytics agent is retired and which components now meet this recommendation.
Evidence
- The recorded decision naming the components that replace the Log Analytics agent
On Azure the tasks check the Defender for Servers components that replace the old agent, then remove any leftover Log Analytics agents.
Task 1Turn on the components that replace the Log Analytics agent
- Sign in to the Azure portal at portal.azure.com and open Microsoft Defender for Cloud > Environment settings, then the subscription.
- In the Servers plan row, select Settings.
- Turn on Endpoint protection and Agentless scanning for machines, and select Continue.
- If the Databases plan covers SQL servers on machines, open its settings and confirm the Azure Monitor Agent is set to provision automatically.
- Select Save.
- Check it: the settings show the components on, and new VMs show as covered without manual installs.
Task 2Remove leftover Log Analytics agents
- Open Virtual machines, then each VM's Extensions + applications.
- Look for the Microsoft Monitoring Agent (MicrosoftMonitoringAgent or OmsAgentForLinux) extension.
- Once the Azure Monitor Agent or Defender components cover the machine, select the old extension and Uninstall.
- Check it: no VM still lists the old agent.
Evidence
- The Defender for Servers settings, showing the current components on
- The extensions list of each VM, without the retired agent
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.