In this article
- Objective
- Readiness checklist
- Steps
Objective
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.
Readiness checklist
Before you begin setup, confirm the following:
- You or a member of your team have reviewed the Overview article
- You or a member of your team have admin access to and experience in your organization’s Azure portal and Microsoft Power Platform
- You or a member of your team are an admin in Coconut (can access Settings)
Steps
Before connecting Microsoft Dynamics with Coconut, you will need to determine whether your organization will use server-to-server authentication and an application user, or user authorized authentication to set up the integration. Coconut recommends using server-to-server authentication. For more information on this approach, please refer to this overview article.
Once decided, please refer to the corresponding section below.
Integrate using server-to-server authentication & an application user
To integrate using this approach, you will need to enable the integration using server-to-server authentication and an application user, associate the application with your organization’s Sales Hub instance, and confirm security role permissions.
If your organization will be integrating using user authorized authentication, please jump ahead to Integrate using user authorized authentication.
Enable the integration using server-to-server authentication & an application user
To connect Dynamics with Coconut using this approach:
- In Coconut, from the navigation menu, click Settings
- From Integrations & API, click CRM
- Click Microsoft Dynamics 365
- Toggle on Use Server to Server Authentication
- Enter the Environment URL for the application that hosts the Sales Hub instance you will be integrating with Coconut
- NOTE: For more info on finding your Environment URL, please refer to Microsoft’s documentation
- Enter the Tenant ID for the application that hosts the Sales Hub instance you will be integrating with Coconut
- NOTE: For more info on finding your Tenant ID, please refer to Microsoft’s documentation
- Click Connect
- A prompt displays requesting that you sign in as an authorized user of the environment that corresponds to the Environment URL and Tenant ID entered in the previous steps
- A follow-up prompt displays once credentials are verified, asking you to consent to an application to access resources associated with the organization corresponding to the Tenant ID provided; click Accept to enable the integration
The integration is enabled and you can access the field mappings and settings areas within Coconut. Next, associate the application used to sign in with your instance of Sales Hub to fully connect the integration.
Associate the application with Sales Hub
To associate the application with your instance of Sales Hub, you will need to access your organization’s Azure portal to retrieve the application ID for the application used to enable the integration.
For details on how to locate an application ID, please refer to Microsoft’s documentation.
Once retrieved, navigate to the admin center in your organization’s Microsoft Power Platform. From the New app user functionality within the platform, you will need to:
- Add the app (hot tip, search for it by App ID and enter the Application ID you retrieved from the Azure portal)
- Ensure the Business Unit label is the environment where your Sales Hub lives
- Ensure the Security Roles align to what you want the application user to have access to
For more information on adding an app, please refer to Microsoft’s documentation.
Confirm Security Role permissions
The following are required permissions for the Security Role in order for a successful Dynamics <> Coconut integration:
Tab | Entity/Row | Privileges | Access | More Info |
Details | Member’s privilege inheritance | Direct user (Basic) access level and Team Privileges | n/a | Please refer to Microsoft's documentation |
Core Records | Activity |
Create (prvCreateActivity) Read (prvReadActivity) Write (prvWriteActivity) Delete (prvDeleteActivity) Append (prvAppendActivity) Append To (prvAppendToActivity) |
Global | Please refer to Microsoft's documentation |
Core Records | Contact |
Read (prvReadContact) Append To (prvAppendToContact) |
Global | Please refer to Microsoft's documentation |
Core Records | Lead |
Create (prvCreateLead) Read (prvReadLead) Write (prvWriteLead) Delete (prvDeleteLead) Append (prvAppendLead) Append To (prvAppendToLead) |
Global | Please refer to Microsoft's documentation |
Core Records | Opportunity |
Create (prvCreateOpportunity) Read (prvReadOpportunity) Write (prvWriteOpportunity) Delete (prvDeleteOpportunity) Append (prvAppendOpportunity) Append To (prvAppendToOpportunity) |
Global | Please refer to Microsoft's documentation |
Core Records | Opportunity Relationship |
Create (prvCreateOpportunityRelationship) Read (prvReadOpportunityRelationship) Write (prvWriteOpportunityRelationship) Delete (prvDeleteOpportunityRelationship) Append (prvAppendOpportunityRelationship) Append To (prvAppendToOpportunityRelationship) |
Global | n/a |
Customization | Entity | Read (prvReadEntity) | Global | Please refer to Microsoft's documentation |
Customization | Field | Read (prvReadField) | Global | Please refer to Microsoft's documentation |
Customization | Relationship | Read (prvReadRelationship) | Global | Please refer to Microsoft's documentation |
Customization |
Web Resource | Read (prvReadWebResource) | Global | Please refer to Microsoft's documentation |
Customization |
System Job | Read (prvReadAsyncOperation) | Global | Please refer to Microsoft's documentation |
Business Management | User | Read (prvReadUser) | Global | n/a |
User Settings | User | Read (prvReadUserSettings) | Global | n/a |
Integrate using user authorized authentication
To integrate using this approach, you will need to enable the integration and confirm security role permissions.
If your organization will be integrating using server-to-server authentication and an application user, please refer to the previous section (Integrate using system-to-system authentication and an application user).
Enable the integration using a specific user
To connect Dynamics with Coconut using this approach:
- In Coconut, from the navigation menu, click Settings
- From Integrations & API, click CRM
- Click Microsoft Dynamics 365
- Enter the Environment URL for the application that hosts the Sales Hub instance you will be integrating with Coconut
- NOTE: For more info on finding your Environment URL, please refer to Microsoft’s documentation
- Enter the Tenant ID for the application that hosts the Sales Hub instance you will be integrating with Coconut
- NOTE: For more info on finding your Tenant ID, please refer to Microsoft’s documentation
- Click Connect
- A prompt displays; click Accept to enable the integration
Confirm Security Role permissions
If your organization uses a user with the system administrator role to connect the integration, the required security role permissions are enabled by default. However, if your organization creates a new user for the purposes of connecting the integration, this user will require a security role with the following permissions applied.
For required security role permissions, please refer to this table.
Confirm matching settings
Once the integration is connected, you can determine how clients in Coconut are matched to existing contacts in Dynamics. You can also determine which field in Dynamics is matched to the staff member in Coconut.
To do this:
- From the navigation menu, click Settings
- From Integrations & API, click CRM
- Click the Settings tab
- Select Use client External ID to identify contacts to set matching settings for clients
- Select the field you want to map to
- Select Use staff External ID to identify users to set matching settings for staff
- Select the field you want to map to
Additional Resources
Please refer to this article for an overview of the integration.
Please refer to this article for creating/updating field mappings between Dynamics and Coconut.
A note on access and visibility
Admin users can access Settings and configure the Dynamics integration.
NOTE: You will require someone at your organization with Microsoft administrator access to fully integrate Dynamics with Coconut.