Review of Azure Storage Queues multi-accounts #7885
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Clarified throttling issues related to Azure Storage Queues and the use of multiple storage accounts.
Clarified language regarding scaling out to multiple storage accounts and throughput limitations.
Removed redundant text and clarified guidance on using multiple storage accounts with Azure Storage Queues.
Restored the Scale Units section with detailed explanations about throughput limitations and resource partitioning.
Added note about throughput limits and scaling strategy.
Updated the section on routing with multiple storage accounts to clarify the use of NServiceBus and the notation for specifying destination addresses.
ngallegos
force-pushed
the
helenktsai-patch-1
branch
from
437d83b to
e1ec6e6
Compare
helenktsai
commented
Nov 4, 2025
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
helenktsai
commented
Nov 4, 2025
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
Corrected grammatical error in the documentation regarding connection string aliases.
Revised wording for clarity and consistency in the documentation regarding endpoint registration and message routing.
ngallegos
approved these changes
Nov 5, 2025
boblangley
reviewed
Nov 10, 2025
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
Comment on lines
54
to
63
| ### Using registered endpoints | ||
|
|
||
| An example of a partitioned application with a different number of deployed scale units is an application deployed in various regions. | ||
| In order to route a message to an endpoint without having to specify the destination each time, the endpoint can be registered for a given command type, assembly, or namespace. | ||
|
|
||
|  | ||
| snippet: storage_account_routing_registered_endpoint | ||
|
|
||
| > [!NOTE] | ||
| > Use real Azure storage accounts. Do not use Azure storage emulator as it only supports a single fixed account named devstoreaccount1.". | ||
| Once the endpoint is registered, no send options need to be specified. | ||
|
|
||
| snippet: storage_account_routing_send_registered_endpoint | ||
|
|
Member
There was a problem hiding this comment.
We should move this above so it immediately follows the connection string aliases as the first example showing and introducing the @ notation.
Member
Author
There was a problem hiding this comment.
Comment on lines
44
to
46
| Aliases can be provided for both the endpoint's connection strings as well as other accounts' connection strings. This enables using the `@` notation for destination addresses like `queue_name@accountAlias`. | ||
|
|
||
| snippet: storage_account_routing_send_options_alias |
Member
There was a problem hiding this comment.
We should remove this lower, perhaps to the end of the configuration section in this article, since this is the "exceptional" scenario for customers. Most of the time they should be using routing configuration.
Member
Author
There was a problem hiding this comment.
I think I addressed this?
Comment on lines
70
to
74
| ### Publishers | ||
|
|
||
| NServiceBus allows to specify destination addresses using an `"endpoint@physicallocation"` when messages are dispatched, in various places such as the [Send](/nservicebus/messaging/send-a-message.md) and [Routing](/nservicebus/messaging/routing.md) API or the `MessageEndpointMappings`. In this notation the `physicallocation` section represents the location where the endpoint's infrastructure is hosted, such as a storage account. | ||
| Similar to sending to an endpoint, the transport can also be configured to subscribe to events published by endpoints in another storage account, using: | ||
|
|
||
| Using this notation it is possible to route messages to any endpoint hosted in any storage account. | ||
| snippet: storage_account_routing_registered_publisher |
Member
There was a problem hiding this comment.
We should make this section follow immediately after the routing configuration.
Comment on lines
64
to
66
| ### Using send options | ||
|
|
||
| Although registering endpoints to route messages is preferred, NServiceBus allows specifying destination addresses using the `<endpoint>@<physicallocation>` notation when messages are dispatched. Using this notation, it is possible to route messages to any endpoint hosted in any storage account. The `physicallocation` element represents the location where the endpoint's infrastructure is hosted, such as a storage account alias. |
Member
There was a problem hiding this comment.
This would be the last section. I am wondering if we should show both the SendOptions and the short context.Send("endpoint@account") form.
Member
Author
There was a problem hiding this comment.
Do you mean "Using send options" should go below the "Publishers" section? I don't have an opinion on whether or not to show both.
helenktsai
commented
Nov 10, 2025
| > Use real Azure storage accounts. Do not use Azure storage emulator as it only supports a single fixed account named "devstoreaccount1". | ||
| > [!NOTE] | ||
| > There are limits to how much using multiple storage accounts increase throughput. Consider using [scale units as a comprehensive scaling strategy](https://learn.microsoft.com/en-us/azure/well-architected/performance-efficiency/scale-partition#choose-a-scaling-strategy) to address higher throughput and reliability needs. |
Member
Author
There was a problem hiding this comment.
Suggested change
| > There are limits to how much using multiple storage accounts increase throughput. Consider using [scale units as a comprehensive scaling strategy](https://learn.microsoft.com/en-us/azure/well-architected/performance-efficiency/scale-partition#choose-a-scaling-strategy) to address higher throughput and reliability needs. | |
| > There are limits to how much increasing storage accounts increases throughput. Consider using [scale units as a comprehensive scaling strategy](https://learn.microsoft.com/en-us/azure/well-architected/performance-efficiency/scale-partition#choose-a-scaling-strategy) to address higher throughput and reliability needs. |
Co-authored-by: Bob Langley <[email protected]>
helenktsai
commented
Nov 10, 2025
transports/azure-storage-queues/multi-storageaccount-support.md
Outdated
Show resolved
Hide resolved
Clarified the use of aliases for connection strings in multi-storage account support.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.