Merge pull request #285112 from ggailey777/postman

JamesJBarnett · web-flow · commit d0979bc88700 · 2024-08-21T10:46:40.000-07:00
[Functions][Postman] Replace big note with reference link.
diff --git a/articles/azure-functions/durable/durable-functions-create-portal.md b/articles/azure-functions/durable/durable-functions-create-portal.md
@@ -76,11 +76,7 @@ If you are creating JavaScript Durable Functions, you'll need to install the [`d
 
 1. Go back to the **HttpStart** function, choose **Get function Url**, and select the **Copy to clipboard** icon to copy the URL. You use this URL to start the **HelloSequence** function.
 
-1. Use one of these HTTP test tools to send an HTTP POST request to the URL endpoint:
-
-   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
-
-   The following example is a cURL command that sends a POST request to the durable function:
+1. Use a secure HTTP test tool to send an HTTP POST request to the URL endpoint. This example is a cURL command that sends a POST request to the durable function:
 
     ```bash
     curl -X POST https://{your-function-app-name}.azurewebsites.net/api/orchestrators/{functionName} --header "Content-Length: 0"
@@ -98,7 +94,7 @@ If you are creating JavaScript Durable Functions, you'll need to install the [`d
     }
     ```
 
-    [!INCLUDE [api-test-http-request-tools-caution](../../../includes/api-test-http-request-tools-caution.md)]
+    Make sure to choose an HTTP test tool that keeps your data secure. For more information, see [HTTP test tools](../functions-develop-local.md#http-test-tools).
 
 1. Call the `statusQueryGetUri` endpoint URI and you see the current status of the durable function, which might look like this example:
 
diff --git a/articles/azure-functions/durable/durable-functions-isolated-create-first-csharp.md b/articles/azure-functions/durable/durable-functions-isolated-create-first-csharp.md
@@ -39,6 +39,8 @@ To complete this quickstart, you need:
 
 * [.NET Core SDK](https://dotnet.microsoft.com/download) version 3.1 or later installed.
 
+* An HTTP test tool that keeps your data secure. For more information, see [HTTP test tools](../functions-develop-local.md#http-test-tools).
+
 [!INCLUDE [quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
 
 ## <a name="create-an-azure-functions-project"></a>Create an Azure Functions project
@@ -111,9 +113,7 @@ Azure Functions Core Tools gives you the capability to run an Azure Functions pr
 
     :::image type="content" source="media/durable-functions-create-first-csharp/isolated-functions-vscode-debugging.png" alt-text="Screenshot of the Azure local output window." lightbox="media/durable-functions-create-first-csharp/isolated-functions-vscode-debugging.png":::
 
-1. Use one of these HTTP test tools to send an HTTP POST request to the URL endpoint:
-
-   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+1. Use an HTTP test tool to send an HTTP POST request to the URL endpoint.
 
    The response is the HTTP function's initial result. It lets you know that the Durable Functions app orchestration started successfully. It doesn't yet display the end result of the orchestration. The response includes a few useful URLs.
 
diff --git a/articles/azure-functions/durable/quickstart-java.md b/articles/azure-functions/durable/quickstart-java.md
@@ -36,6 +36,8 @@ To complete this quickstart, you need:
 
   For Azure Functions _4.x_, Core Tools version 4.0.4915 or later is required.
 
+* An HTTP test tool that keeps your data secure. For more information, see [HTTP test tools](../functions-develop-local.md#http-test-tools).
+ 
 * An Azure subscription. To use Durable Functions, you must have an Azure Storage account.
 
 [!INCLUDE [quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
@@ -355,9 +357,7 @@ Azure Functions Core Tools gives you the capability to run an Azure Functions pr
 
    :::image type="content" source="media/quickstart-java/maven-functions-run.png" alt-text="Screenshot of Azure local output.":::
 
-1. Use an HTTP test tool to send an HTTP POST request to the URL endpoint. 
-
-    [!INCLUDE [api-test-http-request-tools-caution](../../../includes/api-test-http-request-tools-caution.md)]
+1. Use an HTTP test tool to send an HTTP POST request to the URL endpoint.
 
     The response should look similar to the following example:
 
diff --git a/articles/azure-functions/durable/quickstart-js-vscode.md b/articles/azure-functions/durable/quickstart-js-vscode.md
@@ -49,7 +49,8 @@ To complete this quickstart, you need:
 * [Azure Functions Core Tools](../functions-run-local.md) version 4.0.5382 or later installed.
 
 ::: zone-end
-
+* An HTTP test tool that keeps your data secure. For more information, see [HTTP test tools](../functions-develop-local.md#http-test-tools).
+ 
 * An Azure subscription. To use Durable Functions, you must have an Azure Storage account.
 
 ::: zone pivot="nodejs-model-v3"
@@ -261,9 +262,7 @@ Azure Functions Core Tools gives you the capability to run an Azure Functions pr
 
 ::: zone pivot="nodejs-model-v3"
 
-5. Use your browser or one of these HTTP test tools to send an HTTP POST request to the URL endpoint: 
-
-   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+5. Use your browser or an HTTP test tool to send an HTTP POST request to the URL endpoint.
 
    Replace the last segment with the name of the orchestrator function (`HelloOrchestrator`). The URL should be similar to `http://localhost:7071/api/orchestrators/HelloOrchestrator`.
 
