[BUG] NAP does not allow to be activated due to having ipFamilies=null

[isdalp1]

Describe the bug
NAP does not allow to be enabled in AKS

To Reproduce
Steps to reproduce the behavior:

1. Run command 'az aks update -g $RESOURCE_GROUP_NAME -n $CLUSTER_NAME --ip-families IPv4'
   See output "ipFamilies": null"
2. Run command 'az aks update --name $CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME --node-provisioning-mode Auto --network-plugin azure --network-plugin-mode overlay --network-dataplane cilium'
   See error: '(OperationNotAllowed) .properties.nodeProvisioningProfile.mode cannot be Auto unless .properties.networkProfile.ipFamilies is set to one of [IPv4].
   Code: OperationNotAllowed'

Expected behavior
NAP feature should be enabled to allow addition/removal of nodes based on loads and not the current way where all nodes in the same pool are the same size.

Screenshots

Environment (please complete the following information):

• Kubernetes version [1.31.2]
• Nodepool's: 1 system (with taint CriticalAddonsOnly=true:NoSchedule) and 2 userpool

Additional context
How to configure NAP - TrackingID#2501070040009616: "Gracias por la clarificación, entonces el siguiente paso es crear un issue en GitHub [Feature] Node Autoprovision · Issue #2442 · Azure/AKS para que el equipo del proyecto esté al tanto y tome las medidas necesarias para arreglar el problema en el proyecto. Este equipo ya que es independiente a soporte estaría trabajando en ello."