Azure function - import module error

Sasa 41

HI. I'm having an error "ERROR: Failed to generate proxies for remote module 'azureAD'. The -OutputModule parameter does not resolve to a path, and a user module path cannot be found for the provided name" when running the azure function.

All was worked before and I can't remember that I have done any azure app configuration changes other then importing module in a function profile. Tried to remove that but the same results.

Any help is appreciated.

5 answers

Jaroslaw Raczynski 11 Reputation points

2022-07-11T11:24:29.79+00:00

I had a call with MS about that issue. The MS Engineer advised to change the value in FUNCTION_EXTENSION_VERSION to 3.8.2.0. After the change, the problem was solved.

How to find it : Function App -> Configuration -> find FUNCTION_EXTENSION_VERSION and change value clicking on a pencil icon. After implemented changes, click Save
Please sign in to rate this answer.

2 people found this answer helpful.
vidarak 1 Reputation point

2022-07-11T12:03:39.4+00:00

Thanks. This did indeed solve it for me too.

So to conclude: MS has introduced a bug in function extension 3.10.2 which is the version used with the default "~3" value on that variable. Manually downgrading to 3.8.2.0 works.

FAILING:
2022-07-11T11:57:07.815 [Information] OUTPUT: FUNCTIONS_EXTENSION_VERSION ~3
2022-07-11T11:57:07.815 [Information] OUTPUT: FUNCTIONS_RUNTIME_SCALE_MONIT… 0
2022-07-11T11:57:07.815 [Information] OUTPUT: FUNCTIONS_WORKER_DIRECTORY C:\Program Files (x86)\SiteExtensions\Functions\3.10.2\workers\powershell

WORKING:
2022-07-11T12:02:00.093 [Information] OUTPUT: FUNCTIONS_EXTENSION_VERSION 3.8.2.0
2022-07-11T12:02:00.094 [Information] OUTPUT: FUNCTIONS_RUNTIME_SCALE_MONIT… 0
2022-07-11T12:02:00.094 [Information] OUTPUT: FUNCTIONS_WORKER_DIRECTORY C:\Program Files (x86)\SiteExtensions\Functions\3.8.2.1\workers\powershell

Faizal 1 Reputation point

2022-07-11T12:19:18.373+00:00

Thanks this works.

Sasa 41 Reputation points

2022-07-11T12:57:33.697+00:00

Thanks for sharing the information. Our tenants was fixed today but didn't test it thoroughly so I implemented it just in case
Sign in to comment
Steven R 56 Reputation points

2022-07-11T10:20:45.427+00:00

We are also experiencing the exact same issue since last week. I started a thread on this here: https://learn.microsoft.com/en-us/answers/questions/919927/powershell-function-app-fails-to-import-module.html)

Creating a new function app from scratch works - using the exact same code - for a couple of requests. After an undetermined number of tries, it stops working. Import-Module will always fail with the same error.

Any suggestions on how to solve this would be much appreciated.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment
Dillon Silzer 54,291 Reputation points

2022-07-10T18:00:58.217+00:00
I believe a similar issue was explained below. You need to check your PSModulePath.

($env:PSModulePath).split(";")

https://stackoverflow.com/questions/72916606/custom-powershell-module-fails-to-import-in-azure-funtion

https://github.com/PowerShell/PowerShell/issues/12532
Please sign in to rate this answer.
Sasa 41 Reputation points

2022-07-10T19:18:56.22+00:00

I checked and it looks good.
C:\home\data\ManagedDependencies\2207072209326169428.r C:\home\site\wwwroot\Modules C:\Program Files (x86)\SiteExtensions\Functions\3.10.2\workers\powershell\7\Modules
Sign in to comment
MayankBargali-MSFT 68,471 Reputation points

2022-07-11T03:37:58.743+00:00
**Update: **

@Sasa @vidarak @Steven R
Apology for the inconvenience due to this issue. The workaround is to update the runtime version to 3.8.2.0 by updating the FUNCTION_EXTENSION_VERSION in tha application configuration of your function app if you are running PowerShell function version 7.
The product team will be fixing the issue in the latest runtime.

@Sasa Thanks for reaching out. As per the error it looks like there is issue with the module azureAD. Can you please share your requirements.psd1 file and confirm if you have added the AzureAD in your requirements.psd1. For more details on Dependency management, you can refer to this document.

@{ Az = '1.*' AzureAD = '2.0.2.140' }

In Az module I don't see AzureAD dependencies. In case if you have added the dependencies correctly then please share sample code so I can verify at my end.
Please sign in to rate this answer.
Sasa 41 Reputation points

2022-07-11T07:52:24.947+00:00

It is there and this happens to every module, not just AD. I tried to remove and add it back again but the same error.

