Create and send a notification from your app service (deprecated)
The Microsoft Graph notifications API is deprecated and stopped returning data in January 2022. For an alternative notification experience, see Microsoft Azure Notification Hubs. For more information, see the blog post Retiring Microsoft Graph notifications API (beta).
You can create and send a notification to a user by using Microsoft Graph APIs. The notification is stored in the Microsoft Graph Notifications service store and is sent to all app clients on all devices that the target user is signed in on.
In order to send a notification to your user, your application service will:
- Authenticate with the Microsoft identity platform.
- Post a notification to the Microsoft Graph API using the auth token, and target the user with a user notification subscription ID that is obtained from your app client when creating a subscription.
For a simplified authentication story, we recommend using the new and improved, lightweight notification SDK on the client-side with a user notification subscription ID to receive notifications and manage notification state. Alternatively, you can post notifications on behalf of the user via delegated permissions and your app service will need to maintain access tokens and refresh tokens, but this is not recommended. To learn more about OAuth 2.0 OBO flow, see Service-to-service calls that use delegated user identity in the On-Behalf-Of flow.
Guaranteed delivery on iOS
On platforms like iOS, under certain power conditions, raw data notifications might be delayed in delivery due to batching, or not reach the target endpoint at all. For high-priority notifications being delivered to users on iOS, the Microsoft Graph notifications platform allows you to specify a raw-to-visual toast notification "fallback" option that automatically sends a visual toast notification to the target iOS device, thereby ensuring your user gets notified near real-time. To learn how to leverage fallback options, please see the notification resource.