system AI diagnostic case

Windows 11 25H2 Azure Automation Runbook PowerShell 7 Modules Missing

This diagnostic page addresses the issue where PowerShell 7 modules required by Azure Automation Runbooks are missing or not loading correctly on Windows 11 version 25H2. This problem can disrupt automation workflows and cause runbook failures.

Describe your Windows problem

Read-only diagnostic first. No repair without review.

Symptoms

Azure Automation runbooks fail to import or recognize PowerShell 7 modules
Runbook jobs report module not found errors for PowerShell 7 specific modules
PowerShell 7 environment in Azure Automation does not list installed modules
Runbook execution logs show missing module or import errors

Likely causes

PowerShell 7 runtime is not properly installed or registered on Windows 11 25H2
Azure Automation account lacks required modules imported or updated
Runbook environment configured to use PowerShell 5.1 instead of PowerShell 7
Module dependencies are not published or available in the Automation Account

What FixWin checks

Verify PowerShell 7 installation via 'pwsh.exe' availability and version check
Check Azure Automation Account Modules gallery for required modules presence
Confirm runbook runtime version is set to PowerShell 7 in Azure Portal
Review Automation job logs for detailed module import errors
Ensure modules are imported and published in Azure Automation Account

AI diagnostic workflow

Open Windows Terminal and run 'pwsh -v' to confirm PowerShell 7 is installed and accessible
Log into Azure Portal and navigate to the Automation Account > Modules to verify required modules are imported
Check the runbook properties to ensure the runtime version is set to PowerShell 7 (preview or GA)
Review Automation job logs under Jobs > Details for any module import or missing module errors
If modules are missing, import them from the PowerShell Gallery or upload custom modules manually

Related Windows entities

PowerShell 7 (pwsh.exe) component
The runtime required to execute PowerShell 7 scripts and load associated modules in Azure Automation.
Azure Automation Account Modules package
Stores all imported PowerShell modules accessible to runbooks; missing modules cause runbook failures.
Automation Job Logs log
Provides detailed error messages related to module import failures and runbook execution issues.
Windows Event Viewer - Application Logs log
May contain related error messages if local PowerShell 7 runtime or modules fail to load.
Azure Portal Runbook Runtime Settings component
Defines which PowerShell runtime version the runbook uses, affecting module compatibility.

Repair logic

Diagnose if PowerShell 7 is properly installed and accessible on Windows 11 25H2, verify that the required PowerShell modules are imported and published in the Azure Automation Account, and confirm the runbook runtime is configured to use PowerShell 7. Use Automation job logs and Windows Event Viewer to identify specific module import errors. Re-import missing modules or adjust runbook runtime settings accordingly.

FAQ

Why are my PowerShell 7 modules missing in Azure Automation on Windows 11 25H2?

Modules may be missing if PowerShell 7 runtime isn't installed or registered properly, or if the Automation Account does not have the modules imported and published. Also, runbooks configured to use PowerShell 5.1 won't load PowerShell 7 modules.

How do I check which PowerShell version my Azure Automation runbook is using?

In the Azure Portal, navigate to your Automation Account, select the runbook, and check the runtime version setting to confirm whether it is set to PowerShell 7 or PowerShell 5.1.

Can I manually add missing PowerShell 7 modules to Azure Automation?

Yes, you can import modules from the PowerShell Gallery into your Automation Account or upload custom modules manually to ensure they are available for runbooks.

Fix this Windows problem automatically

Start a private FixWin diagnostic session for: Windows 11 25H2 Azure Automation Runbook PowerShell 7 Modules Missing