Connection string in Azure SignalR Service

Connection string is an important concept that contains information about how to connect to SignalR service. In this article, you'll learn the basics of connection string and how to configure it in your application.

What is connection string

When an application needs to connect to Azure SignalR Service, it will need the following information:

  • The HTTP endpoint of the SignalR service instance
  • How to authenticate with the service endpoint

Connection string contains such information.

What connection string looks like

A connection string consists of a series of key/value pairs separated by semicolons(;) and we use an equal sign(=) to connect each key and its value. Keys aren't case sensitive.

For example, a typical connection string may look like this:


You can see in the connection string, there are two main information:

  • Endpoint=https://<resource_name> is the endpoint URL of the resource
  • AccessKey=<access_key> is the key to authenticate with the service. When access key is specified in connection string, SignalR service SDK will use it to generate a token that can be validated by the service.

The following table lists all the valid names for key/value pairs in the connection string.

key Description Required Default value Example value
Endpoint The URI of your ASRS instance. Y N/A
Port The port that your ASRS instance is listening on. N 80/443, depends on endpoint uri schema 8080
Version The version of given connection string. N 1.0 1.0
ClientEndpoint The URI of your reverse proxy, like App Gateway or API Management N null
AuthType The auth type, we'll use AccessKey to authorize requests by default. Case insensitive N null azure, azure.msi,

Use AccessKey

Local auth method will be used when AuthType is set to null.

key Description Required Default value Example value
AccessKey The key string in base64 format for building access token usage. Y null ABCDEFGHIJKLMNOPQRSTUVWEXYZ0123456789+=/

Use Azure Active Directory

Azure AD auth method will be used when AuthType is set to azure, or azure.msi.

key Description Required Default value Example value
ClientId A guid represents an Azure application or an Azure identity. N null 00000000-0000-0000-0000-000000000000
TenantId A guid represents an organization in Azure Active Directory. N null 00000000-0000-0000-0000-000000000000
ClientSecret The password of an Azure application instance. N null ***********************.****************
ClientCertPath The absolute path of a cert file to an Azure application instance. N null /usr/local/cert/app.cert

Different TokenCredential will be used to generate Azure AD tokens with the respect of params you have given.

How to get my connection strings

From Azure portal

Open your SignalR service resource in Azure portal and go to Keys tab.

You'll see two connection strings (primary and secondary) in the following format:


From Azure CLI

You can also use Azure CLI to get the connection string:

az signalr key list -g <resource_group> -n <resource_name>

For using Azure AD application

You can use Azure AD application to connect to SignalR service. As long as the application has the right permission to access SignalR service, no access key is needed.

To use Azure AD authentication, you need to remove AccessKey from connection string and add You also need to specify the credentials of your Azure AD application, including client ID, client secret and tenant ID. The connection string will look as follows:


For more information about how to authenticate using Azure AD application, see this article.

For using Managed identity

You can also use managed identity to authenticate with SignalR service.

There are two types of managed identities, to use system assigned identity, you just need to add AuthType=azure.msi to the connection string:


SignalR service SDK will automatically use the identity of your app server.

To use user assigned identity, you also need to specify the client ID of the managed identity:


For more information about how to configure managed identity, see this article.


It's highly recommended to use Azure AD to authenticate with SignalR service as it's a more secure way comparing to using access key. If you don't use access key authentication at all, consider to completely disable it (go to Azure portal -> Keys -> Access Key -> Disable). If you still use access key, it's highly recommended to rotate them regularly (more information can be found here).

Use connection string generator

It may be cumbersome and error-prone to build connection strings manually.

To avoid making mistakes, we built a tool to help you generate connection string with Azure AD identities like clientId, tenantId, etc.

To use connection string generator, open your SignalR resource in Azure portal, go to Connection strings tab:

Screenshot showing connection string generator of SignalR service in Azure portal.

In this page you can choose different authentication types (access key, managed identity or Azure AD application) and input information like client endpoint, client ID, client secret, etc. Then connection string will be automatically generated. You can copy and use it in your application.


Everything you input on this page won't be saved after you leave the page (since they're only client side information), so please copy and save it in a secure place for your application to use.


For more information about how access tokens are generated and validated, see this article.

Client and server endpoints

Connection string contains the HTTP endpoint for app server to connect to SignalR service. This is also the endpoint server will return to clients in negotiate response, so client can also connect to the service.

But in some applications there may be an extra component in front of SignalR service and all client connections need to go through that component first (to gain extra benefits like network security, Azure Application Gateway is a common service that provides such functionality).

In such case, the client will need to connect to an endpoint different than SignalR service. Instead of manually replace the endpoint at client side, you can add ClientEndpoint to connecting string:


Then app server will return the right endpoint url in negotiate response for client to connect.


For more information about how clients get service url through negotiate, see this article.

Similarly, when server wants to make server connections or call REST APIs to service, SignalR service may also be behind another service like Application Gateway. In that case, you can use ServerEndpoint to specify the actual endpoint for server connections and REST APIs:


Configure connection string in your application

There are two ways to configure connection string in your application.

You can set the connection string when calling AddAzureSignalR() API:


Or you can call AddAzureSignalR() without any arguments, then service SDK will read the connection string from a config named Azure:SignalR:ConnectionString in your config providers.

In a local development environment, the config is stored in file (appsettings.json or secrets.json) or environment variables, so you can use one of the following ways to configure connection string:

  • Use .NET secret manager (dotnet user-secrets set Azure:SignalR:ConnectionString "<connection_string>")
  • Set connection string to environment variable named Azure__SignalR__ConnectionString (colon needs to replaced with double underscore in environment variable config provider).

In production environment, you can use other Azure services to manage config/secrets like Azure Key Vault and App Configuration. See their documentation to learn how to set up config provider for those services.


Even you're directly setting connection string using code, it's not recommended to hardcode the connection string in source code, so you should still first read the connection string from a secret store like key vault and pass it to AddAzureSignalR().

Configure multiple connection strings

Azure SignalR Service also allows server to connect to multiple service endpoints at the same time, so it can handle more connections, which are beyond one service instance's limit. Also if one service instance is down, other service instances can be used as backup. For more information about how to use multiple instances, see this article.

There are also two ways to configure multiple instances:

  • Through code

    services.AddSignalR().AddAzureSignalR(options =>
            options.Endpoints = new ServiceEndpoint[]
                new ServiceEndpoint("<connection_string_1>", name: "name_a"),
                new ServiceEndpoint("<connection_string_2>", name: "name_b", type: EndpointType.Primary),
                new ServiceEndpoint("<connection_string_3>", name: "name_c", type: EndpointType.Secondary),

    You can assign a name and type to each service endpoint so you can distinguish them later.

  • Through config

    You can use any supported config provider (secret manager, environment variables, key vault, etc.) to store connection strings. Take secret manager as an example:

    dotnet user-secrets set Azure:SignalR:ConnectionString:name_a <connection_string_1>
    dotnet user-secrets set Azure:SignalR:ConnectionString:name_b:primary <connection_string_2>
    dotnet user-secrets set Azure:SignalR:ConnectionString:name_c:secondary <connection_string_3>

    You can also assign name and type to each endpoint, by using a different config name in the following format: