First, awesome repo @matt-FFFFFF ... Found this extremely helpful when learning how to deploy VMSS ala Bicep.

What I've come to realize is the ado pipeline will pick-up an instance/agent before cloud-init has completed the post-deployment installations. I thought about incorporating cloud-init status --wait to ensure the pipeline does not progress until cloud-init completes the post-deployment tasks, but that's pretty messy. Every pipeline would need this noise... And the next stage could pick up a totally different instance/agent (let's say one that has not completed the cloud-init).

While not directly related to this repo (everything works beautifully), have you run into this issue before? Curious what your solution was to this dilemma. Thanks for your contributions!