Start VM on Connect is enabled on a pooled host pool and its role assignments are verified. During a connection burst, the first VM starts and reaches its session limit, while additional existing VMs are deallocated. Users temporarily see No resources available. Which documented behavior can explain the delay?

✓ Correct answer

• The feature starts at most one additional VM every five minutes after the first host reaches its session limit.

For pooled hosts, Start VM on Connect starts another VM when the first reaches its session limit, with an additional start no more than once every five minutes. A burst can exceed immediately available capacity. Option explanations: A. The feature permanently stops starting VMs after the first host boots.: Further VM starts are supported subject to the documented interval and capacity behavior. B. The feature starts at most one additional VM every five minutes after the first host reaches its session limit.: The documented additional-start interval can temporarily leave a burst of requests without an available session slot. C. The feature creates a new VM for every user and is waiting for those deployments.: Start VM on Connect starts existing VMs; it does not provision one VM per connecting user. D. The feature requires each end user to be Azure subscription Owner.: The verified service permissions, rather than subscription Owner for every user, govern VM start operations. Sources: Configure Start VM on Connect — https://learn.microsoft.com/azure/virtual-desktop/start-virtual-machine-connect

Read the source reference