User Guide Cancel

Adobe Acrobat Sign for Microsoft Dynamics 365 Online: Installation Guide

  1. Adobe Acrobat Sign Integrations
  2. What's New
  3. Product Versions and Lifecycle
  4. Acrobat Sign for Salesforce
    1. Installation Guide
    2. User Guide
    3. Developer Guide
    4. Advanced Customization Guide
    5. Field Mapping and Templates Guide
    6. Process Builder Guide
    7. Document Builder Guide
    8. Upgrade Guide
    9. Release Notes
    10. Troubleshooting Guide
    11. Additional Articles
  5. Acrobat Sign for Microsoft
    1. Acrobat Sign for Microsoft 365
      1. Installation Guide
    2. Acrobat Sign for Outlook
      1. User Guide
    3. Acrobat Sign for Word/PowerPoint
      1. User Guide
    4. Acrobat Sign for Teams
      1. User Guide
      2. Release Notes
      3. Microsoft Teams Approvals
    5. Acrobat Sign for Microsoft PowerApps and Power Automate
      1. User Guide
      2. Release Notes
    6. Acrobat Sign Connector for Microsoft Search
      1. User Guide
    7. Acrobat Sign for Microsoft Dynamics 
      1. Overview
      2. Dynamics Online: Installation Guide 
      3. Dynamics Online: User Guide 
      4. Dynamics On-Prem: Installation Guide 
      5. Dynamics On-Prem: User Guide
      6. Dynamics Workflow Guide
      7. Dynamics 365 for Talent
      8. Upgrade Guide
      9. Release Notes
    8. Acrobat Sign for Microsoft SharePoint 
      1. Overview
      2. SharePoint On-Prem: Installation Guide
      3. SharePoint On-Prem: Template Mapping Guide
      4. SharePoint On-Prem: User Guide
      5. SharePoint On-Prem: Release Notes
      6. SharePoint Online: Installation Guide
      7. SharePoint Online: Template Mapping Guide
      8. SharePoint Online: User Guide
      9. SharePoint Online: Web Form Mapping Guide
      10. SharePoint Online: Release Notes
  6. Acrobat Sign for ServiceNow
    1. Overview
    2. Installation Guide
    3. Release Notes
  7. Acrobat Sign for HR ServiceNow
    1. Installation Guide
  8. Acrobat Sign for SAP SuccessFactors
    1. Cockpit Installation Guide
    2. Recruiting Installation Guide
    3. Recruiting User Guide
    4. Cloud Foundry Installation Guide
  9. Acrobat Sign for Workday
    1. Installation Guide
    2. Quick Start Guide
    3. Configuration Tutorial
  10. Acrobat Sign for NetSuite
    1. Installation Guide
    2. Release Notes
  11. Acrobat Sign for SugarCRM
  12. Acrobat Sign for VeevaVault
    1. Installation Guide
    2. User Guide
  13. Acrobat Sign for Coupa BSM Suite
    1. Installation Guide
  14. Acrobat Sign Developer Documentation
    1. Overview
    2. Webhooks
    3. Text Tags


Acrobat Sign offers a plug-and-play integration solution with Microsoft Dynamics CRM that provides the following benefits:

  • Accelerates the quote-to-cash process by sending agreements, such as contracts and sales documents.
  • Automatically merges data from Dynamics entities (such as accounts and contacts) into agreements and pushes data gathered from signers during the signing process back to Dynamics.
  • Enables mobile functionality via the Sales Hub. This functionality is available only for installations on Dynamics 365 9.x and later.
  • Allows recipients to easily sign anywhere, anytime, and from any device.
  • Allow senders to track documents sent out for signature from within Dynamics.
  • Eliminates manual steps across the entire process.

Adobe Acrobat Sign for Microsoft Dynamics 365 online: Installation Guide provides instructions on how to:

Additional resources

To upgrade your already installed Adobe Acrobat Sign for Microsoft Dynamics 365 package to the latest version, refer to the Upgrade Guide.

Contact customer support if you've any questions or concerns regarding the installation process.


