Merge pull request #281342 from ecfan/postman

denrea · web-flow · commit 4a2bc6b63863 · 2024-07-19T13:46:33.000-07:00
[SCOPED] Rename include file and update links
diff --git a/articles/connectors/connectors-native-reqres.md b/articles/connectors/connectors-native-reqres.md
@@ -34,7 +34,7 @@ To run your workflow by sending an outgoing or outbound request instead, use the
 
 * The logic app workflow where you want to receive the inbound HTTPS request. To start your workflow with a **Request** trigger, you have to start with a blank workflow. To use the Response action, your workflow must start with the **Request** trigger.
 
-[!INCLUDE [postman-replacements-bullet](../../includes/postman-replacements-bullet.md)]
+[!INCLUDE [api-test-http-request-tools-bullet](../../includes/api-test-http-request-tools-bullet.md)]
 
 <a name="add-request-trigger"></a>
 
diff --git a/articles/logic-apps/connectors/sap-create-example-scenario-workflows.md b/articles/logic-apps/connectors/sap-create-example-scenario-workflows.md
@@ -22,7 +22,7 @@ Both Standard and Consumption logic app workflows offer the SAP *managed* connec
 
 - Before you start, make sure to [review and meet the SAP connector requirements](sap.md#prerequisites) for your specific scenario.
 
-[!INCLUDE [postman-replacements-bullet](../../../includes/postman-replacements-bullet.md)]
+[!INCLUDE [api-test-http-request-tools-bullet](../../../includes/api-test-http-request-tools-bullet.md)]
 
 <a name="receive-messages-sap"></a>
 
diff --git a/articles/logic-apps/connectors/sap-generate-schemas-for-artifacts.md b/articles/logic-apps/connectors/sap-generate-schemas-for-artifacts.md
@@ -29,7 +29,7 @@ Both Standard and Consumption logic app workflows offer the SAP *managed* connec
 
 - If you want to upload your generated schemas to a repository, such as an [integration account](../logic-apps-enterprise-integration-create-integration-account.md), make sure that the repository already exists.
 
-[!INCLUDE [postman-replacements-bullet](../../../includes/postman-replacements-bullet.md)]
+[!INCLUDE [api-test-http-request-tools-bullet](../../../includes/api-test-http-request-tools-bullet.md)]
 
 ## Generate schemas for an SAP artifact
 
diff --git a/articles/logic-apps/create-single-tenant-workflows-azure-portal.md b/articles/logic-apps/create-single-tenant-workflows-azure-portal.md
@@ -55,7 +55,7 @@ In single-tenant Azure Logic Apps, workflows in the same logic app resource and
 
   If you don't have an Office 365 account, you can use [any other available email connector](/connectors/connector-reference/connector-reference-logicapps-connectors) that can send messages from your email account, for example, Outlook.com. If you use a different email connector, you can still follow the example, and the general overall steps are the same. However, your options might differ in some ways. For example, if you use the Outlook.com connector, use your personal Microsoft account instead to sign in.
 
-[!INCLUDE [postman-replacements-bullet](../../includes/postman-replacements-bullet.md)]
+[!INCLUDE [api-test-http-request-tools-bullet](../../includes/api-test-http-request-tools-bullet.md)]
 
 * If you create your logic app resource and enable [Application Insights](../azure-monitor/app/app-insights-overview.md), you can optionally enable diagnostics logging and tracing for your logic app. You can do so either when you create your logic app or after deployment. You need to have an Application Insights instance, but you can create this resource either [in advance](../azure-monitor/app/create-workspace-resource.md), when you create your logic app, or after deployment.
 
diff --git a/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md b/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md
@@ -230,9 +230,9 @@ As you progress, you'll complete these high-level tasks:
 
 1. If you create your logic app resources with settings that support using [Application Insights](../azure-monitor/app/app-insights-overview.md), you can optionally enable diagnostics logging and tracing for your logic app resource. You can do so either when you create your logic app or after deployment. You need to have an Application Insights instance, but you can create this resource either [in advance](../azure-monitor/app/create-workspace-resource.md), when you create your logic app, or after deployment.
 
-1. Install or use a tool that can send HTTP requests, for example:
+1. Install or use a tool that can send HTTP requests to test your solution, for example:
 
-   [!INCLUDE [postman-replacements](../../includes/postman-replacements.md)]
+   [!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
 
 <a name="set-up"></a>
 
diff --git a/articles/logic-apps/logic-apps-enterprise-integration-flatfile.md b/articles/logic-apps/logic-apps-enterprise-integration-flatfile.md
@@ -62,7 +62,7 @@ For more information, review the following documentation:
 
     So, if you don't have or need an integration account, you can use the upload option. Otherwise, you can use the linking option. Either way, you can use these artifacts across all child workflows within the same logic app resource.
 
-[!INCLUDE [postman-replacements-bullet](../../includes/postman-replacements-bullet.md)]
+[!INCLUDE [api-test-http-request-tools-bullet](../../includes/api-test-http-request-tools-bullet.md)]
 
 ## Limitations
 
diff --git a/articles/logic-apps/logic-apps-enterprise-integration-liquid-transform.md b/articles/logic-apps/logic-apps-enterprise-integration-liquid-transform.md
@@ -68,7 +68,7 @@ For more information, review the following documentation:
   > which differs in specific cases from the [Shopify implementation for Liquid](https://shopify.github.io/liquid). 
   > For more information, see [Liquid template considerations](#liquid-template-considerations).
 
-[!INCLUDE [postman-replacements-bullet](../../includes/postman-replacements-bullet.md)]
+[!INCLUDE [api-test-http-request-tools-bullet](../../includes/api-test-http-request-tools-bullet.md)]
 
 <a name="create-template"></a>
 
diff --git a/articles/logic-apps/logic-apps-http-endpoint.md b/articles/logic-apps/logic-apps-http-endpoint.md
@@ -26,7 +26,7 @@ This guide shows how to create a callable endpoint for your workflow by adding t
 
 * A logic app workflow where you want to use the **Request** trigger to create the callable endpoint. You can start with either a blank workflow or an existing workflow where you can replace the current trigger. This example starts with a blank workflow.
 
-[!INCLUDE [postman-replacements-bullet](../../includes/postman-replacements-bullet.md)]
+[!INCLUDE [api-test-http-request-tools-bullet](../../includes/api-test-http-request-tools-bullet.md)]
 
 ## Create a callable endpoint
 
diff --git a/articles/logic-apps/logic-apps-scenario-edi-send-batch-messages.md b/articles/logic-apps/logic-apps-scenario-edi-send-batch-messages.md
@@ -41,7 +41,7 @@ Make sure that your batch receiver and batch sender logic app workflows use the
 
 * To use Visual Studio rather than the Azure portal, make sure you [set up Visual Studio for working with Azure Logic Apps](quickstart-create-logic-apps-with-visual-studio.md).
 
-[!INCLUDE [postman-replacements-bullet](../../includes/postman-replacements-bullet.md)]
+[!INCLUDE [api-test-http-request-tools-bullet](../../includes/api-test-http-request-tools-bullet.md)]
 
 <a name="receiver"></a>
 
diff --git a/articles/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint.md b/articles/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint.md
@@ -37,7 +37,7 @@ For more information, review the following documentation:
   - [What is subnet delegation?](../virtual-network/subnet-delegation-overview.md)
   - [Add or remove a subnet delegation](../virtual-network/manage-subnet-delegation.md)
 
-[!INCLUDE [postman-replacements-bullet](../../includes/postman-replacements-bullet.md)]
+[!INCLUDE [api-test-http-request-tools-bullet](../../includes/api-test-http-request-tools-bullet.md)]
 
 <a name="set-up-inbound"></a>
 
diff --git a/articles/scheduler/migrate-from-scheduler-to-logic-apps.md b/articles/scheduler/migrate-from-scheduler-to-logic-apps.md
@@ -40,7 +40,7 @@ For more information, see [What is Azure Logic Apps?](../logic-apps/logic-apps-o
 
 * An Azure account and subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
-[!INCLUDE [postman-replacements-bullet](../../includes/postman-replacements-bullet.md)]
+[!INCLUDE [api-test-http-request-tools-bullet](../../includes/api-test-http-request-tools-bullet.md)]
 
 ## Migrate by using a script
 
diff --git a/includes/api-test-http-request-tools-bullet.md b/includes/api-test-http-request-tools-bullet.md
@@ -4,10 +4,10 @@ author: ecfan
 ms.author: estfan
 ms.topic: include
 ms.date: 07/18/2024
-# Generic text about Postman alternatives.
+# Generic text about tool options for API testing and sending HTTP requests.
 ---
 
-* Install or use a tool that can send HTTP requests, for example:
+* Install or use a tool that can send HTTP requests to test your solution, for example:
 
   - [Visual Studio Code](https://code.visualstudio.com/download) with an [extension from Visual Studio Marketplace](https://marketplace.visualstudio.com/vscode)
   - [PowerShell Invoke-RestMethod](/powershell/module/microsoft.powershell.utility/invoke-restmethod)
diff --git a/includes/api-test-http-request-tools.md b/includes/api-test-http-request-tools.md
@@ -4,7 +4,7 @@ author: ecfan
 ms.author: estfan
 ms.topic: include
 ms.date: 07/18/2024
-# Generic text about Postman alternatives.
+# Generic text about tool options for API testing and sending HTTP requests.
 ---
 
    - [Visual Studio Code](https://code.visualstudio.com/download) with an [extension from Visual Studio Marketplace](https://marketplace.visualstudio.com/vscode)