@@ -273,9 +272,7 @@ Azure Functions Core Tools gives you the capability to run an Azure Functions pr
 
 ::: zone pivot="nodejs-model-v4"
 
-5. Use your browser or one of these HTTP test tools to send an HTTP POST request to the URL endpoint: 
-
-   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+5. Use your browser or an HTTP test tool to send an HTTP POST request to the URL endpoint.
 
    Replace the last segment with the name of the orchestrator function (`HelloOrchestrator`). The URL should be similar to `http://localhost:7071/api/orchestrators/HelloOrchestrator`.
 
diff --git a/articles/azure-functions/durable/quickstart-powershell-vscode.md b/articles/azure-functions/durable/quickstart-powershell-vscode.md
@@ -27,6 +27,8 @@ To complete this quickstart, you need:
 
 * The latest version of [Azure Functions Core Tools](../functions-run-local.md) installed.
 
+* An HTTP test tool that keeps your data secure. For more information, see [HTTP test tools](../functions-develop-local.md#http-test-tools).
+
 * An Azure subscription. To use Durable Functions, you must have an Azure Storage account.
 
 [!INCLUDE [quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
@@ -155,9 +157,7 @@ Azure Functions Core Tools gives you the capability to run an Azure Functions pr
 
    :::image type="content" source="media/quickstart-js-vscode/functions-f5.png" alt-text="Screenshot of Azure local output.":::
 
-1. Use your browser or one of these HTTP test tools to send an HTTP POST request to the URL endpoint: 
-
-   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+1. Use your browser or an HTTP test tool to send an HTTP POST request to the URL endpoint.
 
    Replace the last segment with the name of the orchestrator function (`HelloOrchestrator`). The URL should be similar to `http://localhost:7071/api/orchestrators/HelloOrchestrator`.
 
diff --git a/articles/azure-functions/durable/quickstart-python-vscode.md b/articles/azure-functions/durable/quickstart-python-vscode.md
@@ -28,6 +28,8 @@ To complete this quickstart, you need:
 
 * The latest version of [Azure Functions Core Tools](../functions-run-local.md) installed.
 
+* An HTTP test tool that keeps your data secure. For more information, see [HTTP test tools](../functions-develop-local.md#http-test-tools).
+
 * An Azure subscription. To use Durable Functions, you must have an Azure Storage account.
 
 * [Python](https://www.python.org/) version 3.7, 3.8, 3.9, or 3.10 installed.
@@ -308,9 +310,7 @@ Azure Functions Core Tools gives you the capability to run an Azure Functions pr
 
 ::: zone pivot="python-mode-configuration"
 
-5. Use your browser or one of these HTTP test tools to send an HTTP POST request to the URL endpoint: 
-
-   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+5. Use your browser or an HTTP test tool to send an HTTP POST request to the URL endpoint.
 
    Replace the last segment with the name of the orchestrator function (`HelloOrchestrator`). The URL should be similar to `http://localhost:7071/api/orchestrators/HelloOrchestrator`.
 
@@ -341,9 +341,7 @@ Azure Functions Core Tools gives you the capability to run an Azure Functions pr
 
 ::: zone pivot="python-mode-decorators"
 
-5. Use your browser or one of these HTTP test tools to send an HTTP POST request to the URL endpoint: 
-
-   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+5. Use your browser or an HTTP test tool to send an HTTP POST request to the URL endpoint.
 
    Replace the last segment with the name of the orchestrator function (`HelloOrchestrator`). The URL should be similar to `http://localhost:7071/api/orchestrators/HelloOrchestrator`.
 
diff --git a/articles/azure-functions/durable/quickstart-ts-vscode.md b/articles/azure-functions/durable/quickstart-ts-vscode.md
@@ -49,7 +49,8 @@ To complete this quickstart, you need:
 * [Azure Functions Core Tools](../functions-run-local.md) version 4.0.5382 or later installed.
 
 ::: zone-end
-
+* An HTTP test tool that keeps your data secure. For more information, see [HTTP test tools](../functions-develop-local.md#http-test-tools).
+ 
 * An Azure subscription. To use Durable Functions, you must have an Azure Storage account.
 
 ::: zone pivot="nodejs-model-v3"
@@ -263,9 +264,7 @@ Azure Functions Core Tools gives you the capability to run an Azure Functions pr
 
 ::: zone pivot="nodejs-model-v3"
 
-5. Use your browser or one of these HTTP test tools to send an HTTP POST request to the URL endpoint: 
-
-   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+5. Use your browser or an HTTP test tool to send an HTTP POST request to the URL endpoint.
 
    Replace the last segment with the name of the orchestrator function (`HelloOrchestrator`). The URL should be similar to `http://localhost:7071/api/orchestrators/HelloOrchestrator`.
 
@@ -275,9 +274,7 @@ Azure Functions Core Tools gives you the capability to run an Azure Functions pr
 
 ::: zone pivot="nodejs-model-v4"
 
-5. Use your browser or one of these HTTP test tools to send an HTTP POST request to the URL endpoint: 
-
-   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+5. Use your browser or an HTTP test tool to send an HTTP POST request to the URL endpoint.
 
    Replace the last segment with the name of the orchestrator function (`HelloOrchestrator`). The URL should be similar to `http://localhost:7071/api/orchestrators/HelloOrchestrator`.
 
diff --git a/articles/azure-functions/event-grid-how-tos.md b/articles/azure-functions/event-grid-how-tos.md
@@ -127,9 +127,7 @@ To test an Event Grid trigger locally, you have to get Event Grid HTTP requests
 1. [Generate a request](#generate-a-request) and copy the request body from the viewer app.
 1. [Manually post the request](#manually-post-the-request) to the localhost URL of your Event Grid trigger function.
 
-To send an HTTP post request, you need an HTTP test tool, like one of these:
-
-[!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
+To send an HTTP post request, you need an HTTP test tool. Make sure to choose a tool that keeps your data secure. For more information, see [HTTP test tools](functions-develop-local.md#http-test-tools).
 
 When you're done testing, you can use the same subscription for production by updating the endpoint. Use the [`az eventgrid event-subscription update`](/cli/azure/eventgrid/event-subscription#az-eventgrid-event-subscription-update) Azure CLI command.
 
diff --git a/articles/azure-functions/functions-create-serverless-api.md b/articles/azure-functions/functions-create-serverless-api.md
@@ -19,6 +19,8 @@ In this article, you learn how to build highly scalable APIs with Azure Function
 
 ## Prerequisites
 
+* An HTTP test tool that keeps your data secure. For more information, see [HTTP test tools](functions-develop-local.md#http-test-tools).
+
 [!INCLUDE [Previous quickstart note](../../includes/functions-quickstart-previous-topics.md)]
 
 After you create this function app, you can follow the procedures in this article.
@@ -63,9 +65,7 @@ Next, test your function to see how it works with the new API surface:
 
 1. Press Enter to confirm that your function is working. You should see the response, "*Hello John*."
 
-1. You can also call the endpoint with another HTTP method to confirm that the function isn't executed. To do so, use one of these HTTP test tools:
-
-[!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
+1. You can also call the endpoint with another HTTP method to confirm that the function isn't executed. For HTTP methods other than GET, you need to use a secure [HTTP test tool](functions-develop-local.md#http-test-tools).
 
 ## Proxies overview
 
diff --git a/articles/azure-functions/functions-custom-handlers.md b/articles/azure-functions/functions-custom-handlers.md
@@ -565,9 +565,7 @@ In Azure, [query Application Insights traces](analyze-telemetry-data.md#query-te
 
 ### Test custom handler in isolation
 
-Custom handler apps are a web server process, so it may be helpful to start it on its own and test function invocations by sending mock [HTTP requests](#request-payload) using one of these tools:
-
-[!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
+Custom handler apps are a web server process, so it may be helpful to start it on its own and test function invocations by sending mock [HTTP requests](#request-payload). For sending HTTP requests with payloads, make sure to choose a tool that keeps your data secure. For more information, see [HTTP test tools](functions-develop-local.md#http-test-tools).
 
 You can also use this strategy in your CI/CD pipelines to run automated tests on your custom handler.
 
diff --git a/articles/azure-functions/functions-develop-local.md b/articles/azure-functions/functions-develop-local.md
@@ -107,6 +107,25 @@ When you develop your functions locally, you need to take trigger and binding be
 
 During local testing, you must be running the host provided by Core Tools (func.exe) locally. For more information, see [Azure Functions Core Tools](functions-run-local.md).
 
+## HTTP test tools
+
+During development, it's easy to call any of your function endpoints from a web browser when they support the HTTP GET method. However, for other HTTP methods that support payloads, such as POST or PUT, you need to use an HTTP test tool to create and send these HTTP requests to your function endpoints. 
+
+> [!CAUTION]  
+> For scenarios where your requests must include sensitive data, make sure to use a tool that protects your data and reduces the risk of exposing any sensitive data to the public. Sensitive data you should protect might include: credentials, secrets, access tokens, API keys, geolocation data, even personally-identifiable information (PII). 
+
+You can keep your data secure by choosing an HTTP test tool that works either offline or locally, doesn't sync your data to the cloud, and doesn't require that you sign in to an online account. Some tools can also protect your data from accidental exposure by implementing specific security features. 
+
+Avoid using tools that centrally store your HTTP request history (including sensitive information), don't follow best security practices, or don't respect data privacy concerns. 
+
+Consider using one of these tools for securely sending HTTP requests to your function endpoints:
+
+- [Visual Studio Code](https://code.visualstudio.com/download) with an [extension from Visual Studio Marketplace](https://marketplace.visualstudio.com/vscode), such as [REST Client](https://marketplace.visualstudio.com/items?itemName=humao.rest-client)
+- [PowerShell Invoke-RestMethod](/powershell/module/microsoft.powershell.utility/invoke-restmethod)
+- [Microsoft Edge - Network Console tool](/microsoft-edge/devtools-guide-chromium/network-console/network-console-tool)
+- [Bruno](https://www.usebruno.com/)
+- [curl](https://curl.se/)
+
 ## Local storage emulator
 
 During local development, you can use the local [Azurite emulator](../storage/common/storage-use-azurite.md) when testing functions with Azure Storage bindings (Queue Storage, Blob Storage, and Table Storage), without having to connect to remote storage services. Azurite integrates with Visual Studio Code and Visual Studio, and you can also run it from the command prompt using npm. For more information, see [Use the Azurite emulator for local Azure Storage development](../storage/common/storage-use-azurite.md).
diff --git a/articles/azure-functions/functions-manually-run-non-http.md b/articles/azure-functions/functions-manually-run-non-http.md
@@ -15,9 +15,7 @@ The procedure described in this article is equivalent to using the **Test/Run**
 
 ## Prerequisites 
 
-The examples in this article use an HTTP test tool. You can obtain and use any of these tools that send HTTP requests:
-
-[!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
+The examples in this article use an HTTP test tool. Make sure to choose a tool that keeps your data secure. For more information, see [HTTP test tools](functions-develop-local.md#http-test-tools).
 
 ## Define the request location
 
diff --git a/articles/azure-functions/functions-run-local.md b/articles/azure-functions/functions-run-local.md
@@ -274,9 +274,7 @@ curl --request POST http://localhost:7071/api/MyHttpTrigger --data "{'name':'Azu
 
 The following considerations apply when calling HTTP endpoints locally:
 
-+ You can make GET requests from a browser passing data in the query string. For all other HTTP methods, you must use an HTTP testing tool that supports POST requests, like one of these: 
-
-   [!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
++ You can make GET requests from a browser passing data in the query string. For all other HTTP methods, you must use a HTTP testing tool that also keeps your data secure. For more information, see [HTTP test tools](functions-develop-local.md#http-test-tools). 
 
 + Make sure to use the same server name and port that the Functions host is listening on. You see an endpoint like this in the output generated when starting the Function host. You can call this URL using any HTTP method supported by the trigger.
 
