Article

Cloud configuration requirements for Pega Sales Automation calendar synchronization with Microsoft Exchange

The location of your Pega application server (client server) and your Microsoft Exchange server has an impact on the configuration requirements for calendar synchronization. If you are hosting one server on-premises and one in the cloud, additional setup is required.

Configuration requirements when your Pega application server is in the cloud and your Microsoft Exchange server is on-premises

If your Pega application server is in the cloud and your Microsoft Exchange server is on premises, review the following configuration requirements for sending requests and receiving notifications from your Microsoft Exchange server.

Sending requests to your Microsoft Exchange server

When your Pega application server is hosted in the cloud, triggering requests to an on-premises Microsoft Exchange server is possible only when the Microsoft Exchange server is accessible to the Pega application server.

You can host your cloud instance as either a private cloud (internal to your network) or public cloud (external to your network).

  • Private cloud – If you have a private cloud instance that uses a VPN site-to-site tunnel, you can allow communications between your Pega application server and your Microsoft Exchange server without exposing any of your environments to the Internet or moving them into the DMZ.
  • Public cloud – If you have a public cloud instance, you must set up a proxy in the DMZ to allow communications between the off-site (external) Pega application server and the on-premises (internal) Microsoft Exchange server. The URL will direct the off-site (external) Pega application server/EWS to the proxy in the DMZ, which will then pass on the communications to the on-premises (internal) Microsoft Exchange server.

Alternatively, you can choose one of the following approaches to allow communications between the off-site (external) Pega application server and the on-premises (internal) Microsoft Exchange server:

  • Use something like an F5 in the DMZ to take the place of the proxy. The functionality will remain the same.
  • Move your Microsoft Exchange server into the DMZ.

Receiving notifications from your Microsoft Exchange server

To receive notifications from your Microsoft Exchange server, you must whitelist the Microsoft Exchange server IP in your cloud configuration.

Configuration requirements when your Pega application server is on-premises and your Microsoft Exchange server is in the cloud

Receiving notifications from your Microsoft Exchange server

If your Pega application server is in the cloud and your Microsoft Exchange server is on premises, review the following configuration requirements to allow your Pega application server to get push notifications from your Microsoft Exchange server.

Requirements

  • Access to the Microsoft Office 365 Administrative Portal
  • Access to configure your network edge devices, for example, firewall, IPS, and Load Balancer
  • Pega application server

Configuration

If your Pega application server is on an internal network and resides behind a firewall, IPS, or load balancer setup, and your Microsoft Exchange server is cloud-based (outside of your network), you must allow your network to permit communications from the cloud-hosted Microsoft Exchange server to the Pega Application server.

Required ports

Identify the port that will be used for inbound traffic to your network. This is often port 443.

For additional security, you should configure your edge device to specify the inbound domains that can send communications to the Pega application server so that only those from Microsoft Exchange online can communicate with the Pega application server.

In many cases, the standard endpoint URL for Microsoft Exchange online is: https://outlook.office365.com/ews/exchange.asmx. In this example, you would configure your edge device’s policy to allow inbound communications from *.office365.com to communicate with the Pega application server on the inbound traffic port. If you are unsure of your endpoint URL, please contact your organization’s Microsoft Office 365/Microsoft Exchange online administrator.

If this approach is too broad to meet your organization’s security policies, or you require more domains to be whitelisted, please see the Office 365 URLs and IP address ranges page on the Microsoft support website.

Sending requests to your Microsoft Exchange server

Because your Microsoft Exchange server is on the cloud, you do not need to maintain any additional configuration settings to connect to it.

Published April 20, 2018 — Updated March 22, 2019

Related Content

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.