Merge pull request #113653 from ecfan/ise-connectivity

Clarity edits about ISE internal endpoints

Author: ttorble

articles/logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md

@@ -120,10 +120,14 @@ When you create your ISE, you can choose to use either internal or external acce
 > [!IMPORTANT]
 > You can select the access endpoint only during ISE creation and can't change this option later.
 
-* **Internal**: Private endpoints permit calls to logic apps in your ISE where you can view and access inputs and outputs from logic apps' runs history *only from inside your virtual network*. Make sure that you have network connectivity between the ISE's private endpoints and the client computer where you view runs history. For example, you can have a computer in a virtual network that's peered with the virtual network for your ISE.
+* **Internal**: Private endpoints permit calls to logic apps in your ISE where you can view and access inputs and outputs from logic apps' runs history *only from inside your virtual network*. Make sure that you have network connectivity between the private endpoints and the computer from where you want to access runs history. For example, your client computer can exist inside the ISE's virtual network or inside a virtual network that's connected to the ISE's virtual network, for example, through peering or a virtual private network.
 
 * **External**: Public endpoints permit calls to logic apps in your ISE where you can view and access inputs and outputs from logic apps' runs history *from outside your virtual network*. If you use network security groups (NSGs), make sure they're set up with inbound rules to allow access to the run history's inputs and outputs. For more information, see [Enable access for ISE](../logic-apps/connect-virtual-network-vnet-isolated-environment.md#enable-access).
 
+To determine whether your ISE uses an internal or external access endpoint, on your ISE's menu, under **Settings**, select **Properties**, and find the **Access endpoint** property:
+
+![Find ISE access endpoint](./media/connect-virtual-network-vnet-isolated-environment-overview/find-ise-access-endpoint.png)
+
 <a name="create-integration-account-environment"></a>
 
 ## Integration accounts with ISE

articles/logic-apps/media/connect-virtual-network-vnet-isolated-environment-overview/find-ise-access-endpoint.png

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: divswa, logicappspm
 ms.topic: article
-ms.date: 01/30/2020
+ms.date: 05/04/2020
 ---
 
 # Monitor run status, review trigger history, and set up alerts for Azure Logic Apps
@@ -14,7 +14,13 @@ After you [create and run a logic app](../logic-apps/quickstart-create-first-log
 
 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/platform/data-platform-logs.md), you can create [log queries](../azure-monitor/log-query/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).
 
-[!INCLUDE [azure-monitor-log-analytics-rebrand](../../includes/azure-monitor-log-analytics-rebrand.md)]
+> [!NOTE]
+> If your logic apps run in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md) 
+> that was created to use an [internal access endpoint](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md#endpoint-access), 
+> you can view and access inputs and outputs from logic app's runs history *only from inside your virtual network*. Make sure that you have network 
+> connectivity between the private endpoints and the computer from where you want to access runs history. For example, your client computer can exist 
+> inside the ISE's virtual network or inside a virtual network that's connected to the ISE's virtual network, for example, through peering or a virtual 
+> private network. For more information, see [ISE endpoint access](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md#endpoint-access). 
 
 <a name="review-runs-history"></a>