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
|**.NET version**|**.NET 6**| This value creates a function project that runs in-process with version 4.x of the Azure Functions runtime. Azure Functions 1.x supports the .NET Framework. For more information, see [Azure Functions runtime versions overview](../articles/azure-functions/functions-versions.md). |
23
+
|**.NET version**|**.NET 6 Isolated**| This value creates a function project that runs in an [isolated worker process](../articles/azure-functions/dotnet-isolated-process-guide.md). For more information, see [Azure Functions runtime versions overview](../articles/azure-functions/functions-versions.md). |
24
24
|**Function template**|**HTTP trigger**| This value creates a function triggered by an HTTP request. |
25
25
|**Storage account (AzureWebJobsStorage)**|**Storage emulator**| Because a function app in Azure requires a storage account, one is assigned or created when you publish your project to Azure. An HTTP trigger doesn't use an Azure Storage account connection string; all other trigger types require a valid Azure Storage account connection string. |
26
26
|**Authorization level**|**Anonymous**| The created function can be triggered by any client without providing a key. This authorization setting makes it easy to test your new function. For more information about keys and authorization, see [Authorization keys](../articles/azure-functions/functions-bindings-http-webhook-trigger.md#authorization-keys) and [HTTP and webhook bindings](../articles/azure-functions/functions-bindings-http-webhook.md). |
|**.NET version**|**.NET 6 Isolated**| This value creates a function project that runs in an [isolated worker process](../articles/azure-functions/dotnet-isolated-process-guide.md). For more information, see [Azure Functions runtime versions overview](../articles/azure-functions/functions-versions.md). |
34
+
|**.NET version**|**.NET 6**| This value creates a function project that runs in-process with version 4.x of the Azure Functions runtime. Azure Functions 1.x supports the .NET Framework. For more information, see [Azure Functions runtime versions overview](../articles/azure-functions/functions-versions.md). |
36
35
|**Function template**|**HTTP trigger**| This value creates a function triggered by an HTTP request. |
37
36
|**Storage account (AzureWebJobsStorage)**|**Storage emulator**| Because a function app in Azure requires a storage account, one is assigned or created when you publish your project to Azure. An HTTP trigger doesn't use an Azure Storage account connection string; all other trigger types require a valid Azure Storage account connection string. |
38
37
|**Authorization level**|**Anonymous**| The created function can be triggered by any client without providing a key. This authorization setting makes it easy to test your new function. For more information about keys and authorization, see [Authorization keys](../articles/azure-functions/functions-bindings-http-webhook-trigger.md#authorization-keys) and [HTTP and webhook bindings](../articles/azure-functions/functions-bindings-http-webhook.md). |
0 commit comments