MayankBargali-MSFT 68,471 Reputation points

2022-07-11T08:34:05.147+00:00

@Sasa Thanks for the confirmation. Can you confirm the PowerShell runtime version on your function so I can test the same at my end.

Steven R 56 Reputation points

2022-07-11T16:32:38.557+00:00

Thanks for the confirmation! Pinning runtime version to 3.8.2.0 solves my issues at the moment. Hopefully the next version will be able to solve this for good.

MayankBargali-MSFT 68,471 Reputation points

2022-07-13T04:58:11.81+00:00

@Steven R Glad to know that it helped to resolve the issue. Feel free to "Accept as Answer" so it can help other community members facing a similar issue.

Steven R 56 Reputation points

2022-07-25T09:54:53.177+00:00

@MayankBargali-MSFT Do you know an ETA for this fix? The last 3.* release from last week did not solve it. I also don't find any ticket on GitHub that references this problem. Should a ticket be created there?

PluckyLeaf 1 Reputation point

2022-08-01T20:11:12.26+00:00

Hi @MayankBargali-MSFT ,

Following this advice changes the error for us. The function app then complains about legacy protocols: "You are using TLS version 1.0, 1.1 and/or 3DES cipher which are deprecated to improve the security posture of Azure AD. Your TenantID is: []. Please refer to https://go.microsoft.com/fwlink/?linkid=2161187 and conduct needed actions to remediate the issue".

We are authenticating using Connect-AzureAD using a certificate as outlined here with PS7.

Sign-in logs for the service principal show:
Azure AD app authentication library : Family: ADAL Library: ADAL.NET 3.19.7.16602 Platform: .NET FW
Legacy TLS (TLS 1.0, 1.1, 3DES) : True

Any thoughts here please? Does the function runtime 3.8.2.0 not support TLS 1.2+? How can we get this app running again?

Thanks in advance.

Thompson, Janine 6 Reputation points

2022-08-10T14:39:33.857+00:00

Has anyone come up with an answer for this?

I have the same issue with the TLS error. I pinned my runtime to 3.8.2.0 and downgraded Powershell to 7.0, but my AZ Function still will not execute because of the TLS error.

ANAND BABU N 0 Reputation points

2022-08-11T15:49:00.473+00:00

Hi @MayankBargali-MSFT

we are facing this proxy issue where we have updated the runtime version to 3.8.2.0 by updating the FUNCTION_EXTENSION_VERSION in the application configuration of our function app. Powershell core stack is used. But still we are getting the below exception

ERROR: Failed to generate proxies for remote module 'AzureAD'. The -OutputModule parameter does not resolve to a path, and a user module path cannot be found for the provided name. Exception : Type : System.InvalidOperationException Message : Failed to generate proxies for remote module 'AzureAD'. The -OutputModule parameter does not resolve to a path, and a user module path cannot be found for the provided name. InnerException : Type : System.Management.Automation.CmdletInvocationException ErrorRecord : Exception : Type : System.ArgumentException Message : The -OutputModule parameter does not resolve to a path, and a user module path cannot be found for the provided name. TargetSite : Name : ThrowTerminatingError DeclaringType : System.Management.Automation.MshCommandRuntime, System.Management.Automation, Version=7.0.11.0

Please help us on this

MrA Obi 11 Reputation points

2022-08-25T13:13:54.94+00:00

Try adding the following to resolve the TLS 1.2 issue

# Set TLS 1.2 for current PS session [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 # Set TLS 1.2 for Win PS session used for AzureAD Module # (add this after the ' Import-Module AzureAD -UseWindowsPowerShell ' command) $currWinPSCompatSession = Get-PSSession -Name WinPSCompatSession -ErrorAction SilentlyContinue if($currWinPSCompatSession){ Invoke-Command -Session $currWinPSCompatSession -Command { [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 } }

Nate Anderson 6 Reputation points

2022-08-29T17:52:57.33+00:00

Thank you, @MrA Obi ! Your solution worked for me.

PluckyLeaf 1 Reputation point

2022-08-31T08:41:00.347+00:00

This resolved my issue too, thanks.

Thompson, Janine 6 Reputation points

2022-08-31T17:06:01.44+00:00

This appears to have resolved my issue as well!!! THANK YOU!!!
Sign in to comment
vidarak 1 Reputation point

2022-07-11T08:09:48.61+00:00

Having the exact same issue occur with Azure Function App timed functions on 3 separate tenants. Last successful run was on July 6th. Failed runs started on 7th. Seems like MS had made a change that introduced a bug.

FYI: I've made a support request on our Unified Enterprise support plan about this. Will update if there are any solutions from them.
Please sign in to rate this answer.
Sasa 41 Reputation points

2022-07-11T08:28:07.473+00:00

About the same
Sign in to comment