Storage Account domain join fails with complex password

[SvenAelterman]

What happened? Provide a clear and concise description of the bug, including deployment details.

This appears to be a regression of #515 or an additional set of special password characters.

The password that caused the issue was structured like this: A)B%C%D-E(F_g[h{i#j&1#2$3]4##|5. (It was purposefully created to detect issues when used in scripts.)

Note: The Azure management VM completes the domain join successfully with the same password.

Please provide the correlation id associated with your error or bug.

5965eb71-e47f-434b-8d98-17cab886e2c4

What was the expected outcome?

Domain join accounts should be able to use passwords of any complexity.

Relevant log output

{"code":"VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'AzureFilesDomainJoin' (publisher 'Microsoft.Compute' and type 'CustomScriptExtension'). Error message: 'Command execution finished, but failed because it returned a non-zero exit code of: '255'. The command had an error output of: 'The user name or password is incorrect\r\n    + CategoryInfo          : AuthenticationError: (:) [], CimException\r\n    + FullyQualifiedErrorId : Win32Error:1326\r\n    + PSComputerName        : localhost\r\n \r\nThe SendConfigurationApply function did not succeed....' For more information, check the instance view by executing Get-AzVmssVm or Get-AzVm (https://aka.ms/GetAzVm). These commands can be executed using CloudShell (https://aka.ms/CloudShell)'. More information on troubleshooting is available at https://aka.ms/VMExtensionCSEWindowsTroubleshoot. "}

[danycontre]

@SvenAelterman thanks for you feedback we are reviewing.