Create and manage function apps in the Flex Consumption plan

1. If you haven't done so already, sign in to Azure:

   az login
   

   The az login command signs you into your Azure account.

2. Use the az functionapp list-flexconsumption-locations command to review the list of regions that currently support Flex Consumption.

   az functionapp list-flexconsumption-locations --output table
   

3. Create a resource group in one of the currently supported regions:

   az group create --name <RESOURCE_GROUP> --location <REGION>
   

   In the above command, replace <RESOURCE_GROUP> with a value that's unique in your subscription and <REGION> with one of the currently supported regions. The az group create command creates a resource group.

4. Create a general-purpose storage account in your resource group and region:

   az storage account create --name <STORAGE_NAME> --location <REGION> --resource-group <RESOURCE_GROUP> --sku Standard_LRS --allow-blob-public-access false
   

   In the previous example, replace <STORAGE_NAME> with a name that is appropriate to you and unique in Azure Storage. Names must contain three to 24 characters numbers and lowercase letters only. Standard_LRS specifies a general-purpose account, which is supported by Functions. The az storage account create command creates the storage account.

   Important

   The storage account is used to store important app data, sometimes including the application code itself. You should limit access from other apps and users to the storage account.

5. Create the function app in Azure:

   az functionapp create --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage-account <STORAGE_NAME> --flexconsumption-location <REGION> --runtime dotnet-isolated --runtime-version 8.0 
   

   C# apps that run in-process aren't currently supported when running in a Flex Consumption plan.

   az functionapp create --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage-account <STORAGE_NAME> --flexconsumption-location <REGION> --runtime java --runtime-version 17 
   

   For Java apps, Java 11 is also currently supported.

   az functionapp create --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage-account <STORAGE_NAME> --flexconsumption-location <REGION> --runtime node --runtime-version 20 
   

   az functionapp create --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage-account <STORAGE_NAME> --flexconsumption-location <REGION> --runtime python --runtime-version 3.11 
   

   For Python apps, Python 3.10 is also currently supported.

   az functionapp create --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage-account <STORAGE_NAME> --flexconsumption-location <REGION> --runtime powershell --runtime-version 7.4 
   

   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.

   Because you created the app without specifying always ready instances, 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.

1. In the Azure portal, from the menu or the Home page, select Create a resource.

2. Select Get started and then Create under Function App.

3. Under Select a hosting option, choose Flex Consumption > Select.

4. On the Basics page, use the function app settings as specified in the following table:

   Expand table

   Setting	Suggested value	Description
   Subscription	Your subscription	The subscription in which you create your new function app.
   Resource Group	myResourceGroup	Name for the new resource group in which you create your function app.
   Function App name	Globally unique name	Name that identifies your new function app. Valid characters are a-z (case insensitive), 0-9, and -.
   Region	Preferred region	Select a region that's near you or near other services that your functions can access. Unsupported regions aren't displayed. For more information, see View currently supported regions.
   Runtime stack	Preferred language	Choose one of the supported language runtime stacks. In-portal editing using Visual Studio Code for the Web is currently only available for Node.js, PowerShell, and Python apps. C# class library and Java functions must be developed locally.
   Version	Language version	Choose a supported version of your language runtime stack.
   Instance size	Default	Determines the amount of instance memory allocated for each instance of your app. For more information, see Instance memory.

5. Accept the default options in the remaining tabs, including the default behavior of creating a new storage account on the Storage tab and a new Application Insight instance on the Monitoring tab. You can also choose to use an existing storage account or Application Insights instance.

6. Select Review + create to review the app configuration you chose, and then select Create to provision and deploy the function app.

7. Select the Notifications icon in the upper-right corner of the portal and watch for the Deployment succeeded message.

8. Select Go to resource to view your new function app. You can also select Pin to dashboard. Pinning makes it easier to return to this function app resource from your dashboard.

1. Press F1, and in the command pallet enter Azure Functions: Create function app in Azure...(Advanced).

2. If you're not signed in, you're prompted to Sign in to Azure. You can also Create a free Azure account. After signing in from the browser, go back to Visual Studio Code.

3. Following the prompts, provide this information:

   Expand table

   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.
   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 near you or near other services that your functions access. Unsupported regions aren't displayed. For more information, see View currently supported regions.
   Select a storage account.	Choose Create new storage account and at the prompt provide a globally unique name for the new storage account used by your function app and then select Enter. Storage account names must be between 3 and 24 characters long and can contain only numbers and lowercase letters. You can also select an existing account.
   Select an Application Insights resource for your app.	Choose Create new Application Insights resource and at the prompt provide the name for the instance used to store runtime data from your functions.

   A notification appears after your function app is created. Select View Output in this notification to view the creation and deployment results, including the Azure resources that you created.

1. In the command palette, enter and then select Azure Functions: Deploy to Function App.

2. Select the function app you just created. When prompted about overwriting previous deployments, select Deploy to deploy your function code to the new function app resource.

