You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/flex-consumption-plan.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,6 +77,8 @@ Flex Consumption includes an _always ready_ feature that lets you choose instanc
77
77
78
78
For example, if you set always ready to 2 for your HTTP group of functions, the platform keeps two instances always running and assigned to your app for your HTTP functions in the app. Those instances are processing your function executions, but depending on concurrency settings, the platform scales beyond those two instances with on-demand instances.
79
79
80
+
No less than two always-ready instances can be configured per function or function group while [zone redundancy is enabled](../reliability/reliability-functions.md?pivots=flex-consumption-plan#availability-zone-support).
81
+
80
82
To learn how to configure always ready instances, see [Set always ready instance counts](flex-consumption-how-to.md#set-always-ready-instance-counts).
81
83
82
84
## Concurrency
@@ -131,7 +133,8 @@ In Flex Consumption many of the standard application settings and site configura
131
133
132
134
Keep these other considerations in mind when using Flex Consumption plan:
133
135
134
-
+**Host**: There's a 30-second time out for app initialization. When your function app takes longer than 30 seconds to start, you might see gRPC-related `System.TimeoutException` entries logged. You can't currently configure this time out. For more information, see [this host work item](https://github.com/Azure/azure-functions-host/issues/10482).
136
+
+**Apps per Plan**: Only one app is allowed per Flex Consumption plan.
137
+
+**Host**: There's a 30-second time-out for app initialization. When your function app takes longer than 30 seconds to start, you might see gRPC-related `System.TimeoutException` entries logged. You can't currently configure this time-out. For more information, see [this host work item](https://github.com/Azure/azure-functions-host/issues/10482).
135
138
+**Durable Functions**: Azure Storage is currently the only supported [storage provider](./durable/durable-functions-storage-providers.md) for Durable Functions when hosted in the Flex Consumption plan. See [recommendations](./durable/durable-functions-azure-storage-provider.md#flex-consumption-plan) when hosting Durable Functions in the Flex Consumption plan.
136
139
+**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`.
137
140
+**Triggers**: While all triggers are fully supported in a Flex Consumption plan, 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.
@@ -142,7 +145,7 @@ Keep these other considerations in mind when using Flex Consumption plan:
142
145
+**Diagnostic settings**: Diagnostic settings aren't currently supported.
143
146
+**Certificates**: Loading certificates with the WEBSITE_LOAD_CERTIFICATES app setting, managed certificates, app service certificates, and other platform certificate-based features are currently not supported.
144
147
+**Key Vault and App Configuration References**: You can't currently use [Azure Key Vault](../app-service/app-service-key-vault-references.md) or [Azure App Configuration](../app-service/app-service-configuration-references.md) references in your Flex Consumption plan app settings when these services are network access restricted. This limitation applies even when the function app has Virtual Network integration enabled. If you must use restricted Key Vault or App Configuration instances, you must use client SDKs to manually retrieve values from references in these services. Functions binding extensions also can't access these references, which means you must also use Azure client SDKs for accessing remote service data from your function code.
145
-
+**Timezones**: `WEBSITE_TIME_ZONE` and `TZ` app settings are not currently supported when running on Flex Consumption plan.
148
+
+**Timezones**: `WEBSITE_TIME_ZONE` and `TZ` app settings aren't currently supported when running on Flex Consumption plan.
Azure Functions lets you run your code in a serverless environment without having to first create a virtual machine (VM) or publish a web application. In this article, you learn how to use Azure Functions to create a "hello world" HTTP trigger function in the Azure portal.
13
-
14
-
Choose your preferred programming language at the top of the article.
15
-
16
-
::: zone pivot="programming-language-csharp"
17
-
>[!NOTE]
18
-
>Editing your C# function code in the Azure portal is currently only supported for [C# script (.csx) functions](functions-reference-csharp.md). To learn more about the limitations on editing function code in the Azure portal, see [Development limitations in the Azure portal](functions-how-to-use-azure-function-app-settings.md#development-limitations-in-the-azure-portal).
19
-
>
20
-
> You should instead [develop your functions locally](functions-develop-local.md) and publish to a function app in Azure. Use one of the following links to get started with your chosen local development environment:
>Editing your Java function code in the Azure portal isn't currently supported. For more information, see [Development limitations in the Azure portal](functions-how-to-use-azure-function-app-settings.md#development-limitations-in-the-azure-portal).
28
-
>
29
-
> You should instead [develop your functions locally](functions-develop-local.md) and publish to a function app in Azure. Use one of the following links to get started with your chosen local development environment:
>+[Visual Studio Code](create-first-function-vs-code-java.md)
37
-
::: zone-end
38
-
::: zone pivot="programming-language-javascript"
39
-
>[!NOTE]
40
-
>Because of [development limitations in the Azure portal](functions-how-to-use-azure-function-app-settings.md#development-limitations-in-the-azure-portal), you should instead [develop your functions locally](functions-develop-local.md) and publish to a function app in Azure. Use one of the following links to get started with your chosen local development environment:
41
-
>+[Visual Studio Code](./create-first-function-vs-code-node.md)
>Because of [development limitations in the Azure portal](functions-how-to-use-azure-function-app-settings.md#development-limitations-in-the-azure-portal), you should instead [develop your functions locally](functions-develop-local.md) and publish to a function app in Azure. Use one of the following links to get started with your chosen local development environment:
47
-
>+[Visual Studio Code](./create-first-function-vs-code-python.md)
>Editing your TypeScript function code in the Azure portal isn't currently supported. For more information, see [Development limitations in the Azure portal](functions-how-to-use-azure-function-app-settings.md#development-limitations-in-the-azure-portal).
53
-
>
54
-
> You should instead [develop your functions locally](functions-develop-local.md) and publish to a function app in Azure. Use one of the following links to get started with your chosen local development environment:
55
-
>+[Visual Studio Code](./create-first-function-vs-code-typescript.md)
>Because of [development limitations in the Azure portal](functions-how-to-use-azure-function-app-settings.md#development-limitations-in-the-azure-portal), you should instead [develop your functions locally](functions-develop-local.md) and publish to a function app in Azure. Use one of the following links to get started with your chosen local development environment:
61
-
>+[Visual Studio Code](./create-first-function-vs-code-powershell.md)
Please review the [known issues](./recover-python-functions.md#development-issues-in-the-azure-portal) for development of Azure Functions using Python in the Azure portal.
9
+
# Create a function app in the Azure portal
10
+
11
+
This article shows you how to use the Azure portal to create a function app that's hosted in Azure Functions. These hosting plan options, which support dynamic, event-driven scaling, are featured:
12
+
13
+
| Hosting option | Description |
14
+
| ----- | ----- |
15
+
|[Flex Consumption plan](./flex-consumption-plan.md)| Linux-only plan that provides rapid horizontal scaling with support for managed identities, virtual networking, and pay-as-you-go billing. |
16
+
|[Premium plan](./functions-premium-plan.md)| Provides longer execution times, more control over CPU/memory, and support for containers and virtual networks. |
17
+
|[Consumption plan](./consumption-plan.md)| Original dynamic hosting plan, which supports portal development for some languages. |
18
+
19
+
Choose your preferred hosting plan at the [top](#top) of the article. For more information about all supported hosting options, see [Azure Functions hosting options](functions-scale.md).
66
20
67
21
## Prerequisites
68
22
@@ -76,46 +30,44 @@ Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
76
30
77
31
You must have a function app to host the execution of your functions. A function app lets you group functions as a logical unit for easier management, deployment, scaling, and sharing of resources.
78
32
79
-
Use these steps to create your function app and related Azure resources, whether or not you're able to edit your code in the Azure portal.
80
-
::: zone pivot="programming-language-csharp"
81
-
To be able to create a C# script app that you can edit in the portal, choose **8 (LTS), in-process model** for .NET **Version**.
82
-
::: zone-end
83
-
84
-
[!INCLUDE [Create function app Azure portal](../../includes/functions-create-function-app-portal.md)]
33
+
Use these steps to create your function app and related Azure resources in the Azure portal.
85
34
86
-
Next, create a function in the new function app.
35
+
::: zone pivot="flex-consumption-plan"
36
+
1. From the Azure portal menu or the **Home** page, select **Create a resource**.
87
37
88
-
::: zone pivot="programming-language-python,programming-language-javascript,programming-language-powershell,programming-language-csharp"
89
-
## <aname="create-function"></a>Create an HTTP trigger function
38
+
1. In the **New** page, select **Function App**.
90
39
91
-
1.In your function app, select **Overview**, and then select **+ Create**under**Functions**. If you don't see the **+ Create** button, you must instead [create your functions locally](./functions-develop-local.md).
40
+
1.Under **Select a hosting option**, select **Flex Consumption**>**Select** to create your app in a [Flex Consumption plan](flex-consumption-plan.md). In this [serverless](https://azure.microsoft.com/overview/serverless-computing/) hosting option, you pay only for the time your functions run. To learn more about different hosting plans, see [Overview of plans](functions-scale.md#overview-of-plans).
92
41
93
-
1.Under **Select a template**, scroll down and choose the **HTTP trigger** template.
42
+
1.On the **Basics** page, use the function app settings as specified in the following table:
94
43
95
-
1. In **Template details**, use `HttpExample` for **New Function**, select **Anonymous** from the **[Authorization level](functions-bindings-http-webhook-trigger.md#http-auth)** drop-down list, and then select **Create**.
44
+
| Setting | Suggested value | Description |
45
+
| ------------ | ---------------- | ----------- |
46
+
|**Subscription**| Your subscription | The subscription under which you create your new function app. |
47
+
|**[Resource Group](../azure-resource-manager/management/overview.md)**|*myResourceGroup*| Name for the new resource group in which you create your function app. You should create a new resource group because there are [known limitations when creating new function apps in an existing resource group](functions-scale.md#limitations-for-creating-new-function-apps-in-an-existing-resource-group).|
48
+
|**Function App name**| Globally unique name | Name that identifies your new function app. Valid characters are `a-z` (case insensitive), `0-9`, and `-`. |
49
+
|**Region**| Preferred region | Select a [region](https://azure.microsoft.com/regions/) that's near you or near other services that your functions can access. |
50
+
|**Runtime stack**| Preferred language | Choose a runtime that supports your favorite function programming language. |
51
+
|**Version**| Version number | Choose the version of your installed runtime. |
52
+
|**Instance Size**| 2048 MB | The instance memory size used for each instance of the app as it scales. |
96
53
97
-
Azure creates the HTTP trigger function. Now, you can run the new function by sending an HTTP request.
98
-
::: zone-end
99
-
::: zone pivot="programming-language-java,programming-language-csharp,programming-language-typescript,programming-language-python"
100
-
## Create your functions locally
54
+
1. 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 Insights instance on the **Monitoring** tab. You can also choose to use an existing storage account or Application Insights instance, and change Azure OpenAI, Networking, Deployment, and Authentication settings.
101
55
102
-
If you aren't able to create your function code in the portal, you can instead create a local project and publish the function code to your new function app.
56
+
1. Select **Review + create** to review the app configuration you chose, and then select **Create** to provision and deploy the function app.
103
57
104
-
1.In your function app, select **Overview**, and then in **Create functions in your preferred environment** under **Functions**.
58
+
1.Select the **Notifications** icon in the upper-right corner of the portal and watch for the **Deployment succeeded** message.
105
59
106
-
1.Choose your preferred local development environment and follow the steps in the linked article to create and publish your first Azure Functions project.
60
+
1.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.
107
61
108
-
>[!TIP]
109
-
>When publishing your new project, make sure to use the function app and related resources you just created.
0 commit comments