Hello, From the specification here - https://azure.microsoft.com/en-au/pricing/details/service-bus/ I understand that the message size a service bus can carry for a single transaction is 1 MB for premium and 256 kb for standard. I'm reaching out to check if there are any tweaks which can be made to increase the size. We need to support request body upto 3 MB. Is it possible by any means? Thanks, PK

Hi @PK Unfortunately, this is the hard limit for the message size for service bus SKUs and cannot be changed. Alternatively, if your business requirement needs more than 1 MB then your sender application should have the logic to split the message to the supported size and at the receiver side, you need to consume/join those messages together. You can leverage sessions in this case where all messages send a particular session will be received in FIFO order i.e. maintaining the order. The other option would be storing the message content in the azure storage blob/or any other storage. The sender application needs to store that message and now pass the storage URL while sending the message. At the receiver end, they need to pull the message content from the storage URL. If you want to go with premium SKU then there is a private preview to explore this new feature service bus premium supporting 100 MB of message size. Please let me know is you are interested in exploring it so we can enable this on your subscription. Note: This is a private preview and should not be used in your production environment until it is GA. Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

Increasing the message size of the Service Bus

Accepted answer

MayankBargali-MSFT 68,471 Reputation points

2021-04-20T07:05:56.407+00:00

Hi @PK

Unfortunately, this is the hard limit for the message size for service bus SKUs and cannot be changed.
Alternatively, if your business requirement needs more than 1 MB then your sender application should have the logic to split the message to the supported size and at the receiver side, you need to consume/join those messages together. You can leverage sessions in this case where all messages send a particular session will be received in FIFO order i.e. maintaining the order.

The other option would be storing the message content in the azure storage blob/or any other storage. The sender application needs to store that message and now pass the storage URL while sending the message. At the receiver end, they need to pull the message content from the storage URL.

If you want to go with premium SKU then there is a private preview to explore this new feature service bus premium supporting 100 MB of message size. Please let me know is you are interested in exploring it so we can enable this on your subscription.

Note: This is a private preview and should not be used in your production environment until it is GA.

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.
Please sign in to rate this answer.

4 people found this answer helpful.
PK 316 Reputation points

2021-04-20T14:09:37.107+00:00

@MayankBargali-MSFT : Thanks for your prompt response.

We have a premium subscription for the service bus. But, the message limitation is 1 MB.

Now, I can get an indication from your comment that, there is a private preview with premium SKU which will facilitate supporting 100 MB of message size, which means, I don't have to change anything, by providing you the subscription, you would be able to enable the private preview which will facilitate 100 MB of message size, correct?

MayankBargali-MSFT 68,471 Reputation points

2021-04-21T12:31:57.433+00:00

@PK As this is a private preview existing premium namespace still supports 1 MB max message size. Once you have shared the details with us we will enable it on your subscription and your new premium namespace will have a 100 MB message size limit. Please refer to my private comment if you are interested and will share more details. But make sure that this is only for testing purposes and not recommended in production until this feature will be GA.

Poojak 1 Reputation point

2021-08-27T13:21:17.227+00:00

Hi @MayankBargali-MSFT ,

I am facing same issue with Service Bus Premium. I understood as you said that 100MB is in Private Preview mode and isn't recommended for Production environment.

But in your first reply, you have recommended to use Azure Storage Queues. I have a message of size approx 2.5 MB and I am trying to leverage Queues but I see in the MS Doc - "A queue message can be up to 64 KB in size". So can we really make use of Azure Queues in this scenario ??

Please help me in further understanding related to Queues and also, do you have any another approach where I can queue my messages of size more than 1 MB ??

MayankBargali-MSFT 68,471 Reputation points

2021-08-30T03:51:35.41+00:00

@Poojak Looks like there was typo. I mean to say "azure storage blob/or any other storage" and not "azure storage queue/or any other storage". My next statement explain how you can achieve it "The sender application needs to store that message and now pass the storage URL while sending the message. At the receiver end, they need to pull the message content from the storage URL."

Your sender application can store the message in the storage blob or any storage and while sending the message your sender application need to send the URL/path of the actual stored message content (i.e. more than 1 MB). At the receiver end you need to get the actual message content from the URL/path.

The support of 100 MB on premium namespace should be soon GA and you can refer to Messagingon Announcement page once it become GA and we will update our document. Right now

Etienne FRITSCH 1 Reputation point

2021-09-27T16:04:52.827+00:00

Hi @MayankBargali-MSFT
thank you very much for the insight on this new 100 MB limitation.
Our company is very interested in this feature and it's now in public preview. Is it ready for production or would you advice against it? If not I would like a hint of the release date, will it be this year?
We are currently facing this limitation and it's very important for us to understand if we must implement a different logic or even migrate to RabbitMQ or if we could wait 2 or 3 months to use this new limitation. Thanks.

MayankBargali-MSFT 68,471 Reputation points

2021-09-30T05:42:58.597+00:00

@Etienne FRITSCH Right now target GA is by end of this year but no specific dates yet. I will update this thread once I have further update on the GA timelines. The suggestion would be not to use it for production workload untill the service is GA.

Manoj Hulikeremath 1 Reputation point

2022-09-28T16:37:06.427+00:00

Hi @MayankBargali-MSFT ,
Thank you for sharing the info regarding Azure Service Bus - Premium and it's queue support for 100 MB message
https://techcommunity.microsoft.com/t5/messaging-on-azure-blog/azure-service-bus-premium-large-message-support-generally/ba-p/2900186

We do see in Azure portal , we can manually change the max message size to 100 MB as per below article.
https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-premium-messaging#large-messages-support

What we are not able to find is , while creating the Azure Service Bus-queue through code (we are using Java SDK), we don't see an option to set the max message size.
Could you please share if there exists an API for the same ? Appreciate your help here.

MayankBargali-MSFT 68,471 Reputation points

2022-10-03T05:41:10.343+00:00

@Manoj Hulikeremath Thanks for reaching out. I will suggest you to open a new Q&A post so it east to search and will help other community members facing the similar issue.
Sign in to comment

Increasing the message size of the Service Bus

0 additional answers