update

Author: terencefan

articles/azure-signalr/includes/signalr-add-role-assignments.md

@@ -9,14 +9,14 @@ ms.author: tefa
 ms.custom: include file
 ---
 
-The following steps describe how to assign a SignalR App Server role to a service principal over an Azure SignalR Service resource. For detailed steps, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal.yml).
+The following steps describe how to assign a **SignalR App Server** role to a service principal or a managed identity for an Azure SignalR Service resource. For detailed steps, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal.yml).
 
 > [!NOTE]
 > A role can be assigned to any scope, including management group, subscription, resource group, or single resource. To learn more about scope, see [Understand scope for Azure RBAC](../role-based-access-control/scope-overview.md).
 
 1. In the [Azure portal](https://portal.azure.com/), go to your Azure SignalR Service resource.
 
-1. Select **Access control (IAM)**.
+1. Select **Access control (IAM)** in the sidebar.
 
 1. Select **Add** > **Add role assignment**.
 
@@ -31,15 +31,24 @@ The following steps describe how to assign a SignalR App Server role to a servic
    | [SignalR REST API Owner](/azure/role-based-access-control/built-in-roles.md#signalr-rest-api-owner)   | Full access to data-plane REST APIs.                                                                      | For using [Azure SignalR Management SDK](/azure/azure-signalr/signalr-howto-use-management-sdk) to manage connections and groups, but does **NOT** make server connections or handle negotiation requests.                          |
    | [SignalR REST API Reader](/azure/role-based-access-control/built-in-roles.md#signalr-rest-api-reader) | Read-only access to data-plane REST APIs.                                                                 | Use it when write a monitoring tool that calls readonly REST APIs.                                      |
 
+1. click Next.
 
-1. On the **Members** tab, select **User, group, or service principal**, and then choose **Select members**.
+1. For Microsoft entra application.
 
-1. Search for and select the application to which you want to assign the role.
+   1. In the `Assign access` to row, select **User, group, or service principal**.
+   1. In the `Members` row, click `select members`, then choose the identity in the pop-up window.
 
-1. On the **Review + assign** tab, select **Review + assign** to assign the role.
+1. For managed identity for Azure resources.
+
+   1. In the `Assign access` to row, select **Managed identity**.
+   1. In the `Members` row, click `select members`, then choose the application in the pop-up window.
+
+1. click Next.
+
+1. Review your assignment, then click **Review + assign** to confirm the role assignment.
 
 > [!IMPORTANT]
-> Azure role assignments might take up to 30 minutes to propagate.
+> Newly added role assignments might take up to 30 minutes to propagate.
 
 To learn more about how to assign and manage Azure roles, see these articles: