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.

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

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?

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

We need native SMS support in Azure. Our customers don't want to deal with multiple vendors and SLAs.

I am using user email addresses as a notification tag.

Email addresses that have a plus ('+') do not work as tags.

Normal email: myemail@gmail.com
Expanded email: myemail+gmailfeature@gmail.com

I get the following exception: Valid tag characters are alphanumeric, _, @, -, ., : and #

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.

It would be good to provide browse/query explorer for registered devices/handles and tags in Portal.

The interface might be similar to DocumentDB document/query explorers in Portal.

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.

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.

The nuget package Microsoft.Azure.NotificationHubs requires a .Net Framework 4.5 Full Profile, can you update to support .NET Core?

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)

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.

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

Also Delete api by tags and PushChannel

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.

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...

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