Automation Runbook Logging Differences

Question

Automation Runbook Logging Differences

Erin Dempster 21

After converting Azure Automation runbooks from PowerShell 5.1 to 7.4, we are seeing some issues in the output logging in Azure Automation. We're getting a lot of gibberish when we run the runbook on a Windows 11 VM used as a Hybrid worker. However, when using the built-in Azure "Sandbox" worker, it's logging as expected. Below are examples of running a short test in each worker type.

What configuration changes are needed on the Windows 11 VM, so we get the expected logging output, not the gibberish?

The function/cmdlet used is not important. I intentionally used an invalid function to generate the error output.

Expected output - as seen in Test Panel with Azure "Sandbox" Worker

Get-KeyVault: 
Line |
   4 |  Get-KeyVault
     |  ~~~~~~~~~~~~
     | The term 'Get-KeyVault' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Current output from Hybrid Worker VM

[0mGet-KeyVault: [0mC:\ProgramData\Microsoft\System Center\Orchestrator\7.2\SMA\Sandboxes\e4kxtt5m.gvu\Temp\jprfahrf.ehk\b6b2393d-9ab4-4ea0-8e1d-377553d8ed92.ps1:4[0m
[0m[0m[36;1mLine |[0m
[0m[0m[36;1m[36;1m   4 | [0m [36;1mGet-KeyVault[0m
[0m[0m[36;1m[36;1m[0m[36;1m[0m[36;1m     | [0m ~~~~~~~~~~~~[0m
[0m[0m[36;1m[36;1m[0m[36;1m[0m[36;1m[0m[0m[36;1m     | [0mThe term 'Get-KeyVault' is not recognized as a name of a cmdlet, function, script file, or executable program.[0m
[0m[0m[36;1m[36;1m[0m[36;1m[0m[36;1m[0m[0m[36;1m[0m[36;1m     | [0mCheck the spelling of the name, or if a path was included, verify that the path is correct and try again.[0m

Siva shunmugam Nadessin 3,025 Reputation points Microsoft External Staff Moderator

2025-11-17T22:27:05.1233333+00:00
Hey Erin Dempster

This likely boils down to configuration changes needed on your Hybrid Worker.

Here's what you can try:

Check Module Imports: Ensure that all required modules are imported correctly into Azure Automation. Sometimes, modules can get outdated or not imported at all, causing unexpected behavior. You might want to add an explicit import-module statement at the beginning of your runbook.

Verify Module Versions: The version of the modules you are using should be up-to-date and compatible with PowerShell 7.4. You can refer to the automation runbook gallery to check the versions.

Review Hybrid Worker Configurations: Make sure your Windows 11 VM is configured properly as a Hybrid Worker. You might want to refer to the Hybrid Runbook Worker troubleshooting guide for more specific settings and checks that might need adjusting.

Logging Configuration: Double-check the logging configuration on your runbook and the execution environment settings. You can find more about logging outputs at Retrieve runbook output and messages.

Check Execution Environment: If the runbook works well with Azure's Sandbox worker but not on your Hybrid Worker, investigate further into the execution environment. Some cmdlets may require a specific context that may not be present in the Hybrid Worker configuration.

Here's a runbook example that applies import-module at the start:

Import-Module AzureRM

I hope this helps you get the expected logging output without the gibberish! If you still face issues, here are some follow-up questions that would help clarify your situation further:

What specific modules are you referencing in your runbook, and are they installed in your Azure Automation account?

Have you made any other recent changes to the configuration of your Hybrid Worker?

Can you verify if other simple PowerShell commands log output correctly on the Hybrid Worker?

Feel free to share any additional details if you're still having trouble, and I'll do my best to assist further!

References:

Troubleshoot Runbook Execution Issues in Azure Automation

Hybrid Runbook Worker

Retrieve Runbook Output and Messages

Modules in PowerShell Gallery

Azure Automation Runbooks

Hybrid Runbook Worker Troubleshooting Guide
Suchitra Suregaunkar 3,540 Reputation points Microsoft External Staff Moderator

2025-11-18T06:00:18.16+00:00

Hello Erin Dempster

Could you please let us know if the solution shared in the comment addressed your query. If you have any other questions or need further support, please feel free to contact us.

Thanks,

Suchitra.
Erin Dempster 21 Reputation points

2025-11-18T14:31:47.45+00:00

@Suchitra Suregaunkar This solution didn't help, as the logging in the Automation Account is still showing unprintable characters. The hybrid worker is a fresh Azure VM running Windows 11. The agent version is 1.3.63. @Siva shunmugam Nadessin reached out for more information, and I'm awaiting any response.

Is there documentation available to help with "Check Execution Environment" that illustrates how the Sandbox worker is configured for logging, so I can implement those settings in the Hybrid worker? This would be extremely helpful for me.

I have eliminated the VM and specific OS, as I can replicate the unprintable characters on a Windows Server 2022 Azure VM running PowerShell 7.
Suchitra Suregaunkar 3,540 Reputation points Microsoft External Staff Moderator

2025-11-19T06:22:48.1966667+00:00
Hello Erin Dempster

PowerShell 7.4 formats errors with ANSI/VT sequences. The Azure sandbox host normalizes styled output before persisting logs, but the Hybrid Worker host can capture the raw ANSI sequences, which appear as unprintable characters.
Behavior differences are due to host rendering, not command correctness.

There is no document on the sandbox worker sets X/Y/Z logging flags to strip ANSI.

The supported, documented path to achieve sandbox‑like error logs on Hybrid Workers is to configure PowerShell’s rendering ($PSStyle.OutputRendering='PlainText') and to run PS 7.4 on a supported (extension‑based) Hybrid Worker.

As a workaround on the Hybrid Worker, set PowerShell rendering to plain text so error output is stored without styling:

$PSStyle.OutputRendering = [System.Management.Automation.OutputRendering]::PlainText $env:__SuppressAnsiEscapeSequences = '1' # optional safeguard

This is supported by PowerShell’s documented $PSStyle controls.

Reference documents:

https://learn.microsoft.com/en-us/dotnet/api/system.management.automation.psstyle.outputrendering?view=powershellsdk-7.4.0

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_ansi_terminals?view=powershell-7.5

Environment prerequisites: Your Hybrid Worker is extension‑based (V2) and on Windows Hybrid Worker extension ≥ 1.3.63, PS 7.4 runbooks are supported only on extension‑based workers.

Reference: https://learn.microsoft.com/en-us/azure/automation/automation-hrw-run-runbooks?tabs=sa-mi

So, could you confirm whether your Hybrid Runbook Workers are all extension‑based (V2) and running the Windows Hybrid Worker extension version 1.3.63 or later? Because PowerShell 7.4 runbooks are supported only on extension‑based workers.

Thanks,

Suchitra.
Erin Dempster 21 Reputation points

2025-11-20T20:00:26.88+00:00

The latest version of the agent is installed and PS 7.4.13 is running on the VM. I'm still getting ANSI characters when errors are logged in the runbook running on the VM. Even with the __SuppressAnsiEscapeSequences = '1' defined in the system environment variables on the VM, it doesn't seem to be effective when the runbook executes. I already have the OutputRendering set to PlainText which helps for everything but warnings/errors being thrown by any and all commands.

I'll keep tinkering with this.
Suchitra Suregaunkar 3,540 Reputation points Microsoft External Staff Moderator

2025-11-21T04:42:32.5466667+00:00
Hello Erin Dempster As the warnings and errors still show ANSI means those streams are bypassing the general renderer. This is a known behavior in PowerShell 7.x: error and warning formatting uses its own styling data ($PSStyle.Formatting.Error, $PSStyle.Formatting.Warning) and sometimes ignores the global rendering setting when the host captures raw strings.

To Override error/warning formatting in the runbook or profile add this at the top of your runbook or in the Hybrid Worker’s profile.ps1 as this clears the style tokens for those streams.

$PSStyle.Formatting.Error = '' $PSStyle.Formatting.Warning = ''

Sanitize messages before writing: If you use Write-Error or Write-Warning, wrap them, This ensures even terminating errors are logged cleanly.

function Remove-Ansi($text) { $text -replace "`e\[[0-9;]*[A-Za-z]", '' } trap { $plain = ($_ | Out-String) | Remove-Ansi Write-Output $plain continue }

Validate host profile loading: Hybrid Worker runs under LocalSystem. Confirm your changes are in:

C:\Program Files\PowerShell\7\profile.ps1

Can you confirm the Hybrid Worker extension version (≥ 1.3.63) and that it’s extension-based (V2) only?

Thanks,

Suchitra.

1 answer

Your answer

Suchitra Suregaunkar 3,540 Reputation points Microsoft External Staff Moderator

2025-11-18T06:00:18.16+00:00

Hello Erin Dempster

Could you please let us know if the solution shared in the comment addressed your query. If you have any other questions or need further support, please feel free to contact us.

Thanks,

Suchitra.
Erin Dempster 21 Reputation points

2025-11-18T14:31:47.45+00:00

@Suchitra Suregaunkar This solution didn't help, as the logging in the Automation Account is still showing unprintable characters. The hybrid worker is a fresh Azure VM running Windows 11. The agent version is 1.3.63. @Siva shunmugam Nadessin reached out for more information, and I'm awaiting any response.

Is there documentation available to help with "Check Execution Environment" that illustrates how the Sandbox worker is configured for logging, so I can implement those settings in the Hybrid worker? This would be extremely helpful for me.

I have eliminated the VM and specific OS, as I can replicate the unprintable characters on a Windows Server 2022 Azure VM running PowerShell 7.
Suchitra Suregaunkar 3,540 Reputation points Microsoft External Staff Moderator

2025-11-19T06:22:48.1966667+00:00

Hello Erin Dempster

PowerShell 7.4 formats errors with ANSI/VT sequences. The Azure sandbox host normalizes styled output before persisting logs, but the Hybrid Worker host can capture the raw ANSI sequences, which appear as unprintable characters.
Behavior differences are due to host rendering, not command correctness.

There is no document on the sandbox worker sets X/Y/Z logging flags to strip ANSI.

The supported, documented path to achieve sandbox‑like error logs on Hybrid Workers is to configure PowerShell’s rendering ($PSStyle.OutputRendering='PlainText') and to run PS 7.4 on a supported (extension‑based) Hybrid Worker.

As a workaround on the Hybrid Worker, set PowerShell rendering to plain text so error output is stored without styling:

$PSStyle.OutputRendering = [System.Management.Automation.OutputRendering]::PlainText $env:__SuppressAnsiEscapeSequences = '1' # optional safeguard

This is supported by PowerShell’s documented $PSStyle controls.

Reference documents:

https://learn.microsoft.com/en-us/dotnet/api/system.management.automation.psstyle.outputrendering?view=powershellsdk-7.4.0

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_ansi_terminals?view=powershell-7.5

Environment prerequisites: Your Hybrid Worker is extension‑based (V2) and on Windows Hybrid Worker extension ≥ 1.3.63, PS 7.4 runbooks are supported only on extension‑based workers.

Reference: https://learn.microsoft.com/en-us/azure/automation/automation-hrw-run-runbooks?tabs=sa-mi

So, could you confirm whether your Hybrid Runbook Workers are all extension‑based (V2) and running the Windows Hybrid Worker extension version 1.3.63 or later? Because PowerShell 7.4 runbooks are supported only on extension‑based workers.

Thanks,

Suchitra.
Erin Dempster 21 Reputation points

2025-11-20T20:00:26.88+00:00

The latest version of the agent is installed and PS 7.4.13 is running on the VM. I'm still getting ANSI characters when errors are logged in the runbook running on the VM. Even with the __SuppressAnsiEscapeSequences = '1' defined in the system environment variables on the VM, it doesn't seem to be effective when the runbook executes. I already have the OutputRendering set to PlainText which helps for everything but warnings/errors being thrown by any and all commands.

I'll keep tinkering with this.
Suchitra Suregaunkar 3,540 Reputation points Microsoft External Staff Moderator

2025-11-21T04:42:32.5466667+00:00

Hello Erin Dempster As the warnings and errors still show ANSI means those streams are bypassing the general renderer. This is a known behavior in PowerShell 7.x: error and warning formatting uses its own styling data ($PSStyle.Formatting.Error, $PSStyle.Formatting.Warning) and sometimes ignores the global rendering setting when the host captures raw strings.

To Override error/warning formatting in the runbook or profile add this at the top of your runbook or in the Hybrid Worker’s profile.ps1 as this clears the style tokens for those streams.

$PSStyle.Formatting.Error = '' $PSStyle.Formatting.Warning = ''

Sanitize messages before writing: If you use Write-Error or Write-Warning, wrap them, This ensures even terminating errors are logged cleanly.

function Remove-Ansi($text) { $text -replace "`e\[[0-9;]*[A-Za-z]", '' } trap { $plain = ($_ | Out-String) | Remove-Ansi Write-Output $plain continue }

Validate host profile loading: Hybrid Worker runs under LocalSystem. Confirm your changes are in:

C:\Program Files\PowerShell\7\profile.ps1

Can you confirm the Hybrid Worker extension version (≥ 1.3.63) and that it’s extension-based (V2) only?

Thanks,

Suchitra.

Answer 1

The issue you are experiencing with the logging output on the Windows 11 VM used as a Hybrid worker may be related to the differences in how PowerShell 7.x handles output compared to PowerShell 5.1. In PowerShell 7.x, the output may include ANSI escape sequences for formatting, which can appear as gibberish if the output is not rendered correctly in the environment you're using.

To resolve this issue and achieve the expected logging output, you can try the following configuration changes on the Windows 11 VM:

Disable ANSI Escape Sequences: You can configure your PowerShell session to disable ANSI escape sequences. This can be done by setting the $OutputPreference variable at the beginning of your runbook:
```
   $OutputPreference = "SilentlyContinue"
```
This setting will suppress the output that includes formatting codes.
Explicitly Set Logging Preferences: Ensure that you explicitly set the logging preferences at the start of your runbook as follows:
```
   $VerbosePreference = "Continue"
   $ProgressPreference = "Continue"
```
This will help ensure that the logging behaves as expected.
Check PowerShell Version Compatibility: Ensure that all modules you are using are compatible with PowerShell 7.x, as some modules may behave differently or have known issues when run in this environment.
Review Runbook Code: If your runbook is dependent on specific internal paths or uses features not supported in PowerShell 7.x, consider revising the code to avoid these dependencies.

By implementing these changes, you should be able to achieve logging output similar to what you see in the Azure "Sandbox" worker.

Share via

Automation Runbook Logging Differences

1 answer

Your answer