Remove "preview" language for Flex GA

ggailey777 · ggailey777 · commit a4c5540b54ea · 2024-11-04T15:02:30.000-08:00
diff --git a/articles/azure-functions/TOC.yml b/articles/azure-functions/TOC.yml
@@ -344,7 +344,7 @@
       items:
         - name: Consumption plan
           href: consumption-plan.md
-        - name: Flex Consumption plan (preview)
+        - name: Flex Consumption plan
           href: flex-consumption-plan.md
         - name: Premium plan
           href: functions-premium-plan.md
diff --git a/articles/azure-functions/event-driven-scaling.md b/articles/azure-functions/event-driven-scaling.md
@@ -102,7 +102,7 @@ The following considerations apply for scale-in behaviors:
 
 ## Per-function scaling
 
-_Applies only to the Flex Consumption plan (preview)_.
+_Applies only to the Flex Consumption plan_.
 
 The [Flex Consumption plan] is unique in that it implements a _per-function scaling_ behavior. In per-function scaling, except for HTTP triggers, Blob (Event Grid) triggers, and Durable Functions, all other function trigger types in your app scale on independent instances. HTTP triggers in your app all scale together as a group on the same instances, as do all Blob (Event Grid), and all Durable Functions triggers, which have their own shared instances.
 
diff --git a/articles/azure-functions/flex-consumption-how-to.md b/articles/azure-functions/flex-consumption-how-to.md
@@ -122,7 +122,7 @@ To support your function code, you need to create three resources:
     ::: zone-end 
     In this example, replace both `<RESOURCE_GROUP>` and `<STORAGE_NAME>` with the resource group and the name of the account you used in the previous step, respectively. Also replace `<APP_NAME>` with a globally unique name appropriate to you. The `<APP_NAME>` is also the default domain name server (DNS) domain for the function app. The [`az functionapp create`] command creates the function app in Azure.
 
