Clarify maxPods setting and impact.

This [PR](#48686) introduced an unfortunate misunderstanding of the maxPods(https://docs.microsoft.com/en-us/rest/api/aks/agentpools/get#agentpool) setting.

This limitation is tied to the concepts described [here](https://docs.microsoft.com/en-us/azure/aks/configure-azure-cni#maximum-pods-per-node)

Author: Mikkel Mork Hegnhoj

articles/aks/windows-node-limitations.md

@@ -50,7 +50,7 @@ AKS clusters with Windows node pools must use the Azure CNI (advanced) networkin
 
 ## Can I change the max. # of pods per node?
 
-It is currently a requirement to be set to a maximum of 30 pods to ensure the reliability of your clusters.
+Yes, take a look here on the implications and options available: [Maximum number of pods][maximum-number-of-pods].
 
 ## How do patch my Windows nodes?
 
@@ -118,3 +118,4 @@ To get started with Windows Server containers in AKS, [create a node pool that r
 [nodepool-limitations]: use-multiple-node-pools.md#limitations
 [preview-support]: support-policies.md#preview-features-or-feature-flags
 [windows-container-compat]: /virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2019%2Cwindows-10-1909
+[maximum-number-of-pods]: configure-azure-cni.md#maximum-pods-per-node