timetobail

Azure Functions · Forced move · Tracked since October 17, 2026 · Sources checked Oct 17

Time to bail on Azure Functions apps on PowerShell 7.4?

Time to Bail · Boarding pass

FromAzure Functions apps on PowerShell 7.4
ToYour pick

Act. You can stay.

PowerShell 7.4 on Azure Functions loses support November 10, 2026. Move to PowerShell 7.6.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
End of support
Time left
23days
Status
Act

Azure Functions PowerShell 7.4 support ends November 10, 2026

Azure Functions support for PowerShell 7.4 ends on November 10, 2026. Apps keep running, but get no security patches. Microsoft supports PowerShell 7.6 until November 14, 2028.

Email me 7 days before Nov 10

One email with the first steps. Nothing else.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

What to do before November 10

Tick steps as you go. Your progress stays in this browser.

  1. Find apps on PowerShell 7.4

    Check the PowerShell version in each function app's configuration.

  2. Test on PowerShell 7.6

    Run your functions locally or in a staging slot on 7.6.

  3. Switch the version

    Change the app to 7.6. On Linux Consumption, move to Flex Consumption first.

Email me 7 days before Nov 10

One email with the first steps. Nothing else.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

Facts we checked

Facts and their sources
End of supportNovember 10, 2026[1]
VersionPowerShell 7.4 on Azure Functions[1]
After that dateApps still run and can be deployed, but get no security patches, new features or performance fixes[2]
Possible limitMicrosoft may limit these apps, including scaling to 1 instance[2]
Move toPowerShell 7.6, supported until November 14, 2028[1]
Linux Consumption planPowerShell 7.4 is the last version there; migrate to Flex Consumption before you move to 7.6[1]
Windows appsaz functionapp config set --powershell-version "<VERSION>"[3]
Apps on PowerShell 7.4Get no security patches after November 10, 2026[1]

Sources

Check it yourself. Every fact above links here.

  1. Supported languages in Azure Functions Microsoft · primary · checked Oct 17
  2. Azure Functions language stack support policy Microsoft · primary · checked Oct 17
  3. Update language stack versions in Azure Functions Microsoft · primary · checked Oct 17
Read the published editorial report

What changed

Time to bail on Azure Functions apps on PowerShell 7.4? Act. You can stay. PowerShell 7.4 on Azure Functions loses support November 10, 2026. Move to PowerShell 7.6.

On our scale this is Act: change a setting or plan before the date. You can stay.

Azure Functions support for PowerShell 7.4 ends on November 10, 2026. Apps keep running, but get no security patches. Microsoft supports PowerShell 7.6 until November 14, 2028.

Here are the facts we checked:

  • End of support: November 10, 2026 (Microsoft)
  • Version: PowerShell 7.4 on Azure Functions (Microsoft)
  • After that date: Apps still run and can be deployed, but get no security patches, new features or performance fixes (Microsoft)
  • Possible limit: Microsoft may limit these apps, including scaling to 1 instance (Microsoft)
  • Move to: PowerShell 7.6, supported until November 14, 2028 (Microsoft)
  • Linux Consumption plan: PowerShell 7.4 is the last version there; migrate to Flex Consumption before you move to 7.6 (Microsoft)
  • Windows apps: az functionapp config set --powershell-version "<VERSION>" (Microsoft)
  • Apps on PowerShell 7.4: Get no security patches after November 10, 2026 (Microsoft)

You can stay on Azure Functions. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Microsoft is the main source for this page. Azure Functions has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Apps on PowerShell 7.4: Get no security patches after November 10, 2026.

The date to remember is November 10, 2026. Make the change before then.

What to do before November 10

  1. Find apps on PowerShell 7.4. Check the PowerShell version in each function app's configuration.
  2. Test on PowerShell 7.6. Run your functions locally or in a staging slot on 7.6.
  3. Switch the version. Change the app to 7.6. On Linux Consumption, move to Flex Consumption first.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Azure Functions apps on PowerShell 7.4 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.