Limit of users for each hostpool

Pankaj Gupta (IT) 0 Reputation points
2023-05-15T10:50:30.65+00:00

Hello,
We are using standard storage with Multisession VMs. We want to move 3000+ users on AVD.
Per VM we are having 8 users configured.
We using Nerdio as our Integration tool.
All those users belongs to one Location but multiple departments.
Is there any limitations for each host pool i.e. we should not allow more than 500 users to connect to one Host Pool.
Please advise.

Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,835 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Alistair Ross 7,466 Reputation points Microsoft Employee
    2023-05-15T11:17:44.11+00:00

    Hello

    The Azure Virtual Desktop Service limits can be found here. https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-virtual-desktop-service-limits (Shared below as well)

    Azure Virtual Desktop Object Per Parent Container Object Service Limit
    Workspace Azure Active Directory Tenant 1300
    HostPool Workspace 400
    Application group Azure Active Directory Tenant 500<sup>1</sup>
    RemoteApp Application group 500
    Role Assignment Any Azure Virtual Desktop Object 200
    Session Host HostPool 10,000

    Using these numbers you can have up to 10,000 VM's per host pool which would be more than enough for your 3000 users.

    As you are looking at setting up multi session hosts for 8 users, I would recommend you read the guidance here. https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/virtual-machine-recs?toc=%2Fazure%2Fvirtual-desktop%2Ftoc.json&bc=%2Fazure%2Fvirtual-desktop%2Fbreadcrumb%2Ftoc.json

    While there is no limit to the number of users per session, the limits will be relating to the number of resources available on the session host per user (CPU, Memory, Disk I/O)

    I hope this answers your question

    Alistair

    0 comments No comments

  2. Prrudram-MSFT 28,201 Reputation points Moderator
    2023-05-15T15:44:25.7133333+00:00

    Hello @Pankaj Gupta (IT)

    We don't have a limit of 500 users per host pool. Nevertheless, you should consider using Premium SSDs for the OS disk on Multi-session VMs as Standard HDD will run into IOPS limits when multiple users are working on a single VM.
    Also, at that scale of users, you will be concerned over network (egress) or on-prem dependencies. Depending on the profile requirements, your best bet is using ANF, but AzFiles can work with this number of users with some effort/planning to balance IOPS and Throughput limits on storage accounts.

    We have remote desktop sizing guidance that you should check out along with the below Service Limits: Azure subscription limits and quotas - Azure Resource Manager | Microsoft Docs

    AVD Service Limits

    Azure subscription limits and quotas - Azure Resource Manager | Microsoft Learn

    https://docs.microsoft.com/en-us/azure/architecture/example-scenario/wvd/windows-virtual-desktop#azure-limitations

    You can currently deploy 399 VMs per Azure Virtual Desktop ARM template deployment without Availability Sets, or 200 VMs per Availability Set. You can increase the number of VMs per deployment by switching off Availability Sets in either the ARM template or the Azure portal host pool enrollment.

    Subscription, Service, Resource Group Limits

    Resources per resource group, per resource type: 800 - Some resource types can exceed the 800 limit. See Resources not limited to 800 instances per resource group.

    ARM LimitsRequest limits and throttling - Azure Resource Manager | Microsoft Learn

    Azure Resource Manager (ARM) subscription API throttling limits don't allow more than 600 Azure VM reboots per hour via the Azure portal. You can reboot all your machines at once via the operating system, which doesn't consume any Azure Resource Manager subscription API calls. For more information about counting and troubleshooting throttling limits based on your Azure subscription, see Troubleshoot API throttling errors.

    Image LimitsOverview of Azure Compute Gallery - Azure Virtual Machines | Microsoft Learn

    For non-Virtual Machine Scale Set deployments - For every 20 VMs that you create concurrently, we recommend you keep one replica. For example, if you are creating 120 VMs concurrently using the same image in a region, we suggest you keep at least 6 replicas of your image.

    For Virtual Machine Scale Set deployments - For each scale set you create concurrently, we recommend you keep one replica.

    If this response helps in answering your question, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community
    User's image

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.