Private app on requestCRM
Microsoft Dynamics 365 logo

Choosing a Docusign Dynamics 365 integration

For a Docusign Dynamics 365 integration, the Docusign add-in sends envelopes from records, and the Docusign App Center app reads and writes them in Workflow Builder. Fluidlabs builds a private app for your account when the process reaches Business Central.

Docusign publishes and supports the Docusign for Dynamics add-in, the Microsoft Dynamics 365 app on the Docusign App Center and a Power Automate connector. Fluidlabs built none of them.

Docusign + Microsoft Dynamics 365What should Microsoft Dynamics 365 and Docusign do together?An engineer replies within 48 hours with a scoped plan and a fixed price.

Used to reply to you about this request. Nothing else.

Status
Private app on request
Public integrations
By Docusign
Private app hosting
US, EU or both
Fluidlabs security
ISO 27001, GDPR, SOC 2 Type II audit in progress

Which Docusign and Dynamics 365 integration fits your process?

Docusign covers the Dynamics 365 customer engagement apps with an add-in, an App Center app and a Power Automate connector. Most teams on Dynamics 365 Sales can start with one of these. The routes differ in where the agreement starts and in which Dynamics 365 apps they reach.

The line above each card names who publishes that route. Fluidlabs publishes none of the public routes. The last card is the private app we build for one customer.

Published by Docusign

Dynamics 365 apps from Docusign

Docusign publishes an add-in and an App Center app, and its guide describes the two together as the Dynamics 365 connector. Its add-in sends envelopes from records such as opportunities and quotes, and a Dynamics workflow writes signed values back. Its App Center app needs a Docusign IAM plan and adds Read, Writeback and Store Files in Dynamics 365 steps to Docusign Workflow Builder.

Choose it when you run Dynamics 365 Sales or another customer engagement app and the signed data returns to Dynamics 365.

Published by Docusign, Microsoft, Zapier and Make

Power Automate and other connectors

Docusign publishes a connector for Power Automate. A flow on the Dataverse trigger runs when a row changes, and the Docusign connector then creates an envelope from a template or starts a Docusign workflow. Microsoft publishes a Business Central connector for Power Automate, and Zapier and Make each list Docusign and Microsoft Dynamics 365 CRM. Your team maintains the flow.

Choose it when a row change in Dynamics 365 or a record change in Business Central must start the agreement, and your team builds flows in Power Automate.

Built by Fluidlabs for you

A private app for your account

The Docusign add-in serves the Dynamics 365 customer engagement apps. Once the process reaches Business Central, your private app connects it to Docusign, maps fields between two record models and handles retries and errors between the systems. We build it for your account alone, publish it so that only your Docusign accounts can install it, and host it.

Choose it when you want us to run the mapping, retries and monitoring between Dynamics 365, Docusign and Business Central or another system.

Dynamics 365 apps from DocusignPower Automate and other connectorsA private app for your account
Who publishes itDocusignDocusign publishes the Power Automate connector. Zapier and Make publish their ownFluidlabs builds it for your account
Where it startsSend with Docusign on a record, Start with Docusign under IAM for Sales, a Dynamics workflow or a Workflow Builder start methodIn a flow, from a row change in Dataverse or a Docusign Connect eventFrom the Dynamics 365 event you name, through a webhook and the API
Reads Dynamics 365 data into the agreementYes, through merge fields in the Docusign add-in and the Read from Dynamics 365 step of the Docusign App Center appDepends on the steps of the flowYes, through the Docusign Read step or a query on the Dataverse Web API
Writes signed values back to Dynamics 365Yes, through a Dynamics workflow in the Docusign add-in and the Writeback to Dynamics 365 step of the Docusign App Center appDepends on the steps of the flowYes, through the Docusign Writeback step or the Dataverse Web API
Stores the signed document in Dynamics 365The Docusign add-in attaches signed documents, or SharePoint stores them. The Store Files in Dynamics 365 step files them from a workflowDepends on the steps of the flowYes, as a note on the row you name, within your environment's file size limit
Business CentralThe Docusign add-in does not support Business Central. Not stated in the Docusign documentation for the App Center appMicrosoft publishes a Business Central connector for Power Automate, in the Premium class, beside the Docusign connectorYes, through Business Central's REST API and webhook subscriptions
What it needsA paid Docusign plan for the Docusign add-in. A Docusign IAM plan for the Docusign App Center appA Power Automate, Zapier or Make accountA written scope with a fixed price, then a monthly hosting plan

