Getting Started


Configuring an endpoint

To use Azure Service Bus as the underlying transport:

var transport = endpointConfiguration.UseTransport<AzureServiceBusTransport>();


These settings control how the transport connects to the broker.


  • UseWebSockets(): Configures the transport to use AMQP over websockets.
  • TimeToWaitBeforeTriggeringCircuitBreaker(TimeSpan): The time to wait before triggering the circuit breaker after a critical error occurred. Defaults to 2 minutes.


  • CustomRetryPolicy(RetryPolicy): Allows replacement of the default retry policy.


Entity creation

These settings control how the transport creates entities in the Azure Service Bus namespace.

Entity creation settings are applied only at creation time of the corresponding entities; they are not updated on subsequent startups.

Access rights

By default the transport requires elevated privileges to manage subscriptions at runtime. If using a shared access policy make sure to include Manage rights or the Azure Service Bus Data Owner role if authenticating using Managed Identities.

To avoid running with elevated privileges:


  • TopicName(string): The topic's name used to publish events between endpoints. All endpoints share this topic, so ensure all endpoints specify the same topic name. Defaults to bundle-1. Topic names must adhere to the limits outlined in the Microsoft documentation on topic creation.


  • EntityMaximumSize(int): The maximum entity size in GB. The value must correspond to a valid value for the namespace type. Defaults to 5. See the Microsoft documentation on quotas and limits for valid values.

  • EnablePartitioning(): Partitioned entities offer higher availability, reliability, and throughput over conventional non-partitioned queues and topics. For more information about partitioned entities see the Microsoft documentation on partitioned messaging entities.

  • SubscriptionNamingConvention(Func<string, string>): By default subscription names are derived from the endpoint name. This callback allows for a replacement name for the subscription. Subscription names must adhere to the limits outlined in the Microsoft documentation on subscription creation.

  • SubscriptionNameShortener(Func<string, string>): Shortens subscription names that exceed the maximum length. The shortener is invoked only when a subscription name exceeds the maximum length.

  • SubscriptionRuleNamingConvention(Func<Type, string>): By default rule names are derived from the message type's full name. This callback allows for a replacement name for the rule. Rule names must adhere to the limits outlined in Service Bus quotas.

  • RuleNameShortener(Func<string, string>): Shortens rule names that exceed the maximum length. The shortener is invoked only when a rule name exceeds the maximum length.

Combining shorteners and naming conventions

When both a shortener and a naming convention are provided for a subscription or subscription rule, the naming convention is applied first, and the result is then passed into the shortener.

Controlling the prefetch count

When consuming messages from the broker, throughput can be improved by having the consumer prefetch additional messages. The prefetch count is calculated by multiplying maximum concurrency by the prefetch multiplier. The default value of the multiplier is 10, but it can be changed by using the following:


Alternatively, the whole calculation can be overridden by setting the prefetch count directly using the following:


To disable prefetching, prefetch count should be set to zero.


For all supported transport transaction modes (except TransportTransactionMode.None), the transport uses a peek-lock mechanism to ensure a single instance of an endpoint can process a message. The default lock duration is specified during the entity creation. By default, the transport uses the SDK's default maximum auto lock renewal duration of 5 minutes.

Message lock renewal is initiated by client code, not the broker. If the request to renew the lock fails after all the SDK built-in retries (.e.g due to a connection-loss), the lock won't be renewed, and the message will become unlocked and available for processing by competing consumers. Lock renewal should be treated as best-effort and not as a guaranteed operation.