Email Notification Service (ENS) is available for customers using the UEM console with both SaaS and on-premises deployments. In standard configuration, you always install the ENS on premises, while Workspace ONE hosts the Cloud Notification Service (CNS). The service account credentials are stored on the ENS server and not in a Workspace ONE database.

ENS and the Exchange server interact with one another based on the message notification functionality of the Exchange server. Depending on the notification functionality, the interaction method between the ENS and Exchange differs, but the basic architecture of the ENS remains the same.

For more information on the notification functions of the Exchange server, see Notification Mechanisms.

Note:

ENS is not available for Android devices with AirWatch Inbox or VMware Boxer.

Push Notification Model

The push model does not have an open connection between the ENS and the email server. The ENS provides real-time notifications when a new message arrives.

 

Email Notification Service (ENS) with On-premises Exchange server

The interactions between the ENS and the on-premises Exchange server to push the email notifications to the AirWatch Inbox or VMware Boxer installed devices is shown.

ENS with Exchange Push Model

  1. ENS server makes an API call periodically to Workspace ONE to check and fetch the user and device details from Workspace ONE. These details are cached and refreshed periodically or on demand. Manual refresh can be done by restarting the ENS.
  2. ENS server subscribes the user to Exchange.
  3. Exchange pushes the message event to ENS when a new message arrives.
  4. ENS fetches the mail details from Exchange using the subscription details upon receiving the message event.

  5. ENS server checks if the device is email-compliant and then sends the notification to CNS.
  6. CNS forwards the notification to Apple Push Notification Service (APNs).

  7. The APNs pushes the email notification to AirWatch Inbox or VMware Boxer on the device.

 

Email Notification Service (ENS) with Office 365

The interaction between the ENS and the Office 365 to push the email notifications to the AirWatch Inbox or VMware Boxer installed devices is shown.

ENS with O365 Push Model

  1. ENS server makes an API call periodically to Workspace ONE to check and fetch the user and device details from Workspace ONE. These details are cached and refreshed periodically or on demand. Manual refresh can be done by restarting the ENS.
  2. ENS server subscribes the user to Office 365.
  3. Office 365 pushes the message event to the ENS when a new message arrives. Since Office 365 is on cloud and ENS in on premises, when using the push model a DNS record is required for the message events to reach the ENS server. This is the only aspect where push model differs from the streaming model.
  4. ENS fetches the mail details from Office 365 using the subscription details upon receiving the message event.

  5. ENS server checks if the device is email-compliant and then sends the notification to CNS.
  6. CNS forwards the notification to Apple Push Notification Service (APNs).

  7. The APNs pushes the email notification to AirWatch Inbox or VMware Boxer on the device.

 

The email notifications from ENS for the AirWatch Inbox or VMware Boxer are displayed on the iOS devices when the apps are running in the background. The notifications appear even when these apps are force quit by the user. However, notifications do not appear when these apps are in foreground.