The following table details the configuration limits of a Horizon Cloud Pod:
| Component | Limit |
| Maximum active sessions per Cloud Pod | 200,000 |
| Maximum number of Horizon pods in a Cloud Pod | 25 |
| Maximum number of sites where Cloud Pod member Horizon pods can be located | 10 |
| Maximum number of Horizon Connection Servers instances in a Cloud Pod | 175 |
| Maximum number of recommended sessions per individual Horizon pod | 10,000 |
It is important to note that while a single Horizon pod can support up to 10,000 (recommended) active sessions, a single Cloud Pod composed of up to 25 individual Horizon pods can support no more than 200,000 active sessions, even though (if not members of a Cloud Pod) those pods could support up to 250,000 active sessions.
The configuration maximums of a Horizon Cloud Pod are subject to change as new versions of Horizon are released. Consult the VMware Horizon documentation (https://docs.vmware.com/en/VMware-Horizon-7/index.html) for current information concerning platform limits.
Admittedly, most readers of this book are not likely to be impacted by the architectural limitations of a Horizon Cloud Pod. Just know that while the feature does expand upon the limits of a single Horizon pod, it doesn't expand them linearly.