Merge pull request #299196 from ggailey777/freshness

[Functions] Update VS quickstart to Flex plan + Freshness

Author: v-ccolin

articles/azure-functions/functions-create-your-first-function-visual-studio.md

@@ -3,7 +3,7 @@ title: "Quickstart: Create your first C# function in Azure using Visual Studio"
 description: "In this quickstart, you learn how to use Visual Studio to create and publish a C# HTTP triggered function to Azure Functions."
 ms.assetid: 82db1177-2295-4e39-bd42-763f6082e796
 ms.topic: quickstart
-ms.date: 02/28/2023
+ms.date: 05/01/2025
 ms.devlang: csharp
 ms.custom: devx-track-csharp, mvc, devcenter, vs-azure, 23113853-34f2-4f, mode-ui, ai-video-demo
 ai-usage: ai-assisted
@@ -95,7 +95,7 @@ After you've verified that the function runs correctly on your local computer, i
 
 ## Publish the project to Azure
 
-Visual Studio can publish your local project to Azure. Before you can publish your project, you must have a function app in your Azure subscription. If you don't already have a function app in Azure, Visual Studio publishing creates one for you the first time you publish your project. In this article, you create a function app and related Azure resources.
+Visual Studio can publish your local project to Azure. Before you can publish your project, you must have a function app in your Azure subscription. If you don't already have a function app in Azure, Visual Studio can help you create one before you publish your project. In this article, you create a function app that runs on Linux in a Flex Consumption plan, which is the recommended plan for event-driven and secure serverless functions.
 
 [!INCLUDE [Publish the project to Azure](../../includes/functions-vstools-publish.md)]
 
@@ -105,7 +105,7 @@ Visual Studio can publish your local project to Azure. Before you can publish yo
 
 1. Under **Functions**, select your new function named **HttpExample**, then in the function page select **Get function URL** and then the **Copy to clipboard icon**. 
 
-1. In the address bar in your browser, paste the URL you just copied and run the request.
+1. In the address bar in your browser, paste the URL you copied and run the request.
 
     The URL that calls your HTTP trigger function is in the following format:
 
@@ -119,7 +119,7 @@ Visual Studio can publish your local project to Azure. Before you can publish yo
 
 *Resources* in Azure refer to function apps, functions, storage accounts, and so forth. They're grouped into *resource groups*, and you can delete everything in a group by deleting the group.
 
