Merge pull request #239209 from schaffererin/scaleupnodepoolsquota

Adding link to service quotas and limits doc for more info on node pool limits

Author: prmerger-automator[bot]

articles/aks/scale-cluster.md

@@ -9,6 +9,10 @@ ms.date: 03/27/2023
 
 If the resource needs of your applications change, your cluster performance may be impacted due to low capacity on CPU, memory, PID space, or disk sizes. To address these changes, you can manually scale your AKS cluster to run a different number of nodes. When you scale down, nodes are carefully [cordoned and drained][kubernetes-drain] to minimize disruption to running applications. When you scale up, AKS waits until nodes are marked **Ready** by the Kubernetes cluster before pods are scheduled on them.
 
+## Before you begin
+
+Review the [AKS service quotas and limits][service-quotas] to ensure your cluster can scale to your desired number of nodes.
+
 ## Scale the cluster nodes
 
 > [!NOTE]
@@ -164,3 +168,4 @@ In this article, you manually scaled an AKS cluster to increase or decrease the
 [cluster-autoscaler]: cluster-autoscaler.md
 [az-aks-nodepool-scale]: /cli/azure/aks/nodepool#az_aks_nodepool_scale
 [update-azaksnodepool]: /powershell/module/az.aks/update-azaksnodepool
+[service-quotas]: ./quotas-skus-regions.md#service-quotas-and-limits