This topic describes some of the common VMware Horizon Cloud Service on Microsoft Azure limits, which are also called supported maximums. This topic currently describes the supported maximums on both the number of desktop and farm RDSH VMs you can deploy in a single subscription and on the total number of concurrent connected sessions you can have per pod. Over time, this topic will be updated to list more of the known limits.
The service is tested up to a certain number of deployed VMs in a single subscription and the number of simultaneous connections that a pod can accommodate.
- Maximum of 2,000 desktop VMs and farm RDSH VMs per subscription
This limit is based on Microsoft Azure API limits that are given on a single subscription. To work well within these API limits during standard operations,
Horizon Cloud supports up to a maximum of 2,000 desktop VMs and farm RDSH VMs per subscription.
The 2,000 number per subscription includes VDI desktop VMs and farm RDSH VMs, and applies across all pods in the single subscription. For example, if you have one pod in your subscription, you might have up to 2,000 VDI desktops on that pod, or 1,950 VDI desktops plus 50 farm RDSH VMs. If you have more than one pod in your subscription, the number of VDI desktops and farms RDSH VMs across all of the pods must not total more than 2,000.
- Maximum of 2,000 sessions per pod
- Horizon Cloud supports running up to 2,000 concurrent connected sessions per pod. That 2,000 number includes connections to VDI desktops, RDS desktops, and RDS applications served by the pod. The pod's session-handling capabilities determine this maximum.