Merge pull request #230870 from ecfan/sql

Azure Logic Apps: SQL Server connector - Clarity updates

Author: American-Dipper

articles/connectors/connectors-create-api-sqlazure.md

@@ -108,7 +108,7 @@ The following steps use the Azure portal, but with the appropriate Azure Logic A
 
 1. In the [Azure portal](https://portal.azure.com), open your blank logic app workflow in the designer.
 
-1. Find and select the [SQL Server trigger](/connectors/sql) that you want to use.
+1. Find and select the [SQL Server trigger](/connectors/sql/#trigger) that you want to use.
 
    1. On the designer, under the search box, select **Standard**.
 
@@ -122,9 +122,9 @@ The following steps use the Azure portal, but with the appropriate Azure Logic A
 
 1. Provide the [information for your connection](#create-connection). When you're done, select **Create**.
 
-1. After the trigger information box appears, specify the interval and frequency for how often the trigger checks the table.
+1. Provide the information required by [your selected trigger](/connectors/sql/#triggers).
 
-1. To add other properties available for this trigger, open the **Add new parameter** list and select those properties.
+1. If any other properties are available for this trigger, open the **Add new parameter** list, and select those properties relevant to your scenario.
 
    This trigger returns only one row from the selected table, and nothing else. To perform other tasks, continue by adding either a [SQL Server connector action](#add-sql-action) or another action that performs the next task that you want in your logic app workflow.
 
@@ -136,7 +136,7 @@ The following steps use the Azure portal, but with the appropriate Azure Logic A
 
 1. In the [Azure portal](https://portal.azure.com), open your blank logic app workflow in the designer.
 
-1. Find and select the SQL Server trigger that you want.
+1. Find and select the SQL Server trigger that you want to use.
 
    1. On the designer, select **Choose an operation**.
 
@@ -146,23 +146,35 @@ The following steps use the Azure portal, but with the appropriate Azure Logic A
 
       * **Azure** to view the [SQL Server managed connector triggers](/connectors/sql/#triggers)
 
-      This example continues with the SQL Server built-in connector.
-
    1. In the search box, enter **sql server**.
 
    1. From the triggers list, select the SQL trigger that you want.
 
-      This example continues with the trigger named **When a row is inserted**.
+      * [Built-in connector triggers](/azure/logic-apps/connectors/built-in/reference/sql/#triggers)
+
+        This example selects the built-in trigger named **When a row is inserted**.
+
+        ![Screenshot showing Standard workflow designer and the selected built-in trigger named When a row is inserted.](./media/connectors-create-api-sqlazure/select-trigger-built-in-standard.png)
+
+      * [Managed connector triggers](/connectors/sql/#triggers)
+
+        This example selects the built-in trigger named **When a row is created**.
+
+        ![Screenshot showing Standard workflow designer and the selected managed trigger named When a row is created.](./media/connectors-create-api-sqlazure/select-trigger-managed-standard.png)
+
+1. Provide the [information for your connection](#create-connection). When you're done, select **Create**.
+
+1. Provide the information required by your selected [built-in trigger](/azure/logic-apps/connectors/built-in/reference/sql/#triggers) or [managed trigger](/connectors/sql/#triggers).
 
-1. Provide the [information for your connection](#create-connection). When you're done, select **Create**.  
+   The following example continues with the built-in trigger named **When a row is inserted**. From the **Table name** list, select the table that you want to use.
 
-1. After the trigger information box appears, specify the interval and frequency for how often the trigger checks the table.
+   ![Screenshot showing Standard workflow designer and the built-in action named When a row is inserted.](./media/connectors-create-api-sqlazure/when-row-inserted-standard.png)
 
-1. To add other properties available for this trigger, open the **Add new parameter** list and select those properties.
+1. If any other properties are available for this trigger, open the **Add new parameter** list, and select those properties relevant to your scenario.
 
-   This trigger returns the row that you inserted in the selected table, and nothing else. To perform other tasks, continue by adding either another SQL Server action or another action that performs the next task that you want in your logic app workflow.
+   In this example, the **When a row is inserted** built-in trigger returns the row that you inserted in the selected table, and nothing else. To perform other tasks, continue by adding either another SQL Server action or another action that performs the next task that you want in your logic app workflow.
 
-   For example, to view the data in this row, you can add other actions that create a file that includes the fields from the returned row, and then send email alerts. To learn about other available actions for this connector, see the [SQL Server built-in connector reference](/azure/logic-apps/connectors/built-in/reference/sql/#triggers) or the [SQL Server managed connector reference](/connectors/sql/).
+   For example, to view the data in this row, you can add other actions that create a file that includes the fields from the returned row, and then send email alerts. To learn about other available actions for this connector, see the [SQL Server built-in connector reference](/azure/logic-apps/connectors/built-in/reference/sql/#actions) or the [SQL Server managed connector reference](/connectors/sql/#actions).
 
 1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
@@ -186,7 +198,7 @@ In this example, the logic app workflow starts with the [Recurrence trigger](../
 
 1. In the [Azure portal](https://portal.azure.com), open your logic app workflow in the designer.
 
-1. Find and select the [SQL Server action](/connectors/sql) that you want to use.
+1. Find and select the [SQL Server action](/connectors/sql/#actions) that you want to use.
 
    This example continues with the action named **Get row**.
 
@@ -228,17 +240,13 @@ In this example, the logic app workflow starts with the [Recurrence trigger](../
 
    1. Under the **Choose an operation** search box, select either of the following options:
 
-      * **Built-in** to view the [SQL Server built-in connector actions](/azure/logic-apps/connectors/built-in/reference/sql/#actions) such as **Execute query**
-
-        ![Screenshot showing the Azure portal, workflow designer for Standard logic app, and designer search box with "Built-in" selected underneath.](./media/connectors-create-api-sqlazure/select-built-in-category-standard.png)
-
-      * **Azure** to view the [SQL Server managed connector actions](/connectors/sql/#actions) such as **Get row**
+      * **Built-in** to view the [SQL Server built-in connector actions](/azure/logic-apps/connectors/built-in/reference/sql/#actions)
 
-        ![Screenshot showing the Azure portal, workflow designer for Standard logic app, and designer search box with "Azure" selected underneath.](./media/connectors-create-api-sqlazure/select-azure-category-standard.png)
+     * **Azure** to view the [SQL Server managed connector actions](/connectors/sql/#actions)
 
    1. In the search box, enter **sql server**.
 
-   1. From the actions list, select the SQL Server action that you want.
+   1. From the actions list, select the SQL Server action that you want to use.
 
       * [Built-in connector actions](/azure/logic-apps/connectors/built-in/reference/sql/#actions)
 
@@ -291,9 +299,9 @@ In the connection information box, complete the following steps:
 
    | Authentication | Description |
    |----------------|-------------|
-   | **Connection String** | - Supported only in Standard workflows with the SQL Server built-in connector. <br><br>- Requires the connection string to your SQL server and database. |
-   | **Logic Apps Managed Identity** | - Supported with the SQL Server managed connector and ISE-versioned connector. In Standard workflows, this authentication type is available for the SQL Server built-in connector, but the option is named **Managed identity** instead. <br><br>- Requires the following items: <br><br>--- A valid managed identity that's [enabled on your logic app resource](../logic-apps/create-managed-service-identity.md) and has access to your database. <br><br>--- **SQL DB Contributor** role access to the SQL Server resource <br><br>--- **Contributor** access to the resource group that includes the SQL Server resource. <br><br>For more information, see the following documentation: <br><br>- [Managed identity authentication for SQL Server connector](/connectors/sql/#managed-identity-authentication) <br>- [SQL - Server-Level Roles](/sql/relational-databases/security/authentication-access/server-level-roles) |
+   | **Connection string** | - Supported only in Standard workflows with the SQL Server built-in connector. <br><br>- Requires the connection string to your SQL server and database. |
    | **Active Directory OAuth** | - Supported only in Standard workflows with the SQL Server built-in connector. For more information, see the following documentation: <br><br>- [Authentication for SQL Server connector](/connectors/sql/#authentication) <br>- [Enable Azure Active Directory Open Authentication (Azure AD OAuth)](../logic-apps/logic-apps-securing-a-logic-app.md#enable-oauth) <br>- [Azure Active Directory Open Authentication](../logic-apps/logic-apps-securing-a-logic-app.md#azure-active-directory-oauth-authentication) |
+   | **Logic Apps Managed Identity** | - Supported with the SQL Server managed connector and ISE-versioned connector. In Standard workflows, this authentication type is available for the SQL Server built-in connector, but the option is named **Managed identity** instead. <br><br>- Requires the following items: <br><br>--- A valid managed identity that's [enabled on your logic app resource](../logic-apps/create-managed-service-identity.md) and has access to your database. <br><br>--- **SQL DB Contributor** role access to the SQL Server resource <br><br>--- **Contributor** access to the resource group that includes the SQL Server resource. <br><br>For more information, see the following documentation: <br><br>- [Managed identity authentication for SQL Server connector](/connectors/sql/#managed-identity-authentication) <br>- [SQL - Server-Level Roles](/sql/relational-databases/security/authentication-access/server-level-roles) |
    | **Service principal (Azure AD application)** | - Supported with the SQL Server managed connector. <br><br>- Requires an Azure AD application and service principal. For more information, see [Create an Azure AD application and service principal that can access resources using the Azure portal](../active-directory/develop/howto-create-service-principal-portal.md). |
    | [**Azure AD Integrated**](/azure/azure-sql/database/authentication-aad-overview) | - Supported with the SQL Server managed connector and ISE-versioned connector. <br><br>- Requires a valid managed identity in Azure Active Directory (Azure AD) that's [enabled on your logic app resource](../logic-apps/create-managed-service-identity.md) and has access to your database. For more information, see these topics: <br><br>- [Azure SQL Security Overview - Authentication](/azure/azure-sql/database/security-overview#authentication) <br>- [Authorize database access to Azure SQL - Authentication and authorization](/azure/azure-sql/database/logins-create-manage#authentication-and-authorization) <br>- [Azure SQL - Azure AD Integrated authentication](/azure/azure-sql/database/authentication-aad-overview) |
    | [**SQL Server Authentication**](/sql/relational-databases/security/choose-an-authentication-mode#connecting-through-sql-server-authentication) | - Supported with the SQL Server managed connector and ISE-versioned connector. <br><br>- Requires the following items: <br><br>--- A data gateway resource that's previously created in Azure for your connection, regardless whether your logic app is in multi-tenant Azure Logic Apps or an ISE. <br><br>--- A valid user name and strong password that are created and stored in your SQL Server database. For more information, see the following topics: <br><br>- [Azure SQL Security Overview - Authentication](/azure/azure-sql/database/security-overview#authentication) <br>- [Authorize database access to Azure SQL - Authentication and authorization](/azure/azure-sql/database/logins-create-manage#authentication-and-authorization) |
@@ -349,7 +357,7 @@ In the connection information box, complete the following steps:
 
 1. For connections to your on-premises SQL server that require the on-premises data gateway, make sure that you've [completed these prerequisites](#multi-tenant-or-ise).
 
-   Otherwise, your data gateway resource won't appear in the **Connection Gateway** list when you create your connection.
+   Otherwise, your data gateway resource doesn't appear in the **Connection Gateway** list when you create your connection.
 
 1. For **Authentication Type**, select the authentication that's required and enabled on your SQL Server: