Add Elliptic Curve Integrated Encryption Scheme (ECIES) option during the device registration process of IoT Hubs.1 vote
Let WFM 1.0 to be configured to use Azure Service Bus and not only local Service Bus1 vote
Any background process which is causing the billing, it should be notified with continous alert. Becz of "service bus"we have got affected
Background Process - Service Bus1 vote
This was made for distributed web systems, Microsoft was a co-author, it's built into WCF - can't imagine why this is not an obvious play inAzure right now.1 vote
Create a platform metric that describes the percentage of space available on a topic or queue, based on the current size of items in the entity.
E.g. topic max size, 1GB. Current size 500MB. Metric value = 50% consumed
This would aid in easily setting threshold triggers in Azure Monitor, by allowing alerts to be triggered when e.g. reached 80% capacity, without requiring any knowledge of the underlying entity max size.
In the Azure Service Bus queue overview blade, I can see summary properties for my queue.
I would like to be able to view the contents of messages currently in the Azure Service Bus queue.
I would like to be able to purge (delete) individual messages from the queue.
I would like to be able to purge all messages.1 vote
Azure allows the names of service bus queues to be up to 260 characters long, but in the action settings for scheduler jobs the limit is 50 characters. Please increase it to 260.1 vote
Currently, the only options when you use the REST API is to pass WRAP or SAS tokens in the Authorization header, even though Service Bus supports managed identity:1 vote
We have some customers wanting to know if this will become available in the near future.1 vote
The pin is missing. See attached1 vote
Thanks for bringing this to our attention. The bug has been moved to the appropriate service area for further review.
Currently in order to allow an application to query how much free space is available on a queue, it has to use the ManagementClient class, which means it requires the "Manage" access policy which grants far more control than I want this application to have.
Can you add more granular policies than Send, Listen and Manage. Allowing an application to read queue runtime information and queue configuration settings should not also require you have to grant permission to edit those settings.1 vote
this link is broken, https://azure.microsoft.com/en-us/documentation/learning-paths/service-bus. where is it?
We need to fix this link or provide working one.1 vote
Raising events from Service Bus is a great way to avoid having to poll and therefore introducing delays in processing and/or the cost of polling.
However currently the way that Logic Apps and Functions are invoked is through a Webhook call directly to their trigger.
This is unfortunate as it means that only a single instance of the message handler will be run regardless of the number of messages queued up for processing. [Please correct me if I'm wrong!]
Ideally the event would trigger the normal "polling" of the Logic App or Function so that multiple instances can be created.0 votes
The current limitation of 256KB, which means that if your messages are somewhere around the max allowed brokered-message size, you'll get only a handful of messages per-operation.
This only makes us make more operations, making everybody work harder :(0 votes
- Don't see your idea?