Clarity edits

ecfan · ecfan · commit 559f68ddfec0 · 2019-10-18T11:55:24.000-07:00
diff --git a/articles/logic-apps/logic-apps-gateway-connection.md b/articles/logic-apps/logic-apps-gateway-connection.md
@@ -13,9 +13,9 @@ 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 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.
+Before you can access data sources on premises from your logic apps, you need to create an Azure resource after you [install the *on-premises data gateway* installed on a local computer](../logic-apps/logic-apps-gateway-install.md). Your logic apps then use this Azure 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).
+This article shows how to create your Azure gateway resource for a previously [installed gateway on your 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).
 
 > [!TIP]
 > To connect to Azure virtual networks, consider creating an 
@@ -53,15 +53,11 @@ Azure Logic Apps supports read and write operations through the data gateway. Ho
 
 * You already [installed the on-premises data gateway on a local computer](../logic-apps/logic-apps-gateway-install.md).
 
-* 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 have the [same Azure account and subscription](../logic-apps/logic-apps-gateway-install.md#requirements) that was used when installing that data gateway.
 
-* Your gateway installation isn't already linked to another Azure gateway resource in Azure.
+* Your gateway installation isn't already registered and claimed by another Azure gateway resource.
 
-  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, 
-  > you need to create an Azure gateway resource for each installation. 
+  When you create a gateway resource in the Azure portal, you select a gateway installation, which links to your gateway resource and only that gateway resource. In Azure Logic Apps, on-premises triggers and actions then use the gateway resource for connecting to on-premises data sources. In these triggers and actions, you select your Azure subscription and the associated gateway resource that you want to use. Each gateway resource links to only one gateway installation, which links to only one Azure account.
 
 <a name="create-gateway-resource"></a>
 
@@ -84,15 +80,15 @@ After you install the gateway on a local computer, create the Azure resource for
    | Property | Description |
    |----------|-------------|
    | **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. |
+   | **Subscription** | Select the Azure subscription for the Azure account that was used for the 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 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. |
+   | **Location** | The same region or 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. Your logic app location can differ from your gateway resource location. |
+   | **Installation Name** | Select a gateway installation, which appears in the list only when these conditions are met: <p><p>- Exists in the same region as the gateway resource that you want to create <br>- Unlinked to another Azure gateway resource <br>- Linked to the same Azure account that you're using to create the gateway resource <p><p>For more information, see the [Frequently asked questions](#faq) section. |
    |||
 
-   Here is an example that shows a gateway installation that exists in the same region as your gateway resource:
+   Here is an example that shows a gateway installation that's in the same region as your gateway resource and is linked to the same Azure account:
 
-   ![Provide details to create your on-premises data gateway](./media/logic-apps-gateway-connection/gateway-details.png)
+   ![Provide details to create data gateway resource](./media/logic-apps-gateway-connection/gateway-details.png)
 
 <a name="connect-logic-app-gateway"></a>
 
@@ -163,14 +159,14 @@ To create a different gateway resource, link your gateway installation to a diff
 
 ## Frequently asked questions
 
-**Q**: Why don't I see my gateway installation when I create the gateway resource in Azure? <br/>
+**Q**: Why doesn't my gateway installation appear when I create my gateway resource in Azure? <br/>
 **A**: This issue can happen for these reasons:
 
-* 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 Azure account has to be the same account that's linked to the gateway installation on the local computer. Check that you're signed in to the Azure portal with the same identity that's linked to the gateway installation.
 
-* 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.
+* Your gateway resource and gateway installation have to use the same region. However, your logic app location can differ from your gateway resource location.
 
-* 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.
+* Your gateway installation is already registered and claimed by another gateway resource. These installations won't appear in the **Installation Name** list. To review your gateway registrations in the Azure portal, find all your Azure resources that have the **On-premises Data Gateways** type across *all* your Azure subscriptions.
 
 [!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
@@ -26,16 +26,18 @@ This article shows how to download, install, and set up your on-premises data ga
 
 ## 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 an Azure account with a 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.
 
-    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 account and only that account. Later, in the Azure portal, you need to use the same Azure account for creating an Azure gateway resource that registers and claims 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 
-    > various Azure subscriptions. Each gateway resource is linked to a single gateway installation.
+    > You can link only one gateway installation and one Azure gateway resource to each other. 
+    > You can't link the same gateway installation to multiple Azure accounts or Azure gateway resources. 
+    > However, an Azure account can link to multiple gateway installations and Azure gateway resources. 
+    > In an on-premises trigger or action, you can select from your various Azure subscriptions, 
+    > and then select an associated gateway resource.
 
   * You need to sign in with either a work account or school account, also known as an *organization* account, which looks like `username@contoso.com`. You can't use Azure B2B (guest) accounts or personal Microsoft accounts, such as @hotmail.com or @outlook.com.
 
@@ -45,10 +47,12 @@ This article shows how to download, install, and set up your on-premises data ga
     > within a tenant in an Azure Active Directory (Azure AD). In most cases, the User Principal 
     > Name (UPN) for your Azure AD account is the same as your email address.
     >
-    > To use a [Visual Studio Standard subscription](https://visualstudio.microsoft.com/vs/pricing/) that's associated 
-    > with a Microsoft account, first [create a tenant in Azure AD](../active-directory/develop/quickstart-create-new-tenant.md), 
-    > or use the default directory. Add a user with a password to the directory, then give that user access to your subscription. 
-    > You can then sign in during gateway installation with this username and password.
+    > To use a [Visual Studio Standard subscription](https://visualstudio.microsoft.com/vs/pricing/) 
+    > that's linked to a Microsoft account, first 
+    > [create a tenant in Azure AD](../active-directory/develop/quickstart-create-new-tenant.md)
+    > or use the default directory. Add a user with a password to the directory, and then give that 
+    > user access to your Azure subscription. You can then sign in during gateway installation 
+    > with this username and password.
 
 * Here are requirements for your local computer:
 
@@ -104,11 +108,11 @@ This article shows how to download, install, and set up your on-premises data ga
 
    ![Review requirements and accept terms of use](./media/logic-apps-gateway-install/accept-terms.png)
 
-1. After the gateway successfully installs, provide the email address for your Azure subscription, and then select **Sign in**, for example:
+1. After the gateway successfully installs, provide the email address for your Azure account, and then select **Sign in**, for example:
 
    ![Sign in with work or school account](./media/logic-apps-gateway-install/sign-in-gateway-install.png)
 
-   Your gateway installation can map to one Azure account and subscription.
+   Your gateway installation can link to only one Azure account.
 
 1. Select **Register a new gateway on this computer** > **Next**. This step registers your gateway installation with the [gateway cloud service](#gateway-cloud-service).
 
@@ -166,7 +170,7 @@ The on-premises data gateway depends on [Azure Service Bus](../service-bus-messa
 
 To avoid single points of failure for on-premises data access, you can have multiple gateway installations (standard mode only) with each on a different computer, and set them up as a cluster or group. That way, if the primary gateway is unavailable, data requests are routed to the second gateway, and so on. Because you can install only one standard gateway on a computer, you must install each additional gateway that's in the cluster on a different computer. All the connectors that work with the on-premises data gateway support high availability.
 
-* You must already have at least one gateway installation within the same Azure subscription as the primary gateway and the recovery key for that installation.
+* You must already have at least one gateway installation with the same Azure account as the primary gateway and the recovery key for that installation.
 
 * Your primary gateway must be running the gateway update from November 2017 or later.
 
@@ -248,15 +252,15 @@ These steps describe what happens when you interact with an element that's conne
 
 A stored credential is used to connect from the gateway to on-premises data sources. Regardless of the user, the gateway uses the stored credential to connect. There might be authentication exceptions for specific services, such as DirectQuery and LiveConnect for Analysis Services in Power BI.
 
-### Azure Active Directory
+### Azure Active Directory (Azure AD)
 
-Microsoft cloud services use [Azure Active Directory (Azure AD)](../active-directory/fundamentals/active-directory-whatis.md) to authenticate users. An Azure AD tenant contains usernames and security groups. Typically, the email address that you use for sign-in is the same as the User Principal Name (UPN) for your account.
+Microsoft cloud services use [Azure AD](../active-directory/fundamentals/active-directory-whatis.md) to authenticate users. An Azure AD tenant contains usernames and security groups. Typically, the email address that you use for sign-in is the same as the User Principal Name (UPN) for your account.
 
 ### What is my UPN?
 
 If you're not a domain admin, you might not know your UPN. To find the UPN for your account, run the `whoami /upn` command from your workstation. Although the result looks like an email address, the result is the UPN for your local domain account.
 
-### Synchronize an on-premises Active Directory with Azure Active Directory
+### Synchronize an on-premises Active Directory with Azure AD
 
 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.
 
