Migrate to Managed Identity Authentication in Azure Monitor Container Insights

Hi Nagashree
You can migrate to Managed Identity authentication from the Monitor settings panel for your AKS cluster. From the Monitoring section, click on the Insights tab. In the Insights tab, click on the Monitor Settings option, check the box for Use managed identity and click on Configure button

https://free.blessedness.top/en-us/azure/azure-monitor/containers/container-insights-authentication?source=recommendations&tabs=portal-azure-monitor#migrate-to-managed-identity-authentication

Please let me know if you face any challenge here, I can help you to resolve this issue further

If the comment was helpful, please click "Upvote"

Hi Naveena,

Thanks for your response. However, my question is a bit different. In my monitor settings, the “Use managed identity” option is already enabled, just as shown in the screenshot you shared.

But when I run the query provided in the documentation (the same link you have shared), it lists the resources that are using legacy authentication. Have pasted query below:

resources        
| where type =~ 'Microsoft.ContainerService/managedClusters'       
| project id, name, aksproperties = parse_json(tolower(properties)), location, identity        
| extend isEnabled = aksproperties.addonprofiles.omsagent.enabled         
| extend workspaceResourceId = iif(isEnabled == true, aksproperties.addonprofiles.omsagent.config.loganalyticsworkspaceresourceid, '')        
| extend useAADAuth  = aksproperties.addonprofiles.omsagent.config.useaadauth  
| where isEnabled =~ "true" and useAADAuth != true 
| extend parts = split(tostring(id), "/")
| extend subscriptionId = parts[2], AKSClusterName = parts[-1], resourceGroupName = parts[4] 
| project AKSClusterName, resourceGroupName, subscriptionId, location, AKSClusterId = tolower(id), workspaceResourceId

This query returns my three clusters. So, even though “Use managed identity” is already checked in the Azure portal for all those 3 cluster's monitor settings , why does the query still show that these clusters are using legacy authentication?