|
1 | 1 | ---
|
2 |
| -title: include file |
3 |
| -description: include file |
| 2 | +title: Include file |
| 3 | +description: Include file |
4 | 4 | author: terencefan
|
5 | 5 | ms.service: azure-signalr-service
|
6 |
| -ms.topic: include |
| 6 | +ms.topic: Include |
7 | 7 | ms.date: 03/12/2025
|
8 | 8 | ms.author: tefa
|
9 |
| -ms.custom: include file |
| 9 | +ms.custom: Include file |
10 | 10 | ---
|
11 | 11 |
|
12 |
| -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](../../role-based-access-control/role-assignments-portal.yml). |
| 12 | +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 by using the Azure portal](../../role-based-access-control/role-assignments-portal.yml). |
13 | 13 |
|
14 | 14 | > [!NOTE]
|
15 |
| -> 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). |
| 15 | +> You can assign a role 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). |
16 | 16 |
|
17 | 17 | 1. In the [Azure portal](https://portal.azure.com/), go to your Azure SignalR Service resource.
|
18 | 18 |
|
19 |
| -1. Select **Access control (IAM)** in the sidebar. |
| 19 | +1. On the left pane, select **Access control (IAM)**. |
20 | 20 |
|
21 | 21 | 1. Select **Add** > **Add role assignment**.
|
22 | 22 |
|
23 | 23 | :::image type="content" source="~/reusable-content/ce-skilling/azure/media/role-based-access-control/add-role-assignment-menu-generic.png" alt-text="Screenshot that shows the page for access control and selections for adding a role assignment.":::
|
24 | 24 |
|
25 |
| -1. On the **Role** tab, select **SignalR App Server** or other SignalR built-in roles depends on your scenario. |
| 25 | +1. On the **Role** tab, select **SignalR App Server**. Other Azure SignalR Service built-in roles depend on your scenario. |
26 | 26 |
|
27 | 27 | | Role | Description | Use case |
|
28 | 28 | | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
|
29 |
| - | [SignalR App Server](../../role-based-access-control/built-in-roles.md#signalr-app-server) | Access to the server connection creation and key generation APIs. | Most commonly used for app server with Azure SignalR resource run in **Default** mode. | |
30 |
| - | [SignalR Service Owner](../../role-based-access-control/built-in-roles.md#signalr-service-owner) | Full access to all data-plane APIs, including REST APIs, the server connection creation, and key/token generation APIs. | For negotiation server with Azure SignalR resource run in **Serverless** mode, as it requires both REST API permissions and authentication API permissions. | |
31 |
| - | [SignalR REST API Owner](../../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. | |
32 |
| - | [SignalR REST API Reader](../../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. | |
| 29 | + | [SignalR App Server](../../role-based-access-control/built-in-roles.md#signalr-app-server) | Access to the APIs that create server connections and generate keys. | Most commonly used for an app server with an Azure SignalR resource running in Default mode. | |
| 30 | + | [SignalR Service Owner](../../role-based-access-control/built-in-roles.md#signalr-service-owner) | Full access to all data-plane APIs, including REST APIs, the APIs that create server connections, and the APIs that generate keys/tokens. | Used for a negotiation server with an Azure SignalR Service resource running in Serverless mode. It requires both REST API permissions and authentication API permissions. | |
| 31 | + | [SignalR REST API Owner](../../role-based-access-control/built-in-roles.md#signalr-rest-api-owner) | Full access to data-plane REST APIs. | Used for the [Azure SignalR Management SDK](/azure/azure-signalr/signalr-howto-use-management-sdk) to manage connections and groups, but it *doesn't* make server connections or handle negotiation requests. | |
| 32 | + | [SignalR REST API Reader](../../role-based-access-control/built-in-roles.md#signalr-rest-api-reader) | Read-only access to data-plane REST APIs. | Used when you write a monitoring tool that calls read-only REST APIs. | |
33 | 33 |
|
34 |
| -1. Select Next. |
| 34 | +1. Select **Next**. |
35 | 35 |
|
| 36 | +1. For Microsoft Entra application: |
36 | 37 |
|
37 |
| -1. For Microsoft Entra application. |
| 38 | + 1. In the **Assign access to** row, select **User, group, or service principal**. |
| 39 | + 1. In the **Members** row, choose **select members**, and then choose the identity in the pop-up window. |
38 | 40 |
|
| 41 | +1. For managed identity for Azure resources: |
39 | 42 |
|
40 |
| - 1. In the `Assign access` to row, select **User, group, or service principal**. |
41 |
| - 1. In the `Members` row, click `select members`, then choose the identity in the pop-up window. |
| 43 | + 1. In the **Assign access to** row, select **Managed identity**. |
| 44 | + 1. In the **Members** row, choose **select members**, and then choose the application in the pop-up window. |
42 | 45 |
|
43 |
| -1. For managed identity for Azure resources. |
| 46 | +1. Select **Next**. |
44 | 47 |
|
45 |
| - 1. In the `Assign access` to row, select **Managed identity**. |
46 |
| - 1. In the `Members` row, click `select members`, then choose the application in the pop-up window. |
47 |
| - |
48 |
| -1. Select Next. |
49 |
| - |
50 |
| - |
51 |
| -1. Review your assignment, then click **Review + assign** to confirm the role assignment. |
| 48 | +1. Review your assignment, and then select **Review + assign** to confirm the role assignment. |
52 | 49 |
|
53 | 50 | > [!IMPORTANT]
|
54 | 51 | > Newly added role assignments might take up to 30 minutes to propagate.
|
55 | 52 |
|
56 |
| -To learn more about how to assign and manage Azure roles, see these articles: |
| 53 | +To learn more about how to assign and manage Azure roles, see: |
57 | 54 |
|
58 |
| -- [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml) |
59 |
| -- [Assign Azure roles using the REST API](../../role-based-access-control/role-assignments-rest.md) |
60 |
| -- [Assign Azure roles using Azure PowerShell](../../role-based-access-control/role-assignments-powershell.md) |
61 |
| -- [Assign Azure roles using the Azure CLI](../../role-based-access-control/role-assignments-cli.md) |
62 |
| -- [Assign Azure roles using Azure Resource Manager templates](../../role-based-access-control/role-assignments-template.md) |
| 55 | +- [Assign Azure roles by using the Azure portal](../../role-based-access-control/role-assignments-portal.yml) |
| 56 | +- [Assign Azure roles by using the REST API](../../role-based-access-control/role-assignments-rest.md) |
| 57 | +- [Assign Azure roles by using Azure PowerShell](../../role-based-access-control/role-assignments-powershell.md) |
| 58 | +- [Assign Azure roles by using the Azure CLI](../../role-based-access-control/role-assignments-cli.md) |
| 59 | +- [Assign Azure roles by using Azure Resource Manager templates](../../role-based-access-control/role-assignments-template.md) |
0 commit comments