Verified on 27 September 2026. The last column describes what a private app can do once we confirm it against your accounts during scoping.

What each Docusign integration with Dynamics 365 covers

Each note below comes from the publisher's own documentation, in its terms. Docusign lists its add-in under the name Docusign for Dynamics and its App Center app under the name Microsoft Dynamics 365. Microsoft lists the Docusign Power Automate connector under the name Docusign.

  1. Built for the customer engagement apps

    App from Docusign, listed as Docusign for Dynamics

    Docusign for Dynamics 365 supports Sales, Customer Service, Field Service, Project Service Automation and Marketing. Docusign lists Business Central, Finance & Operations, Supply Chain Management, Human Resources and Commerce among the environments it does not support.

  2. Dynamics 365 online, version 8.1 or later

    App from Docusign, listed as Docusign for Dynamics

    The Docusign Dynamics connectors do not support on-premises instances of Microsoft Dynamics 365. The Docusign add-in supports Dynamics 365 version 8.1 or later.

  3. Write-back runs through a Dynamics workflow

    App from Docusign, listed as Docusign for Dynamics

    To update a record after signing, you build a Dynamics workflow that checks the envelope status. The workflow needs one Get Field Value activity for each field, and each tag label must be unique across the recipients of the envelope.

  4. One SharePoint folder for each record

    App from Docusign, listed as Docusign for Dynamics

    A Dynamics record links to a single SharePoint folder. A workflow that runs from a record with more than one SharePoint folder returns an error.

  5. A read takes up to five rules

    App from Docusign, listed as Microsoft Dynamics 365

    A Read from Dynamics 365 step takes up to five rules. To read child records, the workflow reads the account first and then adds Read steps on the child objects.

  6. Lookups and picklists arrive as strings

    App from Docusign, listed as Microsoft Dynamics 365

    Docusign handles Lookup, Customer, Owner, Picklist and Unique Identifier columns as the string type. A Writeback step accepts six date formats, and a time value in the wrong format makes the writeback fail.

  7. Wait 15 minutes before configuring a step

    App from Docusign, listed as Microsoft Dynamics 365

    Docusign tells admins to wait at least 15 minutes after install before they configure a step, while Docusign indexes the Dynamics 365 fields.

  8. The Docusign connector allows 250 calls a minute per connection

    Connector from Docusign, listed as Docusign

    Microsoft lists a throttling limit of 250 API calls per connection every 60 seconds for the Docusign connector. Its Connect triggers need Docusign Connect in the Docusign account, and the account does not have it on by default.

What a private app covers

The apps and the Power Automate connector that Docusign publishes send, read, write back and file for Dynamics 365. They also start workflows: from a record with the Start with Docusign button under IAM for Sales, or from a changed row through a Dataverse flow. A private app covers work between the systems, such as the four jobs below. Each rests on an ability that Microsoft or Docusign documents, and we confirm it against your environment during scoping.

Connect Business Central to Docusign

Business Central runs apart from the customer engagement apps the Docusign add-in serves, and Microsoft's Business Central connector runs in Power Automate. Your private app reads and writes sales orders through Business Central's REST API and renews its webhook subscriptions.

Map signed terms between Dynamics 365 and your ERP

Docusign Connect publishes an event when a workflow completes. Your private app maps the signed values to the row through the Dataverse Web API and to the matching record in your ERP, and retries a write that either system rejects.

