Skip to content

Commit 0b760e2

Browse files
committed
Remove legacy banner and streamline Consumption plan description in Azure Functions docs
1 parent 711088d commit 0b760e2

2 files changed

Lines changed: 1 addition & 14 deletions

File tree

articles/azure-functions/consumption-plan.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,13 +10,9 @@ ms.custom:
1010

1111
# Azure Functions Consumption plan hosting (legacy)
1212

13-
[!INCLUDE [functions-consumption-legacy-banner](../../includes/functions-consumption-legacy-banner.md)]
14-
15-
When you use the Consumption plan, the Azure Functions host dynamically adds and removes instances based on the number of incoming events.
16-
1713
[!INCLUDE [functions-linux-consumption-retirement](../../includes/functions-linux-consumption-retirement.md)]
1814

19-
[!INCLUDE [functions-v3-linux-consumption-enforcement](../../includes/functions-v3-linux-consumption-enforcement.md)]
15+
When you use the Consumption plan, the Azure Functions host dynamically adds and removes instances based on the number of incoming events.
2016

2117
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.
2218

includes/functions-consumption-legacy-banner.md

Lines changed: 0 additions & 9 deletions
This file was deleted.

0 commit comments

Comments
 (0)