web

You’re offline. This is a read only version of the page.

News and Announcements icon

Dynamics 365 CommunityForums Microsoft Dynamics 365 | Integration, Dataverse... Syncing emails to an o...

Microsoft Dynamics 365 | Integration, Dataverse...

Answered

Syncing emails to an on prem Dynamics 2016 instance

(1) Share

Report

Report

Posted on by CU20070103-0

4

Hi there

A client of mine has an on prem 2016 instance of Dynamics and was using an email synchronisation feature to import emails from O365, at which point additional Dynamics workflows were run.

A recent update has now stopped this from working

I was thinking I could use an Azure logic app to pull the emails from Office 365, and then hopefully make an API call into the Dynamics instance to push the email into Dynamics.

Does anyone know if this is possible, and if it is, which endpoint I should be looking at using?

Note that it is an OnPrem instance of Dynamics that my client is using. They still need the workflows that were working with the email sync feature to work, so hopefully they still do when using the API's directly?

Sorry if this is a dumb or obvious question. I know very little about Dynamics.

Cheers

Steve

Categories:

Dynamics 365 general

I have the same question (0)

All responses Img

All responses (1)

Answers Img

Answers (1)

Verified answer

DAnny3211 11,417 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi Steve,

Yes, it’s definitely possible to use an Azure Logic App to pull emails from Office 365 and push them into an on-prem Dynamics 2016 instance, but there are a few key things to consider:

1. Accessing Dynamics 2016 On-Prem

Since it’s an on-premises deployment, you’ll need to expose the Dynamics Web API or Organization Service externally (securely) so that Logic Apps can reach it. This typically involves:

Setting up IFD (Internet-Facing Deployment) or

Using a gateway or Azure Hybrid Connection to securely tunnel requests.

2. Which Endpoint to Use

For Dynamics 2016, you’ll likely be using the SOAP-based Organization Service (/XRMServices/2011/Organization.svc) or the Web API (/api/data/v8.0/).
To create an email activity, you’d POST to the Email entity and associate it with the relevant records (e.g., Contact, Case, etc.).

3. Triggering Workflows

If your workflows are set to trigger on email creation or regarding record updates, they should still work as long as the email is created via the API with the correct metadata (e.g., RegardingObjectId, DirectionCode, etc.).

4. Authentication

You’ll need to authenticate against the on-prem instance. If using IFD, this typically involves OAuth with ADFS or legacy authentication depending on your setup.

5. Alternative Approach

If Logic Apps becomes too complex due to network/security constraints, consider using Power Automate Desktop or a custom middleware hosted on-prem to bridge the gap between O365 and Dynamics.

Let me know if you need help with the API payload or setting up the connection!

Best regards,
Daniel

Was this reply helpful? Yes No

Join the conversation

Helpful resources

Quick Links

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1

#2

ManoVerse 58 Super User 2026 Season 1

#3

Last 30 days Overall leaderboard

Featured topics

Welcome to the Microsoft Dynamics 365 forum!

Identifying an Org as CDS or Dynamics

Get batch job history log from D365 FO to Power Automate

Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans