Runtime
Microsoft Azure
Microsoft ends support for the PowerShell 7.4 runtime on Azure Functions on 10 November 2026; function apps keep running but stop receiving security patches, updates, and customer support, and Microsoft directs developers to upgrade to PowerShell 7.6
departs 10 Nov 2026
Quick answers
- Is it true that Azure Functions ends support for PowerShell 7.4 on 10 November 2026?
- Yes. Microsoft Azure has officially announced it, effective 10 Nov 2026. If you run PowerShell function apps on Azure Functions pinned to the PowerShell 7.4 runtime, Microsoft says support for PowerShell 7.4 ends on 10 November 2026.
- When does it take effect?
- 10 Nov 2026. Verified against the vendor's own announcement.
- What should I use instead?
- Microsoft's required action is to upgrade affected function apps to PowerShell 7.6 before 10 November 2026.
What this means for you
If you run PowerShell function apps on Azure Functions pinned to the PowerShell 7.4 runtime, Microsoft says support for PowerShell 7.4 ends on 10 November 2026. This is the Azure Functions runtime end-of-support, not the end of PowerShell 7.4 as a language. Your function apps "will continue to run, but security patches and updates will no longer be provided and customer support for PowerShell 7.4 will be discontinued." In practice a running app is not switched off on the date, but the platform stops patching the PowerShell 7.4 runtime underneath it, so you accumulate unpatched runtime CVEs, lose Microsoft support for any 7.4-specific issue, and — in Microsoft's words — running on an unsupported runtime "may lead to issues and degraded performance." This is distinct from the separate Azure Automation retirement of PowerShell 7.1/7.2 runbook runtimes (30 September 2026): different product (Functions, not Automation) and a different, later date.
Where to go
Microsoft's required action is to upgrade affected function apps to PowerShell 7.6 before 10 November 2026. Inventory every Azure Functions app whose stack is set to the PowerShell 7.4 runtime, test it against PowerShell 7.6 in a staging slot, and roll the change out via a deployment slot swap so you can fall back if a cmdlet or module behaves differently. One platform gotcha to plan for: if your app is on a Linux Consumption plan, Microsoft says you must first move it to the Flex Consumption plan before you can upgrade to PowerShell 7.6 — so budget for a hosting-plan migration, not just a runtime version bump. Watch for modules that pin to older PowerShell behaviour and for any script relying on 7.4-specific defaults.
- PowerShell 7.6 on Azure Functions — Microsoft's named upgrade target (Linux Consumption apps must move to the Flex Consumption plan first)
Microsoft is retiring another Azure runtime version. In an Azure Updates retirement notice, Microsoft says that support for PowerShell 7.4 on Azure Functions ends on 10 November 2026, and directs developers to transition to PowerShell 7.6.
This is an end-of-support for the runtime, not a hard shutoff. Microsoft is explicit that affected apps keep executing: your function apps “will continue to run, but security patches and updates will no longer be provided and customer support for PowerShell 7.4 will be discontinued.” The catch is what that leaves behind — a production runtime that no longer gets security fixes. Microsoft warns that running function apps on an unsupported runtime “may lead to issues and degraded performance.”
Don’t confuse this with the Azure Automation retirement
Azure has two PowerShell retirements in flight, and they are different things. Azure Automation is retiring the PowerShell 7.1 and 7.2 runbook runtimes on 30 September 2026. Azure Functions is retiring PowerShell 7.4 on 10 November 2026. Different product, different versions, different date — check which one actually applies to your workload before you plan the upgrade.
What to do
Microsoft’s required action is to upgrade to PowerShell 7.6 before 10 November 2026. Find every Azure Functions app set to the PowerShell 7.4 stack, test it against 7.6 in a staging slot, and swap it in so you can roll back if a module or cmdlet misbehaves.
One hosting-plan gotcha to budget for: if your app is on a Linux Consumption plan, Microsoft says you must first move it to the Flex Consumption plan before you can upgrade to PowerShell 7.6. For those apps this is a two-step migration — change the plan, then the runtime — not a single version bump, so give it more runway than a straight upgrade.
Entry changelog
- — last reviewed.
- — Entry created from Microsoft's official Azure Updates retirement notice (id 572770, published 23 September 2026), verified against the Microsoft release-communications API (microsoft.com/releasecommunications/api/v2/azure/572770), which returns product "Azure Functions" and the text "Support for PowerShell 7.4 will end on November 10, 2026, please transition to PowerShell 7.6." The Azure Updates page itself is JS-rendered, so the API is the machine-readable primary source. Date 10 November 2026, the PowerShell 7.6 upgrade target, and the Linux-Consumption→Flex-Consumption prerequisite are all quoted directly from Microsoft, not inferred. No detect: fingerprint — the Azure Functions PowerShell runtime version lives in platform configuration (host settings), not in a repository dependency, so any package-level match would false-positive on every PowerShell 7.4 codebase regardless of where it runs.
Put this countdown in your README
Building on Microsoft Azure? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/azure-functions-powershell-7-4-end-of-support)Spot an error or a changed date? Tell us and it’s corrected the same night.