Edit content

Author: JKirsch1

articles/logic-apps/logic-apps-scenario-function-sb-trigger.md

@@ -7,49 +7,50 @@ ms.reviewer: estfan, azla
 ms.topic: how-to
 ms.date: 11/08/2019
 ms.custom: devx-track-csharp
+#Customer intent: As a logic apps developer, I want to use Azure Logic Apps to respond automatically and instantaneously to Azure Service Bus messages so that I don't have to monitor the messages manually.
 ---
 
 # Call or trigger logic apps by using Azure Functions and Azure Service Bus
 
 [!INCLUDE [logic-apps-sku-consumption](../../includes/logic-apps-sku-consumption.md)]
 
-You can use [Azure Functions](../azure-functions/functions-overview.md) to trigger a logic app when you need to deploy a long-running listener or task. For example, you can create a function that listens in on an [Azure Service Bus](../service-bus-messaging/service-bus-messaging-overview.md) queue and immediately fires a logic app as a push trigger.
+You can use [Azure Functions](../azure-functions/functions-overview.md) to trigger a logic app workflow when you need to deploy a long-running listener or task. For example, you can create a function that listens in on an [Azure Service Bus](../service-bus-messaging/service-bus-messaging-overview.md) queue and immediately fires a logic app as a push trigger.
 
 ## Prerequisites
 
-* An Azure subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/).
+* An Azure account and subscription. If you don't have a subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
 * An Azure Service Bus namespace. If you don't have a namespace, [create your namespace first](../service-bus-messaging/service-bus-create-namespace-portal.md).
 
 * A function app, which is a container for your functions. If you don't have a function app, [create your function app first](../azure-functions/functions-get-started.md), and make sure that you select .NET as the runtime stack.
 
-* Basic knowledge about [how to create logic apps](../logic-apps/quickstart-create-first-logic-app-workflow.md)
+* Basic knowledge about [how to create a Consumption logic app workflow](quickstart-create-first-logic-app-workflow.md) or [how to create a Standard logic app workflow](create-single-tenant-workflows-azure-portal.md).
 
-## Create logic app
+## Create a logic app workflow
 
