Troubleshoot Az Module within Logic App Standard

In Logic App Standard, you can use Powershell Code, using the Execute Powershell Script action

If your powershell script depends on Az Module, then the logic app will try to download and install the Az Module within the runtime

In some cases, when the logic app is VNET integrated (has NSG, or routed to Virtual Appliance), or hosted within internal ASE, the logic app will be unable to reach the needed Powershell endpoints, and the download would fail, and the action would fail with below error

This can be seen within the log folder in Kudo site (Path: C:\home\LogFiles\Application\Functions\Function\Powershell), and the error would appear as:

Exception: Failed to install function app dependencies. Error: 'Failed to install function app dependencies. Error: 'The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Unable to save the module 'Az'.'

To troubleshoot this, you need to assure that logic app can reach the needed urls, you can try the simple below steps:

From Kudo console, you can try this curl command:

curl https://cdn.powershellgallery.com/packages/az.accounts.5.1.1.nupkg --output az.accounts.5.1.1.nupkg

It should respond as below:

If there is reachability issue, you would see the below response:

Also, you can test by creating simple workflow, as below:

When you run the HTTP action, it should succeed, however, if you have reachability issue, it would fail as below:

This means logic app cannot reach the needed endpoint, which are clarified in our documentation (Troubleshooting cmdlets - PowerShell | Microsoft Learn)

To resolve this, assure that the NSG, Firewall, or Virtual appliance allows the logic app to reach the mentioned endpoints.,

Another scenario where the Az module installation could fail, is if the storage account capacity is almost utilized, and there is no space available to download the Az module, you can confirm this by only referencing the Az.Accounts module; as this module is small in size. if the Az.Accounts module worked, then the issue is highly likely due to storage capacity