Merge pull request #314849 from ggailey777/thiago-linuxv3note-fixup

[Functions] Linux Consumption v3 notes

Author: v-regandowner

articles/azure-functions/consumption-plan.md

@@ -10,12 +10,10 @@ ms.custom:
 
 # Azure Functions Consumption plan hosting (legacy)
 
-[!INCLUDE [functions-consumption-legacy-banner](../../includes/functions-consumption-legacy-banner.md)]
+[!INCLUDE [functions-linux-consumption-retirement](../../includes/functions-linux-consumption-retirement.md)]
 
 When you use the Consumption plan, the Azure Functions host dynamically adds and removes instances based on the number of incoming events. 
 
-[!INCLUDE [functions-linux-consumption-retirement](../../includes/functions-linux-consumption-retirement.md)]
-
 The Consumption plan automatically scales, even during periods of high load. When you run functions in a Consumption plan, you pay for compute resources only when your functions are running. On a Consumption plan, a function execution times out after a configurable period of time. The Consumption plan is currently the only serverless hosting option that supports Windows.
 
 ## Billing

articles/azure-functions/functions-versions.md

@@ -26,6 +26,8 @@ Azure Functions currently supports only version 4.x of the runtime host.
 > [!IMPORTANT]
 > Versions 2.x and 3.x of the Azure Functions runtime are no longer supported. For more information, see [Retired versions](#retired-versions).
 
+[!INCLUDE [functions-linux-consumption-retirement](../../includes/functions-linux-consumption-retirement.md)]
+
 [Migrate apps from Azure Functions version 3.x to version 4.x](migrate-version-3-version-4.md).
 
 ## Levels of support
@@ -120,9 +122,7 @@ These versions of the Functions runtime reached end of extended support on Decem
 
 Migrate your apps to version 4.x as soon as possible to get full support. For a complete set of language-specific migration instructions, see [Migrate apps to Azure Functions version 4.x](migrate-version-3-version-4.md).
 
-Apps using versions 2.x and 3.x can still be created and deployed from your CI/CD DevOps pipeline, and all existing apps continue to run without breaking changes. But your apps aren't eligible for new features, security patches, and performance optimizations. You can only get related service support after you upgrade your apps to version 4.x.
-
-Versions 2.x and 3.x are no longer supported because .NET Core 3.1, a core dependency, reached end of support. This requirement affects all [languages supported by Azure Functions](supported-languages.md).
+Apps using versions 2.x and 3.x can still be created and deployed from your CI/CD DevOps pipeline, and existing apps continue to run without breaking changes, except for v3 apps on Linux Consumption, which [will stop running after September 30, 2026](#retired-versions). Your apps aren't eligible for new features, security patches, and performance optimizations. You can only get related service support after you upgrade your apps to version 4.x.
 ::: zone pivot="programming-language-csharp"
 ## Locally developed application versions
 

articles/azure-functions/migrate-version-3-version-4.md

@@ -19,11 +19,13 @@ ms.custom:
 
 # Migrate apps from Azure Functions version 3.x to version 4.x 
 
-Azure Functions version 4.x is highly backwards compatible to version 3.x. Most apps should safely migrate to 4.x without requiring significant code changes. For more information about Functions runtime versions, see [Azure Functions runtime versions overview](./functions-versions.md).
-
 > [!IMPORTANT]
 > As of December 13, 2022, function apps running on versions 2.x and 3.x of the Azure Functions runtime have reached the end of extended support. For more information, see [Retired versions](functions-versions.md#retired-versions).
 
+Azure Functions version 4.x is highly backwards compatible to version 3.x. Most apps should safely migrate to 4.x without requiring significant code changes. For more information about Functions runtime versions, see [Azure Functions runtime versions overview](./functions-versions.md).
+
+[!INCLUDE [functions-linux-consumption-retirement](../../includes/functions-linux-consumption-retirement.md)]
+
 This article walks you through the process of safely migrating your function app to run on version 4.x of the Functions runtime. Because project migration instructions are language dependent, make sure to choose your development language from the selector at the top of the article.
 
 ## Identify function apps to migrate

includes/functions-consumption-legacy-banner.md

@@ -7,9 +7,6 @@ ms.author: glenga
 ---
 
 > [!IMPORTANT]  
-> The option to host function apps on Linux in a Consumption plan is being retired. [Migrate your apps to the Flex Consumption plan](../articles/azure-functions/migration/migrate-plan-consumption-to-flex.md) before the retirement date. Apps running on Windows in a Consumption plan aren't currently affected.
+> Function apps still running the [end-of-life v3 runtime](../articles/azure-functions/functions-versions.md#retired-versions) on Linux in a Consumption plan stop running after September 30, 2026. To avoid service disruption, [migrate your app to the v4 runtime](../articles/azure-functions/migrate-version-3-version-4.md).
 >
->| Date | What happens |
->| ------ | ------------- |
->| **September 30, 2025** | No new features or language versions for Linux Consumption. The last supported versions are: .NET 9, Python 3.12, Node.js 22, PowerShell 7.4, and Java 21. The option is removed from the Azure portal, Visual Studio, and Visual Studio Code. You can still manage existing apps by using the Azure CLI and through [resource deployments](../articles/azure-functions/functions-infrastructure-as-code.md). |
->| **September 30, 2028** | Retirement date. No technical support and no new Linux Consumption apps can be created. |
+> The option to host function apps on Linux in a Consumption plan is retiring on 30 September 2028. The Linux Consumption plan isn't getting any new features or [language versions](../articles/azure-functions/supported-languages.md). Apps running on Windows in a Consumption plan aren't currently affected. [Migrate your apps to the Flex Consumption plan](../articles/azure-functions/migration/migrate-plan-consumption-to-flex.md) before the retirement date.