Fleet Manager (Auto-Upgrade Profile) not triggering update run to upgrade AKS and Node Image versions

Question

Hello folks ,

I am trying to upgrade AKS clusters(deployed with 1.32.10) using Fleet Manager without hub cluster to upgrade to 1.33 using Channel as TargetKubernetesVersion.

Manual update runs are working correctly, but the auto-upgrade profile feature does not seem to trigger or apply the updates as per schedule defined in AKS upgrade scheduler.

As per Fleet manager configuration it should create update run of Auto trigger type, waited few days to check auto-upgrade profile to trigger update run but no luck

Can you assist me what configuration is missing w.r.t AKS or Fleet manager and to resolve this issue?

Deployed AKS and Fleet manager(without hub) in same subscription as below:

AKS configuration:

AKS cluster is deployed with Kubernetes version as 1.32.10

Automatic upgrade channel type as None, Node OS upgrade channel type as none

Automatic upgrade scheduler as Start on: Sat Feb 07 2026 17:00 +00:00 (Coordinated Universal Time)

Repeats: Every 2 week(s) on Saturday

Node Image scheduler as

Start on: Sat Feb 07 2026 17:00 +00:00 (Coordinated Universal Time)

Repeats: Every 2 week(s) on Saturday

Fleet manager configuration:

Added AKS under Fleet manager member clusters

Created strategy, stage and update group as below

Created Auto upgrade profiles Channel as TargetKubernetesVersion, Target Kubernetes minor version as 1.33 as below.
Assigned user managed Identity with Azure Kubernetes Service Contributor Role scope on AKS resource group.

Fleet members:

strategy:

auto upgrade profile:

Answer 1

Hello @Kameswara Rao Pudi ,

Your configuration is correct. The Fleet auto-upgrade has not been triggered because no new AKS 1.33 patch has been released in your region since the auto-upgrade profile was created.

Fleet auto-upgrade runs are initiated only when AKS publishes a new Kubernetes or node image version. They are not triggered by versions that were already available prior to the profile’s creation.

As a result, if AKS 1.33.x was already available in your region at the time you set up the auto-upgrade profile, Fleet will not start an upgrade.

Fleet is currently waiting for the next AKS 1.33 patch release in your region. For example, if 1.33.7 is the latest available version and 1.33.8 has not yet been released, no upgrade activity will occur.

If the latest 1.33 patch was released before you created the profile, you must wait for the next one.

Please let us know if you have any further questions. I’m happy to assist. Thank you!