To be able to successfully install and use Acrobat Sign for Microsoft Dynamics 365, you must ensure that:

  • The required Language Packs are installed into Dynamics 365.
  • The user has a licensed enterprise-level Acrobat Sign account or an enterprise-level trial account.
    The email address of the Acrobat Sign admin must be the same as the one for installing Dynamics CRM admin. If a group-level admin creates an integration key, the users must have a membership to that admin’s Primary group to be able to access the application.  
  • All the possible user domains are included. Do not include public domains such as,, and others.
  • You must obtain a list of all users in the Acrobat Sign system using your owned domains and request valid users to be moved into your CRM-linked Acrobat Sign account. 
    Note: All the user email addresses must match the primary email of the CRM user. Else, you must Change the Acrobat Sign email value.
  • Acrobat Sign Users and Administrators are assigned with read /write CRM Cal Licensing within the Dynamics environment.
  • The file upload size limit is configurable in CRM (the default value is 5 MB). Users get an error if they try to attach a file larger than the configured value. If the signed PDF is larger than the configured value, Dynamics prevents the file from attaching to the parent (or mapped) entity.

Supported browsers

  • Chrome - current version
  • Firefox - current version
  • Safari - current version
  • Edge - current version

Edge browsers

For Microsoft Dynamics to work seamlessly in the Microsoft Edge browser you must trust the below sites in your browser security configuration:

  • https://*
  • https://*
  • https://*
  • https://*
  • If using a third-party identity management system, that URL needs to be added as well

Install Adobe Acrobat Sign for Microsoft Dynamics 365 Online

  1. Go to the Microsoft AppSource page for Adobe Acrobat Sign for Microsoft Dynamics 365 package and select Get it now.


  2. On the Confirm your details dialog that appears, verify your user details and review permission details. Once done, select Get it now.


  3. On the Install Adobe Acrobat Sign for Microsoft Dynamics 365 dialog that opens:

    1. From the 'Select an environment' dropdown, select the appropriate environment where you want to install Acrobat Sign.
    2. Select the 'I agree to Microsoft’s Legal Terms and Privacy Statement' checkbox.
    3. Select the 'I agree to the Privacy Statement and Legal Terms for importing packages into Dynamics 365' checkbox.
    4. Select Install.

    If a previous Adobe Acrobat Sign for Dynamics package is already installed, then the package gets upgraded to the new version.


  4. On the Power Platform admin center page that opens, verify the progress of the installation. It may take about 30 minutes. Refresh the page to update the status.


Configure Acrobat Sign for Microsoft Dynamics 365

After installing the Acrobat Sign for Microsoft Dynamics 365 package, you must implement the following configuration settings:

When you install Acrobat Sign for Microsoft Dynamics 365 online for the first time, you must generate an Integration key in Acrobat Sign and enter it into Dynamics 365 online environment. The integration key is the access token that authenticates the Acrobat Sign and Dynamics environments to trust each other and share content.

To generate an Integration Key in Acrobat Sign:

  1. Log in to Microsoft Dynamics 365 using your admin account credentials.
    You admin account in Acrobat Sign holds the Integration Key.

  2. Navigate to Adobe Acrobat Sign > Home.

  3. From under the Integration Key field, select Go to Adobe Sign to generate integration key.

  4. On the Acrobat Sign log-in page, log in using your admin credentials. 

    Your admin account email should be the same email address as your Dynamics admin.

  5. Navigate to Account > Acrobat Sign API > API Information. Next, select Integration Key.


    If you don't see the Integration Key link on your API Information page, contact Customer Support to modify your account settings to expose this required functionality.


  6. On the Create Integration Key interface:

    • Provide an intuitive name for the key, such as Dynamics CRM.
    • Enable the following elements:
      • user_read
      • user_write
      • user_login
      • agreement_read
      • agreement_write
      • agreement_send
      • library_read
      • library_write
    • Select Save.

  7. On the Access Tokens page that opens:

    1. Select the key that you just created. It exposes the Integration Key link, as shown below.
    2. Select Integration Key.
    3. Copy this key and save it for the following step.
    4. Select OK.


  8. Return to the Dynamics CRM environment and complete the following steps:

    1. Navigate to Adobe Sign > Home.
    2. In the Integration Key field, paste the key that you copied earlier and then select Validate.
  9. O the Acrobat Sign Home page that appears:

    1. Paste your key into the Integration Key field.
    2. Select Validate.
    Once the page refreshes, the integration key is locked (with a green check mark indicating successful installation), and the Validate button changes to Launch Adobe Sign.
    Launch Adobe Sign

  10. Select Launch Adobe Sign.

  11. On the Enable Adobe Sign activity feeds dialog that opens, you may select Enable to enable the Adobe Sign activity feeds.

    You can manually enable or disable activity feeds on the Admin Settings > Configuration page.

    Enable Activity Feeds

