Skip to content

Commit c1cc169

Browse files
authored
Merge pull request #103731 from ggailey777/patch-6
Note that a disabled HTTP trigger still runs locally
2 parents 5e6b20a + d368632 commit c1cc169

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/azure-functions/disable-function.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,9 @@ This article explains how to disable a function in Azure Functions. To *disable*
1111

1212
The recommended way to disable a function is by using an app setting in the format `AzureWebJobs.<FUNCTION_NAME>.Disabled`. You can create and modify this application setting in a number of ways, including by using the [Azure CLI](/cli/azure/) and from your function's **Manage** tab in the [Azure portal](https://portal.azure.com).
1313

14+
> [NOTE]
15+
> When you disable an HTTP triggered function by using the methods described in this article, the endpoint may still by accessible when running on your local computer.
16+
1417
## Use the Azure CLI
1518

1619
In the Azure CLI, you use the [`az functionapp config appsettings set`](/cli/azure/functionapp/config/appsettings#az-functionapp-config-appsettings-set) command to create and modify the app setting. The following command disables a function named `QueueTrigger` by creating an app setting named `AzureWebJobs.QueueTrigger.Disabled` set it to `true`.

0 commit comments

Comments
 (0)