Merge pull request #313167 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-15 11:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-functions/TOC.yml

@@ -221,7 +221,7 @@
         href: container-concepts.md
       - name: Azure Container Apps hosting
         href: functions-container-apps-hosting.md
-    - name: Consumption plan
+    - name: Consumption plan (legacy)
       href: consumption-plan.md
     - name: Host MCP servers
       href: self-hosted-mcp-servers.md
@@ -630,6 +630,8 @@
   - name: Migrate from AWS Lambda
     displayName: AWS Lambda, migration
     href: migration/migrate-aws-lambda-to-azure-functions.md
+  - name: Migrate Consumption plan apps to Flex Consumption
+    href: migration/migrate-plan-consumption-to-flex.md
   - name: Upgrade runtime versions
     items:
     - name: Migrate v3.x to v4.x
@@ -643,8 +645,6 @@
       href: update-language-versions.md
     - name: Migrate Node.js to model v4.x
       href: functions-node-upgrade-v4.md
-  - name: Migrate Consumption plan apps to Flex Consumption
-    href: migration/migrate-plan-consumption-to-flex.md
   - name: Migrate .NET apps to the isolated model
     href: migrate-dotnet-to-isolated-model.md
   - name: Move resources

articles/azure-functions/consumption-plan.md

@@ -1,35 +1,35 @@
 ---
-title: Azure Functions Consumption plan hosting
-description: Learn about how Azure Functions Consumption plan hosting lets you run your code in an environment that scales dynamically.
-ms.date: 09/23/2025
+title: Azure Functions Consumption plan hosting (legacy)
+description: Learn about Azure Functions Consumption plan hosting, a legacy serverless hosting option. We recommend the Flex Consumption plan for new serverless function apps.
+ms.date: 03/13/2026
 ms.topic: concept-article
 ms.custom:
   - build-2024
-# Customer intent: As a developer, I want to understand the benefits of using the Consumption plan so I can get the scalability benefits of Azure Functions without having to pay for resources I don't need.
+# Customer intent: As a developer, I want to understand the Consumption plan and how to migrate to the Flex Consumption plan.
 ---
 
-# Azure Functions Consumption plan hosting
+# Azure Functions Consumption plan hosting (legacy)
 
