Skip to content

Commit 2521cad

Browse files
Update links
1 parent cee7db7 commit 2521cad

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-signalr/signalr-concept-serverless-development-config.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ A client application requires a valid access token to connect to Azure SignalR S
3535

3636
Use an HTTP triggered Azure Function and the *SignalRConnectionInfo* input binding to generate the connection information object. The function must have an HTTP route that ends in `/negotiate`.
3737

38-
For more information on how to create the negotiate function, see the [*SignalRConnectionInfo* input binding reference](../azure-functions/functions-bindings-signalr-service.md#input).
38+
For more information on how to create the negotiate function, see the [*SignalRConnectionInfo* input binding reference](../azure-functions/functions-bindings-signalr-service-input.md).
3939

4040
To learn about how to create an authenticated token, refer to [Using App Service Authentication](#using-app-service-authentication).
4141

@@ -45,7 +45,7 @@ Use the *SignalR* output binding to send messages to clients connected to Azure
4545

4646
Users can be added to one or more groups. You can also use the *SignalR* output binding to add or remove users to/from groups.
4747

48-
For more information, see the [*SignalR* output binding reference](../azure-functions/functions-bindings-signalr-service.md#output).
48+
For more information, see the [*SignalR* output binding reference](../azure-functions/functions-bindings-signalr-service-output.md).
4949

5050
### SignalR Hubs
5151

0 commit comments

Comments
 (0)