You must disable legacy form rendering to use Acrobat Sign. To do this:

  1. On the Dynamics CRM environment, navigate to Settings > Administration and then select System Settings.

  2. On the System Settings dialog, ensure that the Use legacy form rendering setting is set to No. Then, select Ok.

    The System Settings page

Every Dynamics user who is expected to use the Acrobat Sign application must have one of the following security roles configured in the Dynamics environment:

  • Acrobat Sign Reader – Allows the user read-only access to Agreement records.
  • Acrobat Sign User – Allows the user to work with Agreements and other application entities. This role permits the user to view only their records and allows User level access to built-in CRM records such as Contacts, Accounts, Leads, Opportunities, Orders, Invoices, and Quotes.
  • Acrobat Sign Administrator – This role includes additional privileges in addition to the Acrobat Sign User role, such as adjusting Global Settings, Data Migration, and allowing visibility over all Agreements throughout the application.

To configure the security roles:

  1. On the Dynamics environment, navigate to Settings > Security.

  2. On the Security page that opens, select Users.

  3. On the Users page that opens:

    1. Select all the users you want to promote to one type of security role.
    2. Select Manage Roles.
    3. From the Manage User Roles dialog that appears, select the checkbox for the desired security role.
    4. Select OK.

The real-time automatic status updates feature uses Acrobat Sign webhooks to trigger a Power Automate flow whenever an agreement status changes.

To enable real-time agreement status updates:

  1. On the Dynamics 365 page, select the app launcher from the top-right corner and select Power Automate to switch to Power Automate.

    Launch Power Automate

  2. Add the Adobe Acrobat Sign connector to your Power Automate list of connectors using the following steps:

    1. From the left panel, select Connectors.
    2. Search for Acrobat Sign and select Adobe Acrobat Sign from the list of available options.

  3. From the left panel, select Templates and then use the search bar to find and add Update Dynamics Agreement record on agreement state change in Adobe Sign.

  4. Authenticate to the following template services:

    • Common Data Service - This is the common data service in Dynamics. Admins can authenticate by selecting the + icon next to the service name.
      You must authenticate with your Dynamics admin user ID if you're not automatically authenticated.
    • Adobe Acrobat Sign - This opens the OAuth authentication to the Adobe Acrobat Sign service. Ensure that you authenticate with the same account-level admin email that was used to create the integration key.

    Once you successfully authenticate to the services, a green checkmark appears next to the authenticated service. Once done, select Continue.

  5. On the template details page that opens:

    1. Under the 'When the state of the agreement changes' section, in the Name field, enter the name of the trigger.
    2. Under the 'Update a record' section, select the correct environment (with Acrobat Sign installed).
    3. Select Save.
    Adobe Sign action

    Update a record action

    Save the flow

Implement custom settings (optional)

You can build templates, map data, and create custom workflows using the tools available on the Acrobat Sign Admin Settings page. 

To access the settings:

  1. Navigate to Adobe Sign > Admin Settings.
  2. On the Admin Settings page, access the required tools under the different tabs as follows:

Account and Setup

It holds the Integration key and checklist for the initial account setup process. You can any time remove the integration key to disconnect the Acrobat Sign services.