Retry writes within Dataverse's limits

Past its service protection limits, Dataverse returns a 429 Too Many Requests error with a Retry-After header. The private app queues each write and sends it again after that interval.

Write workflow failures to the row

Docusign Connect publishes an event when a workflow fails. Your private app writes the failure to a field on the Dynamics 365 row through the Dataverse Web API, and we watch those events as part of running the app.

Microsoft Dynamics 365's API, as we design around it

We took each fact from the vendors' own documentation and listings. The sources list at the foot of this page links each one.

Verified on 27 September 2026.

Authentication
Client applications use OAuth 2.0 to reach the Dataverse Web API, and Microsoft Entra ID is the identity provider. You register the application in your Microsoft Entra ID tenant first. A server-to-server application proves its identity with a client secret or a certificate.
Webhooks
Dataverse sends server events to an external web application through webhooks, as POST requests with a JSON payload. A webhook step runs in synchronous or asynchronous mode, and the timeout is 60 seconds. Microsoft names Azure Service Bus as the option for high scale processing.
API limits
Dataverse applies service protection limits per user, and each web server enforces them. The defaults are 6,000 requests and 20 minutes of combined execution time within a five-minute sliding window, and 52 or more concurrent requests. Past a limit, the Web API returns a 429 Too Many Requests error with a Retry-After header.
Test environment
A sandbox environment is any non-production environment of Microsoft Dataverse. Microsoft describes it as the place to develop and test application changes, isolated from production.
Marketplace listing
Microsoft Marketplace. A publisher lists a Dynamics 365 Customer Engagement offer under the offer type Dynamics 365 apps on Dataverse and Power Apps. An offer must meet the general Microsoft Marketplace certification policies before publication.
API styles
REST, OData 4.0
How a build runs

From the first call to a hosted integration

  1. Scoping call

    Thirty minutes with the engineers. We map the records, the direction of travel and the edge cases.

  2. Written scope

    You get a fixed scope and a fixed price in one document. It quotes hosting and maintenance too.

  3. Build and review

    We build against test accounts. We walk you through the result before anything touches production.

  4. Hosted and monitored

    We run your private app on infrastructure we operate. We version each deploy, so we can roll one back.

What sales and finance teams run on Dynamics 365 and Docusign

Send the contract when a quote changes status

A flow on the Dataverse trigger runs when the quote row changes. The Docusign connector starts the workflow, and the Docusign Read from Dynamics 365 step pulls the account and the amounts into the contract.

Write the contract term and start date to the opportunity

The signer confirms the contract term on the agreement. The Docusign Writeback to Dynamics 365 step puts the term and the start date on the opportunity, and your sales team stops retyping them.

Create the sales order in Business Central when the customer signs

Your private app updates the opportunity in Dynamics 365 Sales and creates the sales order in Business Central with the same values. Finance invoices from that order without asking sales for the signed terms.

Security & compliance

Built to pass your security review

The documents your security team will ask for exist, are current, and are ready to hand over. Terms of service and the privacy policy are published on this site.

ISO/IEC 27001:2022
Certified
SOC 2
In progress

EUR 1M technology and cyber insurance, evidenced on request.

Certification

ISO/IEC 27001:2022 certificate

Independently certified by Swiss Approval, current to May 2027 and verifiable through the issuing body.

Download the certificate (PDF)
Data processing

Standard DPA

GDPR, UK GDPR and Swiss FADP covered, with the EU standard contractual clauses incorporated. Read it now, request the version for signature.

Download the DPA (PDF)
Terms

Service Terms

Licence, support response targets, availability, IP and liability for your use of the extension apps. Personal data stays with the DPA.

Download the Service Terms (PDF)
Security overview

Security & Data Protection Overview

Certifications, hosting and encryption, access control, secure development, monitoring and incident response, in one document for your security assessment.

