Merge pull request #299357 from TimShererWithAquent/us424061-06

Freshness Edit: Azure Functions (6 of several)

Author: JamesJBarnett

articles/azure-functions/consumption-plan.md

@@ -1,7 +1,7 @@
 ---
 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, but you only pay for resources used during execution.
-ms.date: 07/10/2023
+description: Learn about how Azure Functions Consumption plan hosting lets you run your code in an environment that scales dynamically.
+ms.date: 05/06/2025
 ms.topic: conceptual
 ms.custom:
   - build-2024
@@ -10,7 +10,7 @@ ms.custom:
 
 # Azure Functions Consumption plan hosting
 
-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. The Consumption plan, along with the [Flex Consumption plan](./flex-consumption-plan.md), is a fully <em>serverless</em> hosting option for Azure Functions.
+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. The Consumption plan, along with the [Flex Consumption plan](./flex-consumption-plan.md), is a fully *serverless* hosting option for Azure Functions.
 
 ## Benefits
 
@@ -23,29 +23,29 @@ For a comparison of the Consumption plan against the other plan and hosting type
 
 ## 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 the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/).
+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/).
 
 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
 
 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. In the Azure portal or in code, you may 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`.
 
 Use the following links to learn how to create a serverless function app in a Consumption plan, either programmatically or in the Azure portal:
 
-+ [Azure CLI](./scripts/functions-cli-create-serverless.md)
-+ [Azure portal](./functions-get-started.md)
-+ [Azure Resource Manager template](functions-create-first-function-resource-manager.md)
+- [Azure CLI](./scripts/functions-cli-create-serverless.md)
+- [Azure portal](./functions-get-started.md)
+- [Azure Resource Manager template](functions-create-first-function-resource-manager.md)
 
 You can also create function apps in a Consumption plan when you publish a Functions project from [Visual Studio Code](./create-first-function-vs-code-csharp.md#publish-the-project-to-azure) or [Visual Studio](functions-create-your-first-function-visual-studio.md#publish-the-project-to-azure).
 
 ## 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 is 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, 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.
 
 ## Next steps
 
-+ [Azure Functions hosting options](functions-scale.md)
-+ [Event-driven scaling in Azure Functions](event-driven-scaling.md)
+- [Azure Functions hosting options](functions-scale.md)
+- [Event-driven scaling in Azure Functions](event-driven-scaling.md)