The Setup Checklist shows the installation progress as measured by the key configuration points:

  • Link Adobe Sign to Dynamics 365 – Shows a green checkmark when the Integration key is successfully installed.
  • Display Legacy Form Rendering in Dynamics 365 – Shows a green checkmark when Legacy Form Rendering is disabled.
  • Real-time automatic status updates with Power Automate – Shows a green checkmark when real-time updates are configured.


It includes quick links to the most common admin functions and documentation, as well as optional flags for the user experience.

Admin Tools

  • Create new data mapping – Opens the New Data Mapping interface.
  • Create new agreement template – Opens the New Agreement Template interface.
  • Change user access– See how to Manage users section.

Optional Configurations

  • Enable user auto-provisioning – If enabled, new users that are given access to the Adobe Acrobat Sign entity automatically provision a user in the Adobe Acrobat Sign system upon first use.  Provisioning is based on the user's primary email address, not the User Name, and takes place in the background without further action by the user or account administrator.  

Note: New users who are automatically provisioned in Acrobat Sign have a randomized password. Since the integration works as an authenticated application via API, there is no functional problem within the Dynamics environment. However, if the user wants to log in to Acrobat Sign, they must reset their password via the “I forgot my password” link on the Acrobat Sign home page. 

  • Attach signed documents to agreements entity– It pushes a PDF copy of the completed document back into Dynamics, attached to the agreement record (under the Notes section). The authoritative original document is maintained on the Acrobat Sign servers.
  • Attach combined audit trail with signed agreement – When you enable this configuration, the Acrobat Sign audit trail PDF is attached to the agreement record (under the Notes section) once the agreement is signed and completed. The audit trail explicitly enumerates the events (viewed, signed, and delegated) of the agreement, the timeline of those events, and the IP address where the events were enacted.
  • Attach audit trail - When enabled, the Audit report is attached to the agreement record (under the Notes section) as a discrete file.
  • Display document preview images – It attaches an image of the signed or completed document to the record for easy viewing without having to download and open a PDF file. The image is installed at the very bottom of the agreement record.
  • Enable activity feeds on Adobe agreement entity - When checked, activity feeds are enabled for the agreement entity.
Configuration tab

You can configure any authentication method that you want to enable for users in your Acrobat Sign account. To do so:  

  1. Log in to your Acrobat Sign account using your admin credentials.
  2. Navigate to Account > Account Settings > Send Settings > Identity Authentication Methods.

Learn more about Acrobat Sign authentication methods.

Configure authentication methods

If your work process requires you to have CFR 21 part 11 compliant signatures, you must configure your Bio-Pharma controls in your Adobe Acrobat Sign account. To do so:

  1. Log in to your Acrobat Sign account using your admin credentials.
  2. Navigate to Account > Account Settings > Bio-Pharma Settings.

You can remove the current Integration Key from your Dynamics environment to break the trust relationship between Dynamics CRM and Adobe Acrobat Sign, thus stopping all new transactions and updates for existing transactions. Once the key is removed, it can be re-applied at any time to resume the interaction between the two systems.

To remove the key:

  1. Navigate Adobe Sign > Admin Settings.
  2. From the top bar, select Remove Key.

You can also revoke the integration key from your Acrobat Sign account. Revoking the key permanently disables the key from usage in Acrobat Sign.

To revoke a key:

  1. Log in to your administrative user for your Adobe Acrobat Sign account.
  2. Navigate to Account > Personal Preferences > Access Tokens.
  3. Select the key definition for the Integration Key you want to revoke. It exposes the Revoke link.
  4. Select Revoke.
  5. When prompted, select Yes.

You can use Data Mapping to:

  • Improve your agreement generation process and ensure that documents have the correct content in the fields by pulling field values directly from Dynamics CRM.
  • Push new content from completed agreements back into Dynamics, allowing valuable updates to your CRM without engaging in manual data manipulation.  

For successful data mapping, you must have pre-built forms with defined field names to allow you to logically relate the CRM field to the Adobe Acrobat Sign form field. 

