4-WVD-scaling-tool Error: Allocation failed

We have been successfully using this to manage the allocation of our AVD resources in host pools, however recently due to capacity issues at the Microsoft datacentre side in Availability Zone 1 (and 3 on occasion) we are finding that this logic fails to start up the deallocated VM.

How difficult would it be to include some logic to ensure that in the event of allocation in AZ1 fails, it instead launches it can start a VM in an alternate AZ?

Start by locating the 4-WVD-scaling-tool allocation and deallocated-VM startup entry points, then review how failures in Availability Zone 1 are handled. Done means the tool can retry VM startup in an alternate Availability Zone when allocation fails, while preserving the existing host-pool allocation behavior.

Written by the indexing model from the issue text.