Configure Microsoft Defender for Containers components

Microsoft Defender for Containers is the cloud-native solution for securing your containers.

Defender for Containers protects your clusters whether they're running in:

  • Azure Kubernetes Service (AKS) - Microsoft's managed service for developing, deploying, and managing containerized applications.

  • Amazon Elastic Kubernetes Service (EKS) in a connected Amazon Web Services (AWS) account - Amazon's managed service for running Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane or nodes.

  • Google Kubernetes Engine (GKE) in a connected Google Cloud Platform (GCP) project - Google’s managed environment for deploying, managing, and scaling applications using GCP infrastructure.

  • Other Kubernetes distributions (using Azure Arc-enabled Kubernetes) - Cloud Native Computing Foundation (CNCF) certified Kubernetes clusters hosted on-premises or on IaaS. For more information, see the On-prem/IaaS (Arc) section of Supported features by environment.

Learn about this plan in Overview of Microsoft Defender for Containers.

You can first learn how to connect and protect your containers in these articles:

You can also learn more by watching these videos from the Defender for Cloud in the Field video series:

Note

Defender for Containers' support for Arc-enabled Kubernetes clusters, AWS EKS, and GCP GKE is a preview feature. The preview feature is available on a self-service, opt-in basis.

Previews are provided "as is" and "as available" and are excluded from the service level agreements and limited warranty.

To learn more about the supported operating systems, feature availability, outbound proxy and more, see the Defender for Containers feature availability.

Network requirements

Validate the following endpoints are configured for outbound access so that the Defender agent can connect to Microsoft Defender for Cloud to send security data and events:

See the required FQDN/application rules for Microsoft Defender for Containers.

By default, AKS clusters have unrestricted outbound (egress) internet access.

Network requirements

Caution

This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.

Validate the following endpoints are configured for outbound access so that the Defender agent can connect to Microsoft Defender for Cloud to send security data and events:

For public cloud deployments:

Azure Domain Azure Government Domain Microsoft Azure operated by 21Vianet Domain Port
*.ods.opinsights.azure.com *.ods.opinsights.azure.us *.ods.opinsights.azure.cn 443
*.oms.opinsights.azure.com *.oms.opinsights.azure.us *.oms.opinsights.azure.cn 443
login.microsoftonline.com login.microsoftonline.us login.chinacloudapi.cn 443

The following domains are only necessary if you're using a relevant OS. For example, if you have EKS clusters running in AWS, then you would only need to apply the Amazon Linux 2 (Eks): Domain: "amazonlinux.*.amazonaws.com/2/extras/*" domain.

