Yes, there's an internal provisioning for it from the Azure VMSS.

However, that would mean passing back the hostname to the Autoscaler class.

Right now as it's written, the spin_up_worker method doesn't update the class attributes. Following the AWS example that is also the case, where I can see it merely takes the arguments given, such as worker id, and constructs a node with those parameters e.g. hostname etc.

Looking at the supervisor method of the base AutoScaler class, where are the worker IDs kept.
Is it in the class attribute queues ?