A simple form is illustrated below.  The fields are defined by the curly bracket pairs on either side (defining the width of the field) and the field name (the string of characters between the curly brackets). 

Example Form Fields

Text tags can include additional arguments beyond the name value, including validations, calculations, and regular expressions.

See how to build forms and improve the quality of data you capture during the signature process.

See how to build forms in PDF format.


The Text Tag Shortening feature can be very useful in form design and field mapping by establishing a convention for the field names that repeat on every document (and saves time by not having to re-create the formal tag). This expressly improves data mapping across multiple forms and builds an anchor for future forms.

To define a Data Mapping Template, you can use one of the two following ways:

  • Via Data Mappings page
    1. Navigate to Adobe Sign > Data Mapping.
    2. On the Data Mappings page, you can review, edit, or delete the existing data maps.
    3. From the upper-right corner, select +New to access the New Data Mapping page.
  • Via Admin Settings page
    1. On the Admin Settings page, select Create New Data Mapping.
    2. Enter an intuitive name for your data map.
    3. You may choose to set this data mapping as the default.
    4. From the Entity drop-down menu, select the CRM Entity.
      This constrains the fields available for mapping to just the defined entity. You can have multiple data maps per Entity. Once the entity value is set, it cannot be changed. Once the Entity value is set, it exposes the Data Mapping tab.
    5. Select Data Mapping to access the field mapping tools.
 the Active Agreement Mapping Templates page

Data Mapping page

Field mapping tools

Relate the Dynamics CRM Data fields to the Acrobat Sign field names

You can create relationships between Dynamics CRM field names and the Acrobat Sign form field names that you've defined. Data mappings are configured based on how the data flows:

  • MAP CRM DATA TO ADOBE ACROBAT SIGN AGREEMENT - Prefills fields on your form using field values associated with the defined Dynamics Entity.
    You can create a “hunt group” of alternate CRM field values seeking to fill the Acrobat Sign form field. Each group member is then tried in order until a non-null value is found and inserted. (See Below)
  • MAP ADOBE ACROBAT SIGN AGREEMENT DATA TO CRM DATA - Populates the empty fields of the Dynamics Entity using form field values obtained through the signing process (once the agreement is completed).
    By default, Acrobat Sign does not push a new value into a CRM field with content.
    You can define the relationship on the data map to override the content protection and replace existing field values with new content from the signed form.

Supported Data Types

  • Adobe Sign data mapping supports the following data types:
  • Text – Text form fields are supported as single line of text in CRM.
  • Boolean (Two Option)– Checkboxes are supported for CRM Boolean fields.
    If drop-down or radio button form fields are used for Boolean CRM fields, the CRM to Acrobat Sign mapping may fail; however, Acrobat Sign to CRM mapping should work.
  • Option Set – Dropdown lists and radio button form fields are supported for CRM Option Set fields

To Relate CRM Data Fields to Acrobat Sign Agreement Fields:

  1. From the Attribute drop-down menu, select the CRM field.
  2. In the Agreement Field box, type the Adobe Sign form field name.
  3. (Optional) Check the Add Reverse Direction Mapping box if you want to also relate these fields mapping from Acrobat Sign to CRM.
  4. (Optional) Check the Override box if you want this template to ignore existing content in the CRM field and force-populate the field with the new content from the Acrobat Sign field.
  5. Select Add.

Once the new field relation is processed, it appears under the configuration settings.  

If you added Reverse direction mapping, you see the new relationship populate under the Acrobat Sign to CRM configuration fields also. 

If you opted to Override the content protection, you see that indicated on the relationship record.

To Relate Acrobat Sign Agreement Fields to CRM Data Fields:

The process for discretely creating a mapping from Adobe to CRM is the same as above except there is no option to Add Reverse Direction Mapping.

To delete mapped relationships

You can delete one or more mapped relationships by:

  1. Select the records to be deleted by selecting the checkmark near the record.
  2. From the top bar, select the More commands icon and then select Delete.
