Az modules not there when starting with core-tools

I had to Save-Module -Path ~\AppData\Roaming\npm\node_modules\azure-functions-core-tools\bin\workers\powershell\Modules\ -Name Az before I could start with local development where interaction with Azure was needed. Maybe add to the docs or have additional install routine?

[Francisco-Gamino]

@bgelens: This issue will be resolved in the next release of the CLI. The problem was that for the local development scenario, we were downloading the function app dependencies to the functionAppRoot\ManagedDependencies. However, whenever there are file changes under the function app root folder, the Process Host gets restarted. Since installing the Az modules takes more than 20 seconds, before completing the installation, the Process Host will get restarted. Then, at app initialization, the PowerShell worker would try to install the dependencies again, and this would repeat over and over again causing the CLI to go into an infinite loop. To fix this, we will be placing the function app dependencies for the local dev scenario at LocalApplicationData\AzureFunctions\FunctionAppName\ManagedDependencies. Please see https://github.com/Azure/azure-functions-powershell-worker/pull/190 for more info. Lastly, please note that this path gets added to PSModulePath, so the function app can find these modules.

We have updated the PowerShell package in the CLI with this fix. Please see for more info https://github.com/Azure/azure-functions-core-tools/pull/1190.

Closing this issue.

Thanks, Francisco

[daxian-dbw]

It’s using Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData, Environment.SpecialFolderOption.DoNotVerify), which will be ~/.local/share on Linux (or Ubuntu, more specifically).