Clarity edits and formatting cleanup

ecfan · ecfan · commit c73164143226 · 2019-10-18T10:03:39.000-07:00
diff --git a/articles/logic-apps/logic-apps-gateway-connection.md b/articles/logic-apps/logic-apps-gateway-connection.md
@@ -13,7 +13,7 @@ ms.date: 10/18/2019
 
 # Connect to on-premises data sources from Azure Logic Apps
 
-Before you can access data sources on premises from your logic apps, you need to create an Azure resource for an *on-premises data gateway* that you've already [installed on a local computer](../logic-apps/logic-apps-gateway-install.md). Your logic apps then use this gateway resource in the triggers and actions provided by the [on-premises connectors](../connectors/apis-list.md#on-premises-connectors). 
+Before you can access data sources on premises from your logic apps, you need to create an Azure resource for an *on-premises data gateway* that you've previously [installed on a local computer](../logic-apps/logic-apps-gateway-install.md). Your logic apps then use this gateway resource in the triggers and actions provided by the [on-premises connectors](../connectors/apis-list.md#on-premises-connectors) that are available for Azure Logic Apps.
 
 This article shows how to create your Azure gateway resource *after* you [install the gateway on a local computer](../logic-apps/logic-apps-gateway-install.md). For more information about the gateway, see [How the gateway works](../logic-apps/logic-apps-gateway-install.md#gateway-cloud-service).
 
@@ -32,7 +32,7 @@ For information about how to use the gateway with other services, see these arti
 
 ## Supported data sources
 
-For Azure Logic Apps, the on-premises data gateway supports the [on-premises connectors](../connectors/apis-list.md#on-premises-connectors) for these data sources:
+In Azure Logic Apps, the on-premises data gateway supports the [on-premises connectors](../connectors/apis-list.md#on-premises-connectors) for these data sources:
 
 * BizTalk Server 2016
 * File System
@@ -55,9 +55,9 @@ Azure Logic Apps supports read and write operations through the data gateway. Ho
 
 * You have the [same Azure account and Azure subscription](../logic-apps/logic-apps-gateway-install.md#requirements) that you used when you installed the on-premises data gateway.
 
-* You haven't previously linked your gateway installation to another gateway resource in Azure.
+* Your gateway installation isn't already linked to another Azure gateway resource in Azure.
 
-  When you create a gateway resource in the Azure portal, you select an installed gateway that you link to your gateway resource and only that gateway resource. In Azure Logic Apps, on-premises triggers and actions can then use the gateway resource for connecting to on-premises data sources. In these triggers and actions, you can select a gateway resource from your various Azure subscriptions. Each gateway resource links to only one gateway installation, which links to only one Azure subscription.
+  When you create a gateway resource in the Azure portal, you select a gateway installation that links to your gateway resource and only that gateway resource. In Azure Logic Apps, on-premises triggers and actions can then use the gateway resource for connecting to on-premises data sources. In these triggers and actions, you select a gateway resource from your various Azure subscriptions. However, each gateway resource links to only one gateway installation, which links to only one Azure subscription.
 
   > [!TIP]
   > To use more than one gateway installation in an Azure subscription, 
@@ -67,7 +67,7 @@ Azure Logic Apps supports read and write operations through the data gateway. Ho
 
 ## Create Azure gateway resource
 
-After you install the gateway on a local computer, create the Azure resource for your gateway. 
+After you install the gateway on a local computer, create the Azure resource for your gateway.
 
 1. Sign in to the [Azure portal](https://portal.azure.com) with the same Azure account that was used to install the gateway.
 
@@ -83,14 +83,14 @@ After you install the gateway on a local computer, create the Azure resource for
 
    | Property | Description |
    |----------|-------------|
-   | **Resource Name** | Your gateway resource name, which can contain only letters, numbers, hyphens (`-`), underscores (`_`), parentheses (`(`, `)`), and periods (`.`). |
-   | **Subscription** | Your Azure subscription, which must be the same as gateway installation and logic app. The default subscription is based on the Azure account that you used to sign in. |
+   | **Resource Name** | Provide a name for your gateway resource that contains only letters, numbers, hyphens (`-`), underscores (`_`), parentheses (`(`, `)`), or periods (`.`). |
+   | **Subscription** | Select the same Azure subscription that you used for your gateway installation. The default subscription is based on the Azure account that you used to sign in. |
    | **Resource group** | The [Azure resource group](../azure-resource-manager/resource-group-overview.md) that you want to use |
-   | **Location** | The same region as the location that was selected for the gateway cloud service during [gateway installation](../logic-apps/logic-apps-gateway-install.md). Otherwise, your gateway installation won't appear in the **Installation Name** list for you to select. Your logic app location can differ from your gateway resource location. |
-   | **Installation Name** | Select a gateway installation that's already on a local computer. The list shows only gateway installations that meet these conditions: <p><p>- Not already linked to other Azure gateway resources <br>- Already linked to the Azure account and subscription that you're currently using to create the gateway resource. <p><p>Although a gateway installation maps to only one gateway resource and one subscription, in Azure Logic Apps, on-premises triggers and actions can select a gateway resource from your various Azure subscriptions. |
+   | **Location** | The same region as the location that you selected for the gateway cloud service during [gateway installation](../logic-apps/logic-apps-gateway-install.md). Otherwise, your gateway installation won't appear in the **Installation Name** list for you to select. Your logic app location can differ from your gateway resource location. |
+   | **Installation Name** | Select a gateway installation that already exists on a local computer. The list shows only gateway installations that meet these conditions: <p><p>- Exist in the same region as the gateway resource that you want to create <br>- Not already linked to another Azure gateway resource <br>- Linked to the Azure account and subscription that you're using to create the gateway resource <p><p>Although a gateway installation can link to only one gateway resource and one subscription, in Azure Logic Apps, on-premises triggers and actions can select a gateway resource from your various Azure subscriptions. |
    |||
 
-   Here is an example:
+   Here is an example that shows a gateway installation that exists in the same region as your gateway resource:
 
    ![Provide details to create your on-premises data gateway](./media/logic-apps-gateway-connection/gateway-details.png)
 
@@ -104,7 +104,7 @@ After you create your gateway resource and associate your Azure subscription wit
 
 1. Add a connector that supports on-premises connections, for example, **SQL Server**.
 
-1. Select **Connect via on-premises data gateway**. 
+1. Select **Connect via on-premises data gateway**.
 
 1. Under **Gateways**, from the **Subscriptions** list, select your Azure subscription that has the gateway resource you want.
 
@@ -113,34 +113,34 @@ After you create your gateway resource and associate your Azure subscription wit
    > [!NOTE]
    > The gateways list includes gateway resources in other regions because your 
    > logic app's location can differ from your gateway resource's location. 
- 
+
 1. Provide a unique connection name and other required information, which depends on the connection that you want to create.
 
    A unique connection name helps you easily find that connection later, especially if you create multiple connections. If applicable, also include the qualified domain for your username.
-   
+
    Here is an example:
 
    ![Create connection between logic app and data gateway](./media/logic-apps-gateway-connection/logic-app-gateway-connection.png)
 
-1. When you're done, select **Create**. 
+1. When you're done, select **Create**.
 
 Your gateway connection is now ready for your logic app to use.
 
 ## Edit connection
 
 To update the settings for a gateway connection, you can edit your connection.
 
-1. To find all API connections for just your logic app, on your logic app's menu, under **Development Tools**, select **API connections**.
-   
+1. To find all the API connections for just your logic app, on your logic app's menu, under **Development Tools**, select **API connections**.
+
    ![On your logic app menu, select "API Connections"](./media/logic-apps-gateway-connection/logic-app-find-api-connections.png)
 
 1. Select the gateway connection you want, and then select **Edit API connection**.
 
    > [!TIP]
-   > If your updates don't take effect, 
-   > try [stopping and restarting the gateway Windows service account](../logic-apps/logic-apps-gateway-install.md#restart-gateway) for your gateway installation.
+   > If your updates don't take effect, try 
+   > [stopping and restarting the gateway Windows service account](../logic-apps/logic-apps-gateway-install.md#restart-gateway) for your gateway installation.
 
-To find all API connections associated with your Azure subscription: 
+To find all API connections associated with your Azure subscription:
 
 * From the main Azure menu, go to **All services** > **Web** > **API Connections**.
 * Or, from the main Azure menu, go to **All resources**. Set the **Type** filter to **API Connection**.
@@ -149,7 +149,7 @@ To find all API connections associated with your Azure subscription:
 
 ## Delete gateway resource
 
-To create a different gateway resource, link your gateway installation to a different gateway resource, or remove the gateway resource, you can delete the gateway resource without affecting the gateway installation. 
+To create a different gateway resource, link your gateway installation to a different gateway resource, or remove the gateway resource, you can delete the gateway resource without affecting the gateway installation.
 
 1. From the main Azure menu, select **All resources**. Find and select your gateway resource.
 
@@ -166,9 +166,11 @@ To create a different gateway resource, link your gateway installation to a diff
 **Q**: Why don't I see my gateway installation when I create the gateway resource in Azure? <br/>
 **A**: This issue can happen for these reasons:
 
-* Your gateway installation is already registered and claimed by another gateway resource in Azure. Gateway installations don't appear in the instances list after gateway resources are created for them. To check your gateway registrations in the Azure portal, review all your Azure resources with the **On-premises Data Gateways** type for *all* Azure subscriptions.
+* Your gateway resource and gateway installation need to use the same region. Otherwise, your gateway installation won't appear in the **Installation Name** list for you to select. Your logic app location can differ from your gateway resource location.
+
+* Your gateway installation is already registered and claimed by another gateway resource in Azure. These gateway installations don't appear in the **Installation Name** list after they are linked to gateway resources. To check your gateway registrations in the Azure portal, review all your Azure resources that have the **On-premises Data Gateways** type across *all* your Azure subscriptions.
 
-* The Azure AD identity for the person who installed the gateway differs from the person who signed in to the Azure portal. Check that you're signed in with the same identity that installed the gateway.
+* The Azure account that you're using to create the gateway resource in the Azure portal differs from the Azure account that was used to install and register the gateway on the local computer. Check that you're signed in to the Azure portal with the same identity that was used to installed the gateway.
 
 [!INCLUDE [existing-gateway-location-changed](../../includes/logic-apps-existing-gateway-location-changed.md)]
 
diff --git a/articles/logic-apps/logic-apps-gateway-install.md b/articles/logic-apps/logic-apps-gateway-install.md
@@ -28,10 +28,10 @@ This article shows how to download, install, and set up your on-premises data ga
 
 * An Azure subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/).
 
-  * You need to use the same Azure account to install and to administer the gateway on your local computer. 
+  * You need to use the same Azure account to install and to administer the gateway on your local computer.
+
+    During gateway installation, you sign in with your Azure account, which links your gateway installation to your Azure subscription and only that subscription. Later, in the Azure portal, you need to use the same Azure account for creating an Azure gateway resource that links to your gateway installation. In Azure Logic Apps, on-premises triggers and actions then use the gateway resource for connecting to on-premises data sources.
 
-    During gateway installation, you sign in with your Azure account, which links your gateway installation to your Azure subscription and only that subscription. Later, in the Azure portal, you need to use the same Azure account for creating an Azure gateway resource that links to your gateway installation. In Azure Logic Apps, on-premises triggers and actions then use the gateway resource for connecting to on-premises data sources. 
-    
     > [!NOTE]
     > You can't link the same gateway installation to multiple subscriptions or gateway resources. 
     > However, in an on-premises trigger or action, you can select a gateway resource from your 
@@ -258,9 +258,9 @@ If you're not a domain admin, you might not know your UPN. To find the UPN for y
 
 ### Synchronize an on-premises Active Directory with Azure Active Directory
 
-The UPN for your on-premises Active Directory accounts and Azure AD accounts must be the same. So, make sure that each on-premises Active Directory account matches your Azure AD account. The cloud services know only about accounts within Azure AD. So, you don't need to add an account to your on-premises Active Directory. If the account doesn't exist in Azure AD, you can't use that account. 
+The UPN for your on-premises Active Directory accounts and Azure AD accounts must be the same. So, make sure that each on-premises Active Directory account matches your Azure AD account. The cloud services know only about accounts within Azure AD. So, you don't need to add an account to your on-premises Active Directory. If the account doesn't exist in Azure AD, you can't use that account.
 
-Here are ways that you can match your on-premises Active Directory accounts with Azure AD. 
+Here are ways that you can match your on-premises Active Directory accounts with Azure AD.
 
 * Add accounts manually to Azure AD.
 
