Adobe Acrobat Sign rolls out at least three updates per year, categorized as major or minor releases. Additional minor updates may be introduced as needed to address system or customer issues.

Major Releases bring significant updates, new features, and multiple enhancements.
Minor Releases focus on smaller improvements and user experience tweaks. These occur between major updates, typically one to two times per cycle.

To prevent disruptions, new features are disabled by default and must be manually enabled by an account or group admin.

For Health and Life Sciences customers requiring compliance validation, Acrobat Sign partners with a third-party vendor to provide a validation package for every major release containing features to minimize your risk factor.

Note

This Prerelease Notes page is regularly updated as new information becomes available, so its content is relatively dynamic.

While this page is localized, the process takes time, which may result in localized versions differing slightly from the authoritative US English version.

For the most accurate and up-to-date information, we recommend referring only to the US English page.

The prerelease schedule and notes are listed below.

Adobe Acrobat Sign follows a structured schedule for publishing release notes and documentation updates:

8 Weeks Before Production Release

The prerelease page publishes a summary of expected features and updates, typically four weeks before the Sandbox launch.
Any feature changes after this point are noted in the Errata section.
Resolved issues are not included at this stage.

4 Weeks Before Production Release (Sandbox Launch)

The prerelease page is updated with detailed documentation on new and updated features.
Links to prerelease support documentation (available in US English only) are added as needed.
The initial Resolved issues section is published, with ongoing updates over the next four weeks.

Launch Day

The official release notes are updated with final feature details and links to production support documentation.
The prerelease page is refreshed to highlight the next release cycle.
Documentation is published after release verification in the live system, typically after 7 pm PT, though complex updates may take longer.
The final Resolved issues list is added to the US English release notes, with localized versions updated later.

Government Cloud Release

The Government Cloud environment typically updates between two days and several weeks after the production release, as some features may require additional evaluation before deployment.

Note

Sandbox documentation is designed for the production environment. Links found in the prerelease content target production URLs, meaning those links may lead to older existing documentation or 404 results if the target page is new and hasn't been published yet (e.g., when the link is pointing to a new feature in the same release).

The new pages will be published when the release is published, and links will properly resolve to their production URLs.

Sandbox availability

Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.

The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
The Sandbox environment uses the same status page and outage procedures as the regular Production environment.

Releases

Alert

This article contains prerelease information. Release dates, features, and other information are subject to change without notice.

September 8, 2026 (Major release) v17.2

Adobe Acrobat Sign release v17.2

Sandbox deployment: August 4, 2026

Production deployment: September 8, 2026

GovCloud deployment: September 15, 2026

Improved Functionality

Pause and resume agreements after authentication failures - Administrators can now allow agreements to pause when a recipient exceeds the permitted authentication attempts, rather than canceling immediately. Senders can update the recipient’s authentication method and resume the same agreement without requiring completed recipients to sign again.
- Administrators can configure a pause period from 1 to 30 days.
- If the agreement is not resumed before the pause period ends, it is canceled automatically.
- The feature is disabled by default.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group

Share AI-generated agreement summaries with recipients - Acrobat Sign can generate an AI summary of an agreement during authoring. Senders can review the summary and choose whether to make it available to recipients, based on account or group settings.

Recipients who receive the summary can review it in the signing experience before completing the agreement. After sending, the sender can use Modify Agreement to change whether the existing summary is included.

AI-generated summaries are for informational purposes only. Recipients should review the complete agreement before signing.
The feature is available after the account accepts the applicable Adobe AI terms.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group

Digital Identity Gateway support for Send in Bulk - Senders can now require Digital Identity Gateway authentication for recipients in Send in Bulk transactions. DIG can be selected in the authoring interface or assigned to individual recipients through the Send in Bulk CSV.
The CSV also supports per-recipient email-matching options, including approved alternate email addresses. Each generated agreement uses the existing DIG authentication and audit process.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group

Add files from Google Drive - Users can now add supported files directly from Google Drive in the current Request Signatures, Custom Workflow, Send in Bulk, and Create a Library Template experiences.
After authenticating with Google, users can browse and select files through the Google Drive file picker. Native Google Docs are converted to PDF before being added to Acrobat Sign.

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group

Customer-managed encryption keys for agreement files - Eligible Acrobat Sign customers can now use a customer-managed key in AWS Key Management Service to encrypt supported agreement files at rest. Account administrators configure the key and AWS access credentials at the account level.
Access to encrypted files depends on the customer-managed key and credentials remaining available.

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account only

