Update references to Postman

Author: ecfan

articles/logic-apps/connectors/sap-create-example-scenario-workflows.md

@@ -662,7 +662,7 @@ In the following example, the `STFC_CONNECTION` RFC module generates a request a
 
 1. On the designer toolbar, select **Run Trigger** > **Run** to manually start your workflow.
 
-1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. Make sure to include your message content with your request. To send the request, use a tool such as the [Postman API client](https://www.postman.com/api-platform/api-client/).
+1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. Make sure to include your message content with your request. To send the request, use a local tool or app tool such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/).
 
    For this example, the HTTP POST request sends an IDoc file, which must be in XML format and include the namespace for the SAP action that you selected, for example:
 
@@ -690,7 +690,7 @@ You've now created a workflow that can communicate with your SAP server. Now tha
 
 1. Return to the workflow level. On the workflow menu, select **Overview**. On the toolbar, select **Run** > **Run** to manually start your workflow.
 
-1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. Make sure to your message content with your request. To send the request, use a tool such as the [Postman API client](https://www.postman.com/api-platform/api-client/).
+1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. Make sure to your message content with your request. To send the request, use a local tool or app such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/).
 
    For this example, the HTTP POST request sends an IDoc file, which must be in XML format and include the namespace for the SAP action that you selected, for example:
 

articles/logic-apps/connectors/sap-generate-schemas-for-artifacts.md

@@ -186,7 +186,7 @@ Based on whether you have a Consumption workflow in multi-tenant Azure Logic App
 
 1. On the designer toolbar, select **Run Trigger** > **Run** to manually start your workflow.
 
-1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. To send the request, use a tool such as [Postman](https://www.getpostman.com/apps).
+1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. To send the request, use a local tool or app such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/).
 
    For this example, the HTTP POST request sends an IDoc file, which must be in XML format and include the namespace for the SAP action that you selected, for example:
 
