A company has 1,200 users in Germany and 400 users in South Africa. All applications are SaaS and accessed over the internet. You must minimize interactive latency for users when deploying Azure Virtual Desktop. What should you design?

To minimize interactive latency, deploy Azure Virtual Desktop resources geographically close to your users. Creating separate pooled host pools in Germany West Central for EU users and South Africa North for ZA users directly addresses this by placing compute resources near each user group. Storing user profiles (e.g., FSLogix) in the same region as the host pool further reduces latency for profile loading and saves on data transfer costs. Assigning users by group ensures they connect to the correct regional host pool. A single host pool in West Europe with proximity placement groups for South Africa would still incur significant latency for South African users. A single global host pool in East US, even with Azure Front Door, would introduce high latency for both user groups due to geographical distance. Deploying in North Europe and UAE North would not optimally serve users in Germany or South Africa, as neither region is the closest option.