Merge pull request #265862 from AdamSharif-MSFT/adsharif_NAP_stop_start_clarification

Updating stop/start cluster and nodepool and also NAP documentation to add related limitations

Author: PMEds28

articles/aks/node-autoprovision.md

@@ -68,6 +68,7 @@ NAP is based on the Open Source [Karpenter](https://karpenter.sh) project, and t
 - Windows and Azure Linux node pools aren't supported yet
 - Kubelet configuration through Node pool configuration is not supported
 - NAP can only be enabled on new clusters currently
+- It is not currently possible to stop nodepools or clusters which use the NAP feature
 
 ## Enable node autoprovisioning
 

articles/aks/start-stop-cluster.md

@@ -21,6 +21,7 @@ This article assumes you have an existing AKS cluster. If you need an AKS cluste
 When using the cluster stop/start feature, the following conditions apply:
 
 - This feature is only supported for Virtual Machine Scale Set backed clusters.
+- You can't stop clusters which use the [Node Autoprovisioning (NAP)](node-autoprovision.md) feature.
 - The cluster state of a stopped AKS cluster is preserved for up to 12 months. If your cluster is stopped for more than 12 months, you can't recover the state. For more information, see the [AKS support policies](support-policies.md).
 - You can only perform start or delete operations on a stopped AKS cluster. To perform other operations, like scaling or upgrading, you need to start your cluster first.
 - If you provisioned PrivateEndpoints linked to private clusters, they need to be deleted and recreated again when starting a stopped AKS cluster.

articles/aks/start-stop-nodepools.md

@@ -17,6 +17,7 @@ You might not need to continuously run your AKS workloads. For example, you migh
 * Spot node pools are supported.
 * Stopped node pools can be upgraded.
 * The cluster and node pool must be running.
+* You can't stop node pools from clusters which use the [Node Autoprovisioning (NAP)](node-autoprovision.md) feature.
 
 ## Before you begin