You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-signalr/includes/signalr-add-role-assignments.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.author: tefa
9
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 (application) over 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 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).
13
13
14
14
> [!NOTE]
15
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).
@@ -26,10 +26,10 @@ The following steps describe how to assign a SignalR App Server role to a servic
|[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](/azure/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](/azure/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](/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. |
32
+
|[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. |
33
33
34
34
35
35
1. On the **Members** tab, select **User, group, or service principal**, and then choose **Select members**.
@@ -43,8 +43,8 @@ The following steps describe how to assign a SignalR App Server role to a servic
43
43
44
44
To learn more about how to assign and manage Azure roles, see these articles:
45
45
46
-
-[Assign Azure roles using the Azure portal](../role-based-access-control/role-assignments-portal.yml)
47
-
-[Assign Azure roles using the REST API](../role-based-access-control/role-assignments-rest.md)
48
-
-[Assign Azure roles using Azure PowerShell](../role-based-access-control/role-assignments-powershell.md)
49
-
-[Assign Azure roles using the Azure CLI](../role-based-access-control/role-assignments-cli.md)
50
-
-[Assign Azure roles using Azure Resource Manager templates](../role-based-access-control/role-assignments-template.md)
46
+
-[Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal.yml)
47
+
-[Assign Azure roles using the REST API](/azure/role-based-access-control/role-assignments-rest.md)
48
+
-[Assign Azure roles using Azure PowerShell](/azure/role-based-access-control/role-assignments-powershell.md)
49
+
-[Assign Azure roles using the Azure CLI](/azure/role-based-access-control/role-assignments-cli.md)
50
+
-[Assign Azure roles using Azure Resource Manager templates](/azure/role-based-access-control/role-assignments-template.md)
Copy file name to clipboardExpand all lines: articles/azure-signalr/signalr-concept-authorize-azure-active-directory.md
+14-8Lines changed: 14 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,12 @@ The temporary access key expires in 90 minutes. We recommend that you get a new
44
44
45
45
The workflow is built in the [Azure SignalR Service SDK for app servers](https://github.com/Azure/azure-signalr).
46
46
47
+
### Cross tenant access when using Microsoft Entra ID
48
+
49
+
In some cases, your server and your Azure SignalR resource may not in the same tenant for security concerns.
50
+
51
+
A [Multi-tenant applications](/entra/identity-platform/single-and-multi-tenant-apps#best-practices-for-multitenant-apps) could help you in this scenario.
52
+
47
53
## Assign Azure roles for access rights
48
54
49
55
Microsoft Entra ID authorizes access rights to secured resources through [Azure RBAC](../role-based-access-control/overview.md). Azure SignalR Service defines a set of Azure built-in roles that encompass common sets of permissions for accessing Azure SignalR Service resources. You can also define custom roles for access to Azure SignalR Service resources.
@@ -65,19 +71,19 @@ You can scope access to Azure SignalR Service resources at the following levels,
|[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. |
69
-
|[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. |
70
-
|[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. |
71
-
| [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.
74
+
|[SignalR App Server](/azure/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. |
75
+
|[SignalR Service Owner](/azure/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. |
76
+
|[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. |
77
+
| [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.
72
78
73
79
## Next steps
74
80
75
-
- To learn how to create an Azure application and use Microsoft Entra authorization, see [Authorize requests to Azure SignalR Service resources with Microsoft Entra applications](signalr-howto-authorize-application.md).
81
+
- To learn how to create an Azure application and use Microsoft Entra authorization, see [Authorize requests to Azure SignalR Service resources with Microsoft Entra applications](./signalr-howto-authorize-application.md).
76
82
77
-
- To learn how to configure a managed identity and use Microsoft Entra authorization, see [Authorize requests to Azure SignalR Service resources with Microsoft Entra managed identities](signalr-howto-authorize-managed-identity.md).
83
+
- To learn how to configure a managed identity and use Microsoft Entra authorization, see [Authorize requests to Azure SignalR Service resources with Microsoft Entra managed identities](./signalr-howto-authorize-managed-identity.md).
78
84
79
-
- To learn more about roles and role assignments, see [What is Azure role-based access control (Azure RBAC)?](../role-based-access-control/overview.md).
85
+
- To learn more about roles and role assignments, see [What is Azure role-based access control (Azure RBAC)?](/azure/role-based-access-control/overview.md).
80
86
81
-
- To learn how to create custom roles, see [Steps to create a custom role](../role-based-access-control/custom-roles.md#steps-to-create-a-custom-role).
87
+
- To learn how to create custom roles, see [Steps to create a custom role](/azure/role-based-access-control/custom-roles.md#steps-to-create-a-custom-role).
82
88
83
89
- To learn how to use only Microsoft Entra authentication, see [Disable local authentication](./howto-disable-local-auth.md).
Credentials can be different for different endpoints.
68
+
69
+
In this sample, the Azure SignalR SDK will connect to `resource1` with system-assigned managed identity and connect to `resource2` with user-assigned managed identity.
0 commit comments