@koralski @savyasachisamal Can you take a look at this issue?

I figured out this was an issue with how I was handling parameters and strings into the Invoke-AzureRmVMRunCommand call. It would be really nice if the output actually propagated the error to the console window.

Ok to close this ticket.

@muntaserq So what exactly resolved the issue involving the params for Invoke-AzureRmVMRunCommand?

bump^ @muntaserq

@muntaserq So what exactly resolved the issue involving the params for Invoke-AzureRmVMRunCommand?

In this specific context, I had to build up my $parameters HashTable a little differently.

Instead of doing:

$parameters =  @{"Output" = "This is test output" }

I had to do:

$parameters =  @{"Output" = "`"This is test output`"" }

This was the recommendation I got from an Azure Support Engineer. This seems to only be the case when using on parameter in the script. All that being said, I've since moved over to using the latest stable version of the AzureRm PowerShell modules and all my issues with that module have gone away. I use version 6.13.1 and of course you can find all the versions here: https://github.com/Azure/azure-powershell/releases.

@kaveaa You're welcome. Also make sure that there are no syntax errors in your PowerShell script. I've seen the case when this error returns and there ends up being an error in the actual script. One troubleshooting method is to remote desktop into the target virtual machine and view the status of the Invoke-AzureRmVmRunCommand call. To do that, navigate to C:\Packages\Plugins\Microsoft.CPlat.Core.RunCommandWindows\1.1.0\Status and view the latest run status output.