Architecture: BEMS notification flow using the Microsoft Graph API Skip Navigation

Architecture:
BEMS
notification flow using the
Microsoft Graph
API

In 2022,
Microsoft
started to deprecate the
Microsoft Exchange Web Services
(EWS) for Microsoft
Microsoft Exchange Online
APIs replacing the EWS with
Microsoft Graph
. For more information, visit techcommunity.microsoft.com and read 'Upcoming API Deprecations in Exchange Web Services for Exchange Online'.
This diagram shows how
BEMS
uses
Microsoft Graph
to send notifications to devices.
Component name
Description
BEMS
BEMS
consolidates several
BEMS
services used to send work data to and from
BlackBerry Dynamics
apps, including
BlackBerry
Push Notifications
(
BlackBerry
Mail),
BlackBerry Connect
,
BlackBerry Presence
, and
BlackBerry
Docs
.
BEMS
listens for notification URI sent by the
Microsoft Graph
API.
Reverse proxy server
The reverse proxy server receives the
Microsoft Graph
connection and forwards the connection to the private
BEMS
URI.
Microsoft Graph
Microsoft Graph
is a RESTful web API that allows you to communicate with
Microsoft
Cloud service resources.
  1. In the
    BEMS
    console (Mail > Microsoft Graph), you add the External Notification URL that the
    Microsoft Graph
    API will use to initiate connections to the reverse proxy server.
  2. The
    Microsoft Graph
    API initiates connections to your organization’s reverse proxy using the provided External Notification URL.
  3. The reverse proxy server intercepts the
    Microsoft Graph
    connection request and translates/routes the connection request to your private
    BEMS
    instance.
  4. BEMS
    sends the new notification to the user's
    BlackBerry Dynamics
    app (for example, BlackBerry Work).