Merge pull request #275603 from ggailey777/release-flex

[ASK MODE][Build 2024][Functions] Remove unsupported instance size before Build

Author: thomps23

articles/azure-functions/event-driven-scaling.md

@@ -55,7 +55,7 @@ You might decide to restrict the maximum number of instances an app can use for
 
 ### Flex Consumption plan 
 
-By default, apps running in a Flex Consumption plan have limit of `100` overall instances. Currently the lowest maximum instance count value is `40`, and the highest supported maximum instance count value is `1000`. When you use the [`az functionapp create`] command to create a function app in the Flex Consumption plan, use the `--maximum-instance-count` parameter to set this maximum instance count for of your app. This example creates an app with a maximum instance count of `200`:
+By default, apps running in a Flex Consumption plan have limit of `100` overall instances. Currently the lowest maximum instance count value is `40`, and the highest supported maximum instance count value is `1000`. When you use the [`az functionapp create`](/cli/azure/functionapp#az-functionapp-create) command to create a function app in the Flex Consumption plan, use the `--maximum-instance-count` parameter to set this maximum instance count for of your app. This example creates an app with a maximum instance count of `200`:
 
 ```azurecli
 az functionapp create --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage <STORAGE_ACCOUNT_NAME> --runtime <LANGUAGE_RUNTIME> --runtime-version <RUNTIME_VERSION> --flexconsumption-location <REGION> --maximum-instance-count 200

articles/azure-functions/flex-consumption-how-to.md

@@ -415,10 +415,10 @@ At any point, you can change the instance memory size setting used by your app.
 
 ### [Azure CLI](#tab/azure-cli)
 
-This example uses the [`az functionapp scale config set`](/cli/azure/functionapp/scale/config#az-functionapp-scale-config-set) command to change the instance memory size setting to 512 MB: 
+This example uses the [`az functionapp scale config set`](/cli/azure/functionapp/scale/config#az-functionapp-scale-config-set) command to change the instance memory size setting to 4,096 MB: 
 
 ```azurecli
-az functionapp scale config set --resource-group <resourceGroup> --name <APP_NAME> --instance-memory 512
+az functionapp scale config set --resource-group <resourceGroup> --name <APP_NAME> --instance-memory 4096
 ```
 
 ### [Azure portal](#tab/azure-portal)

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

@@ -48,11 +48,11 @@ Flex Consumption expands on the traditional benefits of Consumption plan by addi
 
 When you create your function app in a Flex Consumption plan, you can select the memory size of the instances on which your app runs. See [Billing](#billing) to learn how instance memory sizes affect the costs of your function app. 
 
-Currently, Flex Consumption offers these instance memory size options: 512 MB, 2,048 MB, and 4,096 MB.
+Currently, Flex Consumption offers instance memory size options of both 2,048 MB and 4,096 MB.
 
 When deciding on which instance memory size to use with your apps, here are some things to consider:
 
-+ The 2,048-MB instance memory size is the default and should be used for most scenarios. The 512 MB and 4,096-MB instance memory sizes are available for scenarios that best suit your application's concurrency or processing power requirements. For more information, see [Configure instance memory](flex-consumption-how-to.md#configure-instance-memory). 
++ The 2,048-MB instance memory size is the default and should be used for most scenarios. Use the 4,096-MB instance memory size for scenarios where your app requires more concurrency or higher processing power. For more information, see [Configure instance memory](flex-consumption-how-to.md#configure-instance-memory). 
 + You can change the instance memory size at any time. For more information, see [Configure instance memory](flex-consumption-how-to.md#configure-instance-memory).
 + Instance resources are shared between your function code and the Functions host.
 + The larger the instance memory size, the more each instance can handle as far as concurrent executions or more intensive CPU or memory workloads. Specific scale decisions are workload-specific.
@@ -116,7 +116,6 @@ Currently, each region in a given subscription has a memory limit of 512,000 MB
 
 | Instance memory size (MB) | Max instance counts (per region) |
 | ----- | ---- |
-| `512 MB` | 1,000 |
 | `2048 MB` | 250 |
 | `4096 MB` | 125 |
 

articles/azure-functions/functions-app-settings.md

@@ -838,7 +838,7 @@ In the [Flex Consumption plan](./flex-consumption-plan.md), these site propertie
 | `properties.IsXenon` |Not valid|
 | `properties.windowsFxVersion` |Not valid|
 | `properties.alwaysOn` |Not valid|
-| `properties.siteConfig.preWarmedInstanceCount` | Renamed as `` |
+| `properties.siteConfig.preWarmedInstanceCount` | Renamed as `alwaysReadyInstances` |
 | `properties.siteConfig.functionAppScaleLimit` |Renamed as `maximumInstanceCount`|
 | `properties.containerSize` |Renamed as `instanceMemoryMB`|
 | `properties.javaVersion` | Replaced by `version` in `properties.functionAppConfig.runtime`|

articles/azure-functions/functions-concurrency.md

@@ -39,7 +39,6 @@ The Flex Consumption plan scales all HTTP trigger functions together as a group.
 
 | Instance size (MB) | Default concurrency<sup>*</sup> |
 | ---- | ---- |
-| `512` |  `4` |
 | `2048` | `16` |
 | `4096` | `32` |
 

articles/azure-functions/functions-scale.md

@@ -39,7 +39,7 @@ The following is a summary of the benefits of the various options for Azure Func
 |**[Flex Consumption plan]**| Get high scalability with compute choices, virtual networking, and pay-as-you-go billing.<br/><br/>On the Flex Consumption plan, instances of the Functions host are dynamically added and removed based on the configured per instance concurrency and the number of incoming events. <br/><br/> ✔ Reduce cold starts by specifying a number of pre-provisioned (always ready) instances.<br/> ✔ Supports virtual networking for added security.<br/>✔ Pay when your functions are running.<br/>✔ Scales automatically, even during periods of high load.| 
 |**[Premium plan]**|Automatically scales based on demand using prewarmed workers, which run applications with no delay after being idle, runs on more powerful instances, and connects to virtual networks. <br/><br/>Consider the Azure Functions Premium plan in the following situations: <br/><br/>✔ Your function apps run continuously, or nearly continuously.<br/>✔ You want more control of your instances and want to deploy multiple function apps on the same plan with event-driven scaling.<br/>✔ You have a high number of small executions and a high execution bill, but low GB seconds in the Consumption plan.<br/>✔ You need more CPU or memory options than are provided by consumption plans.<br/>✔ Your code needs to run longer than the maximum execution time allowed on the Consumption plan.<br/>✔ You require virtual network connectivity.<br/>✔ You want to provide a custom Linux image in which to run your functions. |  
 |**[Dedicated plan]** |Run your functions within an App Service plan at regular [App Service plan rates](https://azure.microsoft.com/pricing/details/app-service/windows/).<br/><br/>Best for long-running scenarios where [Durable Functions](durable/durable-functions-overview.md) can't be used. Consider an App Service plan in the following situations:<br/><br/>✔ You have existing and underutilized virtual machines that are already running other App Service instances.<br/>✔ You must have fully predictable billing, or you need to manually scale instances.<br/>✔ You want to run multiple web apps and function apps on the same plan<br/>✔ You need access to larger compute size choices.<br/>✔ Full compute isolation and secure network access provided by an App Service Environment (ASE).<br/>✔ Very high memory usage and high scale (ASE).|  
-| **[Container Apps]** | Create and deploy containerized function apps in a fully managed environment hosted by Azure Container Apps.<br/><br/>Use the Azure Functions programming model to build event-driven, serverless, cloud native function apps. Run your functions alongside other microservices, APIs, websites, and workflows as container-hosted programs. Consider the Azure Functions Premium plan in the following situations:<br/><br/>✔ You want to package custom libraries with your function code to support line-of-business apps.<br/>✔ You need to migration code execution from on-premises or legacy apps to cloud native microservices running in containers.<br/>✔ When you want to avoid the overhead and complexity of managing Kubernetes clusters and dedicated compute.<br/>✔ Your functions need high-end processing power provided by dedicated GPU compute resources. |  
+| **[Container Apps]** | Create and deploy containerized function apps in a fully managed environment hosted by Azure Container Apps.<br/><br/>Use the Azure Functions programming model to build event-driven, serverless, cloud native function apps. Run your functions alongside other microservices, APIs, websites, and workflows as container-hosted programs. Consider hosting your functions on Container Apps in the following situations:<br/><br/>✔ You want to package custom libraries with your function code to support line-of-business apps.<br/>✔ You need to migration code execution from on-premises or legacy apps to cloud native microservices running in containers.<br/>✔ When you want to avoid the overhead and complexity of managing Kubernetes clusters and dedicated compute.<br/>✔ Your functions need high-end processing power provided by dedicated GPU compute resources. |  
 
 The remaining tables in this article compare hosting options based on various features and behaviors. 
 

articles/azure-functions/monitor-functions-reference.md

@@ -31,7 +31,7 @@ These metrics are used specifically when [estimating Consumption plan costs](fun
 
 #### [Flex Consumption plan](#tab/flex-consumption-plan)
 
-These metrics are used to estimate the costs associated with _on demand_ and _always ready_ meters used for billing:
+These metrics are used to estimate the costs associated with _on demand_ and _always ready_ meters used for billing in a [Flex Consumption plan]:
 
 | Metric | Description | Meter calculation |
 | ------ | ---------- | ----------------- |
@@ -41,7 +41,7 @@ These metrics are used to estimate the costs associated with _on demand_ and _al
 | **AlwaysReadyFunctionExecutionUnits** | Total MB-millseconds from always ready instances while actively executing functions. | `AlwaysReadyFunctionExecutionUnits / 1,024,000` is the Always Ready Execution Time meter, in GB-seconds. |
 | **AlwaysReadyUnits** | The total MB-millseconds of always ready instances assigned to the app, whether or not functions are actively executing. | `AlwaysReadyUnits / 1,024,000` is the Always Ready Baseline meter, in GB-seconds. |
 
-In this table, all execution units are calculated by multipling the fixed instance memory size, such as 512 MB and 2,048 MB, by total execution times, in milliseconds.
+In this table, all execution units are calculated by multipling the fixed instance memory size, such as 2,048 MB or 4,096 MB, by total execution times, in milliseconds.
 
 ---
 

includes/functions-limits.md

@@ -37,6 +37,6 @@ Notes on service limits:
 10. Including the production slot.  
 11. There's currently a limit of 5000 function apps in a given subscription. 
 12. The Flex Consumption plan is currently in preview.  
-13. Flex Consumption plan instance sizes are defined as: 512 MB, 2,048 MB, and 4,096 MB. For more information, see [Instance memory](../articles/azure-functions/flex-consumption-plan.md#instance-memory).  
+13. Flex Consumption plan instance sizes are currently defined as either 2,048 MB or 4,096 MB. For more information, see [Instance memory](../articles/azure-functions/flex-consumption-plan.md#instance-memory).  
 14. 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](../articles/azure-functions/flex-consumption-plan.md#instance-memory).
 15. In a Flex Consumption plan, the host doesn't enforce an execution time limit. However, there are currently no guarantees because the platform might need to terminate your instances during scale-in, deployments, or to apply updates.

includes/functions-publish-project-cli.md

@@ -8,6 +8,6 @@ ms.author: glenga
 
 ## Deploy the function project to Azure
 
-After you've successfully created your function app in Azure, you're now ready to deploy your local functions project by using the [func azure functionapp publish](../articles/azure-functions/functions-run-local.md#project-file-deployment) command.  
+After you've successfully created your function app in Azure, you're now ready to deploy your local functions project by using the [`func azure functionapp publish`](../articles/azure-functions/functions-run-local.md#project-file-deployment) command.  
 
 [!INCLUDE [functions-publish-project-cli-clean](functions-publish-project-cli-clean.md)]