Azure-docs: Azure SignalR Service with custom domain

[gjdonkers]

Hi,
Is there any information about the best practice to run the Azure SignalR Service on a custom domain? This is one of the requirements for our end user.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2f191582-0cbe-ef99-5f0c-781365f47b0b
• Version Independent ID: db0c0d78-228a-94b2-312f-e1a1a248ca99
• Content: Scale ASP.NET Core SignalR with Azure SignalR
• Content Source: articles/azure-signalr/signalr-concept-scale-aspnet-core.md
• Service: signalr
• GitHub Login: @sffamily
• Microsoft Alias: zhshang

[SnehaAgrawal-MSFT]

@gjdonkers Thanks for the feedback! We are currently investigating and will update you shortly.

[RyanHill-MSFT]

@gjdonkers the SignalR Service can't be run on a custom domain because it's a hosted as an Azure service; you'll get an Azure domain specific endpoint.

You can, as stated, choose to self-host the service inside an app service that's configured for a custom domain. However, you do forfeit the benefits like availability and performance. Those you'll have to mitigate yourself.

I understand the end-user requirement but I would liken the Azure SignalR Service akin to Azure Storage from a service hosting perspective.

Hope this helps. If not, let me know.

[sffamily]

custom domain is not supported yet, but it is in our current roadmap for the upcoming months as one of the enterprise features. We will publish corresponding doc once the feature is released.

[sffamily]

please-close

[gjdonkers]

Okay, is there a location to follow the roadmap? Any idea what sprint it is planned?

[val1984]

Hello,
Has this feature been delivered?
Thanks in advance 👍

[gjdonkers]

As far as I know nothing has been delivered, as well as the details about the roadmap. @sffamily Can you clarify this for us?

[sffamily]

This feature (actually all features except Raw WebSocket support and full Serverless support) has been pushed back for at least half a year, due to a Microsoft top priority project that Azure SignalR Service has been pulled into since 12/2019. So custom domain support is part of enterprise feature we are going to support, as a stretch goal for the upcoming H2 CY20, but no guarantee. we will try to see whether this can be possible the rest of the year, but the whole PG is still working on to hit the tough milestones from the top priority. Understand the demand here. We will have better estimate when entering September.

[jzhouw]

will app gateway a workaround for this need? it looks ok as per below links
https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-websocket
https://stackoverflow.com/questions/42930124/azure-application-gateway-and-signalr-websockets

[gjdonkers]

This is probably the self hosted version of SignalR, @sffamily can you confirm? We have an application gateway V2, so if not this could be a solution for us.