-You created Azure resources to complete this quickstart. You may be billed for these resources, depending on your [account status](https://azure.microsoft.com/account/) and [service pricing](https://azure.microsoft.com/pricing/). Other quickstarts in this collection build upon this quickstart. If you plan to work with subsequent quickstarts, tutorials, or with any of the services you've created in this quickstart, don't clean up the resources.
+You created Azure resources to complete this quickstart. You could be billed for these resources, depending on your [account status](https://azure.microsoft.com/account/) and [service pricing](https://azure.microsoft.com/pricing/). Other quickstarts in this collection build upon this quickstart. If you plan to work with subsequent quickstarts, tutorials, or with any of the services you've created in this quickstart, don't clean up the resources.
 
 [!INCLUDE [functions-vstools-cleanup](../../includes/functions-vstools-cleanup.md)]
 

articles/azure-functions/functions-premium-plan.md

@@ -3,7 +3,7 @@ title: Azure Functions Premium plan
 description: Learn about details and configuration options (virtual network, no cold start, unlimited execution duration) for the Azure Functions Premium plan.
 author: nzthiago
 ms.topic: concept-article
-ms.date: 04/04/2025
+ms.date: 05/01/2025
 ms.author: thalme
 ms.custom: references_regions, fasttrack-edit, devx-track-azurepowershell, build-2024
 ---
@@ -56,21 +56,21 @@ In the Premium plan, you can have your app always ready on a specified number of
 
 This app-level setting also controls your plan's minimum instances. For example, consider having three function apps in the same Premium plan. When two of your apps have always-ready instance count set to one, and the third app is set to five, the minimum number for your whole plan is five. This also reflects the minimum number of instances for which your plan is billed. The maximum number of always-ready instances we support per app is 20.
 
-# [Portal](#tab/portal)
+#### [Portal](#tab/portal)
 
 You can configure the number of always ready instances in the Azure portal by selecting your **Function App**, going to the **Platform Features** tab, and selecting the **Scale Out** options. In the function app edit window, always ready instances are specific to that app.
 
 :::image type="content" source="media/functions-premium-plan/scale-out.png" alt-text="Screenshot that shows the elastic scale settings in the portal.":::
 
-# [Azure CLI](#tab/azurecli)
+#### [Azure CLI](#tab/azurecli)
 
 You can also configure always ready instances for an app by using the Azure CLI.
 
 ```azurecli-interactive
 az functionapp update -g <RESOURCE_GROUP> -n <FUNCTION_APP_NAME> --set siteConfig.minimumElasticInstanceCount=<YOUR_ALWAYS_READY_COUNT>
 ```
 
-# [Azure PowerShell](#tab/azure-powershell)
+#### [Azure PowerShell](#tab/azure-powershell)
 
 You can also configure always ready instances for an app by using Azure PowerShell.
 
@@ -99,19 +99,19 @@ Consider this example that shows how always ready instances and prewarmed instan
 1. As load increases and your app needs more instances to handle HTTP traffic, that prewarmed instance is swapped to an active instance. HTTP load is now routed to all three instances, and a fourth instance is instantly provisioned to fill the prewarmed buffer.
 1. This sequence of scaling and prewarming continues until the maximum instance count for the app is reached or load decreases causing the platform to scale back in after a period. No instances are prewarmed or activated beyond the maximum.
 
-# [Portal](#tab/portal)
+#### [Portal](#tab/portal)
 
 You can't change the prewarmed instance count setting in the portal. You must instead use the Azure CLI or Azure PowerShell.
 
-# [Azure CLI](#tab/azurecli)
+#### [Azure CLI](#tab/azurecli)
 
 You can modify the number of prewarmed instances for an app using the Azure CLI.
 
 ```azurecli-interactive
 az functionapp update -g <RESOURCE_GROUP> -n <FUNCTION_APP_NAME> --set siteConfig.preWarmedInstanceCount=<YOUR_PREWARMED_COUNT>
 ```
 
-# [Azure PowerShell](#tab/azure-powershell)
+#### [Azure PowerShell](#tab/azure-powershell)
 
 You can modify the number of prewarmed instances for an app using the Azure PowerShell.
 

includes/functions-vstools-publish.md

@@ -2,20 +2,18 @@
 author: ggailey777
 ms.service: azure-functions
 ms.topic: include
-ms.date: 01/30/2024
+ms.date: 05/01/2025
 ms.author: glenga
 ms.custom: devdivchpfy22
 ---
 
 1. In **Solution Explorer**, right-click the project and select **Publish**. In **Target**, select **Azure**, and then select **Next**.
 
-    :::image type="content" source="media/functions-vstools-publish/functions-vs-publish.png" alt-text="Screenshot of the publish pane.":::
+1. On **Specific target**, select **Azure Function App (Linux)** and then select **Next**. 
 
-1. On **Specific target**, select **Azure Function App (Windows)**. A function app that runs on Windows is created. Select **Next**.
+    The Flex Consumption plan requires Linux.
 
-    :::image type="content" source="media/functions-vstools-publish/functions-vs-specific-target.png" alt-text="Screenshot of publish pane that has a specific target.":::
-
-1. On **Functions instance**, select **Create a new Azure Function**.
+1. On **Functions instance**, select **Create new**.
 
     :::image type="content" source="media/functions-vstools-publish/functions-vs-functions-instance.png" alt-text="Screenshot that shows Create a new function app instance.":::
 
@@ -24,22 +22,19 @@ ms.custom: devdivchpfy22
     | Setting      | Value  | Description                                |
     | ------------ |  ------- | -------------------------------------------------- |
     | **Name** | Globally unique name | Name that uniquely identifies your new function app. Accept this name or enter a new name. Valid characters are: `a-z`, `0-9`, and `-`. |
-    | **Subscription** | Your subscription | The Azure subscription to use. Accept this subscription or select a new one from the dropdown list. |
+    | **Subscription name** | Name of your subscription | The Azure subscription to use. Accept this subscription or select a new one from the dropdown list. |
     | **[Resource group](../articles/azure-resource-manager/management/overview.md)** | Name of your resource group |  The resource group in which you want to create your function app. Select **New** to create a new resource group. You can also choose to use an existing resource group from the dropdown list. |
-    | **[Plan Type](../articles/azure-functions/functions-scale.md)** | Consumption | When you publish your project to a function app that runs in a [Consumption plan](../articles/azure-functions/consumption-plan.md), you pay only for executions of your functions app. Other hosting plans incur higher costs. |
-    | **Location** | Location of the app service | Select a **Location** in an [Azure region](https://azure.microsoft.com/regions/) near you or other services your functions access. |
+    | **[Plan Type](../articles/azure-functions/functions-scale.md)** | Flex Consumption | When you publish your project to a function app that runs in a [Flex Consumption plan](../articles/azure-functions/flex-consumption-plan.md), you might pay only for executions of your functions app. Other hosting plans can incur higher costs. |
+    | **Location** | Location of the app service | Select a **Location** in a [Azure region supported by the Flex Consumption plan](../articles/azure-functions/flex-consumption-how-to.md#view-currently-supported-regions). |
+    | **Instance memory size** | 2048 | The [memory size of the virtual machine instances](../articles/azure-functions/flex-consumption-plan.md#instance-memory) in which the app runs, which is unique to the Flex Consumption plan. |  
     | **[Azure Storage](../articles/azure-functions/storage-considerations.md)** | General-purpose storage account | An Azure storage account is required by the Functions runtime. Select **New** to configure a general-purpose storage account. You can also choose to use an existing account that meets the [storage account requirements](../articles/azure-functions/storage-considerations.md#storage-account-requirements).  |
     | **[Application Insights](../articles/azure-functions/functions-monitoring.md)** | Application Insights instance | You should enable Azure Application Insights integration for your function app. Select **New** to create a new instance, either in a new or in an existing Log Analytics workspace. You can also choose to use an existing instance.  |
 
     :::image type="content" source="./media/functions-vstools-publish/functions-vs-function-app.png" alt-text="Screenshot of the Create App Service dialog.":::
 
 1. Select **Create** to create a function app and its related resources in Azure. The status of resource creation is shown in the lower-left corner of the window.
 
-1. On **Functions instance**, make sure that the **Run from package file** checkbox is selected. Your function app is deployed by using [Zip Deploy](../articles/azure-functions/functions-deployment-technologies.md#zip-deploy) with [Run-From-Package](../articles/azure-functions/run-functions-from-deployment-package.md) mode enabled. Zip Deploy is the recommended deployment method for your functions project for better performance.
-
-    :::image type="content" source="media/functions-vstools-publish/functions-vs-publish-profile-step-4.png" alt-text="Screenshot of the Finish profile creation pane.":::
-
-1. Select **Finish**, and on the **Publish** pane, select **Publish** to deploy the package that contains your project files to your new function app in Azure.
+1. Select **Finish**, and then on the **Publish** tab select **Publish** to deploy the package that contains your project files to your new function app in Azure.
 
     When deployment is completed, the root URL of the function app in Azure is shown on the **Publish** tab.