PowerShell 7.1 support in Azure Functions

[stefanushinardi]

Unless there are critical fixes in the release, we currently do not plan to support PowerShell 7.1 as it is not an LTS release.

Please let us know if you have concern about this.

[kilasuit]

Other than it not being an LTS is there any other reason why you aren't planning on supporting it?

Many in the PowerShell world will be looking to Functions to run the latest supported, non preview, version where possible, i.e 7.1 when that releases

[EwertonJordao]

I Agree with @kilasuit.

I know we have an opportunity to implement Custom Handlers for languages without support but if we have this without the need to implement a local server (without serverless way). If we can choose that in the configuration or in development time it's a good way.

[joeskeen]

If PowerShell 7.1 support is not planned for Azure Functions, can we at least make it possible to use the PSNullConditionalOperators experimental feature in 7.0? I've spent an hour trying to figure out why my code will run locally but not in Azure Functions, only to realize that it's behind a feature flag which cannot be changed (When I try Enable-ExperimentalFeature PSNullConditionalOperators I get access denied)

@stefanushinardi thoughts?

[AnatoliB]

We are currently thinking about enabling PowerShell 7.2 early, while it is still in preview. PowerShell 7.2 will become LTS, so we definitely will support it (as opposed to 7.1, which will reach end-of-life in about one year). If you could use PowerShell 7.2 (preview) in Functions soon, would you still have a strong reason to use 7.1 instead?

This is to track the Enable-ExperimentalFeature problem: #579.

[Ayanmullick]

I would like to use the -UseNewRunspace parameter for the ForEach-Object cmdlet in AzFunctions. Currently it doesn't work.