The Security & Data Protection Overview and the DPA prepared for signature are provided on request: , or email secops@fluidlabs.com.

FAQ

Microsoft Dynamics 365 and Docusign, answered

Does Microsoft Dynamics 365 integrate with Docusign?
Yes. Docusign publishes the Docusign for Dynamics add-in, which sends envelopes from Dynamics 365 records, on Microsoft Marketplace. The Microsoft Dynamics 365 app from Docusign, on the Docusign App Center, adds Read, Writeback and Store Files in Dynamics 365 steps to Docusign Workflow Builder. Microsoft lists the Docusign connector for Power Automate, which starts an envelope or a workflow from a flow.
Does Fluidlabs have a Dynamics 365 app on the Docusign App Center?
No. Docusign publishes and supports the Microsoft Dynamics 365 app on the Docusign App Center. For work between systems, such as mapping signed terms into Business Central, we build a private app for your account. We publish it so that only your Docusign accounts can install it, and we host it. If the apps from Docusign cover your process, use them. We can set them up in your account.
Does the Docusign add-in work with Business Central or Finance & Operations?
The Docusign add-in supports the customer engagement apps: Sales, Customer Service, Field Service, Project Service Automation and Marketing. Docusign lists Business Central and Finance & Operations among the environments it does not support. A private app can connect Business Central to Docusign through Business Central's REST API and webhook subscriptions, and a flow can do the same through Microsoft's Business Central connector for Power Automate.
Can a change in Dynamics 365 start a Docusign workflow?
Yes. Power Automate runs a flow when a row of a Dataverse table changes, and the Docusign connector for Power Automate has a Start Docusign workflow action. The action takes the workflow, an instance name and variables. Microsoft lists a limit of 250 API calls per connection every 60 seconds for the Docusign connector.
Which Microsoft Dynamics Docusign integration needs a Docusign IAM plan?
The Microsoft Dynamics 365 app from Docusign, on the App Center, needs an IAM plan, and its steps run in Docusign Workflow Builder. The Docusign add-in, Docusign for Dynamics, needs a paid Docusign plan. The Docusign guide describes the two together as the Dynamics 365 connector.
Can a Docusign workflow call another system's API without a custom build?
Yes, when the other system's API fits the step. On qualifying IAM plans, such as IAM Professional and above, Docusign Workflow Builder has a Make a Web Request step, and Docusign installs the HTTP app the step needs. The step sends GET, POST or PUT requests to another system's API. The Docusign guide "Configure a Make a Web Request Step" lists Basic Auth connections, and the Docusign overview, "Connect to Any Service Using Web Requests", also lists OAuth 2.0 client credentials. If your system's API accepts one of those connections and each call is one of those requests, a workflow can call it. We check that on the scoping call. A custom build covers other sign-in methods and request types, and work that runs outside a workflow.
How does Fluidlabs price a custom integration?
We agree a fixed price in a written scope before work starts, then a monthly hosting plan. You see both numbers in the same document. Nothing bills hourly.
Who hosts and maintains what Fluidlabs builds?
Fluidlabs does. The engineers who build a private app or integration run it, monitor it and patch it. You choose the US region, the EU region or both, and your data stays there. Docusign and the other publishers on this page run and support their own public apps. The security and compliance section on this page has our certificate and agreements to download, and a form to request our security overview.

Related pages

Docusign + Microsoft Dynamics 365

Scope your Microsoft Dynamics 365 and Docusign integration

Thirty minutes with an engineer, then a written scope with a fixed price.

Opens a short form here. You stay on this page.

Sources (49)

Each vendor fact on this page comes from one of the pages below.

Microsoft Dynamics 365 and the other product names and logos on this page are trademarks of their owners. Fluidlabs uses them to identify the products. Their use implies no endorsement. Docusign is a trademark of Docusign, Inc. To ask us to remove a mark, email hello@fluidlabs.com.