Windows Azure Notification Hubs: Tags and creating a breaking news app

This is part 2 of a 3 part series where we will get to know how Notification Hubs work and why they are a cool feature of Windows Azure.

You can get the source code of the projects in this blog post here:


In the first part of this blog series, we created a Notification Hub, a server side app to push notifications as well as a Windows 8 app to consume notifications. In this post, we will see a neat feature of Notification Hubs which is Tags.

What are tags?

In the first part, we used the hub to broadcast a notification to all the users on our hub. But what if we want more granular control? Say what if we are building an application like Bing News and we want to push breaking news notifications to only people who are subscribed to a specific category? Tags give you the power to do exactly so.

Tags can act as “interest groups and frees you from maintaining the tag registrations, as the devices themselves handle that. They are simple strings, so they can be anything. Any of the tags below would work:


Building the Breaking News app

The source code of the app is available on GitHub here: so I won’t be going in details of creating the app, but will highlight the interesting bits of code.


Just like we did in part 1, registrations expire, so you should renew your registration with the Notification Hub upon app launch

// Create the notification hub
NotificationHubClient hub = NotificationHubClient.CreateClientFromConnectionString(
    "Endpoint=sb://[service bus name space];SharedAccessKeyName=DefaultFullSharedAccessSignature;SharedAccessKey=[notification hub full key]",
    "[notification hub name]"
// Get a Push Notification channel from the PushNotificationChannelManager
var channel = await PushNotificationChannelManager.CreatePushNotificationChannelForApplicationAsync();
// This is over simplification. In a real world app, you would probably be getting those through the app and loading them here
string[] tagsToSubscribeTo = { "sports", "politics" };
// Register with the Notification Hub, passing the push channel uri and the string array of tags
await hub.RegisterNativeAsync(channel.Uri, tagsToSubscribeTo);


Building the Breaking News backend

Regardless of how you build your backend, it can be an MVC website, a Web API, a WCF Service or even a console app, this is how you send the notification. Note that we specified the tag name “sports” when sending the notification. We didn’t have to loop over any records on our database to see who is interested in receiving sports update. It is all handled by the Notification Hub

// Create a hub client using the DefaultFullSharedAccessSignature
NotificationHubClient hub = NotificationHubClient.CreateClientFromConnectionString(
    "Endpoint=sb://[your service bus name];SharedAccessKeyName=DefaultFullSharedAccessSignature;SharedAccessKey=[your DefaultFullSharedAccessSignature]",
    "[notification hub name]"
// Since we are using native notifications, we have to construct the payload in the format
// the service is expecting. The example below is for sending a Toast notification on Windows 8
string toastTemplate = @"<toast><visual><binding template=""ToastText01""><text id=""1"">{0}</text></binding></visual></toast>";
// This call essentialy broadcasts a push notification to ALL Windows 8 devices that are registered with the service
// and registered to receive "sports" notifications
var payload = string.Format(toastTemplate, "Messi scored a goal against Brazil in the World Cup Finals");



Download the app from GitHub and play around with it. In the next post, we’ll be covering an exciting feature called Templates. Until then!

Comments (4)

  1. jeniffer says:

    Had no detailed information about tags bt am really happy i hav gained alot

  2. J says:

    where is the third part of the series? it's been 3 month…

  3. dadecki says:

    I was looking for this so long!

    Thank you

  4. oliver says:

    Thanks! Your explanation of tags was helpful. I couldn't find info about this anywhere else online.

Skip to main content