Azure Automation PowerShell 7.6 runtime executes 7.6.0-preview.5 despite verified runtime association

A West US cloud job associated with PowerShell 7.6 should run a supported GA build, so keep production scheduling disabled and open an Azure support request for a probable cloud runtime-image or version-reporting discrepancy.

Azure Automation announced PowerShell 7.6 general availability in all public regions in July 2026, and its runbook documentation supports PowerShell 7.6 for cloud and hybrid jobs in all regions, including West US.^1^^2^

7.6.0-preview.5 is not a GA build. PowerShell documentation says preview releases are not officially supported and should not be used for production; the supported 7.6 channel is LTS.^3^

Cloud-job resolution

There is no documented customer setting for choosing a PowerShell patch build such as 7.6.6 in an Azure Automation cloud sandbox. A Runtime Environment selects the language version (7.6), while its update operations apply to packages/modules. The runtime language and runtime version are immutable.^4^

Because the runbook, Runtime Environment, and completed job all resolve to PowerShell-76, and an isolated probe reproduces the result, further reassociation or module changes would not address the observed engine build. Microsoft must confirm and, if necessary, correct the image assigned to that regional cloud-job runtime.

Open an Azure support request under Azure Automation → Runbooks/Jobs, and include:

1. Automation account name and Azure region (West US).
2. Runtime Environment resource name and ARM resource ID.
3. Runbook name and resource ID.
4. At least two affected Job IDs, with UTC start times.
5. The ARM responses showing:
   • the published runbook’s Runtime Environment;
   • runtime.version equal to 7.6;
   • the completed job’s jobRuntimeEnvironment.runtimeEnvironmentName.
6. The complete output of this minimal probe:

[pscustomobject]@{
    PSVersion       = $PSVersionTable.PSVersion.ToString()
    PSEdition       = $PSVersionTable.PSEdition
    PrereleaseLabel = $PSVersionTable.PSVersion.PreReleaseLabel
    Framework       = [Runtime.InteropServices.RuntimeInformation]::FrameworkDescription
    OS              = [Runtime.InteropServices.RuntimeInformation]::OSDescription
    Architecture    = [Runtime.InteropServices.RuntimeInformation]::OSArchitecture
    PSHome          = $PSHOME
} | Format-List

7. A request for Microsoft to identify the backend worker image/build used by those jobs and confirm whether 7.6.0-preview.5 is being executed or merely reported incorrectly.

Microsoft’s Automation support checklist specifically requests the affected Job ID, a script sample, and the job’s All Logs output.^5^ Provide resource and job identifiers only through the private support channel.

A concise impact statement for the case:

PowerShell 7.6 is documented as GA for cloud jobs in all public regions, but reproducible West US cloud jobs execute or report 7.6.0-preview.5. Runtime association has been verified at the runbook, Runtime Environment, and completed-job levels. No packages, authentication, networking, or Storage operations are involved. Production enablement is blocked because preview PowerShell builds are unsupported.

Controlled GA workaround

If execution cannot wait for the cloud image to be corrected, use an extension-based Hybrid Runbook Worker. This is not a cloud-job fix, but it lets you install and control the GA PowerShell 7.6 executable yourself.

For a Windows Hybrid Worker:

1. Use extension-based Hybrid Worker version 1.3.63 or later.
2. Install a supported GA PowerShell 7.6 build on the worker.
3. Create the system environment variable:
   • Name: powershell_7_6_path
   • Value: full path to the GA pwsh.exe
4. Restart the Hybrid Runbook Worker.
5. Start the runbook on that worker group and rerun the version probe.

These are the documented PowerShell 7.6 Hybrid Worker requirements.^6^

Do not treat switching to PowerShell 7.4 as obtaining GA PowerShell 7.6; it is only a separate supported runtime fallback.

References

1. What's New in Azure Automation | Microsoft Learn
2. Azure Automation Runbook Types | Microsoft Learn
3. PowerShell Support Lifecycle
4. Manage Runtime environment and associated runbooks
5. Data to collect when opening a case for Microsoft Azure Automation
6. Run Automation runbooks on a Hybrid Runbook Worker