Swapping the unhealthy physical node at starting VM
For running VM, "Service healing" will prevents down-time.
On the other hands, for initiation of VM, user have to wait for VM fully starts and user cannot detect the reason why VM starts slowly.
I would propose that Azure automatically retry starting VM on another node in case Azure detect unhealthy node events.
valid suggestion subject to customer upvote