@@ -220,7 +220,7 @@ For more information about reviewing workflow run history, see [Monitor logic ap
 
 1. Return to the workflow level. On the workflow menu, select **Overview**. On the toolbar, select **Run** > **Run** to manually start your workflow.
 
-1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. To send the request, use a tool such as [Postman](https://www.getpostman.com/apps).
+1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. To send the request, use a local tool or app such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/).
 
    For this example, the HTTP POST request sends an IDoc file, which must be in XML format and include the namespace for the SAP action that you selected, for example:
 

articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md

@@ -730,6 +730,7 @@ To test your logic app workflow, follow these steps to start a debugging session
    If you created a stateful workflow, after the request that you sent triggers the workflow, the overview page shows the workflow's run status and history.
 
    > [!TIP]
+   >
    > If the run status doesn't appear, try refreshing the overview page by selecting **Refresh**. 
    > No run happens for a trigger that's skipped due to unmet criteria or finding no data.
 

articles/logic-apps/custom-connector-overview.md

@@ -37,7 +37,6 @@ In [multi-tenant Azure Logic Apps](logic-apps-overview.md), you can create [cust
 
   * [Create an Azure Logic Apps connector](/connectors/custom-connectors/create-logic-apps-connector)
   * [Create a custom connector from an OpenAPI definition](/connectors/custom-connectors/define-openapi-definition)
-  * [Create a custom connector from a Postman collection](/connectors/custom-connectors/define-postman-collection)
   * [Use a custom connector from a logic app](/connectors/custom-connectors/use-custom-connector-logic-apps)
   * [Share custom connectors in your organization](/connectors/custom-connectors/share)
   * [Submit your connectors for Microsoft certification](/connectors/custom-connectors/submit-certification)

articles/logic-apps/logic-apps-enterprise-integration-flatfile.md

@@ -282,7 +282,13 @@ You're now done with setting up your flat file decoding action. In a real world
 
 ## Test your workflow
 
-1. By using [Postman](https://www.getpostman.com/postman) or a similar tool and the `POST` method, send a call to the Request trigger's URL, which appears in the Request trigger's **HTTP POST URL** property, and include the XML content that you want to encode or decode in the request body.
+1. To send a call to the Request trigger's URL, which appears in the Request trigger's **HTTP POST URL** property, follow these steps:
+
+   1. Use a local tool or app such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/) to send the HTTP request.
+
+   1. Send the HTTP request using the **`POST`** method with the URL.
+
+   1. Include the XML content that you want to encode or decode in the request body.
 
 1. After your workflow finishes running, go to the workflow's run history, and examine the Flat File action's inputs and outputs.
 

articles/logic-apps/logic-apps-enterprise-integration-liquid-transform.md

@@ -271,16 +271,22 @@ The following steps show how to add a Liquid transformation action for Consumpti
 
 ## Test your workflow
 
-1. By using [Postman](https://www.getpostman.com/postman) or a similar tool and the `POST` method, send a call to the Request trigger's URL, which appears in the Request trigger's **HTTP POST URL** property, and include the JSON input to transform, for example:
+1. To send a call to the Request trigger's URL, which appears in the Request trigger's **HTTP POST URL** property, follow these steps:
 
-   ```json
-   {
-      "devices": "Surface, Mobile, Desktop computer, Monitors",
-      "firstName": "Dean",
-      "lastName": "Ledet",
-      "phone": "(111)0001111"
-   }
-   ```
+   1. Use a local tool or app such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/) to send the HTTP request.
+
+   1. Send the HTTP request using the **`POST`** method with the URL.
+
+   1. Include the JSON input to transform, for example:
+
+      ```json
+      {
+         "devices": "Surface, Mobile, Desktop computer, Monitors",
+         "firstName": "Dean",
+         "lastName": "Ledet",
+         "phone": "(111)0001111"
+      }
+      ```
 
 1. After your workflow finishes running, go to the workflow's run history, and examine the **Transform JSON to JSON** action's inputs and outputs, for example:
 

articles/logic-apps/logic-apps-scenario-edi-send-batch-messages.md

@@ -218,50 +218,48 @@ batch sender because they're not visible to each other.
 
 1. Create another logic app with this name: "SendX12MessagesToBatch" 
 
-2. In the search box, enter "when a http request" as your filter. 
+1. In the search box, enter "when a http request" as your filter. 
 Select this trigger: **When a HTTP request is received** 
 
    ![Add the Request trigger](./media/logic-apps-scenario-EDI-send-batch-messages/add-request-trigger-sender.png)
 
-3. Add an action for sending messages to a batch.
+1. Add an action for sending messages to a batch.
 
    1. Under the HTTP request action, choose **New step**.
 
-   2. In the search box, enter "batch" as your filter. 
+   1. In the search box, enter "batch" as your filter. 
    Select the **Actions** list, and then select this action: 
    **Choose a Logic Apps workflow with batch trigger - Send messages to batch**
 
       ![Select "Choose a Logic Apps workflow with batch trigger"](./media/logic-apps-scenario-EDI-send-batch-messages/batch-sender-select-batch-trigger.png)
 
-   3. Now select your "BatchX12Messages" logic app that you previously created.
+   1. Now select your "BatchX12Messages" logic app that you previously created.
 
       ![Select "batch receiver" logic app](./media/logic-apps-scenario-EDI-send-batch-messages/batch-sender-select-batch-receiver.png)
 
-   4. Select this action: **Batch_messages - <*your-batch-receiver*>**
+   1. Select this action: **Batch_messages - <*your-batch-receiver*>**
 
       ![Select "Batch_messages" action](./media/logic-apps-scenario-EDI-send-batch-messages/batch-sender-select-batch-messages-action.png)
 
-4. Set the batch sender's properties.
+1. Set the batch sender's properties.
 
    | Property | Description | 
    |----------|-------------| 
    | **Batch Name** | The batch name defined by the receiver logic app, which is "TestBatch" in this example <p>**Important**: The batch name gets validated at runtime and must match the name specified by the receiver logic app. Changing the batch name causes the batch sender to fail. | 
    | **Message Content** | The content for the message you want to send, which is the **Body** token in this example | 
-   ||| 
 
    ![Set batch properties](./media/logic-apps-scenario-EDI-send-batch-messages/batch-sender-set-batch-properties.png)
 
-5. Save your logic app. 
+1. Save your logic app. 
 
    Your batch sender logic app looks like this example:
 
    ![Save your batch sender logic app](./media/logic-apps-scenario-EDI-send-batch-messages/batch-sender-finished.png)
 
-## Test your logic apps
+## Test your workflows
 
 To test your batching solution, post X12 messages to your batch sender logic 
-app from [Postman](https://www.getpostman.com/postman) or a similar tool. 
-Soon, you start getting X12 messages in your request bin, 
+app from a local tool or app that can send HTTP requests, such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/). Soon, you start getting X12 messages in your request bin, 
 either every 10 minutes or in batches of 10, all with the same partition key.
 
 ## Next steps

articles/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint.md

@@ -91,7 +91,7 @@ For more information, review [Create single-tenant logic app workflows in Azure
 
    To trigger the workflow, you call or send a request to this URL.
 
-1. Make sure that the URL works by calling or sending a request to the URL. You can use any tool you want to send the request, for example, Postman.
+1. Make sure that the URL works by calling or sending a request to the URL. You can use any local tool or app that you want for creating and sending HTTP requests, such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/).
 
 ### Set up private endpoint connection