Merge pull request #88394 from ecfan/user-assigned-identity

Updates for user-assigned identity - 02/10/2020

Author: TedA-M

articles/connectors/connectors-native-http.md

@@ -45,10 +45,13 @@ This built-in trigger makes an HTTP call to the specified URL for an endpoint an
 
 1. Provide the values for the [HTTP trigger parameters](../logic-apps/logic-apps-workflow-actions-triggers.md#http-trigger) that you want to include in the call to the target endpoint. Set up the recurrence for how often you want the trigger to check the target endpoint.
 
-   If you select an authentication type other than **None**, the authentication settings differ based on your selection. For more information, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
-
    ![Enter HTTP trigger parameters](./media/connectors-native-http/http-trigger-parameters.png)
 
+   If you select an authentication type other than **None**, the authentication settings differ based on your selection. For more information about authentication types available for HTTP, see these topics:
+
+   * [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound)
+   * [Authenticate access to resources with managed identities](../logic-apps/create-managed-service-identity.md)
+
 1. To add other available parameters, open the **Add new parameter** list, and select the parameters that you want.
 
 1. Continue building your logic app's workflow with actions that run when the trigger fires.
@@ -75,10 +78,13 @@ This built-in action makes an HTTP call to the specified URL for an endpoint and
 
 1. Provide the values for the [HTTP action parameters](../logic-apps/logic-apps-workflow-actions-triggers.md#http-action) that you want to include in the call to the target endpoint.
 
-   If you select an authentication type other than **None**, the authentication settings differ based on your selection. For more information, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
-
    ![Enter HTTP action parameters](./media/connectors-native-http/http-action-parameters.png)
 
+   If you select an authentication type other than **None**, the authentication settings differ based on your selection. For more information about authentication types available for HTTP, see these topics:
+
+   * [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound)
+   * [Authenticate access to resources with managed identities](../logic-apps/create-managed-service-identity.md)
+
 1. To add other available parameters, open the **Add new parameter** list, and select the parameters that you want.
 
 1. When you're done, remember to save your logic app. On the designer toolbar, select **Save**.

articles/connectors/media/connectors-native-http/http-action-multipart.png

@@ -197,11 +197,11 @@ When you want to trigger a logic app from inside an Azure function, the logic ap
 
 To authenticate access to resources in other Azure Active Directory (Azure AD) tenants without having to sign in and provide credentials or secrets, your logic app can use a [managed identity](../active-directory/managed-identities-azure-resources/overview.md) (formerly known as Managed Service Identity or MSI). Azure manages this identity for you and helps secure your credentials because you don't have to provide or rotate secrets. Learn more about [Azure services that support managed identities for Azure AD authentication](../active-directory/managed-identities-azure-resources/services-support-managed-identities.md#azure-services-that-support-azure-ad-authentication).
 
-If you set up your logic app to use the system-assigned managed identity, the Azure functions in your logic app can also use that same identity for authentication. For more information about authentication support for Azure functions in logic apps, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
+If you set up your logic app to use the system-assigned identity or a manually-created user-assigned identity, the Azure functions in your logic app can also use that same identity for authentication. For more information about authentication support for Azure functions in logic apps, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
 
-To set up and use the system-assigned identity with your function, follow these steps:
+To set up and use the managed identity with your function, follow these steps:
 
-1. Enable the system-assigned identity on your logic app, and set up that identity's access to the target resource. See [Authenticate access to Azure resources by using managed identities in Azure Logic Apps](../logic-apps/create-managed-service-identity.md).
+1. Enable the managed identity on your logic app, and set up that identity's access to the target resource. See [Authenticate access to Azure resources by using managed identities in Azure Logic Apps](../logic-apps/create-managed-service-identity.md).
 
 1. Enable authentication in your Azure function and function app by following these steps:
 
@@ -212,7 +212,7 @@ To set up and use the system-assigned identity with your function, follow these
 
 ### Set up anonymous authentication in your function
 
-To use your logic app's system-assigned identity in your Azure function, you have set your function's authentication level to anonymous. Otherwise, your logic app throws a "BadRequest" error.
+To use your logic app's managed identity in your Azure function, you have set your function's authentication level to anonymous. Otherwise, your logic app throws a "BadRequest" error.
 
 1. In the [Azure portal](https://portal.azure.com), find and select your function app. These steps use "FabrikamFunctionApp" as the example function app.
 

articles/connectors/media/connectors-native-http/http-action-parameters.png

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: klam, logicappspm
 ms.topic: article
-ms.date: 01/18/2020
+ms.date: 02/10/2020
 ---
 
 # Limits and configuration information for Azure Logic Apps
@@ -187,8 +187,9 @@ Here are the limits for custom connectors that you can create from web APIs.
 ## Managed identities
 
 | Name | Limit |
-| ---- | ----- |
-| Number of logic apps that have the system-assigned identity in an Azure subscription per region | 100 |
+|------|-------|
+| Managed identities per logic app | Either the system-assigned identity or 1 user-assigned identity |
+| Number of logic apps that have a managed identity in an Azure subscription per region | 100 |
 |||
 
 <a name="integration-account-limits"></a>