Both data mapping fields exposed

Deleting a relationship

To create Alternate field mapping relationships (Hunt Group)

If you define a field on an Adobe Acrobat Sign form that might be filled by one of several CRM fields, then you can create an ordered list (hunt group) of CRM attributes that will seek to populate the Adobe Acrobat Sign field.

For example, you may have the CRM field First Name mapped to a form field named FName, and then map the CRM field Yomi First Name to that same form field name. The application will first attempt to fill the field with content in the First Name field, and if no content is found, Adobe Acrobat Sign will attempt to use content in the Yomi First Name field.  If no content is found in any element of the hunt group, the field is left empty.

To define the hunt group:

  1. Create a CRM to Adobe Sign relationship between your primary CRM attribute and the Adobe Sign form field name.
  2. Once the first record is in place, change the CRM attribute to the secondary CRM attribute, and add that relationship. 
  3. When prompted, select OK.
  4. Once the record is updated in the system, you see that the records have changed to include a prefix in front of the Entity Attribute:

    # will be in front of the primary/default attribute. This field will always be the first field checked for content. Subsequent relations will be numbered 1-N. The first alternate field relationship is indicated by (1) and will always be the first alternate field checked.  (2) would be the second alternate field, and so on. 

Hunt Group

To add attachments to related Entities

Once an agreement is fully signed and executed, Adobe Acrobat Sign will produce a PDF copy of the document and an audit trail of the signing process.  It is possible to have these documents attached as PDF files to any other CRM Entity that is related to the template’s parent Entity.

In the MAP SIGNED AGREEMENT AND AUDIT TRAIL TO CRM ENTITY section of the template page, you will find three Document Types available via drop-down:

  • Signed PDF – The full text of the signed document. This is a copy of the authoritative original that is maintained on the Acrobat Sign servers.
  • Audit Trail – A full enumeration of all major events (signing, delegation, etc.) and the associated metadata (time/date, IP address, etc.)
  • Combined PDF - Both documents are combined in one PDF and attached

You can attach one or more files to any related Entity, but you must explicitly map them individually.

To map an attachment:

  1. Select the Document Type you want from the drop-down
  2. Select the Entity you want to push the document to, using the Attach to CRM Record drop-down list. Only Entities with a defined relationship to the parent Entity will be listed
  3. Select Add.

Attachment relationships will be listed under the configuration settings.

Entity options drop down

To Delete an Attachment

  1. Select the check mark for the records that you want to delete.
  2. Select the More commands icon and then select Delete.
Deleting a record

As an Acrobat Sign Admin in the Dynamics environment, you have the authority to create agreement templates that can pre-configure a majority of the agreement fields, attach files, and tie that agreement to relevant data mapping.

Templates are tied to a Dynamics entity, and become available for agreements sent from that entity when they are flagged as Active.

Send from Template


Data Maps are at the core of Agreement Templates and should be defined before the Agreement Template is configured. 

Use one of the following ways to configure a new Agreement Template:

Via Agreement Templates

  1. Go to Adobe Acrobat Sign > Agreement Templates.
  2. It loads the Agreement Templates page, which will list all the existing templates for you to review, edit, or delete.
  3. From the upper-right corner, select +New to start a new template.
New Template

Via Admin Settings 

  1. Go to Admin Settings page.
  2. Select Create New Agreement.
  3. On the New Agreement Template page:
    1. Provide an intuitive name for the template, so users will know when to use it
    2. Identify the Entity that the template should be tied to.
      The Entity cannot be changed later. Once the Entity is selected, the template is saved and the full agreement template loads.
New Template

The Agreement Template has four tabs each containing editable values that you can configure:

  • Template Details – Defines the relationship between the major objects and if the template is active.
  • Recipients – Allows for a pre-configured signature path for the template.
  • Agreement Details – Contains the elements of the individual agreement.
  • Related – A listing of related objects.

Template Details

The template details show the Template - Entity - Data Map relationship for this template.

Template details

