Hi @dkerins thank you for bubbling this up and for opening an issue on the GitHub tracker. This looks like a bug for sure. I left a comment on the issue with details on what might be happening.
But the tl;dr is that the latest Azure plugin v2.0.0 behaves differently when specifying use_azure_cli_auth. For Azure VMs running Packer builds, if possible, I recommend trying to use a managed system identity for auth by removing the use_azure_cli_auth attribute from your configuration or you can downgrade the plugin version to v1.4.5 to use the version of the plugin that was previously bundled into Packer while we work on a fix.