Service Bus

How can we improve the Windows Azure Service Bus?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Provide a local emulator for Azure Event Hubs

    When developing solutions for Azure, it is very useful to have a local development experience. This is good for development, integration tests, and validation of approaches. When using Azure Storage, Cosmos DB, or Service Fabric, there is a very good local emulator story. But for Event Hubs, there is no local emulator story, so all development and integration testing needs to use the real thing, which causes a number of issues. For example, integration tests now need to provision an isolated Event Hub, and then ensure that it gets torn down.

    It would be much better if we had a…

    547 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Encrypted queues

    Provide optional configuration of queues to use encryption to store messages, perhaps leveraging Azure Storage Service Encryption...

    431 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Resubmit dead-letter message back to the subscription it came from

    I often want to re-submit a subscription's dead-letter message back to the subscription without going through the topic. This is required when the other subscriptions shouldn't reprocess the message, but there is currently no way to do this. The cleanest way I can think of is to add send functionality to the SubscriptionClient. class.

    Other people have asked for this functionality as well: http://stackoverflow.com/questions/22096262/send-message-directly-to-subscription

    331 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Autoscale based on topic-subscription length

    Instead of autoscaling on queue length, i would like to be able to scale on topic-subscription length

    327 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Bring Event Hubs and Service Bus to Azure Stack

    I want to have event hubs in Azure Stack so that I can use it for Azure Functions. I also would like to use it for processing events for IoT and other devices

    285 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide gracefull shutdown feature to Message Pump in Queue and Subscription Clients

    There is not a good way to deal with a graceful shutdown of a Worker role using the OnMessage approach of processing queue messages off the service bus. It would be nice if you could call StopProcessing, or something similar on the QueueClient or SubscriptionClient so that they would stop their internal receive loop, but finish processing the messages they may already be processing. A count property of active processing messages would also be helpful so that in an OnStop method on the worker role you could call the StopProcessing and enter a loop till the active processing messages was…

    280 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Flag idea as inappropriate…  ·  Admin →

    This is a great suggestion Mike. This does not only apply to OnMessage APIs, it will be applicable for making pending Receive(timeout) calls too in the case of a graceful shutdown when several of these are pending. Any specific requirements or suggestions on what API shape/pattern you would like to see are appreciated.

  7. Add Service Bus to VNET

    For internal applications it would be very useful to add Service Bus to a private VNET with no external internet access to ServiceBus

    This would ideally lead to a PaaS solution with App Service, Service Bus, and Azure SQL database in a VNET only accessible from an ExpressRoute connection

    230 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add logging for service-bus access

    It would be helpful if there were a posibility to log the acces to a service bus queue/topic (like activity, IP-address, time).
    We had the problem that some instance was "stealing" the entries from a queue, and we we had no idea which computer was processing them. If there were a was to enable some kind of logging on the service bus, would had been very helpful.

    199 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Queue purge

    Provide an API for purging of a queue, without having to delete and recreate the queue.

    190 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Increase the maximum length of the name of a topic subscription

    Currently, the name of a subscriber to an Azure Service Bus topic is limited to 50 characters. We would like to use very descriptive names for our subscribers, and these names might exceed 50 characters. Please increase the maximum length of this value.

    [Copied from https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/4175354-increase-the-maximum-length-of-the-name-of-a-topic]

    167 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow only selected IP addresses (Whitelist) access to Service Bus

    Additionally to the SAS token it would be great to restrict the IP addresses which can access the service bus. An user can create a whitelist of allowed IP addresses in the management interface. The idea is to limit the impact should a SAS token be compromised.

    See also: http://stackoverflow.com/questions/36308845/

    138 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Update Service Bus SLA to include a maximum delay for delivering messages

    Today the SLA of 99.95% is too weak and doesn't include any maximum delay for delivering messages to consumers.

    Because of an unhealthy partition I experienced getting several messages hours later than their ScheduledEnqueueTimeUtc suggested. I experienced several messages being consumed 8 hours later and creating chaos in the middle of the night (sending thousands of sms text messages in my case).

    Here's the actual description of "downtime" in the Service Bus SLA:
    "Downtime" is the total accumulated Deployment Minutes, across all Queues and Topics deployed by Customer in a given Microsoft Azure subscription, during which the Queue or Topic…

    124 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Change the Service Bus SDK to be a Portable Class Library

    Right now, the Service Bus SDK requires the Full .NET Framework. For Xamarin and .NET Core situations, it would be much better if the Service Bus SDK were released as a Portable Class Library. (Oh, and open-sourcing the SDK would be great, too.)

    97 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add gzip support for sending/receiving multiple events from/to event hub.

    Today, the event hub rest api does not support gzip out of the box, this is very important feature especially when dealing with a lot of events from mobile client for example.

    94 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. alert on number of active messages in a SUBSCRIPTION

    Currently you can only create an alert on the number of messages in a topic...which is pretty useless. We need to be able to target a specific subscription for alerts!

    90 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Enable indefinite storage of events on Event Hub to allow for an Event Sourcing architecture.

    When building an application using Event Sourcing, the events are the true source of all data. Replaying events and creating different projections at any time during the lifetime of the app is crucial. Currently Event Hubs only supports up to a 7 day storage policy. This means that it cannot be used with Event Sourcing. An example of this kind product is Greg Young's EventStore. https://geteventstore.com/

    80 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Using a filter with EventHub data

    Will we be able to use a filter in the future for the EventHub data? I'm designing a new solution for a customer and it looks like EventHubs are great for sending and receiving our near-realtime data. Downside is when receiving the data, we receive all data of all our devices in the world. Most of the time, our clients only want to see data of one (or a few) device. We could of course filter the data by ourselves, client side, but this would cost a lot of bandwith.

    78 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Provide a Service Bus emulator on a local computer

    The existing idea here was closed 5 years ago https://feedback.azure.com/forums/216926-service-bus/suggestions/2565564-provide-a-service-bus-emulator-on-a-local-computer

    There's still a big need for this

    Things like:
    Offline development
    Easy testability without involving talking to a cloud instance

    The accepted solution in the previous idea is no longer valid as the on-premises solution is not maintained and doesn't work with new versions of the service bus SDK

    74 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Service Bus Metrics to Operations Management Suite (OMS)

    Please now that there's a rich API capability for queue metrics, let's support pushing the metrics to OMS for monitoring.
    And make a servicebus OMS Solution?

    67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Support propagating content-type and content-encoding headers as user properties for event hub REST API.

    I would like to request that MSFT consider providing access to these properties so that we can use the same standard properties across both HTTP and AMQP. Currently, when using HTTP to send to event hub if you specificy a Content-Type or Content-Encoding those headers are not included with the user properties as previously stated. When using AMQP to send to event hub (and the EventData class) you can explicitly add Content-Type and Content-Encoding properties as user properties, and that works fine such that they are received as user properties.

    The problem with this is that it creates the requirement…

    65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 8 9
  • Don't see your idea?

Service Bus

Feedback and Knowledge Base