Merge pull request #274273 from mattchenderson/may14-net7

updating references to .NET 7

Author: JamesJBarnett

articles/azure-functions/functions-versions.md

@@ -135,7 +135,11 @@ In Visual Studio, you select the runtime version when you create a project. Azur
 <AzureFunctionsVersion>v4</AzureFunctionsVersion>
 ```
 
-You can choose `net8.0`, `net7.0`, `net6.0`, or `net48` as the target framework if you are using the [isolated worker model](dotnet-isolated-process-guide.md). If you are using the [in-process model](./functions-dotnet-class-library.md), you can only choose `net6.0`, and you must include the `Microsoft.NET.Sdk.Functions` extension set to at least `4.0.0`.
+You can choose `net8.0`, `net6.0`, or `net48` as the target framework if you are using the [isolated worker model](dotnet-isolated-process-guide.md). If you are using the [in-process model](./functions-dotnet-class-library.md), you can only choose `net6.0`, and you must include the `Microsoft.NET.Sdk.Functions` extension set to at least `4.0.0`.
+
+.NET 7 was previously supported on the isolated worker model but reached the end of official support on [May 14, 2024][dotnet-policy].
+
+[dotnet-policy]: https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle
 
 # [Version 1.x](#tab/v1)
 

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

@@ -86,7 +86,7 @@ On version 1.x of the Functions runtime, your C# function app targets .NET Frame
 >
 > Although you can choose to instead use the in-process model, this is not recommended if it can be avoided. [Support will end for the in-process model on November 10, 2026](https://aka.ms/azure-functions-retirements/in-process-model), so you'll need to move to the isolated worker model before then. Doing so while migrating to version 4.x will decrease the total effort required, and the isolated worker model will give your app [additional benefits](./dotnet-isolated-in-process-differences.md), including the ability to more easily target future versions of .NET. If you are moving to the isolated worker model, the [.NET Upgrade Assistant] can also handle many of the necessary code changes for you.
 
-This guide doesn't present specific examples for .NET 7 or .NET 6 on the isolated worker model. If you need to target these versions, you can adapt the .NET 8 isolated worker model examples.
+This guide doesn't present specific examples for .NET 6 on the isolated worker model. If you need to target that version, you can adapt the .NET 8 isolated worker model examples.
 
 ::: zone-end
 

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

@@ -36,7 +36,7 @@ On version 3.x of the Functions runtime, your C# function app targets .NET Core
 >
 > Although you can choose to instead use the in-process model, this is not recommended if it can be avoided. [Support will end for the in-process model on November 10, 2026](https://aka.ms/azure-functions-retirements/in-process-model), so you'll need to move to the isolated worker model before then. Doing so while migrating to version 4.x will decrease the total effort required, and the isolated worker model will give your app [additional benefits](./dotnet-isolated-in-process-differences.md), including the ability to more easily target future versions of .NET. If you are moving to the isolated worker model, the [.NET Upgrade Assistant] can also handle many of the necessary code changes for you.
 
-This guide doesn't present specific examples for .NET 7 or .NET 6 on the isolated worker model. If you need to target these versions, you can adapt the .NET 8 isolated worker model examples.
+This guide doesn't present specific examples for .NET 6 on the isolated worker model. If you need to target that version, you can adapt the .NET 8 isolated worker model examples.
 
 ::: zone-end
 

includes/functions-dotnet-migrate-v4-versions.md

@@ -13,7 +13,6 @@ When you migrate your function app, you have the opportunity to choose the targe
 | .NET version | [.NET Official Support Policy] release type |  Functions process model<sup>1,3</sup> | 
 | --- | --- | --- |
 | .NET 8<sup>2</sup> | LTS | [Isolated worker model] | 
-| .NET 7 | STS (end of support May 14, 2024) |  [Isolated worker model] | 
 | .NET 6 | LTS (end of support November 12, 2024) |  [Isolated worker model],<br/>[In-process model]<sup>3</sup>  | 
 | .NET Framework 4.8 | [See policy][netfxpolicy] | [Isolated worker model] |  
 

includes/functions-dotnet-supported-versions.md

@@ -19,13 +19,17 @@ The following table shows the highest level of .NET or .NET Framework that can b
 
 | Functions runtime version | [Isolated worker model](../articles/azure-functions/dotnet-isolated-process-guide.md) | [In-process model](../articles/azure-functions/functions-dotnet-class-library.md)<sup>5</sup> |
 | ---- | --- | ---- |
-| Functions 4.x | .NET 8.0<br/>.NET 7.0<sup>1</sup><br/>.NET 6.0<sup>2</sup><br/>.NET Framework 4.8<sup>3</sup> | .NET 6.0<sup>2</sup>  |
+| Functions 4.x<sup>1</sup> | .NET 8.0<br/>.NET 6.0<sup>2</sup><br/>.NET Framework 4.8<sup>3</sup> | .NET 6.0<sup>2</sup>  |
 | Functions 1.x<sup>4</sup> | n/a | .NET Framework 4.8 |
 
-<sup>1</sup> .NET 7 reaches the [end of official support] on May 14, 2024.  
-<sup>2</sup> .NET 6 reaches the [end of official support] on November 12, 2024.  
-<sup>3</sup> The build process also requires the [.NET SDK](https://dotnet.microsoft.com/download).
-<sup>4</sup> Support ends for version 1.x of the Azure Functions runtime on September 14, 2026. For more information, see [this support announcement](https://aka.ms/azure-functions-retirements/hostv1). For continued full support, you should [migrate your apps to version 4.x](../articles/azure-functions/migrate-version-1-version-4.md).  
+<sup>1</sup> .NET 7 was previously supported on the isolated worker model but reached the [end of official support] on May 14, 2024.
+
+<sup>2</sup> .NET 6 reaches the [end of official support] on November 12, 2024.
+
+<sup>3</sup> The build process also requires the [.NET SDK](https://dotnet.microsoft.com/download).  
+
+<sup>4</sup> Support ends for version 1.x of the Azure Functions runtime on September 14, 2026. For more information, see [this support announcement](https://aka.ms/azure-functions-retirements/hostv1). For continued full support, you should [migrate your apps to version 4.x](../articles/azure-functions/migrate-version-1-version-4.md).
+
 <sup>5</sup> Support ends for the in-process model on November 10, 2026. For more information, see [this support announcement](https://aka.ms/azure-functions-retirements/in-process-model). For continued full support, you should  [migrate your apps to the isolated worker model](../articles/azure-functions/migrate-dotnet-to-isolated-model.md).  
 
 For the latest news about Azure Functions releases, including the removal of specific older minor versions, monitor [Azure App Service announcements](https://github.com/Azure/app-service-announcements/issues).

includes/functions-supported-languages.md

@@ -48,13 +48,14 @@ For more information, see [Develop C# class library functions using Azure Functi
 | Supported version | Support level | Expected community EOL date |
 | ---- | ---- |--- |
 | .NET 8 | GA | [November 10, 2026][dotnet-policy] |
-| .NET 7 | GA | [May 14, 2024][dotnet-policy] |
 | .NET 6 | GA | [November 12, 2024][dotnet-policy] |
 | .NET Framework 4.8 | GA | [See policy][dotnet-framework-policy] |
 
 [dotnet-policy]: https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle
 [dotnet-framework-policy]: https://dotnet.microsoft.com/platform/support/policy/dotnet-framework
 
+.NET 7 was previously supported on the isolated worker model but reached the end of official support on [May 14, 2024][dotnet-policy].
+
 For more information, see [Guide for running C# Azure Functions in an isolated worker process](../articles/azure-functions/dotnet-isolated-process-guide.md).
 
 ### [v1.x](#tab/v1/isolated-process)