Group-level custom timestamp configuration - Custom timestamp providers can now be configured at the group level. This allows groups within the same account to use different approved timestamp providers for their digital signature workflows.
Groups without an explicit configuration inherit the account-level setting.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group

Include CC notification events in audit reports - Account and group administrators can now include CC notification events in agreement Audit Reports. When enabled, the Audit Report records initial and completion notifications sent to general and recipient-specific CC addresses.

Administrators can separately include completion notification events for automatic CC addresses. Both settings are disabled by default.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group

Configure password strength requirements for Government accounts
Acrobat Sign for Government admins can now configure the password strength requirements to adjust the minimum length and character composition rules. This allows organizations to align password policies with their internal security standards and compliance requirements.

Available environments: Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group

Improved accessibility for uploaded PDFs - Administrators can enable automatic accessibility tagging for supported uploaded PDFs.
Acrobat Sign adds structural tags that improve screen-reader and keyboard navigation and preserves those tags in the completed agreement.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group

Sort and export reporting chart data - Reporting users can now sort supported Agreement and Transaction report charts by activity and export the aggregated chart data to CSV. The exported file respects the report’s active filters and time interval.
The enhancement is available for charts showing agreements or transactions by sender, group, or workflow.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group

New Trust Service Providers - Acrobat Sign regularly adds support for new trust service providers. The following TSPs are newly available in this release:
- Swisscom ZertES CH
- Swisscom eIDAS EU

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group

Experience Changes

Improved library template experience - The library template creation and authoring experience has been streamlined with fewer upfront choices, clearer first-use guidance, a dedicated save action, and improved validation and error messages.
Template-management actions are also easier to access after creation.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group

Improved form field detection - Automatic form field detection in Acrobat Sign has been updated to improve the accuracy of detected fields and reduce incorrect field placement during authoring.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled by default

Improved user-list exports for large accounts - Acrobat Sign now processes large user-list exports asynchronously, improving reliability for accounts with extensive user populations.
Administrators continue to start exports from the existing Users page.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled by default

Default settings updated for new small business accounts - Several existing sending features are now enabled by default for new VIP, VIPMP, and ETLA accounts under $100K.
These default setting updates make commonly used sender capabilities available without requiring an administrator to enable each setting first. Depending on account configuration, new accounts may now have access to document expiration, additional recipient roles, additional recipient authentication methods, SMS and WhatsApp delivery, private recipient messages, and multi-signer web forms by default.
These changes apply only to new accounts in the targeted commercial customer segments. They do not apply to Acrobat Sign for Government.

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default

Modern Request Signature becomes default – Retire Classic Compose, remove switch controls, standardize signing experience
All accounts are now transitioned to the modern Request Signature experience, replacing the classic Compose interface. Switch links and admin controls to revert to the classic experience are removed for commercial accounts, while GovCloud accounts are also transitioned with temporary retention of admin controls. This change standardizes the sending experience across environments and simplifies user onboarding ahead of full Classic retirement.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Not configurable

Modern Create Template becomes default – Promote new authoring experience, expand rollout, maintain admin controls
The modern Create Template experience is now the default for all accounts, including those that share assets across multiple groups. This update expands the rollout of the new authoring interface, ensuring all users benefit from ongoing enhancements, while retaining admin controls to revert to the classic experience if needed.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group

Easier access to Acrobat Sign trials for existing Adobe users - Users whose email address is already associated with an Adobe organization can now start an Acrobat Sign trial without being blocked by their existing Adobe account.
This makes it easier for current Adobe customers to evaluate Acrobat Sign alongside their existing products.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group

Improved recipient removal for in-progress agreements - The recipient-removal experience now supports additional form-field configurations in sequential agreements, reducing cases where a sender must cancel and recreate an agreement.
The existing recipient-removal workflow and administrator controls are unchanged.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group

Power Automate Embed retirement notice - Users with access to Power Automate Embed now see an in-product notice about its upcoming retirement and a link to transition guidance. The feature remains available in release 17.2, and this update does not disable or remove existing workflows.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group

Integration Updates

Increased file-size support for Salesforce transactions - The Acrobat Sign for Salesforce integration now supports larger transaction payloads, improving reliability for agreements with large documents, multiple signers, or signed PDFs saved as separate Salesforce attachments.
Existing Salesforce workflows and settings remain unchanged.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Integration

Control recipient names in Salesforce agreements - Acrobat Sign for Salesforce now allows senders to provide a recipient’s name and prevent the recipient from changing it during signing.
The enhancement improves consistency between Salesforce records and completed agreements.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Integration

