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.
464 votesPush to web is on our roadmap and we will update once we have a more concrete ETA.
-
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)
80 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)
61 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.
-
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.
26 votesWe are looking into E2E telemetry and providing better analytics for our customers.
-
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…
24 votesWe are working on a design for global templates.
-
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)
23 votes -
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?
20 votesWe are looking into this.
-
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
18 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 [email protected]. Thanks!
-
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 -
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 -
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…
6 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.
-
Make NotificationHub fully available in the new UI / RBAC model
Make NotificationHub fully available in the new UI / RBAC model
Our development team really wants to use the notificationhub functionality, but in order to configure / manage it, they need Co-Admin access rights in the old portal on this subscription. This gives them full access to all resources in this subscription which is not acceptable for our information security team.
We really need NotificationHub and related functionality in the new portal so we can use RBAC.
4 votesWe are in progress with migrating all functionalities from the classic portal to the new portal.
-
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.ExpirySince 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 -
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 PNSThis 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
- Don't see your idea?
