Azure Audit Logs Search and Analysis Streamlined with Netwrix AuditorĪdopting cloud services increases the complexity of your IT environment.ServiceHubContext hubContext = serviceManager.CreateHubContextAsync(HubNames.PlanningHub, CancellationToken.None).Result There have been similar topics on the subject that suggest something like this: ServiceManager serviceManager = new ServiceManagerBuilder().WithOptions(option => ).BuildServiceManager() Perhaps this could be the problem, but I'm actually invoking SignalR through IHubContext. I simply fetch a list of users that should receive this message, after which I just invoke: await (x.UserId).SendAsync(.) Īs mentioned before, without Azure SignalR, this works perfectly. Except when broadcasting from the server to a subselection of users, who are retrieved from the cache/database based on several business rules. The hub itself is pretty bland, there's not much going on. + connection.User?.FindFirst('CLAIM2')?.Value! => connection.User?.FindFirst('CLAIM1')?.Value! Public virtual string GetUserId(HubConnectionContext connection) UserIdProvider's code combines two claims from the connection's user: public class UserIdProvider : IUserIdProvider Not much fancy is going on in our app in terms of SignalR config: services Hence the warning message that there aren't any active connections for that user. In the screenshot attached, the user IDs in the first two lines seem to be auto-generated by Azure SignalR Service, while the third row indicates a user id in our app. The result of that is that no message ever arrives in the users’ browsers. However, with Azure SignalR Service, there seems to be a mismatch between connections and User IDs.Ī connection is made, but this doesn’t seem to find its way back to Azure SignalR service, because the other User IDs shown in the trace cannot be traced back to our code. When I use the default, in-memory functionality of SignalR, this works like a charm. I'm using a custom IUserIdProvider in my ASP.NET Core app. In the live trace tool on the Azure portal, I consistently get the message that the user message was not received because there’s no active connection for user XXX

Azure active log