How can we improve Azure Notification Hubs?

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…)
Koby shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

2 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • Uri Goldstein commented  ·   ·  Flag as inappropriate

    Thanks for the response Azure Mobile team, but your answer is somewhat confusing.

    Are you saying notification hubs are no longer priced "per namespace"? Are they now priced "per subscription"? If so - do I understand correctly that the maximum amount of money I will be charge, for a given "premium tier" subscription, is $200/mo (as long as I'm under 10M pushes/mo)?

Feedback and Knowledge Base