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/functions-develop-vs.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ The Azure Functions project template in Visual Studio creates a C# class library
53
53
|**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. |
54
54
|**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](functions-bindings-http-webhook-trigger.md#authorization-keys) and [HTTP and webhook bindings](functions-bindings-http-webhook.md). |

57
57
::: zone-end
58
58
::: zone pivot="in-proc"
59
59
| Setting | Value | Description |
@@ -63,7 +63,7 @@ The Azure Functions project template in Visual Studio creates a C# class library
63
63
|**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. |
64
64
|**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](functions-bindings-http-webhook-trigger.md#authorization-keys) and [HTTP and webhook bindings](functions-bindings-http-webhook.md). |

67
67
::: zone-end
68
68
69
69
Make sure you set the **Authorization level** to **Anonymous**. If you choose the default level of **Function**, you're required to present the [function key](functions-bindings-http-webhook-trigger.md#authorization-keys) in requests to access your function endpoint.
@@ -594,4 +594,4 @@ For more information about the Azure Functions Core Tools, see [Work with Azure
594
594
::: zone pivot="isolated"
595
595
> [!div class="nextstepaction"]
596
596
> [C# isolated worker model guide](./dotnet-isolated-process-guide.md)
0 commit comments