Merge pull request #2629 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-18 06:00 UTC

Author: learn-build-service-prod[bot]

articles/defender-for-cloud/defender-for-containers-azure-overview.md

@@ -71,7 +71,8 @@ Choose the approach that best aligns with your organization's DevOps practices a
 
 Before deploying Defender for Containers on AKS, ensure you meet these requirements:
 
-- AKS clusters running Kubernetes 1.19 or later
+- AKS clusters running Kubernetes 1.22 or later
+
 - Network connectivity for outbound HTTPS to Azure endpoints
 - By default, AKS clusters have unrestricted outbound (egress) internet access. Clusters with restricted egress must allow specific endpoints. See: [Microsoft Defender for Containers - Required FQDN/application rules](/azure/aks/outbound-rules-control-egress#microsoft-defender-for-containers)
 

articles/defender-for-cloud/defender-for-containers-deployment-overview.md

@@ -76,7 +76,8 @@ Before deploying Defender for Containers, make sure you have:
 
 - An active Azure subscription
 - Owner or Contributor role on the subscription
-- Kubernetes cluster version 1.19 or later
+- Kubernetes cluster version 1.22 or later
+
 - Network connectivity to Azure services
 - For sensor-based capabilities: Sufficient cluster resources for Defender components - see [Defender sensor component details](defender-for-containers-architecture.md#defender-sensor-component-details)
 - [Enable an OpenId Connect (OIDC) issuer](/azure/aks/use-oidc-issuer) for your cluster.