SAP SuccessFactors integration compatibility update - The Acrobat Sign integration with SAP SuccessFactors has been updated to remain compatible with changes to the SAP SuccessFactors platform.
Existing agreement workflows remain unchanged.

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Integration

Improved offer tracking in SAP SuccessFactors - The Acrobat Sign integration with SAP SuccessFactors now provides Expired and Approval offer statuses, giving recruiters clearer visibility into offer progress.
A new Actor field in the Job Application entity identifies the candidate or approver responsible for the next action. This helps recruiters determine where an offer is waiting without contacting an SAP administrator.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Integration

REST API/Webhook Updates

The below updates are presented in the prerelease notes for disclosure purposes. Full documentation for API and Webhook updates can be found in the Acrobat Sign developer documentation when the version update is delivered to the production servers.

Release errata

There are no items that have slipped from this release as of this time.

Resolved Issues

Issue	Description
4550652	Summary: Users viewing a shared Send in Bulk transaction could select Download Completed Agreements, but the download failed with a permissions error because the action is supported only for the original sender. Fix: The Manage page now hides Download Completed Agreements from users viewing a shared bulk send. The action remains available to the original sender.
4559237	Summary: When a recipient used a cloud signature, the signer's name could remain set to the sender's incorrect value rather than updating from the signing certificate, due to a saved signature from an earlier signing session. Fix: Cloud signature processing has been updated so the signer name is populated from the selected signing certificate, even when the recipient has a previously saved signature.
4561749	Summary: Descriptions on second-row Home page banner cards could appear clipped because updated text-sizing standards were applied to a layout that had not been adjusted for the new dimensions. Fix: The banner card layout has been updated to accommodate the revised text sizing, ensuring descriptions are not cut off.
4561980	Summary: Text entered through Fill & Sign could appear missing, enlarged, or misaligned in the completed PDF due to differences in how substituted fonts and text spacing were processed during document rendering. Fix: PDF rendering has been updated to preserve the intended font sizing, spacing, and placement, ensuring entered data appears correctly in the completed document.
4561987	Summary: Individual documents downloaded from a completed agreement can become significantly larger than their originals due to excessive data added during the generation of accessible versions of signed PDFs. The increased size could also cause agreement emails to exceed delivery limits. Fix: Accessible PDF processing has been optimized to prevent unnecessary file-size growth when agreements contain multiple documents. Individual downloaded documents now retain a size more consistent with their original content.
4562483	Summary: Some existing library templates failed to open in the modern template experience and displayed a “Something went wrong” error because the template contained field data without the recipient assignment information expected during loading. Fix: Template loading has been updated to handle incomplete recipient assignment data correctly, allowing affected templates and their form fields to open in the modern template experience
4567869	Summary: Agreements containing PDFs with incorrectly formatted font data could remain stuck on a loading screen and fail to complete due to an endless processing loop during document rendering. Fix: PDF processing has been updated to detect and safely handle malformed font-width data, preventing the rendering process from stalling and allowing affected agreements to be sent and signed.
4568289	Summary: Agreement senders who replaced themselves as recipients could not hide the completed agreement because a permissions check treated the original sender as a replaced participant. Fix: Permission validation has been updated so the original sender can hide the agreement even after replacing themselves as a recipient, without changing visibility permissions for other users.
4569692	Summary: Email addresses in a recipient group could appear extremely small in the signature block because the full group address list was used to calculate the field’s text size. Fix: Signature block rendering has been updated to recalculate the email field after a group member opens or signs the agreement, so the active signer’s address displays at a readable size in the signing experience and completed PDF.
4571461	Summary: Landscape-oriented documents used in web forms could contain unexpected blank areas and misplaced fields due to incorrect page-coordinate calculations during document processing. Fix: Document processing has been updated to calculate field placement and covered areas correctly on rotated and landscape pages, preventing blank spaces and misaligned fields in generated agreements.
4574423	Summary: Radio button groups with the same field name in merged reusable templates were not kept in sync because selecting an option cleared the corresponding selection in the other group. Fix: Radio button behavior has been updated so matching options in fields with the same name are selected together across merged templates, while different options remain unchanged.
4574867	Summary: Custom signing date formats created in Acrobat Web reverted to the default date format because the selected display format was not preserved when form fields were removed and recreated during agreement processing. Fix: Agreement processing has been updated to preserve custom date display formats when form fields are recreated, ensuring the signing experience uses the format selected in the original template.
4575022	Summary: Signers using phone authentication could not delegate an agreement from the modern signing experience because the delegation dialog did not collect the new recipient’s phone number. Fix: The delegation dialog now displays and validates a phone number field for phone-authenticated agreements, uses the supported country-code list, and passes the number to the delegated recipient’s authentication request.
4575850	Summary: Text in large, locked multiline fields could appear smaller in the signing experience and completed agreement because the field’s existing appearance was replaced by an unnecessary font-size recalculation. Fix: Multiline field rendering has been updated to preserve the existing text appearance when the content already fits, preventing the font from shrinking unnecessarily.
4576211	Summary: Senders received two completion emails when their address was also configured to receive an extra copy because both the sender and automatic-copy notification paths were triggered for the same recipient. Fix: Completion email processing has been updated to evaluate the sender and automatic-copy rules together, preventing duplicate messages while preserving cases where separate notifications are expected.
4576609	Summary: Senders using a custom workflow could lose access to group-shared templates after returning from authoring and previewing again because the second validation path did not recognize templates shared with the sender’s group. Fix: Template access validation has been aligned across the preview and send paths so users can continue using templates shared directly with them or with their group throughout the custom workflow.
4576624	Summary: Signature fields in agreements with an in-person signer and additional participants could become reassigned or overlap after the sender returned from authoring because participant identifiers changed when the draft agreement was rebuilt. Fix: Draft agreement processing has been updated to remap each field to the corresponding participant after returning from authoring, preserving the correct assignments across supported routing and recipient-role combinations.
4576876	Summary: Required signature fields hidden by conditional logic still counted as incomplete due to an error in how the signing experience recalculated required fields, preventing signers from completing the agreement. Fix: Required-field processing has been updated so hidden signature fields no longer count as incomplete, allowing signers to complete agreements when conditional rules remove those fields from view.
4576961	Summary: Agreement senders who were also signers did not receive the completed agreement email because the notification workflow excluded the sender from the signer notification path. Fix: Completion email processing has been updated, so senders who also sign the agreement receive the completed notification when their notification settings allow it.
4577135	Summary: Replacing a web form recipient updated the email address but retained the original recipient’s name due to incomplete synchronization of the replacement details. The incorrect name could appear to the signer and in the audit report. Fix: Web form recipient replacement has been updated to apply the new recipient’s name consistently across the agreement, signing experience, and audit data.
4577475	Summary: Agreements created from templates could display a transaction footer after the setting was disabled because the template retained the footer state from when it was originally created. Fix: Transaction footer processing has been updated to evaluate the current setting when the agreement is generated, rather than relying on the value stored with the template.
4577531	Summary: Some document names in the transaction footer were truncated because specific character spacing caused the final words to wrap beyond the visible footer area. Fix: The transaction footer now uses a narrower font for document names, allowing more text to fit without wrapping or being cut off.
4578623 / 4579255	Summary: Some AcroForm PDF fields appeared twice in authoring because document processing added a second overlapping field for certain existing form fields. Fix: PDF form-field processing has been updated to prevent duplicate overlapping fields from being added, so each field appears once in authoring, and signers are prompted only once.
4580019	Summary: The Download, Print, and Search buttons in the agreement-viewing experience lacked accessible names, preventing screen readers from identifying their purpose. Fix: Accessible names have been added to the Download, Print, and Search buttons so assistive technologies can announce each action correctly.
4581229	Summary: Changes to the security setting that prevent Acrobat Sign from being embedded in third-party websites were missing from the Settings Activity Report because the setting was not categorized for administrative reporting. Fix: The setting has been added to the Security Settings reporting category, so account- and group-level changes are recorded in the Settings Activity Report.
4582044	Summary: Cloned checkbox fields could move or overlap after signing because they were rotated unnecessarily during the processing of certain PDF page configurations. Fix: Cloned checkbox processing has been updated to preserve the original field orientation and position, preventing the fields from shifting after participants sign.
4582268	Summary: Webhook API requests made directly to the webhooks endpoint may receive the default API throttling limits rather than the webhook-specific limits because the base endpoint was not included in the webhook policy mapping. Fix: Webhook throttling has been updated so requests to both the base endpoint and individual webhook endpoints consistently use the intended webhook-specific rate limits.
4582742	Summary: Updating a participant set could fail with a “more than one participant” error after a previous replacement because the API counted an already replaced recipient when evaluating the active participant set. Fix: Participant-set updates now exclude previously replaced recipients when determining how many active participants are being changed, allowing the recipient email to be updated successfully.