Azure Functions with Azure SignalR returning error 500 after successful Negotiate

Ivan Ferro 5

I have setup an Azure SignalR service (Serverless) with Azure Functions (Isolated).

I have the Azure Functions service configured with a Microsoft Identity Provider.

I can login with Microsoft correctly and use the token received to call the Http function Negotiate, which works correctly and returns the URL and Access Token needed to connect with the HubConnectionBuilder.

The HubConnection is also successful, but the OnConnected function doesn't get triggered.

Then trying to manually invoke any other SignalRTrigger function returns a 500 error, and I can't see the function ever being executed in the logs, so I can't figure out why this is happening.

My Azure SignalR service has System assigned identity turned on, and I have two upstreams configured - one with the signalr_extension key and one with the default Azure Functions key (in that order) - both with the Use Managed Identity option selected and Select from existing Applications pointing to the Azure Functions Identity Provider App Registration.

I also have the Configuration settings in Azure Functions with the AzureSignalRConnectionString (tried changing it but then the Negotiate function also returns a 500 error).

navba-MSFT 17,735 Reputation points Microsoft Employee

2023-08-17T07:28:37.67+00:00
@Ivan Ferro Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

I see that you are encountering the HTTP 500 error code while invoking the SignalRTrigger function and can't see the function ever being executed in the logs.

Please follow the below action plan for now:

Could you please enable the Application insight logs for the FunctionApp and check if there are any invocation exceptions. You can enabled the AppInsights as explained here.You can enabled the AppInsights as explained here.

Enable the server-side logging for Azure SignalR Service issue during negotiate. This trace will help trace to find out the error details when the server tries to connect to Azure SignalR Service. More Info here.

Please check Functions metrics for the HTTP Server Errors at the time of the issue.

Could you also check How to handle errors in the Hub class so that you can confirm if there are any exceptions there.

Please check the Function App detectors by navigating to the Diagnose and Solve Problems section in the Azure Portal for the Functions as shown below: You can rely on the Function App Down or Reporting Errors setting:

You can also query the FunctionLogs as shown below:

More Info here.

Note: If none of the above steps help, Please share the below details over an email at AzCommunity@microsoft.com ( with subject "Attn: Naveen") and include the below details:

Your Azure Function Name

You Azure Function App resource URI in below format: /subscriptions/XXXXXXXXXX/resourceGroups/XXXXXX/providers/Microsoft.Web/sites/XXXXXX

Most recent UTC time of the actual issue where you received HTTP 500 error

Azure SignalR service name and subscription id.

I will look at the backend logs to identify the root cause.

**
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
navba-MSFT 17,735 Reputation points Microsoft Employee

2023-08-19T03:43:16.7033333+00:00

@Ivan Ferro Thanks for sharing the details. I have replied to your email with a set of questions. Please reply once you get a chance.

Share via

Azure Functions with Azure SignalR returning error 500 after successful Negotiate