Add note about monitoring support for Standard

Author: ecfan

articles/logic-apps/create-monitoring-tracking-queries.md

@@ -10,6 +10,10 @@ ms.date: 01/30/2020
 
 # View and create queries for monitoring and tracking in Azure Monitor logs for Azure Logic Apps
 
+> [!NOTE]
+> This article applies only to Consumption logic apps. For information about monitoring Standard logic apps, review 
+> [Enable or open Application Insights after deployment for Standard logic apps](create-single-tenant-workflows-azure-portal.md#enable-open-application-insights).
+
 You can view the underlying queries that produce the results from [Azure Monitor logs](../azure-monitor/logs/log-query-overview.md) and create queries that filter the results based your specific criteria. For example, you can find messages based on a specific interchange control number. Queries use the [Kusto query language](/azure/data-explorer/kusto/query/), which you can edit if you want to view different results. For more information, see [Azure Monitor log queries](/azure/data-explorer/kusto/query/).
 
 ## Prerequisites

articles/logic-apps/create-single-tenant-workflows-azure-portal.md

@@ -317,11 +317,11 @@ In this example, the workflow runs when the Request trigger receives an inbound
 
       ![Screenshot that shows Outlook email as described in the example](./media/create-single-tenant-workflows-azure-portal/workflow-app-result-email.png)
 
-<a name="view-run-history"></a>
+<a name="review-run-history"></a>
 
 ## Review run history
 
-For a stateful workflow, after each workflow run, you can view the run history, including the status for the overall run, for the trigger, and for each action along with their inputs and outputs. In the Azure portal, run history and trigger histories appear at the workflow level, not the logic app level. To review the trigger histories outside the run history context, see [Review trigger histories](#view-trigger-histories).
+For a stateful workflow, after each workflow run, you can view the run history, including the status for the overall run, for the trigger, and for each action along with their inputs and outputs. In the Azure portal, run history and trigger histories appear at the workflow level, not the logic app level. To review the trigger histories outside the run history context, see [Review trigger histories](#review-trigger-history).
 
 1. In the Azure portal, on the workflow menu, select **Overview**.
 
@@ -381,11 +381,11 @@ For a stateful workflow, after each workflow run, you can view the run history,
 
 1. To further review the raw inputs and outputs for that step, select **Show raw inputs** or **Show raw outputs**.
 
-<a name="view-trigger-histories"></a>
+<a name="review-trigger-history"></a>
 
-## Review trigger histories
+## Review trigger history
 
-For a stateful workflow, you can review the trigger history for each run, including the trigger status along with inputs and outputs, separately from the [run history context](#view-run-history). In the Azure portal, trigger history and run history appear at the workflow level, not the logic app level. To find this historical data, follow these steps:
+For a stateful workflow, you can review the trigger history for each run, including the trigger status along with inputs and outputs, separately from the [run history context](#review-run-history). In the Azure portal, trigger history and run history appear at the workflow level, not the logic app level. To find this historical data, follow these steps:
 
 1. In the Azure portal, on the workflow menu, select **Overview**.
 

articles/logic-apps/monitor-b2b-messages-log-analytics.md

@@ -10,6 +10,10 @@ ms.date: 01/30/2020
 
 # Set up Azure Monitor logs and collect diagnostics data for B2B messages in Azure Logic Apps
 
+> [!NOTE]
+> This article applies only to Consumption logic apps. For information about monitoring Standard logic apps, review 
+> [Enable or open Application Insights after deployment for Standard logic apps](create-single-tenant-workflows-azure-portal.md#enable-open-application-insights).
+
 After you set up B2B communication between trading partners in your integration account, those partners can exchange messages by using protocols such as AS2, X12, and EDIFACT. To check that this communication works the way you expect, you can set up [Azure Monitor logs](../azure-monitor/logs/data-platform-logs.md) for your integration account. [Azure Monitor](../azure-monitor/overview.md) helps you monitor your cloud and on-premises environments so that you can more easily maintain their availability and performance. By using Azure Monitor logs, you can record and store data about runtime data and events, such as trigger events, run events, and action events in a [Log Analytics workspace](../azure-monitor/essentials/resource-logs.md#send-to-log-analytics-workspace). For messages, logging also collects information such as:
 
 * Message count and status

articles/logic-apps/monitor-logic-apps-log-analytics.md

@@ -10,6 +10,10 @@ ms.date: 09/24/2020
 
 # Set up Azure Monitor logs and collect diagnostics data for Azure Logic Apps
 
+> [!NOTE]
+> This article applies only to Consumption logic apps. For information about monitoring Standard logic apps, review 
+> [Enable or open Application Insights after deployment for Standard logic apps](create-single-tenant-workflows-azure-portal.md#enable-open-application-insights).
+
 To get richer debugging information about your logic apps during runtime, you can set up and use [Azure Monitor logs](../azure-monitor/logs/data-platform-logs.md) to record and store information about runtime data and events, such as trigger events, run events, and action events in a [Log Analytics workspace](../azure-monitor/essentials/resource-logs.md#send-to-log-analytics-workspace). [Azure Monitor](../azure-monitor/overview.md) helps you monitor your cloud and on-premises environments so that you can more easily maintain their availability and performance. By using Azure Monitor logs, you can create [log queries](../azure-monitor/logs/log-query-overview.md) that help you collect and review this information. You can also [use this diagnostics data with other Azure services](#extend-data), such as Azure Storage and Azure Event Hubs.
 
 To set up logging for your logic app, you can [enable Log Analytics when you create your logic app](#logging-for-new-logic-apps), or you can [install the Logic Apps Management solution](#install-management-solution) in your Log Analytics workspace for existing logic apps. This solution provides aggregated information for your logic app runs and includes specific details such as status, execution time, resubmission status, and correlation IDs. Then, to enable logging and creating queries for this information, [set up Azure Monitor logs](#set-up-resource-logs).

articles/logic-apps/monitor-logic-apps.md

@@ -10,7 +10,12 @@ ms.date: 05/04/2020
 
 # Monitor run status, review trigger history, and set up alerts for Azure Logic Apps
 
-After you [create and run a logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md), you can check that logic app's run status, [runs history](#review-runs-history), [trigger history](#review-trigger-history), and performance. To get notifications about failures or other possible problems, set up [alerts](#add-azure-alerts). For example, you can create an alert that detects "when more than five runs fail in an hour."
+> [!NOTE]
+> This article applies only to Consumption logic apps. For information about reviewing run status and monitoring for Standard logic apps, 
+> review the following sections in [Create an integration workflow with single-tenant Azure Logic Apps](create-single-tenant-workflows-azure-portal.md): 
+> [Review run history](create-single-tenant-workflows-azure-portal.md#review-run-history), [Review trigger history](create-single-tenant-workflows-azure-portal.md#review-trigger-history), and [Enable or open Application Insights after deployment](create-single-tenant-workflows-azure-portal.md#enable-open-application-insights).
+
+After you create and run a [Consumption logic app workflow](quickstart-create-first-logic-app-workflow.md), you can check that workflow's run status, [runs history](#review-runs-history), [trigger history](#review-trigger-history), and performance. To get notifications about failures or other possible problems, set up [alerts](#add-azure-alerts). For example, you can create an alert that detects "when more than five runs fail in an hour."
 
 For real-time event monitoring and richer debugging, set up diagnostics logging for your logic app by using [Azure Monitor logs](../azure-monitor/overview.md). This Azure service helps you monitor your cloud and on-premises environments so that you can more easily maintain their availability and performance. You can then find and view events, such as trigger events, run events, and action events. By storing this information in [Azure Monitor logs](../azure-monitor/logs/data-platform-logs.md), you can create [log queries](../azure-monitor/logs/log-query-overview.md) that help you find and analyze this information. You can also use this diagnostic data with other Azure services, such as Azure Storage and Azure Event Hubs. For more information, see [Monitor logic apps by using Azure Monitor](../logic-apps/monitor-logic-apps-log-analytics.md).
 
@@ -28,7 +33,7 @@ For real-time event monitoring and richer debugging, set up diagnostics logging
 
 Each time that the trigger fires for an item or event, the Logic Apps engine creates and runs a separate workflow instance for each item or event. By default, each workflow instance runs in parallel so that no workflow has to wait before starting a run. You can review what happened during that run, including the status for each step in the workflow plus the inputs and outputs for each step.
 
-1. In the [Azure portal](https://portal.azure.com), find and open your logic app in the Logic App Designer.
+1. In the [Azure portal](https://portal.azure.com), find and open your logic app workflow in the designer.
 
    To find your logic app, in the main Azure search box, enter `logic apps`, and then select **Logic apps**.
 
@@ -104,7 +109,7 @@ Each time that the trigger fires for an item or event, the Logic Apps engine cre
 
 Each logic app run starts with a trigger. The trigger history lists all the trigger attempts that your logic app made and information about the inputs and outputs for each trigger attempt.
 
-1. In the [Azure portal](https://portal.azure.com), find and open your logic app in the Logic App Designer.
+1. In the [Azure portal](https://portal.azure.com), find and open your logic app workflow in the designer.
 
    To find your logic app , in the main Azure search box, enter `logic apps`, and then select **Logic Apps**.
 
@@ -134,8 +139,8 @@ Each logic app run starts with a trigger. The trigger history lists all the trig
    |||
 
    > [!TIP]
-   > You can recheck the trigger without waiting for the next recurrence. On the overview toolbar, select **Run trigger**,
-   > and select the trigger, which forces a check. Or, select **Run** on Logic Apps Designer toolbar.
+   > You can recheck the trigger without waiting for the next recurrence. On the overview toolbar, select **Run Trigger**,
+   > and select the trigger, which forces a check. Or, select **Run Trigger** on designer toolbar.
 
 1. To view information about a specific trigger attempt, on the trigger pane, select that trigger event. If the list shows many trigger attempts, and you can't find the entry that you want, try filtering the list. If you don't find the data that you expect, try selecting **Refresh** on the toolbar.