When you use your address book to select recipients for an e-mail message or attendees of a meeting in Microsoft Outlook, information from your custom Contacts folder (e.g. `CRM Leads` or `CRM Accounts`) does not appear in the list. Learn how to fix this.

Custom fields are commonly used in SugarCRM to allow handling custom type of data. Simple example is ‘Middle Name’ field that is available in the Exchange and missing in the SugarCRM. Below we are going to demonstrate how to enable middle name synchronization.

Sometimes assigning “Full Access” permissions in Exchange is not possible due to company security policy. So we need a flexible way to set “ApplicationImpersonation” permission for connecting user to cover a specific list of users (synchronized mailboxes) in Exchange.

GrinMark Synchronizer needs just one Office 365 account to connect to Exchange and synchronize data for user's mailboxes. This account does not even need an Office 365 license. The only requirement for the account is ApplicationImpersonation admin role.

GrinMark synchronization server needs a working uninterrupted connection to Office 365 to ensure stable and prompt synchronization of data. By default user passwords expire in Office 365 within 90 days. So you may want to make GrinMark user password to never expire. To achieve the goal follow these steps.

By default Name field of a meeting in Sugar has size limit of 50 characters. When a meeting with long subject is synchronized from Exchange to Sugar - the subject is truncated. This may lead to duplicates in Sugar. Learn how to avoid such an issue.

Sugar and Google Apps Sync

This topic describes the steps needed to resolve an AGSync issue reported as follows:
Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console…