Connector Overview & Benefits
The DiliTrust CLM Connector enables seamless integration between Microsoft Dynamics 365 CRM and the DiliTrust CLM platform. From within Dynamics, users can initiate, validate, and send contracts for signature directly, accelerating the contract lifecycle while maintaining full traceability.
Key Benefits:
Trigger contract creation from Opportunity or Quote entities
Automatically map CRM data to CLM templates
Launch validation and signature workflows directly from Dynamics
Maintain a single source of truth for all contract-related actions
Reduce manual data entry and streamline compliance
Use Cases, Prerequisites & Limitations
Typical Scenarios:
Sales reps request pre-filled contract templates from an Opportunity
Legal team sets up workflows for validation and e-signature
CRM users track contract status within the familiar Dynamics UI
Prerequisites:
Microsoft Dynamics 365 (Online), version 9.0+
Power Platform environment with Dataverse enabled
Admin access to Dynamics 365 and DiliTrust CLM
Valid DiliTrust CLM tokens (Access and Refresh)
App Registration with client secret (Azure AD)
Known Limitations:
Only one related record considered in N:1 relationships
Validation workflows in CLM are triggered in sequence; first defined flow is executed if multiple are present
Contracts require at least one configured signatory to initiate signature workflow
Installation Guide
Step 1 – Deploy via Partner Center (for Microsoft certified distribution):
Upload your Connector package zip
Fill in supported countries, privacy policy, and license terms
Add a direct support URL (see support section below)
Step 2 – Import into Dynamics 365:
Import the provided solution (.zip) into your Dynamics environment
Configure required environment variables:
Dilitrust_account_rootfolder
: Folder ID in CLMDilitrust_token_rt
/Dilitrust_token_at
: Refresh/Access tokensDilitrust_CLM URL
/Dilitrust_API URL
: Environment endpointsControl visibility of "Request Contract" button in Opportunity/Quote
Step 3 – Configure Webhook for Status Sync:
Locate the "Update contract state" flow in Power Automate
Copy its URL and update
webhook_url
in CLM via API or Postman
Configuration Guide
App Registration (Azure AD):
Register an app to authenticate CRM–CLM communication
Grant appropriate API permissions
Store client ID, tenant ID, and client secret
User Roles in Dynamics:
Dilitrust CLM User
: Can request contractsDilitrust CLM Send to Sign
: Can initiate signatureDilitrust CLM ReadOnly
: View-only accessDilitrust CLM Admin
: Full access to Connector configuration
Contract Templates & Mapping:
Sync templates from CLM (Admin role required)
Map fields via JSON editor (supports nested relatedEntities)
Example Mapping Snippet:
{
"trigger_entity": "opportunity",
"fields": {
"dt0_date_de_signature": "createdon"
},
"fixedFieldMappings": {
"dt0_representant_legal": {
"entity": "systemuser",
"id": "<guid>",
"attribute": "fullname"
}
}
}
Support & Legal
Support Portal: support.dilitrust.com
Privacy Policy: https://www.dilitrust.com/privacy-policy
Terms & Conditions: Separate from privacy policy, required for Microsoft listing
Changelog & Media
Version: 2.0
Release Date: May 6, 2025
Initial public release of Dynamics 365 Connector
Includes support for contract creation, validation, and e-signature flows
Embedded JSON-based mapping for custom templates
Screenshots & Videos: (Include product screenshots or link to walkthrough video hosted on YouTube or Vimeo)
FAQ & Security Notes
Is the data exchanged between Dynamics and CLM secure?
Yes. OAuth2.0 with Azure AD and HTTPS-secured APIs are used for all interactions.
Can I customize the contract templates?
Yes. Admins can synchronize templates from CLM and configure custom data mappings.
What happens if a user lacks one of the roles?
The corresponding UI actions (e.g., "Request Contract") will not be visible or actionable.
How often is data synchronized?
Template sync occurs once daily. Contract statuses are updated via webhook in real-time.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article