3. When deployment is completed, select View Output to view the creation and deployment results, including the Azure resources that you created. If you miss the notification, select the bell icon in the lower-right corner to see it again.

   

In your root project folder, run this func azure functionapp publish command:

func azure functionapp publish <APP_NAME>

In this example, replace <APP_NAME> with the name of your app. A successful deployment shows results similar to the following output (truncated for simplicity):

...

Getting site publishing info...
Creating archive for current directory...
Performing remote build for functions project.

...

Deployment successful.
Remote build succeeded!
Syncing triggers...
Functions in msdocs-azurefunctions-qs:
    HttpExample - [httpTrigger]
        Invoke url: https://msdocs-azurefunctions-qs.azurewebsites.net/api/httpexample

You can enable virtual network integration by running the az functionapp create command and including the --vnet and --subnet parameters.

1. Create the virtual network and subnet, if you haven't already done so.

2. Complete steps 1-4 in Create a Flex Consumption app to create the resources required by your app.

3. Run the az functionapp create command, including the --vnet and --subnet parameters, as in this example:

   az functionapp create --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage-account <STORAGE_NAME> --flexconsumption-location <REGION> --runtime <RUNTIME_NAME> --runtime-version <RUNTIME_VERSION> --vnet <VNET_RESOURCE_ID> --subnet <SUBNET_NAME>
   

   The <VNET_RESOURCE_ID> value is the resource ID for the virtual network, which is in the format: /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.Network/virtualNetworks/<VNET_NAME>. You can use this command to get a list of virtual network IDs, filtered by <RESOURCE_GROUP>: az network vnet list --resource-group <RESOURCE_GROUP> --output tsv --query "[]".id.

Use these steps to create your function app with virtual network integration and related Azure resources.

1. In the Azure portal, from the menu or the Home page, select Create a resource.

2. Select Get started and then Create under Function App.

3. Under Select a hosting option, choose Flex Consumption > Select.

4. On the Basics page, use the function app settings as specified in the following table:

   Expand table

   Setting	Suggested value	Description
   Subscription	Your subscription	The subscription in which you create your new function app.
   Resource Group	myResourceGroup	Name for the new resource group in which you create your function app.
   Function App name	Globally unique name	Name that identifies your new function app. Valid characters are a-z (case insensitive), 0-9, and -.
   Region	Preferred region	Select a region that's near you or near other services that your functions can access. Unsupported regions aren't displayed. For more information, see View currently supported regions.
   Runtime stack	Preferred language	Choose one of the supported language runtime stacks. In-portal editing using Visual Studio Code for the Web is currently only available for Node.js, PowerShell, and Python apps. C# class library and Java functions must be developed locally.
   Version	Language version	Choose a supported version of your language runtime stack.
   Instance size	Default	Determines the amount of instance memory allocated for each instance of your app. For more information, see Instance memory.

5. Accept the default options in the remaining tabs, including the default behavior of creating a new storage account on the Storage tab and a new Application Insight instance on the Monitoring tab. You can also choose to use an existing storage account or Application Insights instance.

6. In the Networking tab, set Enable public access to Off and Enable network injection to On.

7. For Virtual network, select or create a virtual network that is in the same region as your app.

8. Set Enable VNet integration to On and select or create a subnet.

9. Select Review + create to review the app configuration you chose, and then select Create to provision and deploy the function app with virtual networking.

10. Select the Notifications icon in the upper-right corner of the portal and watch for the Deployment succeeded message.

11. Select Go to resource to view your new function app. You can also select Pin to dashboard. Pinning makes it easier to return to this function app resource from your dashboard.

You can't currently enable virtual networking when you use Visual Studio Code to create your app.

Use the az functionapp vnet-integration add command to enable virtual network integration to an existing function app:

az functionapp vnet-integration add --resource-group <RESOURCE_GROUP> --name <APP_NAME> --vnet <VNET_RESOURCE_ID> --subnet <SUBNET_NAME>

Use the az functionapp vnet-integration remove command to disable virtual network integration in your app:

az functionapp vnet-integration remove --resource-group <RESOURCE_GROUP> --name <APP_NAME>

Use the az functionapp vnet-integration list command to list the current virtual network integrations for your app:

az functionapp vnet-integration list --resource-group <RESOURCE_GROUP> --name <APP_NAME>

You can integrate your existing app with an existing virtual network and subnet in the portal.

1. In your function app page in the Azure portal, expand Settings in the left menu and select Networking.

2. Under Outbound traffic configuration, select Not configured.

3. In the Virtual Network Integration page, select Add virtual network integration.

4. Select an existing Virtual network and Subnet and select Connect.

You can't currently configure virtual networking in Visual Studio Code.

Use the az functionapp create command and supply these additional options that customize deployment storage:

This example creates a function app in the Flex Consumption plan with a separate deployment storage account and user assigned identity:

