How can we improve Azure Notification Hubs?

Bulk tagging of installations

When we need to add a tag for a set of installations, we currently need to perform a request to Azure Notification Hubs for each installation.

This results in very poor performance, ruining one of the main advantages of Notification Hubs: massive scalability.

It is to be expected that many many uses of tags will involve applying tags on installations dynamically in response to business events in the app. Since this may affect as many users as we would later want to send notifications to, it follows that we should have an efficient way to apply tags to many installations at once.

55 votes
Sign in
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Søren Nguyen Boisen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

Thanks for reaching out! We agree that this is an important task customers will need to be able to do. We are working on improving installations and will keep this on our list as we move forward. I will update once we have any ETA/have started working on this item.


Sign in
Sign in with: Microsoft
Signed in as (Sign out)
  • Phil commented  ·   ·  Flag as inappropriate

    Hi John

    Thank you very much for looking into this.

    Actually, it's the bulk export/import capabilities that we would really like to have working for the installation model but they have only ever worked for the registration model. I have had two support tickets that touched on this in the past but the outcome for both was that the installation model did not support the bulk export/import. Has this changed now?

    From memory the problem was that the process always hung during the bulk create or bulk update steps. After investigation by the Notification Hub team it was decided that the feature was not supported.

    Hope this information helps.


  • John M. Wargo commented  ·   ·  Flag as inappropriate

    I checked and this is not possible today, but we'll consider it for the next update to the API.

    You can accomplish this using the export/import capabilities - export the data, update your tags, then import the data back in to Notification Hubs.

  • Phil commented  ·   ·  Flag as inappropriate

    Hello Microsoft!!! I'm guessing there is no update on this one still??? How do we get our suggestions taken seriously if we can't do it here?

  • Anonymous commented  ·   ·  Flag as inappropriate

    It's been 2 years since the last update saying this feature will be improved. Is there any ETA yet?

  • Phil commented  ·   ·  Flag as inappropriate

    Hello, is there any update for this item?

    Currently, we are restricted to using the registration model over the installation model as only the registration model supports using ANH bulk operations (create, update, delete). We need bulk updates for running push campaigns because we don't know our target audience (which can be up to 500,000 devices) until 1-3 days before the notification needs to be sent.

    Using the ANH API to update a single installation (or registration) at a time is impossible because the API requests are throttled at around 8-10K requests. Also, as mentioned in the OP's post "it results in very poor performance".

    Installations would be a much better fit for our usage because we now require maintaining 2+ templates (at least one for standard notifications another for silent notifications). With the registration model, we have to maintain 2+ registrations per device which places a lot more maintenance on the client side. With the installation model we can maintain all of our templates against a single installation.

    If ANH supported bulk operations for the installation model then we could bulk tag our installations (as we currently do with registrations) and move to the preferred installation model.

    I think this feature has a very high priority but this suggestion has been "under review" for over 2 years now. Can we please have progress update?

    Many thanks in advance.

Feedback and Knowledge Base