Skip main navigation

Hurry, only 9 days left to get one year of Unlimited learning for £249.99 £174.99. New subscribers only. T&Cs apply

Find out more

Microsoft Exchange On-Premises

Whereas the previous step dealt with Microsoft Exchange Online services, this step will discuss necessary considerations and differences when working

Whereas the previous step dealt with Microsoft Exchange Online services, this step will discuss necessary considerations and differences when working with an on-premises Microsoft Exchange instantiation.

For the mail processing in Common Data Services (CDS) for Apps, you can connect your apps with Microsoft Exchange Server on-premises.

Before connecting you must ensure that the following prerequisites are met:

Exchange Server Only the following versions are supported: Exchange Server 2010 SP3, Exchange Server 2013 SP1, or Exchange Server 2016
Authentication Windows or Basic authentication must be enabled in Exchange Server
Application Impersonation When connecting to the Exchange server on-premises, CDS needs to access users’ mailboxes. This is done by using a service account with the ApplicationImpersonation role. For more details see Impersonation and EWS in Exchange.
Secured connection Exchange server must support secure (https) connections
Exchange Web Services (EWS) Exchange server must be accessible externally using EWS protocol.

You may need to work with your Exchange Server administrator to ensure that all these prerequisites are met.

Create Server Profile

To connect to the Exchange Server, a new Email Server profile is required. To create a new profile, navigate to Settings for the environment in the Power Platform Admin centre then select Server profiles in the Email section.

screenshot of Power platform with Server Profiles highlighted beneath the Emails category

In the list view, select New > Exchange Server (Hybrid) to create the profile.

a screenshot of New Email Server Profile screen, with Server Type set to Exchange Server (Hybrid)

At a minimum, you need to specify the profile name and the credentials for the Exchange service account that was granted the ApplicationImpersonation role.

For the properly configured standard Exchange Server on-premises deployments, this is usually sufficient; however, you may need to review and adjust some of the advanced settings.

See Connect to Exchange Server for the details.

After the profile has been saved, you can use the Test-Connection command to verify the profile. If you’ve run Test Connection and have issues with the Exchange Server (Hybrid) profile connection, use the information in the Test Connection dialogue box to diagnose and fix the connection.

Once the Microsoft Exchange (Hybrid) profile is verified, it can be used as a default profile for the new mailboxes added to the system. If there are multiple email profiles present in the system, select Microsoft Exchange (Hybrid) profile in the list and select Set as Default.

This article is from the free online

Dynamics 365: Implementing Power Platform Integrations

Created by
FutureLearn - Learning For Life

Reach your personal and professional goals

Unlock access to hundreds of expert online courses and degrees from top universities and educators to gain accredited qualifications and professional CV-building certificates.

Join over 18 million learners to launch, switch or build upon your career, all at your own pace, across a wide range of topic areas.

Start Learning now