To fully move away from the outlook.office.com REST interface for email we need a solution to get notifications for client/desktop software (non windows) and browser based software.
The existing webhook approach does not work well for anything but server to server configurations.
outlook.office.com provides a streaming notification:
<a rel="nofollow noreferrer" href="https://docs.microsoft.com/en-us/previous-versions/office/office-365-api/api/beta/notify-streaming-rest-operations"""">https://docs.microsoft.com/en-us/previous-versions/office/office-365-api/api/beta/notify-streaming-rest-operations"""</a>;
Which meets our requirements
This is an already acknowledged gap in the Graph API.
Please implement a solution for clients to get notifications that doesn't require a webhook.
This is also important to migrate IMAP clients to Graph as a replacement for IMAP IDLE is required.2 votes
Enable a way to create new notifications on Office 365 notifications bell, including:
* Url3 votes
To support Outlook Notifications REST API for services and daemons that use the client credential flow.3 votes
Thank you for your feedback! Could you please provide more information and scenarios in which this would be needed? -EY
Implement the integration of external notifications (from apps for instance) into the notification part of the Office 365 suite bar. That way, apps can become more integrated into the whole and for a user it becomes easier to navigate directly to the stuff that needs their attention.
An easy start would be to fire off a (client side?) call to a webservice which would then return the proper notifications to be shown in the notification bar. In the future maybe provide API calls to push new notifications into the system.10 votes
- Don't see your idea?