The name of the template is expressed in large font at the very top

  • Template Name – The name of the template. This is identical to the name expressed at the top of the page
  • Primary Entity – Templates are tied to a single entity within Dynamics. The declared entity is the only entity that will display this template
    • This value is locked once the agreement is created
  • Data Mapping – This field indicates the name of the Data Map that is bound to the template.
  • Active – This check box dictates if the template is available for users to select when sending from the primary entity
  • One-click send – If enabled, the template automatically sends the agreement when the template is selected. 
    • For  example:  You have an NDA template designed with Contact as the primary entity, and the recipient's section is configured to import the Contact’s email.
      • The Sender only needs to select the NDA template from the Contact they intend to send it to. The configuration phase is skipped, and the agreement is sent without further interaction.
      • If no recipient is configured, One-click is ignored, and the agreement opens for manual configuration


The Recipients section contains the list and signing order of recipients that you want to pre-configure for the template.

Recipient list

Recipients – You can hard code a recipient list within a template by clicking the New Recipient icon in the upper-right of the window.  A pop-down opens exposing the configuration options.

  • By default, the recipient list is left empty for the Sender to manually populate when configuring their agreement
  • Adding a default recipient must be done explicitly by clicking New Recipient and then saving the default values presented with Create from primary entity enabled
  • The Override Default Verification option allows you to escape the default verification method (set in the Security section), and apply a different verification method for just this recipient.
Quick Recipient - Override Auth

  • Adding additional recipients (e.g. internal counter-signature process), or recipients that aren’t involved in the signature process, only requires that you uncheck the Create from primary entity box, and then define the recipient. An excellent option for CCing teams that only need to manage the final documents
Additional recipients

Agreement Details

The  Agreement Details section contains four sections:

  • Message Details -The agreement name and the global message that each recipient sees on the "Please Sign" email
  • Attached Files - The files being sent for signature
  • Agreement Options - Options for configuring the agreement
  • Security Options - The option to secure the PDF with a password
Template - Agreement Details

Message Details

  • Agreement Name – The Agreement Name is prominent in the notification process, surfacing in the email subject line, in bold font in the email body, and in smaller font throughout the boilerplate description (seen in yellow highlight below)
  • Message – The Message field is an open plain text field where you can insert any message or instructions to the signer (seen in green highlight below)
Review and sign email


