SaaS
Microsoft
Microsoft retires Azure App Service on Azure Stack Hub on 30 September 2029; new installations and all new releases, features and enhancements stopped on 30 September 2026, with existing deployments supported until retirement
departs 30 Sept 2029
Quick answers
- Is it true that Azure App Service on Azure Stack Hub retires on 30 September 2029 — new installations already blocked since 30 September 2026; migrate to Azure App Service in Azure?
- Yes. Microsoft has officially announced it, effective 30 Sept 2029. If you run web, API, or function apps on Azure App Service on Azure Stack Hub — the on-premises/edge App Service offering for Microsoft's hybrid Azure Stack Hub appliance — the product is being wound down.
- When does it take effect?
- 30 Sept 2029. Verified against the vendor's own announcement.
- What should I use instead?
- Microsoft's direction is to begin planning migration to Azure App Service in Azure (the public-cloud service) now, to continue receiving support, security updates, platform improvements, and new capabilities.
What this means for you
If you run web, API, or function apps on Azure App Service on Azure Stack Hub — the on-premises/edge App Service offering for Microsoft's hybrid Azure Stack Hub appliance — the product is being wound down. The hard retirement is 30 September 2029, but the clock already started: as of 30 September 2026, new installations are no longer supported and Microsoft is shipping no new product releases, features, or enhancements for it. Existing supported deployments can keep running and can upgrade to the latest available release until retirement, so this is not an imminent outage — but the platform is now frozen, and any team planning new App Service capacity on Stack Hub has already lost the ability to stand it up.
Where to go
Microsoft's direction is to begin planning migration to Azure App Service in Azure (the public-cloud service) now, to continue receiving support, security updates, platform improvements, and new capabilities. For workloads that must remain on-premises or at the edge, that migration is a larger architectural decision than a lift-and-shift — evaluate Azure Arc-enabled options and container-based hosting as part of the plan — so the three-year runway to 30 September 2029 is there to be used, not banked. In the meantime you can keep existing Stack Hub deployments running and upgrade them to the latest available release.
- Azure App Service in Azure (public cloud) — Microsoft's named migration target for continued support and updates
Microsoft is retiring the on-premises edition of its App Service platform. Per Microsoft’s official Azure release-communications notice, Azure App Service on Azure Stack Hub will be retired on 30 September 2029 — and the wind-down milestone that matters right now has already passed.
Two dates, and the first is already here
- 30 September 2026 — platform frozen. As of this date, new installations are no longer supported, and Microsoft is making no new product releases, features, or enhancements for App Service on Azure Stack Hub. Existing supported deployments can continue to run and can upgrade to the latest available release.
- 30 September 2029 — full retirement. On this date App Service on Azure Stack Hub reaches end of support entirely.
The practical consequence of the first date: if you were planning to deploy new App Service capacity onto Azure Stack Hub, that option is already gone. What remains is running and maintaining what you already have, on a platform that will no longer gain features.
What to do
Microsoft’s guidance is to begin planning migration to Azure App Service in Azure — the public-cloud service — now, so that you continue to receive support, security updates, platform improvements, and new capabilities.
For workloads that live on Azure Stack Hub specifically because they must stay on-premises or at the edge, this is more than a lift-and-shift: moving to public-cloud App Service changes where the workload runs, so evaluate Arc-enabled and container-based hosting options as part of the migration. The three-year runway to 30 September 2029 exists to absorb that work — but existing deployments keep running and upgrading in the meantime.
Entry changelog
- — last reviewed.
- — Entry created from Microsoft's Azure release-communications notice (id 568178, published 2026-10-06): Azure App Service on Azure Stack Hub retires 30 September 2029; new installations unsupported and no new releases/features/enhancements as of 30 September 2026; existing supported deployments run and upgrade until retirement; migrate to Azure App Service in Azure. sunsetDate set to 2029-09-30 (the retirement date). No detect: fingerprint — this is a hosting-platform retirement, not a repository-level dependency.
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-app-service-azure-stack-hub-retirement)Spot an error or a changed date? Tell us and it’s corrected the same night.