Integrating Dynamics 365 with DocuSign and Adobe Acrobat Sign

Quotes, contracts, order confirmations, and work completion forms all end in a signature, and the signature almost always happens in DocuSign or Adobe Acrobat Sign rather than anything Microsoft ships. Both vendors have invested in Dynamics 365 for years, so the integration options are mature. The choice between them is less about capability and more about how deeply you want signing woven into the CRM, and how much you trust a vendor-managed solution in your environment.

Route 1: the vendor's Dynamics 365 app

Both DocuSign and Adobe offer a managed solution from AppSource that installs into Dataverse. Each adds a "send for signature" command to the ribbon on the tables you configure, a status table that tracks envelopes or agreements, and a pane on the record showing who has signed and when. Templates can be pre-mapped to Dynamics 365 fields so the recipient's name, the quote total, and the account address populate without anyone typing. When signing completes, the signed PDF is attached back to the record, typically as a note or, better, to the SharePoint folder if SharePoint document management is enabled.

This is the route most Sales teams should take. It is supported by the vendor, it keeps users inside the form, and it handles the status polling and webhook plumbing for you.

The downsides are real. The managed solution has its own release cadence and occasionally lags a Dynamics 365 wave. It adds tables and a plug-in set to your environment that you did not write. Customising the behaviour beyond what its configuration allows means working around it rather than with it. And licensing is separate: the vendor's e-signature plan plus, in some cases, a specific tier for the CRM connector.

Route 2: Power Automate with the vendor connector

Both vendors have premium Power Automate connectors. A flow triggers on a Dataverse event (quote activated, work order completed), generates or fetches the document, creates the envelope or agreement with the recipients from the record, and a second flow, triggered by the vendor's completion event, retrieves the signed PDF and stores it. Status updates flow back to a custom column.

This route suits organisations that want signing to happen without a user clicking anything (automated order confirmations, renewal contracts) or that need signing on tables and processes the vendor app does not cover, such as Business Central documents or a Power Pages flow. It is also the route when the AppSource solution is not permitted in your environment.

You are now maintaining the integration. Envelope creation, template mapping, error handling, and the completion webhook are yours. See Power Automate connectors for Dynamics 365 for the licensing and limits of premium connectors.

Route 3: the vendor's REST API from code

An Azure Function or a plug-in calling the DocuSign eSignature API or the Adobe Sign API directly. Justified when the document generation is complex (multi-document envelopes, conditional fields, embedded signing inside a portal) or when volume makes flow runs expensive. The APIs are well documented and the SDKs are decent. Most organisations do not need this.

Business Central

Business Central has no first-party e-signature feature. ISV apps on AppSource bridge to both vendors for sales quotes, orders, and purchase documents, and the Power Automate route works for anything you can render as a PDF from a report. For most small businesses the ISV app is the pragmatic choice; for anyone already running flows against Business Central, the connector route avoids another per-user licence.

Where the signed document should live

Not in Dataverse as a note attachment, unless the volume is small. Signed contracts are large PDFs, kept for years, and Dataverse file storage is expensive; see Dataverse storage types. Put them in SharePoint through the standard document integration, or in the vendor's own archive with a link on the record, or in a dedicated document store if the organisation has one. Keep the audit certificate the vendor produces alongside the PDF; that is what a dispute will require.

Document generation is the hidden project

The signature step is easy. Producing the document that gets signed is where the effort goes. Word templates in Dynamics 365 handle simple quotes; see document templates and Word mail merge. Complex contracts with clause libraries and conditional sections need a document generation tool, and that tool's output must be mapped into the vendor's template with signature tabs in the right places. Budget for this separately from the integration.

What breaks in practice

Recipients whose email on the record is stale, so the envelope goes to the wrong person and the status shows "sent" forever. Templates edited in the vendor's portal without updating the field mapping, so merged fields go blank. Completion webhooks blocked by a firewall change or a DLP policy, so documents sign but never come back. Users who send documents from the vendor's own app rather than from Dynamics 365, so the record never knows.

Build a reconciliation: a weekly list of envelopes in "sent" state older than a threshold, and a check that every completed envelope has a stored PDF.

Stability verdict

The vendor apps are mature and stable, with the usual caveat that a managed third-party solution in your environment is a dependency you should track. The Power Automate route is stable when the flows are small and monitored. Neither vendor is going anywhere, and the choice between DocuSign and Adobe should be made on commercial terms and the rest of the organisation's tooling, not on the Dynamics 365 integration, which is comparable for both.