Domain Port Host operating systems
amazonlinux.*.amazonaws.com/2/extras/* 443 Amazon Linux 2
yum default repositories - RHEL / Centos
apt default repositories - Debian

You'll also need to validate the Azure Arc-enabled Kubernetes network requirements.

Enable the plan

To enable the plan:

  1. From Defender for Cloud's menu, open the Settings page and select the relevant subscription.

  2. In the Defender plans page, select Defender for Containers and select Settings.

    screenshot of Defender plans page.

    Tip

    If the subscription already has Defender for Kubernetes and/or Defender for container registries enabled, an update notice is shown. Otherwise, the only option will be Defender for Containers.

    Defender for container registries and Defender for Kubernetes plans showing 'Deprecated' and upgrade information.

  3. Turn the relevant component on to enable it.

    screenshot of turning on components.

    Note

    • Defenders for Containers customers who joined before August 2023 and don't have Agentless discovery for Kubernetes enabled as part of Defender CSPM when they enabled the plan, must manually enable the Agentless discovery for Kubernetes extension within the Defender for Containers plan.
    • When you turn off Defender for Containers, the components are set to off and are not deployed to any more containers but they are not removed from containers that they are already installed on.

Enablement method per capability

By default, when enabling the plan through the Azure portal, Microsoft Defender for Containers is configured to automatically enable all capabilities and install all required components to provide the protections offered by the plan, including the assignment of a default workspace.

If you don't want to enable all capabilities of the plans, you can manually select which specific capabilities to enable by selecting Edit configuration for the Containers plan. Then, in the Settings & monitoring page, select the capabilities you want to enable. In addition, you can modify this configuration from the Defender plans page after initial configuration of the plan.

For detailed information on the enablement method for each one the capabilities, see the support matrix.

Roles and permissions

Learn more about the roles used to provision Defender for Containers extensions.

Assigning custom workspace for Defender agent

You can assign a custom workspace through Azure Policy.

Manual deployment of Defender agent or Azure policy agent without auto-provisioning using recommendations

Capabilities that require agent installation can also be deployed on one or more Kubernetes clusters, using the appropriate recommendation:

Agent Recommendation
Defender Agent for Kubernetes Azure Kubernetes Service clusters should have Defender profile enabled
Defender Agent for Arc-enabled Kubernetes Azure Arc-enabled Kubernetes clusters should have the Defender extension installed
Azure policy agent for Kubernetes Azure Kubernetes Service clusters should have the Azure Policy Add-on for Kubernetes installed
Azure policy agent for Arc-enabled Kubernetes Azure Arc-enabled Kubernetes clusters should have the Azure Policy extension installed

Perform the following steps to perform deployment of the Defender agent on specific clusters:

  1. From Microsoft Defender for Cloud's recommendations page, open the Enable enhanced security security control or search directly for one of the above recommendations (or use the above links to open the recommendation directly)

  2. View all clusters without an agent via the unhealthy tab.

  3. Select the clusters to deploy the desired agent on and select Fix.

  4. Select Fix X resources.

Deploying Defender agent - all options

You can enable the Defender for Containers plan and deploy all of the relevant components from the Azure portal, the REST API, or with a Resource Manager template. For detailed steps, select the relevant tab.

Once the Defender agent has been deployed, a default workspace is automatically assigned. You can assign a custom workspace in place of the default workspace through Azure Policy.

Note

The Defender agent is deployed to each node to provide the runtime protections and collect signals from those nodes using eBPF technology.

Use the fix button from the Defender for Cloud recommendation

A streamlined, frictionless, process lets you use the Azure portal pages to enable the Defender for Cloud plan and setup auto provisioning of all the necessary components for defending your Kubernetes clusters at scale.

A dedicated Defender for Cloud recommendation provides:

  • Visibility about which of your clusters has the Defender agent deployed
  • Fix button to deploy it to those clusters without the agent
  1. From Microsoft Defender for Cloud's recommendations page, open the Enable enhanced security security control.

  2. Use the filter to find the recommendation named Azure Kubernetes Service clusters should have Defender profile enabled.

    Tip

    Notice the Fix icon in the actions column

  3. Select the clusters to see the details of the healthy and unhealthy resources - clusters with and without the agent.

  4. From the unhealthy resources list, select a cluster and select Remediate to open the pane with the remediation confirmation.

  5. Select Fix X resources.

Enable the plan

To enable the plan:

  1. From Defender for Cloud's menu, open the Settings page and select the relevant subscription.

  2. In the Defender plans page, select Defender for Containers and select Settings. screenshot of Defender plans page.

    Tip

    If the subscription already has Defender for Kubernetes or Defender for container registries enabled, an update notice is shown. Otherwise, the only option will be Defender for Containers.

    Defender for container registries and Defender for Kubernetes plans showing 'Deprecated' and upgrade information.

  3. Turn the relevant component on to enable it.

    screenshot of turning on components.

    Note

    When you turn off Defender for Containers, the components are set to off and are not deployed to any more containers but they are not removed from containers that they are already installed on.

By default, when enabling the plan through the Azure portal, Microsoft Defender for Containers is configured to automatically install required components to provide the protections offered by plan, including the assignment of a default workspace.

If you want to disable automatic installation of components during the onboarding process, select Edit configuration for the Containers plan. The Advanced options will appear, and you can disable automatic installation for each component.

In addition, you can modify this configuration from the Defender plans page.

Note

If you choose to disable the plan at any time after enabling it through the portal as shown above, you'll need to manually remove Defender for Containers components deployed on your clusters.

You can assign a custom workspace through Azure Policy.

If you disable the automatic installation of any component, you can easily deploy the component to one or more clusters using the appropriate recommendation:

Learn more about the roles used to provision Defender for Containers extensions.

Prerequisites

Before deploying the agent, ensure you:

Deploy the Defender agent

You can deploy the Defender agent using a range of methods. For detailed steps, select the relevant tab.

Use the fix button from the Defender for Cloud recommendation

A dedicated Defender for Cloud recommendation provides:

  • Visibility about which of your clusters has the Defender agent deployed
  • Fix button to deploy it to those clusters without the agent
  1. From Microsoft Defender for Cloud's recommendations page, open the Enable enhanced security security control.

  2. Use the filter to find the recommendation named Azure Arc-enabled Kubernetes clusters should have Defender for Cloud's extension installed.

    Microsoft Defender for Cloud's recommendation for deploying the Defender agent for Azure Arc-enabled Kubernetes clusters.

    Tip

    Notice the Fix icon in the actions column

  3. Select the agent to see the details of the healthy and unhealthy resources - clusters with and without the agent.

  4. From the unhealthy resources list, select a cluster and select Remediate to open the pane with the remediation options.

  5. Select the relevant Log Analytics workspace and select Remediate x resource.

    Deploy Defender agent for Azure Arc with Defender for Cloud's 'fix' option.

Verify the deployment

To verify that your cluster has the Defender agent installed on it, follow the steps in one of the tabs below:

Use Defender for Cloud recommendation to verify the status of your agent

  1. From Microsoft Defender for Cloud's recommendations page, open the Enable Microsoft Defender for Cloud security control.

  2. Select the recommendation named Azure Arc-enabled Kubernetes clusters should have Microsoft Defender for Cloud's extension installed.

    Microsoft Defender for Cloud's recommendation for deploying the Defender agent for Azure Arc-enabled Kubernetes clusters.

  3. Check that the cluster on which you deployed the agent is listed as Healthy.

Enable the plan

Important

To protect your EKS clusters, enable the Containers plan on the relevant account connector:

  1. From Defender for Cloud's menu, open Environment settings.

  2. Select the AWS connector.

    Screenshot of Defender for Cloud's environment settings page showing an AWS connector.

  3. Verify that the toggle for the Containers plan is set to On.

    Screenshot of enabling Defender for Containers for an AWS connector.

  4. To change optional configurations for the plan, select Settings.

    Screenshot of Defender for Cloud's environment settings page showing the settings for the Containers plan.

    • Defender for Containers requires control plane audit logs to provide runtime threat protection. To send Kubernetes audit logs to Microsoft Defender, toggle the setting to On. To change the retention period for your audit logs, enter the required time frame.

      Note

      If you disable this configuration, then the Threat detection (control plane) feature will be disabled. Learn more about features availability.

    • Agentless discovery for Kubernetes provides API-based discovery of your Kubernetes clusters. To enable the Agentless discovery for Kubernetes feature, toggle the setting to On.

    • The Agentless Container Vulnerability Assessment provides vulnerability management for images stored in ECR and running images on your EKS clusters. To enable the Agentless Container Vulnerability Assessment feature, toggle the setting to On.

  5. Continue through the remaining pages of the connector wizard.

  6. If you're enabling the Agentless Discovery for Kubernetes feature, you need to grant control plane permissions on the cluster. You can do this in one of the following ways:

    • Run this Python script to grant the permissions. The script adds the Defender for Cloud role MDCContainersAgentlessDiscoveryK8sRole to the aws-auth ConfigMap of the EKS clusters that you wish to onboard.

    • Grant each Amazon EKS cluster the MDCContainersAgentlessDiscoveryK8sRole role with the ability to interact with the cluster. Sign into all existing and newly created clusters using eksctl and execute the following script:

          eksctl create iamidentitymapping \ 
          --cluster my-cluster \ 
          --region region-code \ 
          --arn arn:aws:iam::account:role/MDCContainersAgentlessDiscoveryK8sRole \ 
          --group system:masters\ 
          --no-duplicate-arns
      

      For more information, see Enabling IAM principal access to your cluster.

  7. Azure Arc-enabled Kubernetes, the Defender agent, and Azure Policy for Kubernetes should be installed and running on your EKS clusters. There is a dedicated Defender for Cloud recommendations to install these extensions (and Azure Arc if necessary):

    • EKS clusters should have Microsoft Defender's extension for Azure Arc installed

    For each of the recommendations, follow the steps below to install the required extensions.

    To install the required extensions:

    1. From Defender for Cloud's Recommendations page, search for one of the recommendations by name.

    2. Select an unhealthy cluster.

      Important

      You must select the clusters one at a time.

      Don't select the clusters by their hyperlinked names: select anywhere else in the relevant row.

    3. Select Fix.

    4. Defender for Cloud generates a script in the language of your choice: select Bash (for Linux) or PowerShell (for Windows).

    5. Select Download remediation logic.

    6. Run the generated script on your cluster.

    7. Repeat steps "a" through "f" for the second recommendation.

    Video of how to use the Defender for Cloud recommendation to generate a script for your EKS clusters that enables the Azure Arc extension.

View recommendations and alerts for your EKS clusters

Tip

You can simulate container alerts by following the instructions in this blog post.

To view the alerts and recommendations for your EKS clusters, use the filters on the alerts, recommendations, and inventory pages to filter by resource type AWS EKS cluster.

Screenshot of how to use filters on Microsoft Defender for Cloud's security alerts page to view alerts related to AWS EKS clusters.

Enable the plan

Important

If you haven't already connected a GCP project, connect your GCP projects to Microsoft Defender for Cloud.

To protect your GKE clusters, you'll need to enable the Containers plan on the relevant GCP project.

Note

Verify that you don't have any Azure policies that prevent the Arc installation.

To protect Google Kubernetes Engine (GKE) clusters:

  1. Sign in to the Azure portal.

  2. Navigate to Microsoft Defender for Cloud > Environment settings.

  3. Select the relevant GCP connector

    Screenshot showing an example GCP connector.

  4. Select the Next: Select plans > button.

  5. Ensure that the Containers plan is toggled to On.

    Screenshot that shows the containers plan is toggled to on.

  6. To change optional configurations for the plan, select Settings.

    Screenshot of Defender for Cloud's environment settings page showing the settings for the Containers plan.

    • Kubernetes audit logs to Defender for Cloud: Enabled by default. This configuration is available at the GCP project level only. It provides agentless collection of the audit log data through GCP Cloud Logging to the Microsoft Defender for Cloud back end for further analysis. Defender for Containers requires control plane audit logs to provide runtime threat protection. To send Kubernetes audit logs to Microsoft Defender, toggle the setting to On.

      Note

      If you disable this configuration, then the Threat detection (control plane) feature will be disabled. Learn more about features availability.

    • Auto provision Defender's agent for Azure Arc and Auto provision Azure Policy extension for Azure Arc: Enabled by default. You can install Azure Arc-enabled Kubernetes and its extensions on your GKE clusters in three ways:

    • Agentless discovery for Kubernetes provides API-based discovery of your Kubernetes clusters. To enable the Agentless discovery for Kubernetes feature, toggle the setting to On.

    • The Agentless Container Vulnerability Assessment provides vulnerability management for images stored in Google Registries (GAR and GCR) and running images on your GKE clusters. To enable the Agentless Container Vulnerability Assessment feature, toggle the setting to On.

  7. Select the Copy button.

    Screenshot showing the location of the copy button.

  8. Select the GCP Cloud Shell > button.

  9. Paste the script into the Cloud Shell terminal, and run it.

The connector will update after the script executes. This process can take up to 6-8 hours up to complete.

Deploy the solution to specific clusters

If you disabled any of the default auto provisioning configurations to Off, during the GCP connector onboarding process, or afterwards. You'll need to manually install Azure Arc-enabled Kubernetes, the Defender agent, and the Azure Policy for Kubernetes to each of your GKE clusters to get the full security value out of Defender for Containers.

There are 2 dedicated Defender for Cloud recommendations you can use to install the extensions (and Arc if necessary):

  • GKE clusters should have Microsoft Defender's extension for Azure Arc installed
  • GKE clusters should have the Azure Policy extension installed

Note

When installing Arc extensions, you must verify that the GCP project provided is identical to the one in the relevant connector.

To deploy the solution to specific clusters:

  1. Sign in to the Azure portal.

  2. Navigate to Microsoft Defender for Cloud > Recommendations.

  3. From Defender for Cloud's Recommendations page, search for one of the recommendations by name.

    Screenshot showing how to search for the recommendation.

  4. Select an unhealthy GKE cluster.

    Important

    You must select the clusters one at a time.

    Don't select the clusters by their hyperlinked names: select anywhere else in the relevant row.

  5. Select the name of the unhealthy resource.

  6. Select Fix.

    Screenshot showing the location of the fix button.

  7. Defender for Cloud will generate a script in the language of your choice:

    • For Linux, select Bash.
    • For Windows, select PowerShell.
  8. Select Download remediation logic.

  9. Run the generated script on your cluster.

  10. Repeat steps 3 through 8 for the second recommendation.

View your GKE cluster alerts

  1. Sign in to the Azure portal.

  2. Navigate to Microsoft Defender for Cloud > Security alerts.

  3. Select the button.

  4. In the Filter dropdown menu, select Resource type.

  5. In the Value dropdown menu, select GCP GKE Cluster.

  6. Select Ok.

Simulate security alerts from Microsoft Defender for Containers

A full list of supported alerts is available in the reference table of all Defender for Cloud security alerts.

  1. To simulate a security alert, run the following command from the cluster:

    kubectl get pods --namespace=asc-alerttest-662jfi039n
    

    The expected response is No resource found.

    Within 30 minutes, Defender for Cloud detects this activity and trigger a security alert.

    Note

    To simulate agentless alerts for Defender for Containers, Azure Arc isn't a prerequisite.

  2. In the Azure portal, open Microsoft Defender for Cloud's security alerts page and look for the alert on the relevant resource:

    Sample alert from Microsoft Defender for Kubernetes.

Remove the Defender agent

To remove this - or any - Defender for Cloud extension, it's not enough to turn off auto provisioning:

  • Enabling auto provisioning, potentially impacts existing and future machines.
  • Disabling auto provisioning for an extension, only affects the future machines - nothing is uninstalled by disabling auto provisioning.

Nevertheless, to ensure the Defender for Containers components aren't automatically provisioned to your resources from now on, disable auto provisioning of the extensions as explained in Configure auto provisioning for agents and extensions from Microsoft Defender for Cloud.

You can remove the extension using Azure portal, Azure CLI, or REST API as explained in the tabs below.

Use Azure portal to remove the extension

  1. From the Azure portal, open Azure Arc.

  2. From the infrastructure list, select Kubernetes clusters and then select the specific cluster.

  3. Open the extensions page. The extensions on the cluster are listed.

  4. Select the cluster and select Uninstall.

    Removing an extension from your Arc-enabled Kubernetes cluster.

Default Log Analytics workspace for AKS

The Log Analytics workspace is used by the Defender agent as a data pipeline to send data from the cluster to Defender for Cloud without retaining any data in the Log Analytics workspace itself. As a result, users won't be billed in this use case.

The Defender agent uses a default Log Analytics workspace. If you don't already have a default Log Analytics workspace, Defender for Cloud will create a new resource group and default workspace when the Defender agent is installed. The default workspace is created based on your region.

The naming convention for the default Log Analytics workspace and resource group is:

  • Workspace: DefaultWorkspace-[subscription-ID]-[geo]
  • Resource Group: DefaultResourceGroup-[geo]

Assign a custom workspace

When you enable the auto-provision option, a default workspace will be automatically assigned. You can assign a custom workspace through Azure Policy.

To check if you have a workspace assigned:

  1. Sign in to the Azure portal.

  2. Search for and select Policy.

    Screenshot that shows how to locate the policy page.

  3. Select Definitions.

  4. Search for policy ID 64def556-fbad-4622-930e-72d1d5589bf5.

    Screenshot that shows where to search for the policy by ID number.

  5. Select Configure Azure Kubernetes Service clusters to enable Defender profile.

  6. Select Assignment.

    Screenshot showing where to locate the assignments tab.

  7. Follow the Create a new assignment with custom workspace steps if the policy hasn't yet been assigned to the relevant scope. Or, follow the Update assignment with custom workspace steps if the policy is already assigned and you want to change it to use a custom workspace.

Create a new assignment with custom workspace

If the policy hasn't been assigned, you'll see Assignments (0).

Screenshot showing that no workspace has been assigned.

To assign custom workspace:

  1. Select Assign.

  2. In the Parameters tab, deselect the Only show parameters that need input or review option.

  3. Select a LogAnalyticsWorkspaceResource ID from the dropdown menu.

    Screenshot showing where the dropdown menu is located.

  4. Select Review + create.

  5. Select Create.

Update assignment with custom workspace

If the policy has already been assigned to a workspace, you'll see Assignments (1).

Screenshot that shows Assignment (1), meaning a workspace has already been assigned.

Note

If you have more than one subscription the number might be higher.

To assign custom workspace:

  1. Select the relevant assignment.

    Screenshot that shows where to select the relevant assignment from.

  2. Select Edit assignment.

  3. In the Parameters tab, deselect the Only show parameters that need input or review option.

  4. Select a LogAnalyticsWorkspaceResource ID from the dropdown menu.

    Screenshot showing where the dropdown menu is located.

  5. Select Review + save.

  6. Select Save.

Default Log Analytics workspace for Arc

The Log Analytics workspace is used by the Defender agent as a data pipeline to send data from the cluster to Defender for Cloud without retaining any data in the Log Analytics workspace itself. As a result, users won't be billed in this use case.

The Defender agent uses a default Log Analytics workspace. If you don't already have a default Log Analytics workspace, Defender for Cloud will create a new resource group and default workspace when the Defender agent is installed. The default workspace is created based on your region.

The naming convention for the default Log Analytics workspace and resource group is:

  • Workspace: DefaultWorkspace-[subscription-ID]-[geo]
  • Resource Group: DefaultResourceGroup-[geo]

Assign a custom workspace

When you enable the auto-provision option, a default workspace will be automatically assigned. You can assign a custom workspace through Azure Policy.

To check if you have a workspace assigned:

  1. Sign in to the Azure portal.

  2. Search for, and select Policy.

    Screenshot that shows how to locate the policy page for Arc.

  3. Select Definitions.

  4. Search for policy ID 708b60a6-d253-4fe0-9114-4be4c00f012c.

    Screenshot that shows where to search for the policy by ID number for Arc.

  5. Select Configure Azure Arc enabled Kubernetes clusters to install Microsoft Defender for Cloud extension..

  6. Select Assignments.

    Screenshot that shows where the assignments tab is for Arc.

  7. Follow the Create a new assignment with custom workspace steps if the policy hasn't yet been assigned to the relevant scope. Or, follow the Update assignment with custom workspace steps if the policy is already assigned and you want to change it to use a custom workspace.

Create a new assignment with custom workspace

If the policy hasn't been assigned, you'll see Assignments (0).

Screenshot showing that no workspace has been assigned for Arc.

To assign custom workspace:

  1. Select Assign.

  2. In the Parameters tab, deselect the Only show parameters that need input or review option.

  3. Select a LogAnalyticsWorkspaceResource ID from the dropdown menu.

    Screenshot showing where the dropdown menu is located for Arc.

  4. Select Review + create.

  5. Select Create.

Update assignment with custom workspace

If the policy has already been assigned to a workspace, you'll see Assignments (1).

Note

If you have more than one subscription the number might be higher. If you have a number 1 or higher, the assignment might still not be on the relevant scope. If this is the case, you will want to follow the Create a new assignment with custom workspace steps.

Screenshot that shows Assignment (1), meaning a workspace has already been assigned for Arc.

To assign custom workspace:

  1. Select the relevant assignment.

    Screenshot that shows where to select the relevant assignment from for Arc.

  2. Select Edit assignment.

  3. In the Parameters tab, deselect the Only show parameters that need input or review option.

  4. Select a LogAnalyticsWorkspaceResource ID from the dropdown menu.

    Screenshot showing where the dropdown menu is located for Arc.

  5. Select Review + save.

  6. Select Save.

Remove the Defender agent

To remove this - or any - Defender for Cloud extension, it's not enough to turn off auto provisioning:

  • Enabling auto provisioning, potentially impacts existing and future machines.
  • Disabling auto provisioning for an extension, only affects the future machines - nothing is uninstalled by disabling auto provisioning.

Nevertheless, to ensure the Defender for Containers components aren't automatically provisioned to your resources from now on, disable auto provisioning of the extensions as explained in Configure auto provisioning for agents and extensions from Microsoft Defender for Cloud.

You can remove the extension using the REST API or a Resource Manager template as explained in the tabs below.

Use REST API to remove the Defender agent from AKS

To remove the extension using the REST API, run the following PUT command:

https://management.azure.com/subscriptions/{{SubscriptionId}}/resourcegroups/{{ResourceGroup}}/providers/Microsoft.ContainerService/managedClusters/{{ClusterName}}?api-version={{ApiVersion}}
Name Description Mandatory
SubscriptionId Cluster's subscription ID Yes
ResourceGroup Cluster's resource group Yes
ClusterName Cluster's name Yes
ApiVersion API version, must be >= 2022-06-01 Yes

Request body:

{
  "location": "{{Location}}",
  "properties": {
    "securityProfile": {
            "defender": {
                "securityMonitoring": {
                    "enabled": false
                }
            }
        }
    }
}

Request body parameters:

Name Description Mandatory
location Cluster's location Yes
properties.securityProfile.defender.securityMonitoring.enabled Determines whether to enable or disable Microsoft Defender for Containers on the cluster Yes

Learn more

You can check out the following blogs:

Next steps

Now that you enabled Defender for Containers, you can: