Usage caps
What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
Administer
- Admin Console Overview
- User Management
- Adding users
- Create function-focused users
- Check for users with provisioning errors
- Change Name/Email Address
- Edit a user's group membership
- Edit a user's group membership through the group interface
- Promote a user to an admin role
- User Identity Types and SSO
- Switch User Identity
- Authenticate Users with MS Azure
- Authenticate Users with Google Federation
- Product Profiles
- Login Experience
- Account/Group Settings
- Settings Overview
- Global Settings
- Account tier and ID
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Custom Send Workflows
- Power Automate Workflows
- Library Documents
- Collect form data with agreements
- Limited Document Visibility
- Attach a PDF copy of the signed agreement
- Include a link in the email
- Include an image in the email
- Files attached to email will be named as
- Attach audit reports to documents
- Merge multiple documents into one
- Download individual documents
- Upload a signed document
- Delegation for users in my account
- Allow external recipients to delegate
- Authority to sign
- Authority to send
- Power to add Electronic Seals
- Set a default time zone
- Set a default date format
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- Transaction Footer
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup
- Add logo
- Customize company Hostname/URL
- Add company name
- Post agreement URL redirect
- Signature Preferences
- Well formatted signatures
- Allow recipients to sign by
- Signers can change their name
- Allow recipients to use their saved signature
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Restart agreement workflow
- Decline to sign
- Allow Stamps workflows
- Require signers to provide their Title or Company
- Allow signers to print and place a written signature
- Show messages when e-signing
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Exclude company name and title from participation stamps
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- New report experience
- Classic report settings
- Security Settings
- Single Sign-on settings
- Remember-me settings
- Login password policy
- Login password strength
- Web session duration
- PDF encryption type
- API
- User and group info access
- Allowed IP Ranges
- Account Sharing
- Account sharing permissions
- Agreement sharing controls
- Signer identity verification
- Agreement signing password
- Document password strength
- Block signers by Geolocation
- Phone Authentication
- Knowledge-Based Authentication (KBA)
- Allow page extraction
- Document link expiration
- Upload a client certificate for webhooks/callbacks
- Timestamp
- Send settings
- Show Send page after login
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- CCs
- Recipient Agreement Access
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Message Templates
- Bio-Pharma Settings
- Workflow Integration
- Notarization Settings
- Payments Integration
- Signer Messaging
- SAML Settings
- SAML Configuration
- Install Microsoft Active Directory Federation Service
- Install Okta
- Install OneLogin
- Install Oracle Identity Federation
- SAML Configuration
- Data Governance
- Time Stamp Settings
- External Archive
- Account Languages
- Email Settings
- Migrating from echosign.com to adobesign.com
- Configure Options for Recipients
- Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Download Agreements in Bulk
- Claim your domain
- Report Abuse links
Send, Sign, and Manage Agreements
- Recipient Options
- Cancel an email reminder
- Options on the e-signing page
- Overview of the e-sign page
- Open to read the agreement without fields
- Decline to sign an agreement
- Delegate signing authority
- Restart the agreement
- Download a PDF of the agreement
- View the agreement history
- View the agreement messages
- Convert from an electronic to a written signature
- Convert from a written to an electronic signature
- Navigate the form fields
- Clear the data from the form fields
- E-sign page magnification and navigation
- Change the language used in the agreement tools and information
- Review the Legal Notices
- Adjust Acrobat Sign Cookie Preferences
- Send Agreements
- Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Authoring FAQ
- Sign Agreements
- Manage Agreements
- Manage page overview
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
- More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Audit Report
- Reporting and Data exports
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Transfer ownership of web forms and library templates
- Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
- Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- How to obtain an integration key
Acrobat Sign Developer
- REST APIs
- Webhooks
Support and Troubleshooting
Overview
What is Microsoft Power Automate?
Microsoft Power Automate is a cloud-based workflow engine allowing users to easily automate processes with over 500 applications and services, including standard connectors like MS Dynamics, MS Planner, OneDrive for Business, Box, and Dropbox. For example, a Power Automate flow can trigger when an Acrobat Sign agreement completes successfully and then automatically store that signed agreement in a SharePoint directory.
What is Adobe Acrobat Sign Workflow Automation integrated with Microsoft Power Automate?
Adobe has enabled seamless access to Power Automate workflows right within the Acrobat Sign web interface. With this integration, Power Automate workflow creation, management, and execution capabilities are available right within Acrobat Sign. This creates a seamless, integrated experience for users to create and manage advanced workflows to automate their pre- and post-signing tasks regardless of whether they have existing Power Automate entitlements.
How is this feature different from using Acrobat Sign and Power Automate separately?
While Power Automate is usually an external web-based application that requires a separate entitlement from Microsoft, Acrobat Sign comes seeded with Power Automate entitlements and is activated upon feature enablement, eliminating Power Automate procurement complexities. In other words, with this feature, Acrobat Sign enterprise license holders get access to both standard and premium connectors of Power Automate to develop e-signature workflows.
What are some use cases that can be supported with this feature?
Examples of signature related automation workflows that can be supported include:
- Automating contract creation
- Downloading and saving signed PDFs to cloud storage such as OneDrive, SharePoint, Box, and Google Drive
- Automating conditional approver routing or template selections
- Extracting data and pushing it to downstream systems to trigger downstream processing
- Sending reminders and notifications via different channels such as Microsoft Teams or Slack.
Prerequisites
- An Adobe Acrobat Sign enterprise or business license is required to access the integration.
- A Microsoft Work or School account with an Azure Active Directory is required to enable Microsoft Power Automate.
- Instructions are provided on the enablement page if you don't have such an account.
- Third-party cookies must be enabled in the user's browser settings to access the embedded Power Automate widgets.
- Customers need to have the following allow-list settings in place if they have firewall restrictions: https://docs.microsoft.com/en-us/power-automate/ip-address-configuration
Customers familiar with Power Automate will notice that the process builder and functionality are similar to the Microsoft Power Automate stand-alone experience.
Customers that are not familiar with Power Automate should refer to the official Microsoft documentation for full details:
Beginner level:
- https://learn.microsoft.com/en-us/training/modules/get-started-flows/
- https://learn.microsoft.com/en-us/training/modules/email-power-automate/
- https://learn.microsoft.com/en-us/training/modules/input-parameters/
Intermediate level:
- https://learn.microsoft.com/en-us/training/modules/introduction-expressions/
- https://learn.microsoft.com/en-us/training/modules/use-teams-connector/
- https://learn.microsoft.com/en-us/training/modules/advanced-business-process-flows/
Advanced level:
The full list of learning modules can be found here:
Microsoft Power Automate entitlements that are included with the Adobe Acrobat Sign enterprise license
The Power Automate entitlements in the Acrobat Sign integration provide full use of a library of connectors, such as Premium connectors and Microsoft Dataverse, included as part of your Acrobat Sign enterprise license (limits on excessive use apply).
The Power Automate entitlements (referred to here as Included Entitlement) are activated for your organization by activating the Acrobat Sign Workflow Automation feature. The Included Entitlement is capped at usage limits outlined below and governed by Terms of Included Entitlement. Additional Power Automate entitlements can be procured directly from Microsoft for customers with a higher volume of transactions than the capacity below allows. Existing Power Automate customers can also apply their existing entitlements to automated workflows designed or run from within Acrobat Sign.
Terms of Included Entitlement
- Flow created under the Included Entitlement must have at least one Acrobat Sign connector.
- Adobe may discontinue this feature at any time upon notice to you, in which case you'll have the option of directly procuring entitlements from Microsoft to continue using the Power Automate workflows you have developed using this Included Entitlement.
- Upon renewal of your sales order, Adobe may charge a fee for this feature.
Limits on use capacity
Power Automate flows, Dataverse storage, and API calls per month are subject to the following usage caps. Usage caps are calculated against the Microsoft tenant linked to your Acrobat Sign account. You can procure additional capacity at any time directly from Microsoft.
|
Limit |
---|---|
Number of Flow runs per month |
1,000 |
Number of Flows |
50 |
API calls per month |
10,000 |
Dataverse Storage |
1.5 GB |
Known Issues
- Third-party cookies must be enabled in the user's browser settings.
- Power Automate functionality isn't available through account sharing.
- Flows created in the embedded experience will appear under the Solutions section rather than the My flows section in the Power Automate portal.
- Flows created directly in Power Automate under My Flows section don't appear in the Acrobat Sign integration.
The problem that triggers this error: There are two common issues to be aware of:
- The user has disabled third-party cookies in their browser configuration.
- The user has pop-ups disabled, blocking the Microsoft login pop-up.
How to fix the problem:
- Allow third-party cookies in the browser configuration.
- Allow pop-up the first time the user attempts to load the feature to ensure that the Microsoft login pop-up is available (and completed).
- Authenticating to Microsoft is a one time operation, and users may disable pop-up activity after they have authenticated the first time.
- Authenticating to Microsoft is a one time operation, and users may disable pop-up activity after they have authenticated the first time.
Problem that triggers this error: The flow has been created without an Acrobat Sign connector.
How to fix the problem: All flows must have an Acrobat Sign connector before being saved.
The problem that triggers this error: The user does not have Azure Active Directory (AAD) account.
How to fix the problem: Setup an AAD account using the instructions in Get Started link.
The problem that triggers this error: A transient system error occurred while activating the integration.
How to fix the problem: Try again.
The problem that triggers this error: The tenant corresponding to the Microsoft user account entered is already activated for use with another Acrobat Sign account. A single tenant cannot be mapped to more than one Acrobat Sign account.
How to fix the problem: Work with your Microsoft tenant administrator to identify the Acrobat Sign account mapped to the tenant.
The problem that triggers this error: The user attempting to enable the service is not part of the Microsoft tenant that the Admin has enabled the feature for.
How to fix the problem: Logout from all Microsoft sessions and try again with another Microsoft tenant/user.
The problem that triggers this error: The user is attempting to enable OAuth with a different username thazn was used previously.
How to fix the problem: Logout from all Microsoft sessions and try again with the Microsoft tenant/user that initially configured the service.
The problem that triggers this error: The tenant that the administrator is linking to (via OAuth) is not a School or Work account.
How to fix the problem: Determine if you have a Work or School account with Microsoft, and ensure you are authenticating to that tenant.
The problem that triggers this error: A pop-up blocker in you browser is denying the pop-up inputs form Microsoft.
How to fix the problem: Turn off pop-up blockers for the site in your browser.
The problem that triggers this error: A refresh token for the integration is either expired or has been revoked by the administartor.
How to fix the problem: Refresh the OAuth connection (automatically triggered).
The problem that triggers this error: This is a generic OAuth error triggered outside of the Acrobat Sign environment.
How to fix the problem: Retry the action.
The problem that triggers this error: This is a generic error triggered by the provisioning organization outside of the Acrobat Sign environment.
How to fix the problem: Retry the action.
The problem that triggers this error: This is a generic error message triggered when granting a license to the user flow outside of the Acrobat Sign environment.
How to fix the problem: Retry the action.
The problem that triggers this error: The user has not accepted the Microsoft Terms and Conditions.
How to fix the problem: Accept the Terms and Conditions. (The page to accept the terms and conditions will appear automatically.)
The problem that triggers this error: This is a generic error message triggered when nythinga fails with a miscellaneous error outside of the Acrobat Sign environment.
How to fix the problem: Retry the action.
The problem that triggers this error: Generic error when deprovisioning the integration fails.
How to fix the problem: Retry the action.
The problem that triggers this error: The administrator has not consented to the Microsoft Terms and Conditions and is attempting to connect via OAuth.
How to fix the problem: Accept the Terms and Conditions. (The page to accept the terms and conditions will appear automatically.)
Beginner level:
- https://learn.microsoft.com/en-us/training/modules/get-started-flows/
- https://learn.microsoft.com/en-us/training/modules/email-power-automate/
- https://learn.microsoft.com/en-us/training/modules/input-parameters/
Intermediate level:
- https://learn.microsoft.com/en-us/training/modules/introduction-expressions/
- https://learn.microsoft.com/en-us/training/modules/use-teams-connector/
- https://learn.microsoft.com/en-us/training/modules/advanced-business-process-flows/
Advanced level:
https://learn.microsoft.com/en-us/training/modules/power-automate-architecture/
Troubleshooting:
https://learn.microsoft.com/en-us/power-automate/triggers-troubleshoot?tabs=classic-designer
User can go to https://make.powerautomate.com/support and raise a ticket.
Detailed execution data of each flow is available when you select the flow details from the Acrobat Sign workflows page. Alternatively, you can find the same by navigating to http://powerautomate.com as well. Users will get periodic email notifications if their flows have run errors.
As a best practice, it's recommended to add a co-owner to the flow. This ensures that after the primary user leaves the company, there will be someone to ensure the flow can be managed. You can find more details about flow sharing here: https://learn.microsoft.com/en-us/power-automate/create-team-flows
For team-level flows, you can share the flow with your team using a service account.
Alternatively, if you are a Power Platform administrator, there are several tools to manage scenarios when a flow owner leaves the company. You can find it here: https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/manage-orphan-flow-when-owner-leaves-org.
Power Automate supports a variety of automation scenarios across functions and industries. The best way to leverage Power Automate to enhance productivity within your organization is by catering to your specific needs and business objectives. You can find a variety of best practices for using Power Automate via the following links:
https://learn.microsoft.com/en-us/power-automate/guidance/automation-coe/overview
Also, you can find documentation on several popular scenarios here: (use the left nav)
https://learn.microsoft.com/en-us/power-automate/use-chatgpt-plugin
Maintenance
Usage data is available for consumption for Acrobat Sign Account Administrator using the “View Usage” option under the Acrobat Sign Account Menu-> Workflow Integration tab. Usage data is refreshed monthly, and the hover on “View Usage” displays last month’s usage info. An account administrator is able to view up to 12 months’ usage by downloading the CSV file using the Download option.
This usage information is provided by MSFT based on the usage against the MSFT tenant that the account is linked to. Please visit the Power Platform Admin Center or make.powerautomate.com to get details on your automations.
If you have further questions about usage data, you can reach out to Microsoft support using this process.
Usage information is only reported against the AAD tenant that the account is linked to. If you have multiple Acrobat Sign accounts linked against the same AAD tenant, you'll see this report of consolidated usage across all those accounts. Admins can go to the Power Platform admin portal or Power Automate portal to view which flows are causing high usage. For granular reporting on usage at a user level against your Adobe included entitlements, you can contact your Power Platform Admin or open a support ticket with Microsoft.
Adobe does not resell Power Automate entitlements. If you have a high usage scenario exceeding the fair use limits, you can purchase Power Automate standard licenses for such users or flows, depending on your needs.
(More information on Power Automate per-user or per-flow plans.)
Admins can go to the Power Platform admin portal or Power Automate portal to view which flows are causing high usage.
Future development is planned for Acrobat Sign to generate email alerts when your account is nearing capacity.
Security
Adobe Acrobat Sign is a multi-tenant application that embeds Power Automate workflows within its service. As an embedded solution, all security and governance constructs for Power Platform are applied to this solution:
No data is automatically exchanged between Adobe and Microsoft as part of enabling this integration. This integration is just a seamless way for Adobe users to build workflows without needing to context switch from their Acrobat Sign application. Users are assigned an internal license to enable them to create workflows using premium connectors in the context of Acrobat Sign.
At the end of the month, Microsoft sends consolidated usage data (number of active flows, flow runs etc. at the tenant level) consumed by this integration to Adobe. No personal data or end user identifiable data is exchanged between Adobe and Microsoft as part of this integration. If the Adobe integration is used (within Acrobat Sign or within Power Automate) and the created flow transfers a document from Acrobat Sign to SharePoint or vice-versa, for example, that's a customer-initiated action done via the connector.