az functionapp create --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage <STORAGE_NAME> --runtime dotnet-isolated --runtime-version 8.0 --flexconsumption-location "<REGION>" --deployment-storage-name <DEPLOYMENT_ACCOUNT_NAME> --deployment-storage-container-name <DEPLOYMENT_CONTAINER_NAME> --deployment-storage-auth-type UserAssignedIdentity --deployment-storage-auth-value <MI_RESOURCE_ID>

You can't currently configure deployment storage when creating your app in the Azure portal. To configure deployment storage during app creation, instead use the Azure CLI to create your app.

You can use the portal to modify the deployment settings of an existing app, as detailed in the next section.

You can't currently configure deployment storage when creating your app in Azure using Visual Studio Code.

Use the az functionapp deployment config set command to modify the deployment storage configuration:

az functionapp deployment config set --resource-group <RESOURCE_GROUP> --name <APP_NAME> --deployment-storage-name <DEPLOYMENT_ACCOUNT_NAME> --deployment-storage-container-name <DEPLOYMENT_CONTAINER_NAME>

1. In your function app page in the Azure portal, expand Settings in the left menu and select Deployment settings.

2. Under Application package location, select an existing Storage account and then select an existing empty container in the account.

3. Under Storage authentication, select your preferred authentication type

   • If you selected Connection string, select the name of the app setting that contains the connection string for the deployment storage account.

   • If you selected User assigned identity, select the identity you would like to use.

4. Select Save to update the app.

You can't currently configure deployment storage for your app in Azure using Visual Studio Code.

Specify the --instance-memory parameter in your az functionapp create command. This example creates a C# app with an instance size of 4096:

az functionapp create --instance-memory 4096 --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage-account <STORAGE_NAME> --flexconsumption-location <REGION> --runtime dotnet-isolated --runtime-version 8.0

When you create your app in a Flex Consumption plan in the Azure portal, you can choose your instance memory size in the Instance size field in the Basics tab. For more information, see Create a Flex Consumption app.

You can't currently control the instance memory size when you use Visual Studio Code to create your app. The default size is used.

This example uses the az functionapp scale config set command to change the instance memory size setting to 4,096 MB:

az functionapp scale config set --resource-group <resourceGroup> --name <APP_NAME> --instance-memory 4096

1. In your function app page in the Azure portal, expand Settings in the left menu and select Scale and concurrency.

2. Select an Instance memory option and select Save to update the app.

You can't currently change the instance memory size setting for your app using Visual Studio Code.

Use the --always-ready-instances parameter with the az functionapp create command to define one or more always ready instance designations. This example sets the always ready instance count for all HTTP triggered functions to 5:

az functionapp create --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage <STORAGE_NAME> --runtime <LANGUAGE_RUNTIME> --runtime-version <RUNTIME_VERSION> --flexconsumption-location <REGION> --always-ready-instances http=10

This example sets the always ready instance count for all Durable trigger functions to 3 and sets the always ready instance count to 2 for a service bus triggered function named function5:

az functionapp create --resource-group <RESOURCE_GROUP> --name <APP_NAME> --storage <STORAGE_NAME> --runtime <LANGUAGE_RUNTIME> --runtime-version <RUNTIME_VERSION> --flexconsumption-location <REGION> --always-ready-instances durable=3 function:function5=2

You can't currently define always ready instances when creating your app in the Azure portal. To define always ready instances during app creation, instead use the Azure CLI to create your app.

You can use the portal to modify always ready instances on an existing app, as detailed in the next section.

You can't currently define always ready instances when creating your app in Azure using Visual Studio Code.

This example uses the az functionapp scale config always-ready set command to change the always ready instance count for the HTTP triggers group to 10:

az functionapp scale config always-ready set --resource-group <RESOURCE_GROUP> --name <APP_NAME> --settings http=10

To remove always ready instances, use the az functionapp scale config always-ready delete command, as in this example that removes all always ready instances from both the HTTP triggers group and also a function named hello_world:

az functionapp scale config always-ready delete --resource-group <RESOURCE_GROUP> --name <APP_NAME> --setting-names http function:hello_world

1. In your function app page in the Azure portal, expand Settings in the left menu and select Scale and concurrency.

2. Under Always-ready instance minimum type http, blob, durable, or a specific function name using the format function:<FUNCTION_NAME>=n in Trigger and type the Number of always-ready instances.

3. Select Save to update the app.

You can't currently modify always ready instances using Visual Studio Code.

Use the az functionapp scale config set command to set specific HTTP concurrency limits for your app, regardless of instance size.

az functionapp scale config set --resource-group <RESOURCE_GROUP> --name <APP_NAME> --trigger-type http --trigger-settings perInstanceConcurrency=10

This example sets the HTTP trigger concurrency level to 10. After you specifically set an HTTP concurrency value, that value is maintained despite any changes in your app's instance size setting.

1. In your function app page in the Azure portal, expand Settings in the left menu and select Scale and concurrency.

2. Under Concurrency per instance select Assign manually and type a specific limit.

3. Select Save to update the app.

You can't currently set HTTP concurrency limits using Visual Studio Code.