Microsoft ends support for Java 8, 11 and 17 on Azure App Service on 1 September 2027; apps keep running but receive no security updates or customer support, and Microsoft directs customers to upgrade to Java 25

Microsoft is ending support for three long-standing Java versions on Azure App Service. Per Microsoft’s official Azure release-communications notice, on 1 September 2027 support for Java 8, 11 and 17 will end on App Service.

What actually changes on the date

This is not an immediate shutoff. Microsoft is explicit: your apps hosted on App Service will continue to run. What stops is the support behind the runtime:

• No more security updates for the Java 8, 11, and 17 runtimes on App Service.
• No more customer service for those versions — a support case about the runtime is out of scope after the date.

So the risk is cumulative, not instantaneous: an app left on Java 8/11/17 keeps serving traffic, but every Java security fix released after 1 September 2027 is one your platform no longer receives.

What to do

Microsoft’s stated required action is to upgrade your App Service app to Java 25 before 1 September 2027. Treat it as a standard major-version JDK migration rather than a config flip:

1. Target Java 25 in a deployment slot, not production, first.
2. Rebuild and test against the new runtime — check Spring Boot / Jakarta EE API compatibility, any libraries doing reflection or reaching into JDK internals, and bytecode/agent tooling, which are the usual breakage points across major Java versions.
3. Confirm the runtime stack setting in App Service offers the exact version you expect, then swap the slot into production.

Starting early matters here precisely because nothing breaks on the date — it is easy to let a working app drift past the deadline and sit on an unpatched runtime.