在Runbook中执行Invoke-AzureRmVMRunCommand时Output字段无返回

I’ve run into this exact issue before—when Invoke-AzureRmVMRunCommand works perfectly in a local PowerShell terminal but returns empty Output in an Azure Automation Runbook. Let’s break down the most common causes and fixes:

1. Your Script Is Using the Wrong Output Cmdlet #

Local PowerShell is pretty forgiving with Write-Host, but in the Automation Runbook environment, Write-Host sends output directly to the console (which doesn’t get captured by Invoke-AzureRmVMRunCommand). Instead, you need to use Write-Output in your validation script to ensure output gets passed to the command’s return object.

For example, replace:

Write-Host "Validation passed: $result"

With:

Write-Output "Validation passed: $result"

2. You’re Not Accessing the Correct Part of the Return Object #

The structure of the response from Invoke-AzureRmVMRunCommand can behave differently in Runbooks compared to local PowerShell. The actual script output isn’t stored directly in $ValidationResult.Output—you need to dig into the Value property of the response object.

Update your Runbook code to explicitly fetch the output like this:

$ValidationResult = Invoke-AzureRmVMRunCommand -ResourceGroupName $VM.ResourceGroupName -VMName $VM.Name -CommandId "RunPowerShellScript" -ScriptPath $ValidationScript

# Extract the script output from the response
$scriptOutput = $ValidationResult.Value[0].Output

# If the output is an array, format it into a readable string
$formattedOutput = $scriptOutput -join "`n"

# Write the output to the Runbook log (and use it as needed)
Write-Output "Script Execution Result:`n$formattedOutput"

3. Outdated AzureRM Module Version #

Azure Automation accounts sometimes ship with older versions of the AzureRM module, which can have inconsistencies in how run command responses are structured.

• Go to your Azure Automation account > Modules
• Check the version of AzureRM.Compute (the module that includes Invoke-AzureRmVMRunCommand)
• If it’s not the latest compatible version, update it. Alternatively, consider migrating to the Az module (since AzureRM is deprecated) and use Invoke-AzVMRunCommand instead—this is the supported long-term solution.

4. Permissions or Execution Context Issues #

Double-check that the service principal used by your Automation account has the necessary permissions to run commands on the VM:

• The service principal needs the Microsoft.Compute/virtualMachines/runCommand/action permission on the target VM (or its resource group)
• Also, ensure your validation script doesn’t rely on interactive context or resources that aren’t available in the VM’s system PowerShell session (e.g., user-specific profiles, unmounted drives)

5. Check Runbook Job Logs for Clues #

If none of the above fixes work, head to your Runbook’s Jobs tab, select the failed/empty run, and look at the detailed logs. Often, you’ll find hidden errors (like script execution failures) that explain why no output was generated.

内容的提问来源于stack exchange，提问作者Amogh Natu