Skip to main content

Cloud configuration requirements for Pega application calendar synchronization with Microsoft Exchange

Suggest edit Updated on July 1, 2020

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

For more information, see the Pega Cloud product page.

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

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):

  • 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.
  • 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 directs the off-site (external) Pega application server or Exchange Web Services (EWS) to the proxy in the DMZ, which then passes 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 an F5 in the DMZ to take the place of the proxy. The functionality remains the same.
  • Move your Microsoft Exchange server into the DMZ.

To receive notifications from your Microsoft Exchange server, you must add the Microsoft Exchange server IP to the allow list in your cloud configuration.

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

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

You must have access to the following elements:

  • Microsoft Office 365 Administrative Portal
  • Network edge devices, for example, firewall, IPS, and Load Balancer
  • Pega application server

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 for inbound traffic to your network, for example, port 443.

For additional security, consider configuring your edge device to specify the inbound domains that 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 can 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, contact your organization’s Microsoft Office 365 or Microsoft Exchange online administrator.

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

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us