Private app on requestDocuments and storage
Microsoft SharePoint logo

Choosing a Docusign SharePoint integration

A Docusign SharePoint integration starts with Docusign apps: Docusign for SharePoint sends documents from a library, and the SharePoint app files agreements from Workflow Builder. Fluidlabs builds a private app for your account that writes agreement values to library columns.

Docusign publishes and supports the SharePoint app on the Docusign App Center, Docusign for SharePoint in Microsoft Marketplace and a Power Automate connector. Fluidlabs built none of them.

Docusign + Microsoft SharePointWhat should Microsoft SharePoint 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 SharePoint Docusign integration fits your process?

For most teams, a Docusign integration with SharePoint means one of the apps Docusign publishes. The routes differ in where the agreement starts and in what returns to SharePoint.

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

SharePoint apps from Docusign

Docusign publishes Docusign for SharePoint in Microsoft Marketplace, in an Organization Edition and a Site Edition. You send and sign from a document library, and Docusign for SharePoint saves completed agreements back to SharePoint. The SharePoint app from Docusign on the Docusign App Center adds Store Files and Export Data steps to Docusign Workflow Builder.

Choose it when documents start in a SharePoint library, or a Workflow Builder workflow should file agreements and export their data to SharePoint.

Published by Docusign, Microsoft, Zapier and Make

Power Automate and other connectors

Docusign publishes a connector for Power Automate, and Microsoft's SharePoint connector starts flows on new files and changed list items. A flow then sends an envelope from a template or starts a Docusign workflow. For SharePoint list data, Docusign points you to this route. Zapier and Make each list Docusign and SharePoint, and your team maintains the flow.

Choose it when a SharePoint list or library change must start the agreement and your team builds flows in Power Automate.

Built by Fluidlabs for you

A private app for your account

Your private app adds SharePoint steps your process needs beyond filing and export, such as writing agreement values to library columns or starting from a list change, and it can reach a third system. We build it for your account alone, publish it so that only your Docusign accounts can install it, and host and maintain it, so no flow sits with your team.

Choose it when you want us to build, host and maintain the SharePoint steps, or the process reaches past SharePoint and Docusign into another system.

SharePoint apps from DocusignPower Automate and other connectorsA private app for your account
Who publishes itDocusignDocusign publishes the Power Automate connector. Microsoft publishes the SharePoint connector. Zapier and Make publish their ownFluidlabs builds it for your account
Where it startsFrom a document library, or inside a Workflow Builder workflowIn a flow, from a SharePoint trigger or a Docusign Connect eventFrom the list or library change you name, through a Graph subscription or a SharePoint webhook
Files the signed document in SharePointYes. Docusign for SharePoint saves it back, and the Store Files step files it in the site and folder you chooseYes, through file actions such as Create file in Power Automate or Upload File in ZapierYes, through Microsoft Graph, in the library and folder you name
Writes agreement data to SharePointExport Data writes string-type variables to a CSV or Excel file. Copy metadata copies source column metadata to the signed copyYes, through actions such as Update item and Update file properties in the flowYes, to the list item or file columns you name
Starts from a SharePoint listNot stated for the apps. Docusign states that Docusign for SharePoint does not support SharePoint list data mappingYes, from a SharePoint trigger on a new or changed list itemYes, from a change notification on the list
Bulk sendingDocusign for SharePoint does not support bulk sending from SharePointThe Docusign connector has Bulk send envelope using template and Create bulk send list actionsOne Workflow Builder instance per list row, started through the Workflow Builder API, with each signed copy filed back
What it needsA Docusign eSignature account and admin consent for Docusign for SharePoint. A Docusign IAM plan for the Docusign App Center appA Power Automate, Zapier or Make account, and Docusign Connect for the Connect triggerA 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 SharePoint covers

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

  1. SharePoint list data runs through Power Automate

    App from Docusign, listed as Docusign for SharePoint

    Docusign states that Docusign for SharePoint does not support SharePoint list data mapping, and points to Docusign for Microsoft Power Automate for similar functionality.

  2. Bulk sending from SharePoint

    App from Docusign, listed as Docusign for SharePoint

    Docusign for SharePoint does not support bulk sending from SharePoint. Docusign states that envelopes sent with a bulk recipient will likely not save back to SharePoint.

  3. 32 MB per upload, and Managed Metadata fields

    App from Docusign, listed as Docusign for SharePoint

    Docusign sets a limit of 32 MB per upload to an envelope. Managed Metadata fields do not save back to SharePoint through the Metadata functionality.

  4. Runs in SharePoint's modern experience

    App from Docusign, listed as Docusign for SharePoint

    The Organization Edition and Site Edition connectors do not run in the Classic Experience view of SharePoint. The Require Check Out library setting does not support the Docusign capabilities.

  5. New sites need Docusign for SharePoint added

    App from Docusign, listed as Docusign for SharePoint

    An admin adds Docusign for SharePoint by hand to each new site created after installation. A free 30-day trial account does not support the connector.

  6. Exports string-type variables

    App from Docusign, listed as SharePoint

    The Export Data to SharePoint step exports only string-type workflow variables, to a CSV or MS Excel file that already sits in SharePoint. Column headers must match the field names.

  7. Store Files with an embedded first signer

    App from Docusign, listed as SharePoint

    Docusign tells builders not to use a SharePoint store files step when the first of several signers signs as an embedded signer. The step would archive the document before later participants act.

  8. The Docusign connector allows 250 calls a minute

    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 trigger needs Docusign Connect, which the account does not have on by default.