Both the Agreement Name and Message fields permit the insertion of Dynamics field values, to improve personalization for the recipient. To open a list of possible values, type a left brace: {

Attach Files

This section allows you to pre-attach a file for the agreement.  For example, if you create a template for an NDA, then you can attach the company NDA file directly in the template so the sender doesn’t have to.

Template - attach files

Agreement Options:

Template - Agreement options

  • Preview and position signatures before sending – When checked, the agreement automatically opens the authoring environment so the sender can place form fields
  • Agreement expires – If checked, the agreement defines a termination date when the agreement expires
    • Days until agreement expires – This defines the number of days the agreement remains signable when the Agreement expires feature is enabled
  • Add post-signing landing page – When enabled, you can dictate what URL the recipient is routed to after they complete their interaction with the agreement
    • Post-signing landing page – This field contains the URL for the page you want to direct recipients to when Add post-signing landing page is enabled
    • Delay in seconds for redirect - Define how many seconds the redirect waits until routing the recipient to your landing page
  • Require In-person signing – If you need to have the signer sign on the sender’s local system or tablet without involving email, senders can host the signature using this option
  • Require My Signature – Used when the sender will be part of the signature process
    • The sender must sign first, last, or be the only signer
    • The signing order will be Order Entered
  • Signing Order – Choose between two workflows for getting your document signed
    • Any Order notifies all signers at one time and allows them to sign without waiting on anyone else
    • Order Entered enforces a strict sequential signature process based on the order you define the signers on the agreement
  • Signature Type – Choose the format in which you want the document signed
    • ESIGN routes your agreements to be signed electronically using email and expects the recipients to sign electronically
    • WRITTEN delivers your documents via email, prompting the signer to print the document and physically sign it. Then they must upload the document back to Acrobat Sign system using the same email link
  • Schedule recipient reminders  Defines a reminder cycle for the transaction.  Reminders can be configured to be sent to the current recipient on a daily or weekly cycle
  • Signing Language – This setting defines the language used when the agreement is sent to the signer.  The emails and on-screen instructions for the signer are in the language chosen.

Security Options

This section defines the default verification method for the recipients, and the optional password for the final PDF document

Template - Security options

  • Set password to open signed PDF – Enable this if you would like to apply a password to the final document to prevent un-authenticated access
  • Identity Verification  Defines the second-factor verification to authenticate the recipient
    • Email – No second-factor verification is applied
    • Password – Standard alphanumeric password field. When used, the sender must communicate the password to the signer out of band
    • Knowledge base  – Knowledge base authentication uses public databases to ask the signer several questions about their past to verify their identity
    • Web Identity - Social media is used to apply a second authentication

Acrobat Sign for the Sales Hub, Customer Service Hub, and Field Services

If your company has deployed Adobe Acrobat Sign for Dynamics version 9.2 or later, you have access to the Adobe Acrobat Sign functionality on the Dynamics Sales Hub, Customer Service Hub, and Field Services.

These Hubs offers the same functionality with improved formatting, allowing direct access for phones, tablets, and any other mobile device.

The Sales Hub Dashboard gives you a quick graphical report of the agreements associated to your user.

The reports allow you to drill down in to each element and produce new graphs specific to that sub-set of data.

The page is broken out into three default sections:

  • Agreements by status
  • Agreement status by month
  • Agreements sent out this week 
Sales hub - Dashboard

The Agreements section gives you a full listing of your agreements as well as the ability to sort the Agreements by their meta-data (status, creation date, signed date, etc).

It is also possible to create a new Agreement as needed.

Sales Hub - Agreements

Users that have access to Data Mappings can sort, review, and edit existing Data Mappings.

New Data Maps can also be created.

Sales Hub - Data Mapping

Users that have the system authority to access Templates can review, sort and edit existing templates.

New Agreement Templates can also be created.

Sales hub - Agreement templates

Dynamics Administrators can access and edit the admin-level settings for the Adobe Acrobat Sign integration.

Sales hub - Admin Settings

Add Custom CRM Entities to Acrobat Sign

Several built-in CRM entities are included in the Adobe Acrobat Sign package that you can relate your agreements to:

  • Contacts
  • Accounts
  • Leads
  • Opportunities
  • Quotes
  • Invoices
  • Orders
  • Contracts

You can add your custom CRM entity (or any other built-in CRM entity) to this scope by following a few steps.


Custom entities can only start an agreement from the Request Signatures menu item.

You cannot use the Quick Create system to start an agreement from a custom entity.

For our example, let’s assume there is a custom CRM entity called “Customer”.

  • Navigate to Settings > Customization
Navigate to Main > Settings > Customization

The Customization page loads

  • Click the Customize the System option
The Customization page

The Default Solution page opens in a separate window

In the left side rail under Components

  • Expand the Entities list
  • Find the custom entity (“Customer” in this case) and expand it
  • Single click the name of the Entity to display the fields and controls
The Default Solution page

  • Copy the value from the Name field (in this example the value is “new_customer”). 
    • This is the internal system name of your custom Entity.
  • Navigate to the 1:N Relationships option, under your custom Entity
    • Click the New 1-to-Many Relationship button.
 the 1:N Relationships option

A new Relationship window opens

Create the new relationship:

  1. Choose Agreement from the Related Entity field
    • The Name field changes to show {entityName}_adobe_agreement 

     2. Paste the name of your custom entity (“new_customer” in our example) into the Display Name field.

  • The Name field changes its value to be “new_” + {entityName} + “Id”. (new_new_customerID)

    3. Click Save and Close

  • The Relationship window closes
  • Click Publish All Customizations at the top of the 1:N Relationships page
Publish All Customizations at the top of the 1:N Relationships page

Adobe logo

Sign in to your account