Skip to content

Commit 7ab14a0

Browse files
committed
edits
1 parent 09ee9b8 commit 7ab14a0

File tree

1 file changed

+3
-10
lines changed

1 file changed

+3
-10
lines changed

articles/azure-signalr/howto-use-managed-identity.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This article shows you how to create a managed identity for Azure SignalR Servic
2121

2222
## Prerequisites
2323

24-
To use a managed identity, you must have the following:
24+
To use a managed identity, you must have the following items:
2525

2626
- An Azure subscription. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
2727
- An Azure SignalR resource.
@@ -61,8 +61,6 @@ To add a user-assigned identity to your SignalR instance, you need to create the
6161
## Use a managed identity in serverless scenarios
6262

6363
Azure SignalR Service is a fully managed service. It uses a managed identity to obtain an access token. In serverless scenarios, the service adds the access token into the `Authorization` header in an upstream request.
64-
> [!NOTE]
65-
> QUESTION: Is this a specific type of upstream request? If so, we should say so.
6664

6765
### Enable managed identity authentication in upstream settings
6866

@@ -71,9 +69,7 @@ Once you've added a [system-assigned identity](#add-a-system-assigned-identity)
7169
1. Browse to your SignalR instance.
7270
1. Select **Settings** from the menu.
7371
1. Select the **Serverless** service mode.
74-
1. Enter the upstream URL pattern in the **Add an upstream URL pattern** text box.
75-
> [!NOTE]
76-
> QUESTION: Where do I get the upstream URL pattern?
72+
1. Enter the upstream URL pattern in the **Add an upstream URL pattern** text box. See [URL template settings](concept-upstream#url-template-settings)
7773
1. Select Add one Upstream Setting and select any asterisk to get into a detailed page as shown below.
7874
:::image type="content" source="media/signalr-howto-use-managed-identity/pre-msi-settings.png" alt-text="pre-msi-setting":::
7975

@@ -112,10 +108,7 @@ You can easily set access validation for a Function App without code changes usi
112108
1. Navigate to SignalR Service and follow the [steps](howto-use-managed-identity.md#add-a-system-assigned-identity) to add a system-assigned identity or user-assigned identity.
113109
1. go to **Upstream settings** in SignalR Service and choose **Use Managed Identity** and **Select from existing Applications**. Select the application you created previously.
114110

115-
> [!NOTE]
116-
> QUESTION: What application was created previously? The Function App?
117-
118-
After configuring these settings, the Function App will reject requests without an access token in the header.
111+
After you configure these settings, the Function App will reject requests without an access token in the header.
119112

120113
> [!IMPORTANT]
121114
> To pass the authentication, the *Issuer Url* must match the *iss* claim in token. Currently, we only support v1 endpoint (see [v1.0 and v2.0](../active-directory/develop/access-tokens.md)).

0 commit comments

Comments
 (0)