Azure Notification Hubs Blog
Learn about Push Notifications and updates, releases and features of Notification Hubs
Latest posts
Security Update: Changes to URI Expiry Time in Azure Notification Hubs
As part of our ongoing efforts to enhance the security of Azure Notification Hubs, we are making an important change to the expiry time of the generated URIs. Starting from October 2024, the expiry time of PnsErrorDetailsUri will be reduced from 10 days to 5 days. This means that the PnsErrorDetailsUri returned will now be valid for only 5 days and will expire thereafter. The PnsErrorDetailsUri is returned from the Get Notification Message Telemetry API, which provides additional telemetry on the finished states of outgoing push notifications. Learn more about Get Notification Message Telemetry API here. Consum...
Support of Azure Notification Hubs’ Firebase Cloud Messaging (FCM) legacy API will be deprecated on June 20, 2024.
GCM/FCM is being deprecated: Customers have less than a month to migrate to FCM v1 Firebase Cloud Messaging (FCM) is a service that, among other things, facilitates developers sending push notifications to Google Play supported Android devices. ANH previously communicated with FCM using the Legacy HTTP protocol. FCM v1 is an updated API that offers more features and capabilities. Google will stop supporting FCM legacy HTTP on June 20, 2024. All customers must migrate your applications and notification payloads to the new format (FCM v1) before then. The Firebase Cloud Messaging (FCM) legacy API will be depr...
Announcing Browser Push GA with Azure Notification Hubs
We are extremely excited to announce the general availability of Azure Notification Hubs Browser Push Notifications, also known as Web Push Notifications. We know this has been a long asked for feature and we’re happy to say that you can now send notification messages via web browsers with ANH. This feature can be used through the Azure Portal, our REST APIs or Server-side SDKs. Azure Notification Hubs now supports Browser Push for all major browsers including Microsoft Edge, Google Chrome and Mozilla Firefox. Apple Safari is not included as you can use existing APNS support as described in Configuring Safari Pu...
Announcing FCM v1 for ANH
We are happy to announce that Azure Notification Hubs (ANH) Firebase Cloud Messaging (FCM) v1 is now generally available all customers. This means that you can start using the new features and capabilities of FCM v1 with ANH today. FCM v1 offers better security, performance, and reliability than the legacy FCM HTTP API, which will be deprecated by Google on June 20, 2024. To avoid any disruption in service, we strongly recommend that you migrate your applications and notification payloads to FCM v1 before then. To help you with the migration, we have updated our documentation with the steps and best practices fo...
FCM v1 SDK preview program
We are excited to announce that core capabilities for the integration of Azure Notification Hubs (ANH) with Firebase Cloud Messaging (FCM) v1 SDKs are ready for testing. As a reminder, Google will stop supporting FCM Legacy HTTP on June 20, 2024, so you will need to migrate your applications and notification payloads to the new format before then. All methods of onboarding will be ready for migration March 1, 2024. To help you with this transition, we are inviting you to join our preview program and test the FCM v1 onboarding process for SDKs in February. This will give you early access to the new features and c...
FCM v1 Update as of Jan 2024
We are excited to announce that core capabilities for the integration of Azure Notification Hubs (ANH) with Firebase Cloud Messaging (FCM) v1 is ready for testing. As a reminder, Google will stop supporting FCM Legacy HTTP on June 20, 2024, so you will need to migrate your applications and notification payloads to the new format before then. All methods of onboarding will be ready for migration March 1, 2024. To help you with this transition, we are inviting you to join our preview program and test the FCM v1 onboarding process for Rest APIs in February. This will give you early access to the new features and ca...
Introducing Private Link (Public Preview)
We are excited to announce the public preview of Private Link, a new feature that enables you to connect to your data sources privately and securely from within your own virtual network. Private Link provides a direct and encrypted connection between your virtual network and your data source, without exposing your data to the public internet. This means you can access your data with lower latency, higher reliability, and enhanced security. Private Link is easy to set up and use. You can create a private endpoint for your data source in a few clicks. To get started with Private Link visit our documentation page h...
Announcing Public Preview of Web Push Notifications with Azure Notification Hubs
We are extremely excited to announce the public preview of Azure Notification Hubs Web Push Notifications. We know this has been a long asked for feature and we’re happy to say that you can now send notification messages via web browsers with ANH. Azure Notification Hubs now supports Browser Push for all major browsers including Microsoft Edge, Google Chrome and Mozilla Firefox. Apple Safari is not included as you can use existing APNS support as described in the Configuring Safari Push Notifications , with certificate-based authentication. Browser Push capability is currently supported across platforms with the...
Introducing Availability Zones GA for Azure Notification Hubs
We are excited to announce another new general available feature that improves the high availability of your push notifications: Availability Zones. This feature is available for an extra cost of $350 a month for all tiers. Starting October 9th, all customers including those who were previously in preview will begin to be billed for the feature add-on. You can only configure availability zones for new namespaces at this time. These zones are physically separate locations within each Azure region that are tolerant to local failures. Failures can range from software and hardware failures to events such as earthqua...
Introducing flexible recovery region for Azure Notification Hubs
Flexible recovery region now in GA We are excited to announce that flexible recovery region for Azure Notification Hubs is now generally available (GA) for all customers. All tiers provide a flexible recovery region option, enabling you to choose from a list of supported regions. In regions with availability zones and no region pair, you can use flexible recovery to choose a failover region that provides resiliency in the event of a full region failure. Azure Notification Hubs is a scalable, reliable, and cost-effective service that enables you to send push notifications to millions of devices across platforms...
FCM v1 Migration Steps (Preview)
Firebase Cloud Messaging (FCM) legacy API will be deprecated by Jul 2024. The ANH team is preparing so customers can begin migrating from Legacy HTTP protocol to FCM v1. Customers may start this migration process March 1, 2024 and will need to be migrated by June 2024. No action is required at this time, further instructions will be made available in Feb 2024. Concepts for FCM v1: To migrate from FCM legacy to FCM v1, here’s what you can expect: Provide credentials for FCM v1: You will need to provide your FCM v1 credentials to set up notifications. Update Client App to start registering as FCMv1 device...
New high availability features for Azure Notification Hubs (Preview)
We are excited to announce that the new high availability features Availability Zones and flexible disaster recovery are now available for preview for your ANH push notifications. Azure Notification Hubs currently offers default paired secondary regions that act as a backup in case of a regional outage. If the primary region becomes unavailable, ANH will automatically fail over to the secondary region and resume sending push notifications to your devices. What is high availability? High availability is a key requirement for any modern cloud application. High availability is the ability of a system to remain ope...
Migrating Notification Hubs from FCM Legacy HTTP to FCM v1
Update as of June 2023: Firebase Cloud Messaging (FCM) is a service that, among other things, facilitates developers sending push notifications to Google Play supported Android devices. ANH currently communicates with FCM using the Legacy HTTP protocol. FCM v1 is an updated API that offers more features and capabilities. Google announced that they will be deprecating FCM Legacy HTTP and will stop supporting it on June 20, 2024. Therefore, developers who use Azure Notification Hubs to communicate with Google Play supported Android devices today, will need to migrate their applications and notification payloads to...
Targeting Random Users
Computer systems are notorious for being able to do many precise operations quickly, but struggling to do things at random. Imagine you want to A/B test two different notifications on a small set of your user base before broadcasting a promotional offer to everyone. How would you choose two random subsets of your users? How would you make sure that there was no intersection between those subsets? Finally, how would you exclude the users whom were tested on from the later notification so that they didn't see the same promotional offer twice? Using Azure Notification Hubs tag expressions, and one simple technique, ...
Announcing availability of end-to-end Azure Notification Hubs samples using React native
Today, we are super excited to announce the availability of Azure Notification Hubs samples, to better demonstrate the awesome capabilities of Azure Notification Hubs end to end using react native on multiple platforms such as Android and iOS.
Bintray Sunset
Bintray Sunset Since Azure Notification Hubs published its first SDKs to JFrog's Bintray in April of 2016, many other Azure services have joined us and started publishing Java SDKs. However, this led to some divergence, with other SDKs by-and-large being published on Maven Central. This has long been a papercut we've wanted to fix, but without any trouble forcing urgency on the matter. However on February 3rd, 2021, JFrog announced that they will begin shutting down services that are currently used to host our SDKs. This has provided the catalyst necessary to move our SDKs to Maven Central. What's Moving? Ava...
Use Templates Effectively
Every time development of a new mobile app starts, one of the first questions that needs to be answered is, "How are we going to support both iOS and Android?" Deciding on a technology to build the client-side app logic and UI alone is complicated enough, extending client specific knowledge into your backend is only going to exacerbate that pain. Using Azure Notification Hubs' templates, you can let each client maintain full control of how notifications will look, protecting your backend server from needing to know platform details. Define Personalization on the Client Let's say you're writing an application f...
Welcome!
Welcome blog to the Azure Notification Hubs service