Integrate Microsoft® Dynamics with Coconut to provide staff members with the ability to sync and view appointments and clients in either application.

NOTE: Microsoft Dynamics is an optional add-on. Please connect with your Customer Success Manager to get started.

The Microsoft Dynamics integration enables users to complete client-related activities in one application and have them sync to the other. As a result, clients need only share their details once, increasing organizational efficiency while also delivering an improved customer experience.

The following info can help provide an understanding of how the integration works and what is required prior to enabling it at your organization. Please review to help prepare before beginning setup.

The Dynamics <> Coconut integration can be connected using server-to-server authentication & an application user or through a specific user. Please see below for more details and links to resources related to server-to-server authentication.

Regardless of the approach your organization takes, setting up the Dynamics integration requires a member of your team that can:

It is possible to leverage server-to-server authentication when setting up the Dynamics integration. Considered to be a more secure approach, this means that authentication is based, not on an existing Microsoft user, but on an application user associated with a service principal. For more information on server-to-server authentication, please refer to Microsoft’s documentation.

A service principal is an identity that can be created in Azure for use in conjunction with applications to access Azure resources. For more information on service principals, please refer to Microsoft’s documentation.

A security role is associated with a service principal and defines what can be accessed at which permission level by the service principal. For more information on security roles, please refer to Microsoft’s documentation.

The following are synced from Coconut to Microsoft Dynamics:

NOTE: If a client is included in an appointment booking and that client is not found in Dynamics, a lead is created in Dynamics to represent that client as part of the sync. If a client is updated in Coconut (for example, the spelling of their name), but that client is already synced in Dynamics as the result of a previous appointment, the update will not be synced to Dynamics.

Please refer to this article for connecting the Microsoft Dynamics integration with Coconut.

Please refer to this article for creating/updating field mappings between Dynamics and Coconut.

Please refer to this article for Quickstart information for your users.