{"id":5603,"date":"2020-11-19T15:20:03","date_gmt":"2020-11-19T23:20:03","guid":{"rendered":"https:\/\/officedevblogs.wpengine.com\/?p=5603"},"modified":"2020-11-19T15:20:03","modified_gmt":"2020-11-19T23:20:03","slug":"retiring-microsoft-graph-notifications","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/retiring-microsoft-graph-notifications\/","title":{"rendered":"Retiring Microsoft Graph notifications API (beta)"},"content":{"rendered":"

The\u00a0<\/span>Microsoft Graph\u00a0<\/span>notifications<\/span>\u00a0API<\/span><\/a>,\u00a0<\/span>a<\/span>\u00a0<\/span>preview\u00a0<\/span>service designed to enable\u00a0<\/span>delivery of push notifications<\/span>\u00a0(typically visual ones)<\/span>\u00a0to users\u2019 registered device endpoints,<\/span>\u00a0was announced in 2017 at Microsoft Build<\/span>.<\/span>\u00a0<\/span>At that time,<\/span>\u00a0our<\/span>\u00a0goal was to release\u00a0<\/span>Microsoft\u00a0<\/span>Graph notifications for General Availability at Microsoft Ignite in November 2019. After collecting feedback from Microsoft customers and partners<\/span>, we<\/span>\u00a0decided\u00a0<\/span>not to<\/span>\u00a0move forward with\u00a0<\/span>making\u00a0<\/span>this service<\/span>\u00a0generally<\/span>\u00a0<\/span>available.<\/span>\u00a0<\/span>Instead, w<\/span>e<\/span>\u00a0have<\/span>\u00a0<\/span>worked<\/span>\u00a0to unify our notification strategy and\u00a0<\/span>focus on<\/span>\u00a0<\/span>usage of Azure Notification Hubs<\/span>, which\u00a0<\/span>has been a successful public offering with a wide set of customers<\/span>\u00a0for the past few years.<\/span>\u00a0<\/span>\u00a0<\/span><\/p>\n

Note:\u00a0<\/span><\/b>to avoid confusion, this is\u00a0<\/span>announcement\u00a0<\/span>has no impact on\u00a0<\/span>Microsoft Graph<\/span>\u00a0<\/span>change notifications for resources<\/span><\/a>, also known as webhooks.<\/span>\u00a0<\/span><\/p>\n

We will retire\u00a0<\/span><\/b>Microsoft\u00a0<\/span><\/b>Graph notifications on\u00a0<\/span><\/b>February<\/span><\/b>\u00a01, 2021<\/span><\/b>\u00a0<\/span>to give customers who were potentially exploring using this\u00a0<\/span>service time<\/span>\u00a0to\u00a0<\/span>begin exploring<\/span>\u00a0Azure Notification Hubs<\/span>\u00a0instead.<\/span>\u00a0<\/span><\/p>\n

Why\u00a0Azure Notification Hubs<\/h3>\n

We believe there is a better experience for developers in Azure Notification Hubs<\/span>. I<\/span>t<\/span>\u00a0<\/span>simplifies the device onboarding process\u00a0<\/span>and offers<\/span>\u00a0additional features that make the overall experience better for current Azure Notification Hubs customers and\u00a0<\/span>Microsoft\u00a0<\/span>Graph notifications beta users.<\/span>\u00a0<\/span><\/p>\n

Azure Notification Hubs enables developers to send notifications\u00a0<\/span>to iOS, Android and Windows platforms from any back-end.\u00a0<\/span>Additionally,\u00a0<\/span>Notifications Hubs has\u00a0<\/span>a\u202fnew\u202fpreview release of the Notification Hubs SDK for\u202f<\/span>Android<\/span><\/a>\u202fand\u202f<\/span>iOS<\/span><\/a>.\u00a0<\/span>\u00a0<\/span><\/p>\n

Azure Notification Hubs Features<\/h3>\n

Here are a few\u202fkey\u202ffeatures of\u202fthe\u202fAzure Notification Hubs\u202fSDK.<\/span>\u00a0<\/span><\/p>\n

Device Registration<\/span><\/b>\u00a0<\/span><\/p>\n

Getting started with notifications is now much easier given our streamlined registration experience. The new SDK supports automatic\u00a0device<\/span>\u00a0<\/span>registration\u00a0with Notification Hubs via\u202f<\/span>Installations<\/span><\/a>\u202fand now automatically handles device registration for push notifications once you add the SDK to your app and enable push.<\/span>\u00a0<\/span><\/p>\n

Notification\u202fTargeting\u202fwith Tags<\/span><\/b>\u00a0<\/span><\/p>\n

Notification Hubs custom<\/span>ers have a similar capability\u202f<\/span>to<\/span>\u202f<\/span>t<\/span>ags.\u202fThe benefit\u00a0<\/span>of<\/span>\u00a0using tags is that you can have richer expressions with custom tag expressions\u202fas well as near real time targeting.<\/span>\u00a0<\/span><\/p>\n

Tags\u202ffor Installations<\/span><\/b>\u00a0<\/span><\/p>\n

You can add\u202fcustom\u202ftags to a\u202fdevice\u202finstallation,\u202fwhich allows for\u202fdeveloper specified\u202faudiences\u202fpotentially\u202fdefined by app\/OS\u202fversion,\u202flanguage, country,\u202fdevice\u202fmodel\u202fetc.<\/span>\u00a0<\/span><\/p>\n

Tags for Users<\/span><\/b>\u00a0<\/span><\/p>\n

Microsoft\u00a0<\/span>Graph notifications<\/span>\u202f<\/span>allow<\/span>ed<\/span>\u202fyou to associate users\u202fwith devices<\/span>\u00a0(user-centric notifications)<\/span>,\u202fand with the new Notification Hubs\u202fSDK,\u202fyou can\u202fachieve the same\u202fresult\u202fby\u202fsetting a custom\u202f<\/span>userID<\/span>\u202fproperty\u202ftag.<\/span>\u00a0<\/span><\/p>\n

Alert\/Silent\u202fNotifications<\/span><\/b>\u00a0<\/span><\/p>\n

With the\u202fAzure Notification Hubs SDK, you can set up a listener\u202fand\u202fbe notified whenever a push notification is received in\u202fthe\u202fbackground\u202f(silent push notification),\u202for an alert\u202fhas been clicked by the user.<\/span>\u00a0<\/span><\/p>\n

Online\/Offline\u202fSync<\/span><\/b>\u00a0<\/span><\/p>\n

A\u202fbackground synchronization manager\u202fensures\u202fthat\u202fwhen\u202fa device is offline,\u202fall\u202finstallation\u202fchanges are tracked\u202fand once network connectivity is re-established,\u202fthey are synchronized with the\u202fservice.<\/span>\u00a0<\/span><\/p>\n

Enabling\/Disabling Push<\/span><\/b>\u00a0<\/span><\/p>\n

The<\/span>\u00a0Notification Hubs SDK allows applications to enable or disable push. When disabled,\u202fpush tokens are not refreshed but\u202fpushes are still received\u202funtil the current\u202ftoken\u202fexpires.<\/span>\u00a0<\/span><\/p>\n

There are a few features\u00a0<\/span>(notification state and history, privacy and compliance)\u00a0<\/span>of Graph notifications that are not currently supported by Azure Notification<\/span>\u00a0<\/span>Hubs<\/span>.\u00a0<\/span>Based on\u00a0<\/span>customer feedback<\/span><\/a>\u00a0w<\/span>e\u00a0<\/span>will<\/span>\u00a0<\/span>prioritize\u00a0<\/span>the\u00a0<\/span>ad<\/span>d<\/span>ition of<\/span>\u00a0<\/span>those items\u00a0<\/span>to our backlog<\/span>.<\/span>\u00a0<\/span><\/p>\n

Getting\u202fStarted with Notification\u202fHubs<\/h3>\n

To help you get started,\u00a0<\/span>please refer to the\u00a0<\/span>Azure Notification Hubs Documentation<\/span><\/a>\u00a0<\/span>.\u00a0<\/span>\u00a0<\/span><\/p>\n

Developer Support\/Feedback<\/h3>\n

We want to hear from you\u202f<\/span>as you begin exploring and using Azure Notification Hubs. We are here to help you and answer any questions and address concerns\u00a0<\/span>and encourage you to share any issues,\u202fconcerns, or feedback through\u202fthe\u202fAzure\u202fNotification\u00a0Hubs\u202f<\/span>repository<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

We will retire\u00a0Microsoft\u00a0Graph notifications on\u00a0February\u00a01, 2021\u00a0to give customers who were potentially exploring using this\u00a0service time\u00a0to\u00a0begin exploring\u00a0Azure Notification Hubs\u00a0instead.\u00a0<\/p>\n","protected":false},"author":69076,"featured_media":25159,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-5603","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-graph"],"acf":[],"blog_post_summary":"

We will retire\u00a0Microsoft\u00a0Graph notifications on\u00a0February\u00a01, 2021\u00a0to give customers who were potentially exploring using this\u00a0service time\u00a0to\u00a0begin exploring\u00a0Azure Notification Hubs\u00a0instead.\u00a0<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/5603","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69076"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=5603"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/5603\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/25159"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=5603"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=5603"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=5603"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}