Update limitations sections

Author: chasewilson

articles/aks/configure-azure-cni-static-block-allocation.md

@@ -44,11 +44,13 @@ This article shows you how to use Azure CNI Networking for static allocation of
 ## Limitations
 
 Below are some of the limitations of using Azure CNI Static Block allocation:
-* Minimum Kubernetes Version required is 1.28
-* Maximum subnet size supported is x.x.x.x/12 ~ 1 million IPs
-* The property of --pod-ip-allocation mode is only available in `aks create` and `aks nodepool add` commands. This means you cannot update an existing node pool that is running in Dynamic IP allocation mode to Static Block.
-* One subnet can only be used in a single mode of operation across all node pools. If a subnet is used in Static Block mode it cannot be used in Dynamic IP allocation mode in a different cluster or node pool and vice versa.
-* Across all the CIDR blocks assigned to a node in the node pool, one IP will be selected as the primary IP of the node. Thus, for network administrators selecting the `--max-pods` value try to use the calculation below to best serve your needs and have optimal usage of IPs in the subnet:  
+- Minimum Kubernetes Version required is 1.28
+- Maximum subnet size supported is x.x.x.x/12 ~ 1 million IPs
+- Not supported for Windows node pools (Windows support coming soon)
+- Not supported for Cilium Data Plane (support coming soon)
+- Only a single mode of operation can be used per subnet. If a subnet uses Static Block allocation mode, it cannot be use Dynamic IP allocation mode in a different cluster or node pool with the same subnet and vice versa.
+- Only supported in new clusters or when adding node pools with a different subnet to existing clusters. Migrating or updating existing clusters or node pools is not supported.
+- Across all the CIDR blocks assigned to a node in the node pool, one IP will be selected as the primary IP of the node. Thus, for network administrators selecting the `--max-pods` value try to use the calculation below to best serve your needs and have optimal usage of IPs in the subnet:  
 `max_pods` = (N * 16) - 1`
 where N is any positive integer and N > 0