Server-side synchronization is the preferred option for organizations with users who run customer engagement apps (Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Dynamics 365 Project Service Automation) in a web browser or on a mobile device, such as a tablet or smartphone. Server-side synchronization provides direct apps-to-email server synchronization. When you use Exchange, this includes bidirectional synchronization of email, contacts, tasks, and appointments. The data synchronized for each user can be controlled by using synchronization filters that are available on the Synchronization tab in the user options dialog box.
If you use a POP3 email server, the data that is synchronized includes email only.
Using server-side synchronization makes messaging data available to a web browser, tablet, or smartphone that's running customer engagement apps. More information: Server-side synchronization of email, appointments, contacts, and tasks
A user can only map to a single Exchange or POP3 mailbox. Similarly, an Exchange or POP3 mailbox can only be mapped to a single user. When customer engagement apps detect that an Exchange or POP3 mailbox has already been mapped to a user, a dialog box is displayed to present a choice to the user whether to map the user to the Exchange mailbox. When the user selects Yes, it breaks the previous user-to-Exchange-mailbox mapping and, subsequently, the synchronization that would occur between the user and the Exchange mailbox.
Server-side synchronization frequency
Server-side synchronization runs on a schedule for each mailbox and has different synchronization delays based on the workload processed. Available workloads are incoming emails, outgoing emails, and appointments, contacts, and tasks synchronization.
After a mailbox has been successfully tested and enabled, server-side synchronization will start processing for the configured workloads continuously. When workload processing starts, server-side synchronization will interact with your mailbox on the external email service provider, and also with your data in the environment. These interactions can take time based on the responsiveness of the email service provider, the number of items being synchronized, connection throttling, the amount of data exchanged, and the number of attachments. Furthermore, these interactions can take additional time based on the active customizations deployed to Dynamics 365.
Because the next scheduled synchronization time for a given workload is calculated at the end of its processing cycle, this means that a prolonged synchronization cycle for a workload might affect the overall throughput of a mailbox. As such, there is no defined SLA for the duration of a synchronization cycle because it's directly influenced by the external factors mentioned previously.
Incoming sync frequency
After an incoming sync cycle is completed, a mailbox will postpone the processing of incoming emails for five minutes. This means the mailbox will be ready for processing again in five minutes.
Having long-running synchronous customizations (plug-ins and workflows) in the email delivery flow can lead to lower throughput. Moving these customizations to async execution can improve throughput.
Outgoing sync frequency
Server-side synchronization scans your environment for outgoing email messages that are in a "Pending Send" status and have been sent by using the Send SDK request. It updates the status on outgoing email messages as "Pending Send" for the active mailbox at a frequency of every five minutes and submits these email messages to the configured email service provider.
Generating a massive amount of outgoing email messages in Dynamics 365 that exceeds your email service capacity can cause a backlog and a delay of new email messages from the same mailbox.
Before creating bulk outgoing email messages, review your email service throttling limits:
Appointments, contacts, and tasks sync frequency
After a sync cycle is completed for appointments, contacts, and tasks, a mailbox will be postponed for processing for 5 to 12 minutes after the synchronization. This means that the mailbox will be ready for processing again in 5 to 12 minutes, based on how active the mailbox has been in the last sync cycles.
If the mailbox is enabled for appointments, contacts, and tasks and incoming email as well, the postpone time will be from 5 to 15 minutes.
Features available with server-side synchronization
Some features offered by server-side synchronization include the following:
Sent Items folder: If your server version is 9.1.0000.16819 or later, email messages sent from Dynamics 365 apps by using a server-side synchronization–enabled Exchange mailbox will be visible in the Sent Items folder in the Exchange sender's mailbox. To determine your version, sign in, and in the upper-right corner of the screen, select Settings > About.
Note: This functionality can be disabled by toggling the SSSSaveOutgoingEmailToExchangeSentFolder OrgDbOrgSetting to false.
Email folder tracking: You can simply drag email to a folder to track it. Folder tracking works on any mobile device that supports Microsoft Exchange, which means you can track email from just about any device.
Doesn't require Outlook: You don't have to have the Dynamics 365 for Outlook add-in open to synchronize records. You can still use Dynamics 365 for Outlook to track records manually even if you do server-side synchronization. This also helps to boost the performance of the Outlook add-in.
Support for Dynamics 365 App for Outlook: You can track incoming email with the new Dynamics 365 App for Outlook. Dynamics 365 App for Outlook works with Outlook on the web, so all you need is a browser to track incoming email.
Features available with server-side synchronization in both customer engagement apps and Customer Engagement (on-premises)
Some features offered by server-side synchronization include the following:
Efficient resource utilization: Server-side synchronization provides integrated mailbox management. You can disable inactive mailboxes that have permanent errors. It prevents resource hogging by applying an upper limit on the allocated capacity and time-out requests.
Connection throttling: Server-side synchronization provides a way to control the number of parallel connections opened against an email server, to prevent overloading the mail server.
Data migration: Server-side synchronization supports migrating configuration data from the Email Router to server-side synchronization by using the migration wizard.
Service isolation: Server-side synchronization has separate queue-management and configuration settings for asynchronous operations, outgoing activities, and mailboxes. It's based off of asynchronous service architecture and might share the same process. In all cases, it manages server resources while maintaining isolation with the asynchronous service.
Error reporting for users and administrators: Server-side synchronization supports logging and reporting of errors specific to an email or one or more mailboxes. More information: Error logging for server-side synchronization
In customer engagement apps, you can synchronize emails by using Dynamics 365 for Outlook or server-side synchronization. If server-side synchronization is selected, the synchronization doesn't require that you run Dynamics 365 for Outlook. However, you'll still need Dynamics 365 for Outlook to promote an item from Outlook.
Submit and view feedback for