-    This command creates a function app running in the Flex Consumption plan. The specific language runtime version used is one that is currently supported in the preview. 
+    This command creates a function app running in the Flex Consumption plan. 
 
     Because you created the app without specifying [always ready instances](#set-always-ready-instance-counts), your app only incurs costs when actively executing functions. The command also creates an associated Azure Application Insights instance in the same resource group, with which you can monitor your function app and view logs. For more information, see [Monitor Azure Functions](functions-monitoring.md).
     ```
@@ -148,7 +148,7 @@ To support your function code, you need to create three resources:
     | Prompt |  Selection |
     | ------ |  ----------- |
     | Enter a globally unique name for the new function app. | Type a globally unique name that identifies your new function app and then select Enter. Valid characters for a function app name are `a-z`, `0-9`, and `-`. |
-    | Select a hosting plan. | Choose **Flex Consumption (Preview)**. |
+    | Select a hosting plan. | Choose **Flex Consumption**. |
     | Select a runtime stack. | Choose one of the supported language stack versions. |
     | Select a resource group for new resources. | Choose **Create new resource group** and type a resource group name, like `myResourceGroup`, and then select enter. You can also select an existing resource group. |
     | Select a location for new resources. | Select a location in a supported [region](https://azure.microsoft.com/regions/) near you or near other services that your functions access. Unsupported regions aren't displayed. For more information, see [View currently supported regions](#view-currently-supported-regions).|
@@ -541,7 +541,7 @@ You can't currently set HTTP concurrency limits using Visual Studio Code.
 
 ## View currently supported regions
 
-During the preview, you're only able to run on the Flex Consumption plan only in selected regions. To view the list of regions that currently support Flex Consumption plans: 
+To view the list of regions that currently support Flex Consumption plans: 
 
 [!INCLUDE [functions-flex-supported-regions-cli](../../includes/functions-flex-supported-regions-cli.md)]
 
diff --git a/articles/azure-functions/flex-consumption-plan.md b/articles/azure-functions/flex-consumption-plan.md
@@ -12,9 +12,6 @@ ms.custom: references_regions, build-2024
 
 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.
 
-> [!IMPORTANT]
-> The Flex Consumption plan is currently in preview. For a list of current limitations when using this hosting plan, see [Considerations](#considerations). For current information about billing during the preview, see [Billing](#billing).
-
 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).
 
 ## Benefits
@@ -119,7 +116,7 @@ This table shows the language stack versions that are currently supported for Fl
 
 ## Regional subscription memory quotas
 
-Currently in preview each region in a given subscription has a memory limit of `512,000 MB` for all instances of apps running on Flex Consumption plans. This means that, in a given subscription and region, you could have any combination of instance memory sizes and counts, as long as they stay under the quota limit. For example, each the following examples would mean the quota has been reached and the apps would stop scaling:
+Currently, each region in a given subscription has a memory limit of `512,000 MB` for all instances of apps running on Flex Consumption plans. This means that, in a given subscription and region, you could have any combination of instance memory sizes and counts, as long as they stay under the quota limit. For example, each the following examples would mean the quota has been reached and the apps would stop scaling:
 
 + You have one 2,048 MB app scaled to 100 and a second 2,048 MB app scaled to 150 instances
 + You have one 2,048 MB app that scaled out to 250 instances
@@ -134,20 +131,19 @@ In Flex Consumption, many of the standard application settings and site configur
 
 ## Considerations
 
-Keep these other considerations in mind when using Flex Consumption plan during the current preview:
+Keep these other considerations in mind when using Flex Consumption plan:
 
 + **Host**: There is a 30 seconds timeout for the app initialization. If your function app takes longer than 30 seconds to start you will see gRPC related System.TimeoutException entries. This timeout will be configurable and a more clear exception will be implemented as part of [this host work item](https://github.com/Azure/azure-functions-host/issues/10482).
 + **Durable Functions**: Due to the per function scaling nature of Flex Consumption, to ensure the best performance for Durable Functions we recommend setting the [Always Ready instance count](./flex-consumption-how-to.md#set-always-ready-instance-counts) for the `durable` group to `1`. Also, with the Azure Storage provider, consider reducing the [queue polling interval](./durable/durable-functions-azure-storage-provider.md#queue-polling) to 10 seconds or less. Only Azure Storage is supported as a backend storage providers for Flex Consumption hosted durable functions.
-+ **VNet Integration** Ensure that the `Microsoft.App` Azure resource provider is enabled for your subscription by [following these instructions](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider). The subnet delegation required by Flex Consumption apps is `Microsoft.App/environments`.
++ **Virtual network integration** Ensure that the `Microsoft.App` Azure resource provider is enabled for your subscription by [following these instructions](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider). The subnet delegation required by Flex Consumption apps is `Microsoft.App/environments`.
 + **Triggers**: All triggers are fully supported except for Kafka and Azure SQL triggers. The Blob storage trigger only supports the [Event Grid source](./functions-event-grid-blob-trigger.md). Non-C# function apps must use version `[4.0.0, 5.0.0)` of the [extension bundle](./functions-bindings-register.md#extension-bundles), or a later version. 
 + **Regions**: Not all regions are currently supported. To learn more, see [View currently supported regions](flex-consumption-how-to.md#view-currently-supported-regions).
 + **Deployments**: Deployment slots are not currently supported.
-+ **Scale**: The lowest maximum scale in preview is `40`. The highest currently supported value is `1000`. 
++ **Scale**: The lowest maximum scale is currently `40`. The highest currently supported value is `1000`. 
 + **Managed dependencies**: [Managed dependencies in PowerShell](functions-reference-powershell.md#dependency-management) aren't supported by Flex Consumption. You must instead [define your own custom modules](functions-reference-powershell.md#custom-modules).
 + **Diagnostic settings**: Diagnostic settings are not currently supported.
 + **Certificates**: Loading certificates with the WEBSITE_LOAD_CERTIFICATES app setting is currently not supported.
-+ **Key Vault References**: Key Vault references in app settings do not work when Key Vault is network access restricted, even if the function app has Virtual Network integration. The current workaround is to directly reference the Key Vault in code and read the required secrets.
-+ **Azure Files file share mount**: [Mounting an Azure Files file share](./scripts/functions-cli-mount-files-storage-linux.md) does not work when the function app has Virtual Network integration. 
++ **Key Vault References**: Key Vault references in app settings don't work when Key Vault is network access restricted, even if the function app has Virtual Network integration. The current workaround is to directly reference the Key Vault in code and read the required secrets.
 
 ## Related articles
 
diff --git a/articles/azure-functions/functions-how-to-use-azure-function-app-settings.md b/articles/azure-functions/functions-how-to-use-azure-function-app-settings.md
@@ -355,7 +355,7 @@ Consider these limitations when you develop your functions in the [Azure portal]
 
 + In-portal editing is supported only for functions that were created or last modified in the Azure portal.
 + In-portal editing is supported only for JavaScript, PowerShell, Python, and C# Script functions.
-+ In-portal editing isn't supported in the preview release of the [Flex Consumption plan](flex-consumption-plan.md#considerations).
++ In-portal editing isn't currently supported by the [Flex Consumption plan](flex-consumption-plan.md#considerations).
 + When you deploy code to a function app from outside the Azure portal, you can no longer edit any of the code for that function app in the portal. In this case, just continue using [local development](functions-develop-local.md).
 + For Python, development with custom modules isn't currently supported in the portal. To add custom modules to your function app, you must [develop your app locally](functions-develop-local.md).
 + For compiled C# functions and Java functions, you can create the function app and related resources in the portal. However, you must create the functions code project locally and then publish it to Azure.
diff --git a/articles/azure-functions/functions-scale.md b/articles/azure-functions/functions-scale.md
@@ -13,7 +13,7 @@ When you create a function app in Azure, you must choose a hosting option for yo
 | Hosting option | Service | Availability | Container support |
 | --- | --- | --- | --- | 
 | **[Consumption plan]** | Azure Functions | Generally available (GA) | None |
-| **[Flex Consumption plan]** | Azure Functions | Preview  |  None | 
+| **[Flex Consumption plan]** | Azure Functions | GA  |  None | 
 | **[Premium plan]** | Azure Functions | GA | Linux |
 | **[Dedicated plan]** | Azure Functions | GA | Linux |
 | **[Container Apps]** | Azure Container Apps | GA | Linux |
diff --git a/articles/azure-functions/storage-considerations.md b/articles/azure-functions/storage-considerations.md
@@ -171,7 +171,7 @@ By default, function apps hosted in Premium and Consumption plans use [zip deplo
 Using Azure Files requires the use of a connection string, which is stored in your app settings as [`WEBSITE_CONTENTAZUREFILECONNECTIONSTRING`](functions-app-settings.md#website_contentazurefileconnectionstring). Azure Files doesn't currently support identity-based connections. If your scenario requires you to not store any secrets in app settings, you must remove your app's dependency on Azure Files. You can do this by creating your app without the default Azure Files dependency. 
 
 >[!NOTE]
->You should also consider running in your function app in the Flex Consumption plan, which is currently in preview. The Flex Consumption plan provides greater control over the deployment package, including the ability use managed identity connections. For more information, see [Configure deployment settings](flex-consumption-how-to.md#configure-deployment-settings) in the Flex Consumption article.
+>You should also consider running in your function app in the Flex Consumption plan, which provides greater control over the deployment package, including the ability use managed identity connections. For more information, see [Configure deployment settings](flex-consumption-how-to.md#configure-deployment-settings) in the Flex Consumption article.
 
 To run your app without the Azure file share, you must meet the following requirements:
 
diff --git a/includes/functions-flex-preview-note.md b/includes/functions-flex-preview-note.md
diff --git a/includes/functions-limits.md b/includes/functions-limits.md
@@ -4,20 +4,20 @@ ms.service: azure-functions
 ms.custom:
   - build-2024
 ms.topic: include
-ms.date: 08/08/2024
+ms.date: 10/22/2024
 ms.author: glenga
 ---
-| Resource |[Consumption plan](/azure/azure-functions/consumption-plan)|[Flex Consumption plan](/azure/azure-functions/flex-consumption-plan)<sup>13</sup>|[Premium plan](/azure/azure-functions/functions-premium-plan)|[Dedicated plan](/azure/azure-functions/dedicated-plan)/[ASE](/azure/app-service/environment/intro)| [Container Apps](/azure/azure-functions/functions-container-apps-hosting)|
+| Resource |[Consumption plan](/azure/azure-functions/consumption-plan)|[Flex Consumption plan](/azure/azure-functions/flex-consumption-plan)|[Premium plan](/azure/azure-functions/functions-premium-plan)|[Dedicated plan](/azure/azure-functions/dedicated-plan)/[ASE](/azure/app-service/environment/intro)| [Container Apps](/azure/azure-functions/functions-container-apps-hosting)|
 | --- | --- | --- | --- | --- | --- | 
-| Default [timeout duration](/azure/azure-functions/functions-scale#timeout) (min) |5 | 30 | 30 |30<sup>1</sup> | 30<sup>16</sup> |
-| Max [timeout duration](/azure/azure-functions/functions-scale#timeout) (min) |10 | unbounded<sup>8</sup> | unbounded<sup>8</sup> | unbounded<sup>2</sup> | unbounded<sup>17</sup> |
+| Default [timeout duration](/azure/azure-functions/functions-scale#timeout) (min) |5 | 30 | 30 |30<sup>1</sup> | 30<sup>15</sup> |
+| Max [timeout duration](/azure/azure-functions/functions-scale#timeout) (min) |10 | unbounded<sup>8</sup> | unbounded<sup>8</sup> | unbounded<sup>2</sup> | unbounded<sup>16</sup> |
 | Max outbound connections (per instance) | 600 active (1200 total) | unbounded | unbounded | unbounded | unbounded |
 | Max request size (MB)<sup>3</sup> | 100 | 100 | 100 | 100 |  100 |
 | Max query string length<sup>3</sup> | 4096 | 4096 | 4096 | 4096 |   4096 | 
 | Max request URL length<sup>3</sup> | 8192 | 8192 | 8192 | 8192 | 8192 | 
 |[ACU](/azure/virtual-machines/acu) per instance | 100 | varies | 210-840 | 100-840/210-250<sup>9</sup> | [varies](/azure/container-apps/billing) |
-| Max memory (GB per instance) | 1.5 | 4<sup>14</sup> | 3.5-14 | 1.75-14/3.5-14 | [varies](/azure/container-apps/billing) |
-| Max instance count (Windows/Linux) | 200/100 | 1000 <sup>15</sup> | 100/20 | varies by SKU/100<sup>10</sup> |  10-300<sup>18</sup> | 
+| Max memory (GB per instance) | 1.5 | 4<sup>13</sup> | 3.5-14 | 1.75-14/3.5-14 | [varies](/azure/container-apps/billing) |
+| Max instance count (Windows/Linux) | 200/100 | 1000 <sup>14</sup> | 100/20 | varies by SKU/100<sup>10</sup> |  10-300<sup>17</sup> | 
 | Function apps per plan<sup>12</sup> | 100 | 100 | 100 | unbounded<sup>4</sup> | unbounded<sup>4</sup> |
 | [App Service plans](/azure/app-service/overview-hosting-plans) | 100 per [region](https://azure.microsoft.com/global-infrastructure/regions/) | n/a | 100 per resource group |100 per resource group | n/a |
 | [Deployment slots](/azure/azure-functions/functions-deployment-slots) per app<sup>11</sup> | 2 | n/a | 3 | 1-20<sup>10</sup> | not supported |
@@ -40,9 +40,8 @@ Notes on service limits:
 10. See [App Service limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits) for details.  
 11. Including the production slot.  
 12. There's currently a limit of 5000 function apps in a given subscription. 
-13. The Flex Consumption plan is currently in preview.  
-14. Flex Consumption plan instance sizes are currently defined as either 2,048 MB or 4,096 MB. For more information, see [Instance memory](/azure/azure-functions/flex-consumption-plan#instance-memory).  
-15. Flex Consumption plan during preview has a regional subscription quota that limits the total memory usage of all instances across a given region. For more information, see [Instance memory](/azure/azure-functions/flex-consumption-plan#instance-memory).  
-16. When the [minimum number of replicas](/azure/container-apps/scale-app#scale-definition) is set to zero, the default timeout depends on the specific triggers used in the app.
-17. When the [minimum number of replicas](../articles/container-apps/scale-app.md#scale-definition) is set to one or more.
-18. On Container Apps, you can set the [maximum number of replicas](/azure/container-apps/scale-app#scale-definition), which is honored as long as there's enough cores quota available.
+13. Flex Consumption plan instance sizes are currently defined as either 2,048 MB or 4,096 MB. For more information, see [Instance memory](/azure/azure-functions/flex-consumption-plan#instance-memory).  
+14. Flex Consumption plan has a regional subscription quota that limits the total memory usage of all instances across a given region. For more information, see [Instance memory](/azure/azure-functions/flex-consumption-plan#instance-memory).  
+15. When the [minimum number of replicas](/azure/container-apps/scale-app#scale-definition) is set to zero, the default timeout depends on the specific triggers used in the app.
+16. When the [minimum number of replicas](../articles/container-apps/scale-app.md#scale-definition) is set to one or more.
+17. On Container Apps, you can set the [maximum number of replicas](/azure/container-apps/scale-app#scale-definition), which is honored as long as there's enough cores quota available.
