Notification Hubs

  1. Add webhooks to Azure Notification Hubs

    Add the ability for Notification hubs to call an endpoint when an event has occurred on a push notification (push delivered, failed ...etc)

    99 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    For the notification related events, we can only report if the message was successfully sent to the respective provider’s PNS. The actual delivery of the message is handled by the PNS and we don’t have any direct visibility in this. Where we can add some hooks are instances where maybe the registration expires etc. Let me know if there are any other places you will find this useful.

  2. Add ability to move NotificationHub from one namespace to another within the same subscription id

    According to this answer in the forums:
    https://social.msdn.microsoft.com/Forums/azure/en-US/08a3ffc8-dbf3-4212-8533-d639371e2016/moving-notification-hub-from-one-namespaces-to-another?forum=notificationhubs&prof=required

    It requires contacting support in order to move notification hub between namespaces (sometimes one app get's bigger audience and it's necessary to move it to different pricing namespace e.g. from Basic to Standard)

    69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…

    55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Get Installation and Delete Installation By Tags, By PushChannel

    I think azure must provide api to get installation record by Tags and PushChannel.

    Also Delete api by tags and PushChannel

    47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. cli support notification hub

    Support creating and managing Notification Hubs from the CLI. Not everybody uses powershell...

    Please make Azure-CLI a first class citizen to manage resources...

    37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Notification hub - Better way of analytic for push notifications send using Azure

    Notification hub currently provides a way to send PN across all plateforms but the analytic provided is not very usable and real time.

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow Global Templates

    As I understand it, templates are only held at a specific user registration level.
    For our (enterprise) app this makes life difficult, as I now need to register a large number of templates to a large number of registrations, and worse keep this in sync as templates are changed.

    It would work better in our scenario to have 'global' templates ready in the hub (referenced by name), then send a message to whatever tags, specifying the template desired.

    Under this scenario we would handle any personalisation via the back end app - using either tags or other means (I'm either…

    33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add the ability to read certificate (APNS) from Key Vaults

    Instead of uploading a certificate to the notification hub (Scattering certificate management across many resources). Having certificates consolidated in a Key Vault makes it easier to manage certificates and makes expiring certificates less common.

    We rely heavily on Key Vaults, for managing our domains SSL certificates, to Azure Service Fabric Cluster Certificate and others. Having the APNs Certificate there provides a one stop shop for all certificates on the portal.

    24 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 →
  9. APN Tokens should be hidden (password field) in the portal?

    From what I've read the token in the Apple (APNS) section of the notification hub should be the contents of the p8 private key file.

    I pasted this in and it is working fine however the full private key is there in plain text for anyone to see.

    Did i use the wrong key / token here or should this be somehow hidden to stop someone copying it and then using it elsewhere?

    16 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 →

    You are correct, anyone with access to the notification hub can view the notification credentials for all notification providers. This is how the underlying API is built and while we could use a password field to hide the value in the UI, the value is still available in the browser. Additionally, it is common for customers to have trouble inputting these values and it’s important for them to be able to verify the value when troubleshooting. It’s important to control access to your notification hubs to prevent unauthorized users from accessing the stored credentials.”

    From our side, we are planning to refresh this UI and we could consider hiding by default with a checkbox to show the value. Technically it’s not secure, but at least hides the value from casual access.

  10. Portal: Show Active Devices, total registrations count

    They only exposed in old portam, but both two values are super important to manage tier. Please make them display in new portal.

    12 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 →
  11. Azure Notification hub Monitoring via Azure Portal and from Azure Log Analytics

    Generally we have an option to monitor Azure PaaS components via Azure portal (ie, Dashboards, alert notify) and from OMS portal.

    But Azure Notification hub doesn't have capability in ARM portal for Monitoring it. But it as in Classic Portal.

    Please advice whether we can monitor Notification hub from ARM Portal and from OMS? Is it available in ARM?

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add integration with unity apps

    I'd like to use Notification Hubs with FCM and APNs to push notifications to a unity app. It would be useful to have a tutorial for this and/or a unity plugin which does the job.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Send push even if APNS certificate expired error occurred

    Today, our service had a problem that Template push notification was not working.

    The push service in server did not throw exception so only NH debug mode helped to investigate the error. The cause was "Apns certificate expired"

    It seems that NH validates all push notification providers' availability in template mode. It could make serious service blockage as today.

    What I suggest is;
    1. Send push to other validated notification provider
    - or -
    2. Show error message when such error is occurred. In Monitor tab, there was no error count and only "0 message sent" is displayed in chart.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. incorrect hints when sending test message on TestSend blade

    We have devices register as GCM template device. When we send native message on TestSend blade, it show 'Successfully send test message'. It is not correct, it should tell me the sending failed, please use 'Custom Template' to send message.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Notification Hub debugging system like Onesignal

    Hello, sorry for my english.

    We use several applications with notifications, some with OneSignal and others with Azure Notification Hub.
    With OneSignal, it's easy to test a specific device, run a test campaign and manage everything. See if people have disabled notification, application version, etc. etc.
    Make debugging easier. Manage the certificate easily with a lot of documentation.

    In Azure, it's really very hard and boring.

    It is very difficult to send a notification test to a specific device. We are not sure to send 30 000 devices a test notification, etc.
    The monitoring system is not really useful, because…

    3 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 →
  16. Use DateTime for InstallationTemplate.Expiry property in .NET API

    Right now the datatype for the APNS-specific Expiry property on InstallationTemplate is a string. I have... no idea what to put there. The API reference is less than helpful:
    https://msdn.microsoft.com/en-us/library/azure/microsoft.azure.notificationhubs.installationtemplate.expiry.aspx#P:Microsoft.Azure.NotificationHubs.InstallationTemplate.Expiry

    Since it looks like the expiry ends up as a binary encoded integer value of seconds since the UNIX epoch, I can't really use that to guess what format Azure expects.

    This would all be moot if the Notification Hub .NET API used a DateTime for the expiry and handled the translation to the format APNS requires.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add a loopback fake test PNS to the PNS list - Test receive

    Having a loopback PNS can:
    -improve the test capabilities
    -improve the onboarding experience, a new user can just set up a notification hub on azure management portal, use the test send and then see the messages arriving in the loopback PNS

    This could be a plus: from the loopback PNS it should be possible to manage the registration and the tags to receive, in this way the users can have a complete testing environment for onboarding and get familiar with the technology, without opening development accounts with Google/Microsoft/Apple/Amazon.

    3 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 →
  18. Increasing the 60 tags per device limitation of Notification Hubs

    Having this limitation requires a workaround for implementations that focus on managing the complexity of social relationships

    2 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 →
  19. Return FCM messageId in REST Api Response Header for all pricing tiers

    The Notifications Hubs REST API Method "Send a Template Notification" should always return the FCM message_id in the Response Body for all Notification Hub tiers. Without this functionality,
    it’s of limited use in secure and auditable applications where message notification tracking is vital.

    The alternative is to bypass Notification Hubs altogether for the purposes of sending and use the Firebase Api directly.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Notification Hubs

Categories

Feedback and Knowledge Base