Veeam VBR Integration and Control Characters In Password Unsupported

[mbroaders]

I came across an issue this week where i was updating a Veeam VBR v11 to V12 that had Veeam Backup for Azure integrated. Post v12 update when it was updating the Veeam Backup for Azure appliance it kept failing to update. Looking at the activity logs in Azure i could see that the ARM template used by Veeam was failing due to a password issue. The issue ended up being the local account on the Veeam Backup for Azure used to connect to Veeam VBR had control characters in it which are unsupported in ARM templates.

Changing the password resolved the issue. Would it make sense to restrict control characters from being used in the password for Veeam Backup for Azure to avoid this scenario?

[Vitaliy S.]

Yes, it definitely makes sense to do it. Thanks for the heads up! I will pass this to our QA team.