-For this scenario, you have a function running each logic app that you want to trigger. First, create a logic app that starts with an HTTP request trigger. The function calls that endpoint whenever a queue message is received.
+For this scenario, you have a function running for each logic app that you want to trigger. First, create a logic app workflow that starts with an HTTP request trigger. The function calls that endpoint whenever a queue message is received.
 
 1. Sign in to the [Azure portal](https://portal.azure.com), and create blank logic app.
 
    If you're new to logic apps, review [Quickstart: Create your first logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md).
 
 1. In the search box, enter `http request`. From the triggers list, select the **When a HTTP request is received** trigger.
 
-   ![Select trigger](./media/logic-apps-scenario-function-sb-trigger/when-http-request-received-trigger.png)
+   :::image type="content" source="./media/logic-apps-scenario-function-sb-trigger/when-http-request-received-trigger.png" alt-text="Screenshot of the designer in the portal. The search box contains 'http request.' Under 'Triggers,' 'When a HTTP request is received' is highlighted.":::
 
    With the Request trigger, you can optionally enter a JSON schema to use with the queue message. JSON schemas help the Logic App Designer understand the structure for the input data, and make the outputs easier for you to use in your workflow.
 
 1. To specify a schema, enter the schema in the **Request Body JSON Schema** box, for example:
 
-   ![Specify JSON schema](./media/logic-apps-scenario-function-sb-trigger/when-http-request-received-trigger-schema.png)
+   :::image type="content" source="./media/logic-apps-scenario-function-sb-trigger/when-http-request-received-trigger-schema.png" alt-text="Screenshot of the details of an HTTP request trigger. Some JSON code is visible in the 'Request Body JSON Schema' box.":::
 
    If you don't have a schema, but you have a sample payload in JSON format, you can generate a schema from that payload.
 
    1. In the Request trigger, select **Use sample payload to generate schema**.
 
    1. Under **Enter or paste a sample JSON payload**, enter your sample payload, and then select **Done**.
 
-      ![Enter sample payload](./media/logic-apps-scenario-function-sb-trigger/enter-sample-payload.png)
+      :::image type="content" source="./media/logic-apps-scenario-function-sb-trigger/enter-sample-payload.png" alt-text="Screenshot of the details of an HTTP request trigger. Under 'Enter or paste a sample JSON payload,' some payload data is visible.":::
 
    This sample payload generates this schema that appears in the trigger:
 
@@ -89,7 +90,7 @@ For this scenario, you have a function running each logic app that you want to t
 
    The callback URL appears in the **HTTP POST URL** property.
 
-   ![Generated callback URL for trigger](./media/logic-apps-scenario-function-sb-trigger/callback-URL-for-trigger.png)
+   :::image type="content" source="./media/logic-apps-scenario-function-sb-trigger/callback-URL-for-trigger.png" alt-text="Screenshot of the details of an HTTP request trigger. Next to 'HTTP POST URL,' a URL is visible.":::
 
 ## Create a function
 
@@ -99,17 +100,11 @@ Next, create the function that acts as the trigger and listens to the queue.
 
 1. Under your function app name, expand **Functions**. On the **Functions** pane, select **New function**.
 
-   ![Expand "Functions" and select "New function"](./media/logic-apps-scenario-function-sb-trigger/add-new-function-to-function-app.png)
+   :::image type="content" source="./media/logic-apps-scenario-function-sb-trigger/add-new-function-to-function-app.png" alt-text="Screenshot of the 'Functions' page of a function app in the portal, with 'Create' highlighted. On the navigation menu, 'Functions' is highlighted.":::
 
-1. Select this template based on whether you created a new function app where you selected .NET as the runtime stack, or you're using an existing function app.
+1. Select the **Azure Service Bus Queue trigger** template.
 
-   * For new function apps, select this template: **Service Bus Queue trigger**
-
-     ![Select template for new function app](./media/logic-apps-scenario-function-sb-trigger/current-add-queue-trigger-template.png)
-
-   * For an existing function app, select this template: **Service Bus Queue trigger - C#**
-
-     ![Select template for existing function app](./media/logic-apps-scenario-function-sb-trigger/legacy-add-queue-trigger-template.png)
+   :::image type="content" source="./media/logic-apps-scenario-function-sb-trigger/current-add-queue-trigger-template.png" alt-text="Screenshot of the 'Create function' page of a function app in the portal. Under 'Template,' 'Azure Service Bus Queue trigger' is highlighted.":::
 
 1. Under **Template details**, enter a name for your function, and set up the **Service Bus connection** for the queue, which uses the Azure Service Bus SDK `OnMessageReceive()` listener. Next, enter the queue name, and then select **Create**.
 
@@ -142,9 +137,23 @@ Next, create the function that acts as the trigger and listens to the queue.
    }
    ```
 
-1. To test the function, add a queue message by using a tool such as the [Service Bus Explorer](https://github.com/paolosalvatori/ServiceBusExplorer).
+## Test your logic app workflow
+
+1. To test your logic app workflow, use a tool to add a message to your Service Bus queue.
+
+1. In the Azure portal, open your Service Bus namespace.
+
+1. On the Service Bus namespace navigation menu, select **Queues**.
+
+   :::image type="content" source="./media/logic-apps-scenario-function-sb-trigger/service-bus-namespace-queues.png" alt-text="Screenshot of a Service Bus namespace in the Azure portal. On the navigation menu, 'Queues' is highlighted.":::
+
+1. Select the queue that you linked to your function through its Service Bus connection.
+
+1. On the queue navigation menu, select **Service Bus Explorer**, and then select **Send messages**.
+   
+   :::image type="content" source="./media/logic-apps-scenario-function-sb-trigger/select-service-bus-explorer.png" alt-text="Screenshot of a Service Bus queue page in the portal, with 'Send message' highlighted. On the navigation menu, 'Service Bus Explorer' is highlighted.":::
 
-   The logic app triggers immediately after the function receives the message.
+1. Use the tool to send a message to your Service Bus queue. The message triggers your logic app.
 
 ## Next steps