Clarity around Windows and Virtual Node/Kubelet

Virtual Node installation on Portal does not support Windows Server containers.

Author: macolso

articles/aks/virtual-nodes-portal.md

@@ -64,7 +64,7 @@ Virtual Nodes functionality is heavily dependent on ACI's feature set. The follo
 * [Host aliases](https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/)
 * [Arguments](../container-instances/container-instances-exec.md#restrictions) for exec in ACI
 * [DaemonSets](concepts-clusters-workloads.md#statefulsets-and-daemonsets) will not deploy pods to the virtual node
-* [Windows Server nodes (currently in preview in AKS)](windows-container-cli.md) are not supported alongside virtual nodes. You can use virtual nodes to schedule Windows Server containers without the need for Windows Server nodes in an AKS cluster.
+* [Windows Server nodes (currently in preview in AKS)](windows-container-cli.md) are not supported alongside virtual nodes. You can manually install the open source [Virtual Kubelet ACI provider](https://github.com/virtual-kubelet/azure-aci) to schedule Windows Server containers without the need for Windows Server nodes in an AKS cluster. Visit [ACI's documentation](https://docs.microsoft.com/en-us/azure/container-instances/container-instances-overview#linux-and-windows-containers) to learn more Windows Server containers' preview limitations. 
 
 ## Sign in to Azure
 
@@ -241,4 +241,4 @@ Virtual nodes are one component of a scaling solution in AKS. For more informati
 [aks-hpa]: tutorial-kubernetes-scale.md
 [aks-cluster-autoscaler]: cluster-autoscaler.md
 [aks-basic-ingress]: ingress-basic.md
-[az-provider-list]: /cli/azure/provider#az-provider-list
+[az-provider-list]: /cli/azure/provider#az-provider-list