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
@@ -76,7 +76,7 @@ To support your function code, you need to create three resources:
76
76
az group create --name <RESOURCE_GROUP> --location <REGION>
77
77
```
78
78
79
-
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](#view-currently-supported-regions). The [az group create](/cli/azure/group#az-group-create) command creates a resource group.
79
+
In the previous command, replace `<RESOURCE_GROUP>` with a value that's unique in your subscription and `<REGION>` with one of the [currently supported regions](#view-currently-supported-regions). The [az group create](/cli/azure/group#az-group-create) command creates a resource group.
80
80
81
81
4. Create a general-purpose storage account in your resource group and region:
82
82
@@ -166,41 +166,117 @@ You can skip this section if you choose to instead [create and deploy your app u
166
166
167
167
You can choose to deploy your project code to an existing function app using various tools:
You can use the Azure CLI to upload a deployment package file to the deployment share for function app in Azure. To do this, you must produce a .zip package file that can run when the package is mounted to your app.
172
+
::: zone pivot="programming-language-csharp,programming-language-java"
173
+
This package file must contain all of the build output files and referenced libraries required for your project to run.
174
+
::: zone-end
175
+
::: zone pivot="programming-language-javascript,programming-language-typescript"
176
+
For projects with a large amount of libraries, you should package the root of your project file and request a [remote build].
177
+
::: zone-end
178
+
::: zone pivot="programming-language-python"
179
+
For Python projects, you should package the root of your project file and always request a [remote build]. Using a remote build prevents potential issues that can occur when you build a project on Windows to be deployed on Linux.
180
+
::: zone-end
181
+
::: zone pivot="programming-language-csharp"
182
+
1. Using your preferred development tool, build the code project.
172
183
173
-
### [Azure CLI](#tab/azure-cli)
184
+
2. Create a .zip file that contains the output of the build directory. For more information, see [Project structure](dotnet-isolated-process-guide.md#project-structure).
174
185
175
-
You can use the `az functionapp deployment source config-zip` command to deploy a ready-to-run .zip containing your application package to your function app.
186
+
3. When required, sign in to your Azure account and select the active subscription using the [`az login`](/cli/azure/reference-index#az-login) command.
176
187
177
-
1. First, produce a ready-to-run .zip of your application package. From your project root, perform the required build steps for your project's runtime. Then zip the contents of the build directory. Refer to the "Folder structure" section of your runtime's Developer reference guide ([Python example](./functions-reference-python.md#folder-structure)).
188
+
```azurecli
189
+
az login
190
+
```
178
191
179
-
1. Before you can deploy, sign in to your Azure subscription using the Azure CLI.
192
+
4. Run the [`az functionapp deployment source config-zip`](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip) command to deploy the application package located in the relative `<FILE_PATH>`.
1. Using your preferred development tool, build the code project.
200
+
201
+
2. Create a .zip file that contains the output of the build directory. For more information, see [Folder structure](./functions-reference-java.md#folder-structure).
202
+
203
+
3. When required, sign in to your Azure account and select the active subscription using the [`az login`](/cli/azure/reference-index#az-login) command.
180
204
181
205
```azurecli
182
206
az login
183
207
```
184
208
185
-
The [`az login`](/cli/azure/reference-index#az-login) command signs you into your Azure account.
209
+
4. Run the [`az functionapp deployment source config-zip`](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip) command to deploy the application package located in the relative `<FILE_PATH>`.
1. Create a .zip file that contains the root directory of your code project. For more information, see [Folder structure](./functions-reference-powershell.md#folder-structure).
217
+
218
+
2. When required, sign in to your Azure account and select the active subscription using the [`az login`](/cli/azure/reference-index#az-login) command.
219
+
220
+
```azurecli
221
+
az login
222
+
```
186
223
187
-
1. Run the following command to deploy the application package located in the relative `<FILE_PATH>`. Only set `--build-remote true` if you need to perform a [remote build](./functions-deployment-technologies.md#remote-build).
224
+
3. Run the [`az functionapp deployment source config-zip`](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip) command to deploy the application package located in the relative `<FILE_PATH>`.
::: zone pivot="programming-language-javascript,programming-language-typescript"
231
+
1. Create a .zip file that contains the root directory of your code project. For more information, see [Folder structure](./functions-reference-node.md#folder-structure).
192
232
193
-
### [Core Tools](#tab/core-tools)
233
+
2. When required, sign in to your Azure account and select the active subscription using the [`az login`](/cli/azure/reference-index#az-login) command.
3. Run the [`az functionapp deployment source config-zip`](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip) command to deploy the application package located in the relative `<FILE_PATH>`.
Make sure to set `--build-remote true` to perform a [remote build].
246
+
::: zone-end
247
+
::: zone pivot="programming-language-python"
248
+
1. Create a .zip file that contains the root directory of your code project. For more information, see [Folder structure](./functions-reference-python.md#folder-structure).
249
+
250
+
2. When required, sign in to your Azure account and select the active subscription using the [`az login`](/cli/azure/reference-index#az-login) command.
251
+
252
+
```azurecli
253
+
az login
254
+
```
255
+
256
+
3. Run the [`az functionapp deployment source config-zip`](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip) command to deploy the application package located in the relative `<FILE_PATH>`.
Azure Functions has a custom GitHub Action and Azure DevOps Task to support continuous deployment. Please refer the the following guides to incorporate these tools in your CI/CD pipelines:
267
+
Azure Functions has a custom GitHub Action and Azure DevOps Task to support continuous deployment. Refer the following guides to incorporate these tools in your CI/CD pipelines:
200
268
201
269
- [Build and deploy using Azure Pipelines](./functions-how-to-azure-devops.md)
202
270
- [Build and deploy using GitHub Actions](./functions-how-to-github-actions.md)
@@ -248,7 +324,7 @@ You can use Maven to create a Flex Consumption hosted function app and required
248
324
249
325
## Enable virtual network integration
250
326
251
-
You can enable [virtual network integration](functions-networking-options.md#virtual-network-integration) for your app in a Flex Consumption plan. The examples in this section assume that you already have [created a virtual network with subnet](../virtual-network/quick-create-cli.md#create-a-virtual-network-and-subnet) in your account. You can enable virtual network integration when you create your app or at a later time.
327
+
You can enable [virtual network integration](functions-networking-options.md#virtual-network-integration) for your app in a Flex Consumption plan. The examples in this section assume that you've already [created a virtual network with subnet](../virtual-network/quick-create-cli.md#create-a-virtual-network-and-subnet) in your account. You can enable virtual network integration when you create your app or at a later time.
252
328
253
329
> [!IMPORTANT]
254
330
> The Flex Consumption plan currently doesn't support subnets with names that contain underscore (`_`) characters.
@@ -297,8 +373,8 @@ You can't currently enable virtual networking when you use Visual Studio Code to
297
373
298
374
For end-to-end examples of how to create apps in Flex Consumption with virtual network integration see these resources:
299
375
300
-
+ [Flex Consumption: HTTP to Event Hubs using VNET Integration](https://github.com/Azure-Samples/azure-functions-flex-consumption-samples/blob/main/README.md)
301
-
+ [Flex Consumption: triggered from Service Bus using VNET Integration](https://github.com/Azure-Samples/azure-functions-flex-consumption-samples/blob/main/README.md)
376
+
+ [Flex Consumption: HTTP to Event Hubs using virtual network Integration](https://github.com/Azure-Samples/azure-functions-flex-consumption-samples/blob/main/README.md)
377
+
+ [Flex Consumption: triggered from Service Bus using virtual network Integration](https://github.com/Azure-Samples/azure-functions-flex-consumption-samples/blob/main/README.md)
302
378
303
379
To modify or delete virtual network integration in an existing app:
304
380
@@ -340,12 +416,12 @@ You can't currently configure virtual networking in Visual Studio Code.
340
416
341
417
---
342
418
343
-
When choosing a subnet, these considerations apply:
419
+
When you're choosing a subnet, these considerations apply:
344
420
345
421
+ The subnet you choose can't already be used for other purposes, such as with private endpoints or service endpoints, or be delegated to any other hosting plan or service.
346
-
* You cannot share the same subnet between a Container Apps environment and a Flex Consumption app.
347
-
+ You can share the same subnet with more than one app running in a Flex Consumption plan. Because the networking resources are shared across all apps, one function app might impact the performance of others on the same subnet.
348
-
+ In a Flex Consumption plan, a single function app might use up to 40 IP addresses, even when the app scales beyond 40 instances. While this rule of thumb is helpful when estimating the subnet size you need, it's not strictly enforced.
422
+
* You can't share the same subnet between a Container Apps environment and a Flex Consumption app.
423
+
+ You can share the same subnet with more than one app running in a Flex Consumption plan. Because the networking resources are shared across all apps, one function app might affect the performance of others on the same subnet.
424
+
+ In a Flex Consumption plan, a single function app might use up to 40 IP addresses, even when the app scales beyond 40 instances. While this rule of thumb is helpful when estimating the subnet size you need, it isn't strictly enforced.
349
425
350
426
## Configure deployment settings
351
427
@@ -368,14 +444,14 @@ To configure deployment settings when you create your function app in the Flex C
368
444
369
445
### [Azure CLI](#tab/azure-cli)
370
446
371
-
Use the [`az functionapp create`] command and supply these additional options that customize deployment storage:
447
+
Use the [`az functionapp create`] command and supply these extra options that customize deployment storage:
372
448
373
449
| Parameter | Description |
374
450
|--|--|--|
375
451
|`--deployment-storage-name`| The name of the deployment storage account. |
376
452
|`--deployment-storage-container-name`| The name of the container in the account to contain your app's deployment package. |
377
453
|`--deployment-storage-auth-type`| The authentication type to use for connecting to the deployment storage account. Accepted values include `StorageAccountConnectionString`, `UserAssignedIdentity`, and `SystemAssignedIdentity`. |
378
-
|`--deployment-storage-auth-value`| When using `StorageAccountConnectionString`, this parameter is set to the name of the application setting that contains the connection string to the deployment storage account. When using`UserAssignedIdentity`, this parameter is set to the name of the resource ID of the identity you want to use. |
454
+
|`--deployment-storage-auth-value`| When using `StorageAccountConnectionString`, this parameter is set to the name of the application setting that contains the connection string to the deployment storage account. When you set`UserAssignedIdentity`, this parameter is set to the name of the resource ID of the identity you want to use. |
379
455
380
456
This example creates a function app in the Flex Consumption plan with a separate deployment storage account and user assigned identity:
381
457
@@ -475,16 +551,16 @@ You can't currently change the instance memory size setting for your app using V
475
551
476
552
## Set always ready instance counts
477
553
478
-
You can set a number of always ready instances for the [Per-function scaling](flex-consumption-plan.md#per-function-scaling) groups or individual functions, to keep your functions loaded and ready to execute. There are three special groups, as in per-function scaling:
554
+
You can set a specific number of always ready instances for the [Per-function scaling](flex-consumption-plan.md#per-function-scaling) groups or individual functions, to keep your functions loaded and ready to execute. There are three special groups, as in per-function scaling:
479
555
+`http` - all the HTTP triggered functions in the app scale together into their own instances.
480
556
+`durable` - all the Durable triggered functions (Orchestration, Activity, Entity) in the app scale together into their own instances.
481
557
+`blob` - all the blob (Event Grid) triggered functions in the app scale together into their own instances.
482
558
483
-
Use `http`, `durable` or `blob` as the name for the name value pair setting to configure always ready counts for these groups. For all other functions in the app you need to configure always ready for each individual function using the format `function:<FUNCTION_NAME>=n`.
559
+
Use `http`, `durable`, or `blob` as the name for the name value pair setting to configure always ready counts for these groups. For all other functions in the app you need to configure always ready for each individual function using the format `function:<FUNCTION_NAME>=n`.
484
560
485
561
### [Azure CLI](#tab/azure-cli)
486
562
487
-
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`:
563
+
To define one or more always ready instance designations, use the `--always-ready-instances` parameter with the [`az functionapp create`] command. This example sets the always ready instance count for all HTTP triggered functions to `5`:
0 commit comments