Final pre-GA revisions (remove preview)

ggailey777 · ggailey777 · commit 613c83075072 · 2024-11-05T09:33:32.000-08:00
diff --git a/articles/azure-functions/flex-consumption-plan.md b/articles/azure-functions/flex-consumption-plan.md
@@ -95,9 +95,7 @@ Deployments in the Flex Consumption plan follow a single path. After your projec
 
 The minimum billable execution period for both execution modes is 1,000 ms. Past that, the billable activity period is rounded up to the nearest 100 ms. You can find details on the Flex Consumption plan billing meters in the [Monitoring reference](monitor-functions-reference.md?tab=flex-consumption-plan#metrics).
 
-For details about how costs are calculated when you run in a Flex Consumption plan, including examples, see [Consumption-based costs](functions-consumption-costs.md?tabs=flex-consumtion-plan#consumption-based-costs). 
-
-For the most up-to-date information on execution pricing, always ready baseline costs, and free grants for on demand executions, see the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/).  
+For details about how costs are calculated when you run in a Flex Consumption plan, including examples, see [Consumption-based costs](functions-consumption-costs.md?tabs=flex-consumtion-plan#consumption-based-costs).   
 
 ## Supported language stack versions
 
diff --git a/articles/azure-functions/functions-consumption-costs.md b/articles/azure-functions/functions-consumption-costs.md
@@ -1,7 +1,7 @@
 ---
 title: Estimating consumption-based costs in Azure Functions
 description: Learn how to better estimate the costs that you might incur when running your function app in either the Consumption plan or the Flex Consumption plan in Azure Functions.
-ms.date: 5/05/2024
+ms.date: 11/05/2024
 ms.topic: conceptual
 ms.custom:
   - build-2024
@@ -57,16 +57,6 @@ In addition to execution time, when using one or more always ready instances, yo
 >[!IMPORTANT]
 >In this article, prices are only provided to help understand example calculations. Always check the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/) when estimating costs you might incur while running your functions in the Flex Consumtion plan. 
 
-For the examples in this section, consider the discounted preview pricing in this table for pay-as-you-go in East US.
-
-| Mode        | Meter             | Free monthly grants        | Consumption rates        |
-| ------------| ----------------- | -------------------------- | ------------------------ | 
-| On-demand | Execution time (GB-s)   | `100,000`              | `$0.000016` per GB-s         |
-| On-demand | Executions (count)  | `250,000` | `$0.20` per million executions              |
-| Always ready | Baseline (idle) time (GB-s)  | \-         | `$0.000004` per GB-s               |
-| Always ready | Execution time (GB-s)        | \-         | `$0.000009` per GB-s               |
-| Always ready | Executions (count)           | \-         | `$0.20` per million executions |
-
 Consider a function app that is comprised only of HTTP triggers with and these basic facts:
 
 + HTTP triggers handle 40 constant requests per second.
diff --git a/articles/azure-functions/functions-event-grid-blob-trigger.md b/articles/azure-functions/functions-event-grid-blob-trigger.md
@@ -18,7 +18,7 @@ This article shows how to create a function that runs based on events raised whe
 > * Create an event-based Blob Storage triggered function in a new project.
 > * Validate locally within Visual Studio Code using the Azurite emulator.
 > * Create a blob storage container in a new storage account in Azure.
-> * Create a function app in the Flex Consumption plan (preview).
+> * Create a function app in the Flex Consumption plan.
 > * Create an event subscription to the new blob container.
 > * Deploy and validate your function code in Azure.
 
diff --git a/articles/azure-functions/functions-reference-python.md b/articles/azure-functions/functions-reference-python.md
@@ -46,7 +46,7 @@ As a Python developer, you might also be interested in these topics:
 
 ## [Hosting options](#tab/hosting)
 
-+ [Flex Consumption plan](./flex-consumption-plan.md): Linux-based serverless hosting option that features full support for managed identities, virtual networks, and flexible deployments. This plan is currently in preview.
++ [Flex Consumption plan](./flex-consumption-plan.md): Linux-based serverless hosting option that features full support for managed identities, virtual networks, and flexible deployments. 
 + [Container hosting options](container-concepts.md): Run and deploy your Python functions on Linux in a Docker container, including integrated [Azure Container Apps hosting](functions-container-apps-hosting.md).
 + [Compare hosting options...](functions-scale.md) 
 
diff --git a/includes/functions-flex-consumption-billing-table.md b/includes/functions-flex-consumption-billing-table.md
@@ -4,7 +4,7 @@ ms.service: azure-functions
 ms.custom:
   - build-2024
 ms.topic: include
-ms.date: 05/13/2024
+ms.date: 11/05/2024
 ms.author: glenga
 ---
 There are two modes by which your costs are determined when running your apps in the Flex Consumption plan. Each mode is determined on a per-instance basis.
@@ -13,3 +13,5 @@ There are two modes by which your costs are determined when running your apps in
 | ---- | ---- |
 | **On Demand** | When running in _on demand_ mode, you are billed only for the amount of time your function code is executing on your available instances. In on demand mode, no minimum instance count is required. You're billed for:<br/><br/>• The total amount of memory provisioned while each on demand instance is _actively_ executing functions (in GB-seconds), minus a free grant of GB-s per month.<br/>• The total number of executions, minus a free grant (number) of executions per month. |
 | **Always ready** | You can configure one or more instances, assigned to specific trigger types (HTTP/Durable/Blob) and individual functions, that are always available to be able handle requests. When you have any always ready instances enabled, you're billed for:<br/><br/>• The total amount of memory provisioned across all of your always ready instances, known as the _baseline_ (in GB-seconds).<br/>• The total amount of memory provisioned during the time each always ready instance is _actively_ executing functions (in GB-seconds).<br/>• The total number of executions.<br/><br/>In always ready billing, there are no free grants. |
+
+For the most up-to-date information on execution pricing, always ready baseline costs, and free grants for on demand executions, see the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/#pricing).
