Skip to content

Commit bb1e890

Browse files
Alt text
1 parent 52ad21a commit bb1e890

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-functions/functions-develop-vs.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ The Azure Functions project template in Visual Studio creates a C# class library
5353
| **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. |
5454
| **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). |
5555

56-
![Azure Functions project settings](./media/functions-develop-vs/functions-project-settings-v4-isolated.png)
56+
![Screenshot of Azure Functions project settings](./media/functions-develop-vs/functions-project-settings-v4-isolated.png)
5757
::: zone-end
5858
::: zone pivot="in-proc"
5959
| Setting | Value | Description |
@@ -63,7 +63,7 @@ The Azure Functions project template in Visual Studio creates a C# class library
6363
| **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. |
6464
| **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). |
6565

66-
![Azure Functions project settings](./media/functions-develop-vs/functions-project-settings.png)
66+
![Screenshot of Azure Functions project settings](./media/functions-develop-vs/functions-project-settings.png)
6767
::: zone-end
6868

6969
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
594594
::: zone pivot="isolated"
595595
> [!div class="nextstepaction"]
596596
> [C# isolated worker model guide](./dotnet-isolated-process-guide.md)
597-
::: zone-end
597+
::: zone-end

0 commit comments

Comments
 (0)