cwash05

@captainsafia any update on this pr? this feature is very much needed for my scenario.

Hi @mcgallan Yes everything looks good. The cluster has this configuration ``` param userAssignedIdentities_kubelet_agiccustom_mi_externalid string = '/subscriptions/b307d0ad-1b29-41b8-bfdc-5d79f52426eb/resourceGroups/agiccustom-centralus-rg/providers/Microsoft.ManagedIdentity/userAssignedIdentities/kubelet-agiccustom-mi' addonProfiles: { IngressApplicationGateway: { enabled: true config: { applicationGatewayId: applicationGateways_agiccustom_appgw_externalid effectiveApplicationGatewayId: applicationGateways_agiccustom_appgw_externalid enableHttp2:...

@mcgallan when you create the addon and give the custom MI, it's supposed to use that MI for its operations. That's not happening. It's still using the default MI. After...

i didn't use this syntax ``` var clusterData = new ContainerServiceManagedClusterData(location == null ? resourceGroup.Data.Location : location.Value) { //other properties AddonProfiles = { { "IngressApplicationGateway", new ManagedClusterAddonProfile(isEnabled: true) { Config...

@mcgallan I don't think adding it directly in the data section would cause any more of an issue during the creation process. Everything seems to be created correctly. the issue...

@mcgallan if you go and get the logs for the ingress pod, there are no authentication errors?