Scenario
When integrating Microsoft Exchange® with Coconut, you have the option to configure your Exchange service account to use either impersonation or delegate permissions. Read on for key aspects of each in relation to Coconut and for links to Microsoft support materials.
Impersonation Permissions
When the Exchange service account is configured with impersonation permissions, it takes on the permission levels of the user or user group it is impersonating to complete an action.
Impersonation permissions:
-
Provide a quicker setup experience, because you can assign impersonation permissions to multiple users at one time
Impersonation permissions can also be limited to a specific group of accounts by creating a management scope
Reduce throttling
Automatically log all impersonation permission activity through IIS or EWS
Ensure service account actions are communicated using TLS 1.2+ encryption
For more information on impersonation and Microsoft Exchange®, please refer to this article.
For more information on configuring impersonation, please refer to this article.
Delegate Permissions
When the Exchange service account is configured with delegate permissions, it is granted the ability to complete actions on behalf of a specified user without adopting the permission levels of that user.
Delegate permissions:
Require additional permission to access calendar items that are controlled by the user
Have a complex setup, because delegate permissions must be applied per user
For more information on configuring delegate permissions, please refer to this article.
NOTE: The above article relates specifically to Microsoft Exchange® 2019. For earlier versions, please refer to Microsoft support materials.
Recommendation
Coconut recommends using the permission type that best meets your organization’s policies and requirements. Once the service account is configured, you can set up the Microsoft Exchange® integration.
To connect Microsoft Exchange® to Coconut using OAuth, please refer to this article.
To connect Microsoft Exchange® to Coconut using Basic Auth/NTLM, please refer to this article.