Merge pull request #298854 from cephalin/overview2

outdated runtimes

Author: v-ccolin

articles/app-service/configure-language-dotnet-framework.md

@@ -37,6 +37,8 @@ For CLR 2 runtime versions (.NET Framework 3.5 and below):
 ls "D:\Program Files (x86)\Reference Assemblies\Microsoft\Framework"
 ```
 
+If the runtime your application requires isn't supported, you can deploy it with a custom container.
+
 ## Show current .NET Framework runtime version
 
 Run the following command in the [Cloud Shell](https://shell.azure.com):
@@ -55,6 +57,8 @@ By default, App Service uses the latest supported .NET Framework version to run
 az webapp config set --resource-group <resource-group-name> --name <app-name> --net-framework-version v2.0
 ```
 
+[!INCLUDE [outdated-runtimes](includes/outdated-runtimes.md)]
+
 ## Access environment variables
 
 In App Service, you can [set app settings](configure-common.md#configure-app-settings) and connection strings outside of your app code. Then you can access them in any class using the standard ASP.NET pattern:

articles/app-service/configure-language-dotnetcore.md

@@ -67,6 +67,8 @@ az webapp config set --name <app-name> --resource-group <resource-group-name> --
 
 ::: zone-end
 
+[!INCLUDE [outdated-runtimes](includes/outdated-runtimes.md)]
+
 ::: zone pivot="platform-linux"
 
 ## Customize build automation

articles/app-service/configure-language-java-deploy-run.md

@@ -91,6 +91,8 @@ az webapp list-runtimes --os windows | grep java
 
 For more information on version support, see [App Service language runtime support policy](language-support-policy.md).
 
+[!INCLUDE [outdated-runtimes](includes/outdated-runtimes.md)]
+
 ## Deploying your app
 
 ### Build tools

articles/app-service/configure-language-nodejs.md

@@ -86,6 +86,8 @@ This setting specifies the Node.js version to use, both at runtime and during au
 
 ::: zone-end
 
+[!INCLUDE [outdated-runtimes](includes/outdated-runtimes.md)]
+
 ## Get port number
 
 Your Node.js app needs to listen to the right port to receive incoming requests.

articles/app-service/configure-language-php.md

@@ -87,6 +87,8 @@ az webapp config set --resource-group <resource-group-name> --name <app-name> --
 
 ::: zone-end
 
+[!INCLUDE [outdated-runtimes](includes/outdated-runtimes.md)]
+
 ::: zone pivot="platform-windows"  
 
 ## Run Composer

articles/app-service/configure-language-python.md

@@ -64,8 +64,7 @@ You can use either the [Azure portal](https://portal.azure.com) or the Azure CLI
 
 You can run an unsupported version of Python by building your own container image instead. For more information, see [use a custom Docker image](tutorial-custom-container.md?pivots=container-linux).
 
-<!-- <a> element here to preserve external links-->
-<a name="access-environment-variables"></a>
+[!INCLUDE [outdated-runtimes](includes/outdated-runtimes.md)]
 
 ## Customize build automation
 > [!NOTE]
@@ -354,6 +353,9 @@ App Service ignores any errors that occur when processing a custom startup comma
     python3.7 -m aiohttp.web -H localhost -P 8080 package.module:init_func
     ```
 
+<!-- <a> element here to preserve external links-->
+<a name="access-environment-variables"></a>
+
 ## Access app settings as environment variables
 
 App settings are values stored in the cloud specifically for your app, as described in [Configure app settings](configure-common.md#configure-app-settings). These settings are available to your app code as environment variables and accessed using the standard [os.environ](https://docs.python.org/3/library/os.html#os.environ) pattern.

articles/app-service/includes/outdated-runtimes.md

@@ -0,0 +1,15 @@
+---
+author: cephalin
+ms.service: azure-app-service
+ms.topic: include
+ms.date: 04/25/2025
+ms.author: cephalin
+---
+
+## What happens to outdated runtimes in App Service?
+
+Outdated runtimes are deprecated by the maintaining organization or found to have significant vulnerabilities. Accordingly, they're removed from the create and configure pages in the portal. When an outdated runtime is hidden from the portal, any app that's still using that runtime continues to run. 
+
+If you want to create an app with an outdated runtime version that's no longer shown on the portal, use the Azure CLI, ARM template, or Bicep. These deployment alternatives let you create deprecated runtimes that have been removed in the portal, but are still being supported.
+
+If a runtime is fully removed from the App Service platform, your Azure subscription owner receives an email notice before the removal.