-When you're using the Consumption plan, instances of the Azure Functions host are dynamically added and removed based on the number of incoming events. 
+[!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. 
 
-The Consumption plan scales automatically, even during periods of high load. When running functions in a Consumption plan, you're charged for compute resources only when your functions are running. On a Consumption plan, a function execution times out after a configurable period of time.
+[!INCLUDE [functions-linux-consumption-retirement](../../includes/functions-linux-consumption-retirement.md)]
 
-> [!TIP]  
-> [!INCLUDE [functions-flex-consumption-recommended-serverless](../../includes/functions-flex-consumption-recommended-serverless.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
 
-Billing is based on number of executions, execution time, and memory used. Usage is aggregated across all functions within a function app. For more information, see [Azure Functions pricing](https://azure.microsoft.com/pricing/details/functions/).
+Billing is based on the number of executions, execution time, and memory used. The system aggregates usage across all functions within a function app. For more information, see [Azure Functions pricing](https://azure.microsoft.com/pricing/details/functions/).
 
 To learn more about how to estimate costs when running in a Consumption plan, see [Understanding Consumption plan costs](functions-consumption-costs.md).
 
-## Create a Consumption plan function app
+## Create a legacy Consumption plan function app
 
-When you create a function app in the Azure portal, the Consumption plan is the default. When using APIs to create your function app, you don't have to first create an App Service plan as you do with Premium and Dedicated plans.
+In Consumption plan hosting, each function app typically runs in its own plan, which the platform creates for you along with the app. In the Azure portal or in code, you might also see the Consumption plan referred to as `Dynamic` or `Y1`.
 
-In Consumption plan hosting, each function app typically runs in its own plan. In the Azure portal or in code, you might also see the Consumption plan referred to as `Dynamic` or `Y1`.
+> [!TIP]
+> For new function apps, consider using the [Flex Consumption plan](flex-consumption-plan.md), which offers faster scaling, virtual network integration, and configurable instance sizes.
 
 Use the following links to learn how to create a serverless function app in a Consumption plan, either programmatically or in the Azure portal:
 
@@ -41,9 +41,14 @@ You can also create function apps in a Consumption plan when you publish a Funct
 
 ## Multiple apps in the same plan
 
-The general recommendation is for each function app to have its own Consumption plan. However, if needed, function apps in the same region can be assigned to the same Consumption plan. Keep in mind that there's a [limit to the number of function apps that can run in a Consumption plan](functions-scale.md#service-limits). Function apps in the same plan still scale independently of each other.
+The general recommendation is for each function app to have its own Consumption plan. However, if needed, you can assign function apps in the same region to the same Consumption plan. Keep in mind that there's a [limit to the number of function apps that can run in a Consumption plan](functions-scale.md#service-limits). Function apps in the same plan still scale independently of each other.
+
+## Migrate to Flex Consumption
+
+If you have existing function apps running on the Consumption plan, migrate them to the Flex Consumption plan. The Flex Consumption plan provides faster scaling, reduced cold starts, virtual network integration, and configurable instance sizes. Because the Flex Consumption plan is Linux-only, Windows Consumption plan apps must also migrate to Linux as part of this process. For step-by-step instructions, including Windows-specific guidance, see [Migrate Consumption plan apps to the Flex Consumption plan](migration/migrate-plan-consumption-to-flex.md).
 
 ## Next steps
 
+- [Migrate Consumption plan apps to the Flex Consumption plan](migration/migrate-plan-consumption-to-flex.md)
 - [Azure Functions hosting options](functions-scale.md)
 - [Event-driven scaling in Azure Functions](event-driven-scaling.md)

articles/azure-functions/container-concepts.md

@@ -24,7 +24,6 @@ There are several options for hosting your containerized function apps in Azure:
 | Hosting option | Benefits |
 | --- | --- |  
 | **[Azure Container Apps]** | Azure Functions provides integrated support for developing, deploying, and managing containerized function apps on [Azure Container Apps](../container-apps/overview.md). This integration enables you to manage your apps using the same Functions tools and pages in the Azure portal. Use Azure Container Apps to host your function app container in the same environment as other microservices, APIs, websites, workflows, or other container hosted programs. Container Apps hosting lets you run your functions in a managed Kubernetes-based environment with built-in support for open-source monitoring, mTLS, Dapr, and KEDA. Supports scale-to-zero and provides a serverless pay-for-what-you-use hosting model. You can also request dedicated hardware, even GPUs, by using workload profiles. _Recommended hosting option for containerized function apps n Azure._ | 
-| **Azure Arc-enabled Kubernetes clusters (preview)** | You can host your function apps on Azure Arc-enabled Kubernetes clusters as either a code-only deployment or in a custom Linux container. Azure Arc lets you attach Kubernetes clusters so that you can manage and configure them in Azure. _Hosting Azure Functions containers on Azure Arc-enabled Kubernetes clusters is currently in preview._ For more information, see [Working with containers and Azure Functions](functions-how-to-custom-container.md?pivots=azure-arc).|
 | **[Azure Functions]** | You can host your containerized function apps in Azure Functions by running the container in an [Elastic Premium](./functions-premium-plan.md) or an [App Service (Dedicated)](./dedicated-plan.md) plan. Use Container Apps hosting for rich container support from Container Apps. Premium plan hosting provides you with the benefits of dynamic scaling. You might want to use Dedicated plan hosting to take advantage of existing unused App Service plan resources.  |  
 | **[Kubernetes]** | Because the Azure Functions runtime provides flexibility in hosting where and how you want, you can host and manage your function app containers directly in Kubernetes clusters. [KEDA](https://keda.sh) (Kubernetes-based Event Driven Autoscaling) pairs seamlessly with the Azure Functions runtime and tooling to provide event driven scale in Kubernetes. **Important:** Kubernetes hosting of your containerized function apps, either by using KEDA or by direct deployment, is an open-source effort that you can use free of cost. _Best-effort_ support for this hosting scenario is provided only by contributors and by the community. You're responsible for maintaining your own function app containers in a cluster, even when deploying them to Azure Kubernetes Service (AKS). |
 

articles/azure-functions/flex-consumption-plan.md

@@ -14,7 +14,7 @@ ms.custom:
 
 # Azure Functions Flex Consumption plan hosting
 
-Flex Consumption is a Linux-based Azure Functions hosting plan that builds on the Consumption _pay for what you use_ serverless billing model. It gives you more flexibility and customizability by introducing private networking, instance memory size selection, and fast/large scale-out features still based on a <em>serverless</em> model.
+Flex Consumption is a Linux-based Azure Functions hosting plan that builds on the Consumption _pay for what you use_ serverless billing model. It gives you more flexibility and customizability by introducing private networking, instance memory size selection, and fast/large scale-out features still based on a <em>serverless</em> model. Flex Consumption is the recommended serverless hosting plan for Azure Functions.
 
 You can review end-to-end samples that feature the Flex Consumption plan in the [Flex Consumption plan samples repository](https://github.com/Azure-Samples/azure-functions-flex-consumption-samples).
 
@@ -38,6 +38,7 @@ This table helps you directly compare the features of Flex Consumption with the
 | Dedicated compute (mitigate cold starts) | ❌ None | ✅ Always ready instances (optional) | 
 | Billing | Execution-time only | Execution-time + always-ready instances |
 | Scale-out instances (max) | 200 | 1000 |
+| Windows support | ✅ Yes | ❌ Linux only |
 
 For a complete comparison of the Flex Consumption plan against the Consumption plan and all other plan and hosting types, see [function scale and hosting options](functions-scale.md).
 

articles/azure-functions/functions-create-function-app-portal.md

@@ -14,7 +14,7 @@ This article shows you how to use the Azure portal to create a function app that
 | ----- | ----- |
 | [Flex Consumption plan](./flex-consumption-plan.md) | Linux-only plan that provides rapid horizontal scaling with support for managed identities, virtual networking, and pay-as-you-go billing. |
 | [Premium plan](./functions-premium-plan.md) | Provides longer execution times, more control over CPU/memory, and support for containers and virtual networks. |
-| [Consumption plan](./consumption-plan.md) | Original dynamic hosting plan, which supports portal development for some languages. |
+| [Consumption plan](./consumption-plan.md) | Legacy dynamic hosting plan that supports Windows apps. |
 
 The Flex Consumption plan is the recommended plan for hosting serverless compute resources in Azure.
 

articles/azure-functions/functions-deployment-technologies.md

@@ -31,10 +31,10 @@ The deployment method also depends on the hosting plan and operating system on w
 Currently, Functions offers five options for hosting your function apps:
 
 + [Flex Consumption plan](flex-consumption-plan.md)
-+ [Consumption](consumption-plan.md)
 + [Elastic Premium plan](functions-premium-plan.md)
 + [Dedicated (App Service) plan](dedicated-plan.md)
 + [Azure Container Apps](../container-apps/functions-overview.md)
++ [Consumption plan](consumption-plan.md) (legacy)
 
 Each plan has different behaviors. Not all deployment technologies are available for each hosting plan and operating system. This chart provides information on the supported deployment technologies:
 

articles/azure-functions/functions-how-to-custom-container.md

@@ -22,7 +22,7 @@ This article demonstrates the support that Azure Functions provides for containe
 [!INCLUDE [functions-aca-v2-note](../../includes/functions-aca-v2-note.md)]
 
 ::: zone-end
-:::zone pivot="azure-functions,azure-arc"
+:::zone pivot="azure-functions"
 This article demonstrates the support that Azure Functions provides for function apps that run in Linux containers.
 ::: zone-end
 
@@ -38,9 +38,6 @@ To learn more about deployments to Azure Container Apps, see [Azure Container Ap
 :::zone pivot="azure-functions"
 > [Create your first containerized Azure Functions](functions-deploy-container.md)
 :::zone-end
-:::zone pivot="azure-arc"
-> [Working with containers and Azure Functions](functions-how-to-custom-container.md?pivots=azure-arc)
-::: zone-end
 >
 >[!IMPORTANT]
 >This article currently shows how to connect to the default storage account by using a connection string. For the best security, instead create a managed identity-based connection to Azure Storage using Microsoft Entra authentication. For more information, see [Connections](./functions-reference.md#connections).
@@ -170,10 +167,6 @@ The specified image version is deployed to your app.
 The specified image version is deployed to your app.
 ::: zone-end  
 
-:::zone pivot="azure-arc"
-This feature isn't documented.
-::: zone-end
-
 ---
 
 :::zone pivot="azure-functions"  
@@ -297,10 +290,6 @@ Based on your changes, a new image is deployed to your app or new allocations ar
 The new image is deployed to your app based on your new settings.
 ::: zone-end
 
-:::zone pivot="azure-arc"
-This feature isn't documented.
-::: zone-end
-
 ---
 
 :::zone pivot="container-apps"