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
We have a couple .netcore applications connected to signalr services through aad auth. Last week the clients that connect to the negotiated endpoint get 401 errors. If I change the AddAzureSignalR connection string from the "Endpoint=https://nnn.service.signalr.net;AuthType=aad;" to the Primary connectionstring from Keys in azure portal everything works again. Did something change related to AAD auth?
Hi @terencefan, our services run in west europe and north europe. We assign User assigned managed identities through IAM role assignments from deployment pipeline (SignalR App Server (Preview) role)
We have a couple .netcore applications connected to signalr services through aad auth. Last week the clients that connect to the negotiated endpoint get 401 errors. If I change the AddAzureSignalR connection string from the "Endpoint=https://nnn.service.signalr.net;AuthType=aad;" to the Primary connectionstring from Keys in azure portal everything works again. Did something change related to AAD auth?
Thanks in advance.
The text was updated successfully, but these errors were encountered: