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 whitelisted 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 whitelisting requirements.

Table 1. Exchange Server IP Whitelisting 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

For information on the architecture design and functionality of ENS2, see Architecture Overview.

Note:

The Exchange outbound connections are required to Cloud ENS and CNS. 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 whitelisted 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 whitelist SEG IP addresses as all outbound connections from the Exchange server is going to the ENS server and not to the SEG EWS proxy.