Service Bus

  1. [BUG] Change service bus namespace scale in manage windowsazure not functional

    In manage.windowsazure.com after service bus namespace scale tier change, there is button for save changes. After click at save button, there are two options: Yes and No, but only No options works. Yes is not functional. I have tried IE 11.9600.17728 an Chrome 42.0.2311.90.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. We need to be able to create Service Bus in Azure RM portal.

    We need to be able to create Service Bus in Azure RM portal.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. More control & documentation on Subscription filters

    Hi, If I define multiple filters on a subscription , what is the evaluation logic ?

    I found no official documentation and different answers on the internet. According to my test they are evaluated with an OR logic.

    I'd like to have an official statement from the esb team to know exactly what is the expected behavior ...

    BTW: I would have liked to have an AND condition .. and generally speaking have the option to choose among OR and AND

    regards

    enrico

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add ECIES Device Auth Option To IoT Hubs

    Add Elliptic Curve Integrated Encryption Scheme (ECIES) option during the device registration process of IoT Hubs.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Workflow Manager 1.0 on Azure Service Bus

    Let WFM 1.0 to be configured to use Azure Service Bus and not only local Service Bus

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. WS-Transaction

    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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add Metric for % of space consumed

    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.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Increase max queue name length for scheduler jobs to match actual 260 character limit

    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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add support for managed identity tokens for Service Bus REST API

    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:

    https://docs.microsoft.com/en-us/rest/api/servicebus/send-message-batch

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  13. Azure Service Bus - Disable Default Secure Access Key

    Now we have RBAC controls for Azure Service Bus, There is no longer a need for the SAP primary and secondary keys, in effect this is a security loop hole if using standard service bus as you can't set up fire walling to prevent external access to the PAAS service.

    If either the default SAP at the namespace could be removed or the keys cleared this would allow only access via RBAC through Azure AD

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add more granular access policies for querying queue information such as free space

    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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Event Grid events should trigger "normal" behaviour

    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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Increase the batch/prefetch size limit

    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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
1 2 6 7 8 10 Next →
  • Don't see your idea?

Service Bus

Categories

Feedback and Knowledge Base