After you onboard to Horizon Cloud Service - next-gen, you can use the VMware Configuration Maximums online tool to help size your deployment based on the number of VMs, users, service principals, and so on, supported per provider and Horizon Edge Gateway.

The information in the VMware Configuration Maximums tool for Horizon Cloud Service - next-gen tends to sufficiently convey the meaning of each of the listed limits. However, this topic provides additional background information for specified limits as necessary to more thoroughly explain the impact that those specific limits can have on the performance of your deployment.

Apply the information that follows to the appropriate Horizon Cloud Service - next-gen configuration limits provided in the VMware Configuration Maximum tool.

Impact of the Number of Service Principals on Provisioning Time
To provision a desktop during virtual machine lifecycle management workflows, Horizon Cloud Service – next gen issues several Microsoft Azure API calls. Microsoft Azure API throttling is service principal based. Therefore, increasing the number of service principals enables more APIs to be issued concurrently, which improves the performance of the virtual machine lifecycle management workflows. Workflow examples include pool creation and deletion, bulk virtual machine power operations, and so on.
Impact of App Volumes Delivery File Shares on Application Loading Times
App Volumes applications are delivered to desktops by mounting the VHD files present in the delivery file shares. The higher the number of concurrent mounts in a file share, the longer the application provisioning takes to complete within a session or desktop. Increasing the number of delivery file shares improves the application provisioning process, which results in the applications becoming ready sooner.