Microsoft Defender for Cloud
Cloud and workloadsVerify Defender for Containers deployment
In brief
The documentation now specifies that Defender collectors for Arc-enabled clusters and Helm deployments run as a Kubernetes DaemonSet, with a pod scheduled on each node.
What Defender admins need to know
Administrators can use this clarification when verifying Defender deployment across cluster nodes.
Summaries are generated from the documentation change itself.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Verify Defender for Containers deployment
Verify the Defender DaemonSet (Arc-enabled clusters and Helm)
For Arc-enabled clusters and Helm deployments, the Defender collectors run as a Kubernetes DaemonSet, which ensures a pod is scheduled on each node. You can also verify that the Defender DaemonSet is deployed correctly.correctly:
kubectl get ds -n mdc microsoft-defender-collectors-ds
@@ -2,8 +2,9 @@ title: Verify Defender for Containers deployment description: Learn how to verify that Microsoft Defender for Containers sensors and extensions are running correctly on Kubernetes clusters. ms.topic: how-to-ms.date: 03/12/2026+ms.date: 07/03/2026 ai-usage: ai-assisted+ms.custom: msecd-doc-authoring-1013 --- # Verify Defender for Containers deployment@@ -104,7 +105,7 @@ Confirm that the Defender sensor pods are in a `Running` state. ## Verify the Defender DaemonSet (Arc-enabled clusters and Helm) -You can also verify that the Defender DaemonSet is deployed correctly.+For Arc-enabled clusters and Helm deployments, the Defender collectors run as a Kubernetes DaemonSet, which ensures a pod is scheduled on each node. You can verify that the DaemonSet is deployed correctly: ```bash kubectl get ds -n mdc microsoft-defender-collectors-ds