Thanks for following up, and my sincere apologies about the delay in getting back to you. I unfortunately didn’t see your messages come through and only saw as a result of the GitHub issue you linked this thread in.
I’ve been able to reproduce this behavior, and sure enough it’s a bug as it seems to be searching for the variable name instead of the Azure Account name when attempting to deploy. I’ve raised this issue at the following link for you to track.
I was able to work around this by renaming my variable to match the Azure Account ID exactly and then updating the binding in the step template to match this variable name change. You can get the Azure Account ID in the URL when viewing the account in the web portal. The ID is after the
/accounts/ in the URL as I’ve highlighted below.
We’ve had recent reports of a bug that is very similar (and maybe has the exact same root cause). I can’t confirm at this stage if it’s an exact match, but it may only require upgrading to 2019.7.0 once it’s shipped as that will include the fix to that bug. You can reference that issue here.
I’m going to attempt to reproduce this once again when 2019.7.0 is available and I’ll let you know the outcome.
I’m very sorry again for the lack of communication on my part, and I’ve bookmarked this thread to ensure it won’t happen again.