Notification Hubs
-
Add support for Azure Notification Hubs to push messages to web browsers
Azure Notification Hubs should be able to deliver messages to users via web browsers.
This should be done through lightweight javascript. The script should be cross browser compatible with desktop, mobile and legacy browsers.
Basically this would replace the need for hosting SignalR unless you're building something like a chatroom.
714 votesPush to web is on our roadmap and we will update once we have a more concrete ETA.
-
Microsoft.Azure.NotificationHubs add support for .NET CORE
The nuget package Microsoft.Azure.NotificationHubs requires a .Net Framework 4.5 Full Profile, can you update to support .NET Core?
274 votesWe are looking into this.
-
Use new APNs HTTP/2 API
Notification Hubs uses the old APNs binary protocol. Moving to the new HTTP/2 protocol would enable new features like updating existing notifications (using the 'apns-collapse-id' header)
97 votes -
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)
88 votesFor 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.
-
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=requiredIt 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 votesWith the new billing model – http://azure.microsoft.com/en-us/pricing/details/notification-hubs/ this will be a valid request. We will look into this.
-
Support grouping notifications
If using PNS for iOS and Android directly, notifications can be grouped by using apns-collapse-id https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/CommunicatingwithAPNs.html and summary notification ID https://developer.android.com/training/notify-user/group.
It would very useful if I could pass apns-collapse-id (for iOS) and summary notification ID (for Android) through Azure Notification Hub.
50 votes -
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…
49 votesThanks 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.
-
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
37 votesWe want to provide get installations by tags, and I’d love to understand more about your scenarios around delete installations by tags and get/delete by push channel if you don’t mind sending me an email at yuaxu@microsoft.com. Thanks!
-
Support push variables in all properties of templates
Currently push variables are only supported inside the message property of a notification payload. Our suggestion is that push variables should be available to use in all properties. For example...
In our case we use template registrations and send to large audiences using a single "batch tag" which we apply to registrations using a bulk registration update ahead of a push campaign.
When it comes time to send the template notification using the batch tag we need the ability to personalise other properties of the notification payload for each registration and not just the message property. Specifically, we need to…
33 votes -
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…
32 votesWe are working on a design for global templates.
-
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.
30 votesWe are looking into E2E telemetry and providing better analytics for our customers.
-
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 -
one notification hub to send push notifications to multiple apps
I would like to be able to use one notification hub to send push notifications to multiple apps.
For example, I might have a standard, pro, and enterprise level app that need to all work with the same Azure back end and be able to send notifications work with one another. The user should be able to seamlessly upgrade and still interact with other users who have different tiers of the same app.
15 votes -
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 votesThank you for the suggestion. This is currently under review.
/Shantaram – Program Manager
-
Add telemetry as an optional extra regardless of Notification Hub tier
Rich telemetry is important to ensure notifications get delivered and that old device tokens are effectively removed. This is only avaialable in the Standard Tier, which is very expensive. I'd like to see access to the PNS Feedback made optional, so that users on low volumes can see ensure those notifications are accepted by the PNS.
12 votes -
Make telemetry data available for a longer time
Based on my tests, telemetry data can be read only within ~24 hours after the message was sent out. After that time the backend unable to find the data for a given notificationid. So I guess you delete this statistics. It would be great to be able to get these information after much more time. I think it would be a good idea to make the telemetry availability time as a configurable value in the portal.
But making it available for minimum 1 week would be good. If it is possible please extend the current short time. Thank you in…11 votes -
Make Notifications Hub .NET Client Open Source.
As it seems you don't care in make .NET Notification Hub Clients available for .NET Core platform without .NET Full Profile requirement, please turn Notification Hub .NET Client Open Source and let the community work to bring .NET Core support for Notification Hub .NET Client a reality.
11 votes -
Make Notification Hub as simple as Firebase from google
I think you know that we have products addressing the same problem as we are. but they do it simpler than we are. For example Firebase code required from dev- much less than Notification Hub.
https://developers.google.com/cloud-messaging/faq"You no longer have to write your own registration or subscription retry logic. " - why we can't do something simple like that!
Recently when we discussed with customer usage of notification hub and I can't explain why they should use it instead of firebase after feature comparison
10 votes -
Please check and fix possible problems with PUSH notifications in Android and node.js
A lot of users are having problems with these services.
Problems with devices registering and unregistering, updating tags, devices that disappear from the registered devices list after two or three days and it starts the "Error deleting the push registration-Error: NotFound." problems...
7 votes -
guarantee SLA for delivering notifications
it would be nice to provide "real-time" notifications to use the service for transaction authentication number delivery
6 votes
- Don't see your idea?