What a private app covers

The apps and the Power Automate connector that Docusign publishes cover most teams. A private app fits when you want us to build and host the SharePoint steps, or when the process reaches a third system. It does the four jobs below. Each rests on an ability that Microsoft or Docusign documents, and we confirm it against your tenant during scoping.

File the signed copy in the library you name

Docusign for SharePoint saves completed agreements to the library, and the Docusign Store Files step files them from a workflow. Outside both, your private app uploads the PDF through Microsoft Graph, with an upload session for files over 250 MB.

Write agreement values to library columns

Your private app updates existing library columns with a PATCH request on the item's fields. It changes the columns you name, such as the renewal date and the contract value, and leaves the other values alone.

Start from a list or library change

A Microsoft Graph subscription or a SharePoint webhook sends your private app a notification once a list changes. The private app reads the new items and starts the Workflow Builder workflow through its API.

Reach only the sites you assign

Your private app asks for Sites.Selected or Lists.SelectedOperations.Selected, which limit it to the site collections or lists that your admin or the resource's owner assigns. Docusign for SharePoint's Site Edition also limits Docusign to the site collections you select.

Microsoft SharePoint'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
An app registers in Microsoft Entra ID and proves its identity with a client secret, a certificate or a federated identity credential. It calls Microsoft Graph with delegated access for a signed-in user, or under its own identity with no user signed in.
Webhooks
Microsoft Graph sends change notifications for content within a SharePoint list, and a list subscription lasts up to 42,300 minutes before renewal. SharePoint webhooks cover list items in a list or a document library, and a notification carries no change details, so the app calls GetChanges.
API limits
SharePoint Online meters each app in each tenant in resource units, from 1,250 a minute and 1,200,000 a day for tenants with up to 1,000 licenses. A throttled request returns HTTP 429 or 503 with a Retry-After header.
Test environment
Eligible members of the Microsoft 365 Developer Program request a Microsoft 365 E5 developer subscription as a sandbox, separate from production. Visual Studio Professional or Enterprise subscribers qualify, among other paths.
Marketplace listing
Microsoft Marketplace. Microsoft stopped accepting new SharePoint Add-Ins for submission on 1 March 2024. A SharePoint Framework solution declares its component types in its description, justifies high permission requests and carries full configuration instructions in the Notes for Certification.
API styles
REST
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 legal, HR and procurement teams run on SharePoint and Docusign

File each signed contract in the legal library and log it in a register

The SharePoint app from Docusign covers this one. Its Store Files in SharePoint step files the signed contract in the legal library, and its Export Data to SharePoint step adds the envelope data to an Excel register.

Start the NDA when a request lands in the legal intake list

A new item in the intake list starts the NDA workflow, through a Power Automate flow with the Docusign connector or through your private app, which subscribes to changes in the list. The counterparty's name and company come from the item.

Write the renewal date to the contract's library columns

The signer confirms the term on the agreement. Your private app writes the renewal date and the contract value to the signed file's columns, and procurement filters the library by renewal month.

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 SharePoint and Docusign, answered

Does Microsoft SharePoint integrate with Docusign?
Yes. Docusign publishes Docusign for SharePoint in Microsoft Marketplace. With it, you send and sign documents from a SharePoint document library, and it saves completed agreements back. The SharePoint app from Docusign on the Docusign App Center adds Store Files in SharePoint and Export Data to SharePoint steps to Docusign Workflow Builder.
Does Fluidlabs have a SharePoint app on the Docusign App Center?
No. Docusign publishes and supports the SharePoint app on the Docusign App Center. We build a private app for your account that adds SharePoint steps, such as writing agreement values to library columns, and we host and maintain it. We publish it so that only your Docusign accounts can install it. If the apps from Docusign cover your process, use them. We can set them up in your account.
Which edition of Docusign for SharePoint do I need?
The Organization Edition installs at the tenant level, and a tenant admin consents to access across all site collections. The Site Edition installs at the site level, with access to selected site collections. Docusign does not recommend installing both, and it recommends the Organization Edition if you are moving from its legacy Docusign for SharePoint Online connector.
Can Docusign for SharePoint fill an envelope from a SharePoint list?
No. Docusign states that Docusign for SharePoint does not support SharePoint list data mapping, and points to Docusign for Microsoft Power Automate for similar functionality. In Power Automate, a SharePoint trigger on a new or changed list item starts the flow, and the Docusign Power Automate connector sends the envelope or starts the workflow.
Can a new file in a SharePoint library start a Docusign workflow?
Yes, through Power Automate. Microsoft's SharePoint connector starts a flow once a file lands in a library, and the Docusign connector has a Start Docusign workflow action. Microsoft lists a limit of 250 API calls per connection every 60 seconds for the Docusign connector, and your team maintains the flow.
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 SharePoint

Scope your Microsoft SharePoint 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 (39)

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

Microsoft SharePoint 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.