Azure Service Bus has several size limits and restrictions that developers should be aware of when designing and deploying their messaging solutions. These limits vary depending on the type of Service Bus entity (queues, topics, and subscriptions) and the pricing tier (Basic, Standard, or Premium).
Until recently, the maximum limit of a message that we could send to a Queue or Topic on a Service Bus was 1MB, and we had to use the Service Bus premium tier. Now, we can send a message up to a maximum of 100MB on the same premium tier
Here’s an overview of the key size limits and restrictions:
- Message Size Limits
- Maximum Message Size:
- Basic and Standard Tiers: 256 KB per message.
- Premium Tier: 100 MB per message.
- Maximum Message Size:
Note: The total message size includes both the message body and headers (properties). If you need to send larger payloads, consider using Azure Blob Storage for large data and passing the Blob URL in the message.
- Queue and Topic Size Limits
- Maximum Size of Queues and Topics:
- When creating queues and topics, you can configure their maximum size, which determines the total storage limit for all messages in the entity.
- The Basic and Standard tiers offer 1 GB, 2 GB, 3 GB, 4 GB, and 5 GB size options.
- In the Premium tier, you can scale up to 80 GB per messaging unit (MU), and each namespace can have up to 4 MUs, allowing for a maximum of 320 GB per namespace.
- Maximum Size of Queues and Topics:
Community Note: It is very important to note that the 100MB message size is only for AMQP and not for HTTP and SBMP. For these protocols it is still 1 MB, even at the premium tier. – contribution from Chadi Al Souliman.
To lazy to read? We’ve got you covered! Check out our video version of this content!
I hope you find this helpful! If you liked the content or found it helpful and want to help me write more content, you can buy (or help buy) my son a Star Wars Lego!
