Retirement: HELM chart-based onboarding workflow for the Azure Monitor Container Insights agent is retiring on October 1, 2025

Starting October 1, 2025, the HELM chart-based onboarding workflow for the Container Insights agent will be retired. To ensure your clusters are secure and running smoothly, please migrate to Azure Arc Kubernetes Container Insights Extension by October 1, 2025\. If you’re hosting your Kubernetes cluster outside of Azure and have enabled Container Insights using unmanaged onboarding methods such as HELM, your cluster may have an outdated version of the Container Insights agent that does not receive automatic updates, leaving it vulnerable to security threats. You’ll need to connect your cluster to [Azure Arc for Kubernetes ](https://learn.microsoft.com/azure/azure-arc/kubernetes/overview)and then enable Container Insights through the [Azure Arc Kubernetes extension](https://learn.microsoft.com/azure/azure-arc/kubernetes/extensions-release#container-insights-in-azure-monitor). **Required action** To ensure your cluster remains secure and continues receiving critical security, quality and feature updates: * To view impacted resources in the Azure Portal, visit to [AzureMonitoringBrowseBlade](https://portal.azure.com/#view/Microsoft%5FAzure%5FMonitoring/AzureMonitoringBrowseBlade/~/containerInsights) and Monitored clusters, and look for "non-AKS" cluster type * Remove the Container Insights installed through HELM, by following the steps outlined [here](https://learn.microsoft.com/azure/azure-monitor/containers/kubernetes-monitoring-disable#remove-container-insights-with-helm). * Connect your existing Kubernetes cluster to Azure Arc, by following the steps outlined [here](https://learn.microsoft.com/azure/azure-arc/kubernetes/quickstart-connect-cluster?tabs=azure-cli). * Re-enable monitoring for your Kubernetes cluster using official Container Insights onboarding to ensure compliance and security. Follow the instructions [here](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Fcontainers%2Fkubernetes-monitoring-enable%3Ftabs%3Dcli&data=05%7C02%7Cgangams%40microsoft.com%7C65d99540f2ed4b16590608dd6c936a64%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638786102620069406%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=AcvfInekUZ1w1uQrZYicslT8kKHCDIMxSzHisZGpTlI%3D&reserved=0). **Recommended action** For more information, review our [FAQ](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Fcontainers%2Fcontainer-insights-faq&data=05%7C02%7Cgangams%40microsoft.com%7C65d99540f2ed4b16590608dd6c936a64%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638786102620079059%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=mBjwitxXaxrGY5fnRgTeIAIcULovS0m8bPctHKir1vk%3D&reserved=0).