Feature
Microsoft
Microsoft is retiring the Azure Functions v1 hosting model on Azure Container Apps on 29 September 2027; after that date existing Functions v1 apps on Azure Container Apps stop running and no longer process requests or event-driven triggers, and must be moved to the Functions v2 hosting model (a native Azure Container App with kind=functionapp)
departs 29 Sept 2027
Quick answers
- Is it true that Azure Functions v1 hosting model on Azure Container Apps retires 29 September 2027 — migrate to the v2 hosting model (kind=functionapp)?
- Yes. Microsoft has officially announced it, effective 29 Sept 2027. If you run **Azure Functions on Azure Container Apps** using the original **v1 hosting model**, Microsoft is retiring that hosting model on **29 September 2027**.
- When does it take effect?
- 29 Sept 2027. Verified against the vendor's own announcement.
- What should I use instead?
- Move every affected app to the **Functions v2 hosting model** before 29 September 2027.
What this means for you
If you run **Azure Functions on Azure Container Apps** using the original **v1 hosting model**, Microsoft is retiring that hosting model on **29 September 2027**. This is a hosting-model retirement, not a change to the Functions *programming* model your code targets — but the consequence is blunt: after the date, existing v1 apps on Azure Container Apps **stop running and stop processing requests and event-driven triggers**, so an unmigrated app simply goes dark. It affects the platform configuration your function apps are deployed under, not the function code itself; Microsoft says the standard migration path does not require code changes. The good news is that the replacement is a first-party, like-for-like target — the **v2 hosting model**, a native Azure Container App configured with `kind=functionapp` — and you can reuse your existing container image. The work is re-creating each app under the v2 model and re-applying its configuration, which is real but bounded, and there is a migration assistant to do most of it.
Where to go
Move every affected app to the **Functions v2 hosting model** before 29 September 2027. The v2 model is a native Azure Container App configured with `kind=functionapp`, and you can **reuse your existing container image** — the standard path requires no function-code changes. Microsoft provides an "Azure Functions on Azure Container Apps v1 migration assistant" that handles most of the move. To migrate manually: (1) record the v1 app's full configuration — secrets, managed identity, networking, and scaling rules; (2) create a v2 app with `kind=functionapp` and re-apply that configuration; (3) test all triggers, shift production traffic to the v2 app, then decommission the v1 app. Complete migration and production validation well ahead of the retirement date so no event-driven workload is left on the v1 model when it stops processing on 29 September 2027.
- Azure Functions v2 hosting model on Azure Container Apps (native Container App, kind=functionapp) — Microsoft's direct replacement; reuses the existing container image
Microsoft is retiring the Azure Functions v1 hosting model on Azure Container Apps on 29 September 2027. The official retirement notice (published 29 September 2026) is explicit about the consequence: after that date, existing Functions v1 apps on Azure Container Apps stop running and no longer process requests or event-driven triggers.
What this is — and isn’t
This is a hosting-model retirement, not a change to the Functions programming model your code is written against. It applies to how your function apps are deployed on Azure Container Apps (the v1 model), not to the runtime version your function code targets. So the code mostly stays; the deployment moves.
The replacement is first-party and like-for-like: the v2 hosting model, which is a native Azure Container App configured with kind=functionapp. You can reuse your existing container image, and Microsoft says the standard migration path does not require function-code changes.
How to migrate
Microsoft provides an “Azure Functions on Azure Container Apps v1 migration assistant” that handles most of the move. To do it manually:
- Record the v1 app’s configuration — secrets, managed identity, networking, and scaling rules.
- Create a v2 app with
kind=functionappand re-apply that configuration. - Test all triggers, shift production traffic to the v2 app, then decommission the v1 app.
Finish migration and production validation well before 29 September 2027 — an event-driven app left on the v1 model doesn’t degrade gracefully, it stops processing triggers entirely on the retirement date.
Entry changelog
- — last reviewed.
- — Entry created from Microsoft's official Azure retirement notice (Azure Updates id 570800, published 29 September 2026). The Azure Updates page is JavaScript-rendered and does not fetch server-side, so the retirement date (29 September 2027), the affected hosting model, and the migration path (v2 hosting model, native Container App with kind=functionapp, existing image reusable, v1 migration assistant) were verified against Microsoft's server-rendered release-communications API (id 570800). No detect fingerprint: the v1 hosting model is a platform/deployment configuration, not a package, image tag, or literal string a source repository would reliably contain, and the v2 marker kind=functionapp identifies the replacement, which must never be fingerprinted (SOURCING §6).
Put this countdown in your README
Building on Microsoft? 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-v1-hosting-model-container-apps-retirement)Spot an error or a changed date? Tell us and it’s corrected the same night.