azurerm_linux_function_app powershell 7.6 not working

Peters, A.A. (Alwin) 0 Reputation points
2026-09-23T07:47:10.8266667+00:00

There has been an message on end of support for Powershell 7.4.

It is stated that this should be updated to Powershell 7.6.

That is possible within the portal, but when using terraform with azurerm_linux_function_app, 7.6 is not supported yet.

Is it clear when this will be available within terraform?

Regards,

Alwin

Azure Functions
Azure Functions

An Azure service that provides an event-driven serverless compute platform.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Tejaswini Billakurthi 760 Reputation points Microsoft External Staff Moderator
    2026-09-23T11:08:05.01+00:00

    Hello @Peters, A.A. (Alwin) ,

    Thank you for reaching out to Microsoft Q & A !

    There are two separate aspects here: Azure Functions platform support and Terraform AzureRM provider support.

    I don’t have a verified release date for PowerShell 7.6 support in azurerm_linux_function_app.

    Microsoft Azure Functions supports PowerShell 7.6 for applicable hosting plans, but whether you can configure 7.6 through azurerm_linux_function_app also depends on the version of the AzureRM Terraform provider you are using.

    If your installed provider rejects:

    powershell_core_version = "7.6"
    

    during Terraform validation, that indicates the provider version you are using does not currently accept that value.

    One important consideration is the hosting plan. If your Function App uses Linux Consumption, Microsoft’s guidance is to migrate to Flex Consumption before upgrading from PowerShell 7.4 to 7.6, rather than only changing the runtime version.

    Microsoft documentation: Azure Functions supported languages

    For the Terraform-specific part, could you provide:

    AzureRM provider version.

    The exact Terraform error and relevant application_stack configuration, with sensitive values removed.

    The Function App hosting plan (Linux Consumption, Flex Consumption, Premium, App Service, etc.).

    With those details, we can determine whether the limitation is coming from the hosting plan/runtime support or from the AzureRM provider schema.

    I would also recommend checking the AzureRM provider changelog for your specific provider version before upgrading or making an out-of-band portal change. If the runtime is changed outside Terraform, review the subsequent terraform plan carefully to see whether Terraform attempts to revert the change.

    Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.