ENS2 can be deployed on a cloud-hosted service. This topic describes configuring ENS2 on a cloud-hosted service.

Email Notification Service for Cloud

Use Workspace ONE UEM console to configure Workspace ONE Boxer for your cloud deployment.

Prerequisites for Workspace ONE UEM Console 2011 and lower

  • An API token and ENS2 server URL received from VMware is required to activate the ENS service using the Workspace ONE UEM console. To provision the ENS cloud API token, contact VMware Support.
  • Ensure the ENS server certificate is available on the user's Exchange server.

Prerequisites for Workspace ONE UEM Console 2101 and later

  • Obtain the ENS2 server URL from VMware which is required to activate the ENS service using the Workspace ONE UEM console.
  • The ENS cloud API token is obtained automatically and not shared by the VMware Support.

To configure ENS2 and email related settings for Workspace ONE Boxer see the Assign Workspace ONE Boxer with Email Settings section in the Workspace ONE Boxer Admin Guide.

ENS Endpoints and IP Allowlist

The API endpoints supported by ENS2 are listed in this topic.

When using cloud ENS servers, you must ensure that the ENS is accessible from the Exchange or Office 365 environment. The inbound IP addresses must be allowlisted to permit the ENS traffic into Exchange or Office 365. The IP address is selected based on the region the ENS is hosted in. The following table describes the Exchange server IP allowlist requirements.

Table 1. Exchange Server IP Allowlist Requirements
Location API Endpoint ENS Outbound to Exchange Inbound
North America https://ens.getboxer.com/api/ens

35.170.156.92

52.203.205.147

Asia Pacific https://ens-apj.getboxer.com/api/ens

54.248.56.175

54.249.212.171

European Union (EU) https://ens-eu.getboxer.com/api/ens

18.195.84.245

18.196.197.192

United Kingdom (UK) https://ens-uk.getboxer.com/api/ens

3.10.97.61

18.132.5.114

America (Federal) https://ens.gc.workspaceone-gov.com/api/ens

52.61.66.193

15.200.44.192

52.61.178.90

For information on the architecture design and functionality of ENS2, see the ENS2 Architecture section in the Introduction to Email Notification Service topic.

Note:

The Exchange CNS outbound connections are required when ENS is hosted on cloud and on-premises deployment. VMware leverages the public cloud providers for the greatest availability of services and cannot provide a static list of IPs. If there is a requirement to limit the outbound connectivity, the following hostnames can be used. For ENS use ens.getboxer.com, ens-eu.getboxer.com, ens-uk.getboxer.com, and ens-apj.getboxer.com (based on region in which the ENS is used) and for CNS use cns.awmdm.com

The outbound IP addresses must be allowlisted from the Microsoft Exchange client access rules (including Office 365) and any other firewall. This permits the outbound communication from the Exchange server into the ENS server. You need not allowlist SEG IP addresses as all outbound connections from the Exchange server is going to the ENS server and not to the SEG EWS proxy.

Subscribe to ENS2 Cloud System Status

You can subscribe to receive status updates on Workspace ONE Email Notification Service 2. To subscribe for the ENS2 status updates, perform the following steps:

  1. Login to status.workspaceone.com.
  2. Click Subscribe to Updates.
  3. Select Workspace ONE Email Notification Service 2.
  4. Select your Region.

Verify VMware Boxer Settings

Use Workspace ONE Boxer to verify your email connnectvity.

After you have added the ENS configuration keys to VMware Boxer in Workspace ONE UEM, check the Boxer settings on your device to confirm it has received these keys and that the ENS is activated.

  1. Open Boxer, tap the Settings icon and then select the appropriate email account.
  2. In the email settings, verify the Use Push Service is enabled.
  3. In the email settings, verify the Notifications display Push as the default selection.

Results: If the Use Push Service is enabled and Notifications display Push, then the ENS is activated.