Azure builder doesn't report meaningful error when Azure can't allocate the target VM due to capacity or allocation constraints

[jasonzio]

If the region targeted by Packer is capacity-constrained for the chose SKU, or if the subscription used by Packer has exhausted allocation for that SKU in that region, packer will just timeout while "Waiting for SSH to become available..." instead of issuing a helpful error message.

[paulmey]

Thanks for the suggestion. Can you add some detail on how Packer should detect this situation?
I guess deployment succeeds, because Packer continues to waiting for SSH? Does VM start eventually fail?

[ghost]

This issue has been automatically migrated to hashicorp/packer-plugin-azure#14 because it looks like an issue with that plugin. If you believe this is not an issue with the plugin, please reply to hashicorp/packer-plugin-azure#14.