The Adobe Acrobat Sign Technical Notifications are ordered below, with the current update at the top, and rolling back in time as you scroll down the page.
The Technical Notifications page is updated regularly with new information, making its content highly dynamic. While localized versions are available, the translation process may cause slight differences from the authoritative US English version. Always refer first to the US English page for the most accurate and up-to-date information.
[Important] The next Adobe Acrobat Sign release is scheduled for March 18, 2025
This minor patch release will address customer-reported defects and apply necessary optimization and security updates.
The Sandbox environment will receive these patches four weeks before the scheduled release. A list of resolved issues will be published at that time and updated 14 days prior to release.
Feature Release: Adobe Acrobat Sign – February 11th Release Completed
The release was completed to all shards with no downtime to any services.
|
First Reported: September 2024 - Updated February 2025 |
Current |
|---|
To improve Adobe Acrobat Sign service security and robustness, we will start to roll out network changes to include a web application firewall (WAF) in February 2025. These changes will route traffic into Acrobat Sign application servers through the WAF service. This routing will be invisible to most customers. Usage will not interfere with access to Acrobat Sign from any Adobe clients or integrations.
Action Required
None.
This change will not affect customer integrations, as the Acrobat Sign API and API domain names will not change. This solution is backward compatible with the published IP ranges.
Customers who have updated their security devices don't need to revert or make any other changes.
The current update schedule is:
- Production Sandbox updates February 24, 2025.
- Production shards: IN1, JP1, AU1, and SG1 will update March 3, 2025.
- Production shards: NA2, NA3, and EU2 will update March 6, 2025.
- Production shards: NA1, NA4, and EU1 will update March 11, 2025.
-
Ingress and Egress Access to Acrobat Sign
Acrobat Sign is no longer retiring the list of server ingress IP addresses as previously announced.
The server ingress and egress IP addresses, as documented on the System Requirements for Acrobat Sign page, will remain viable. -
Why is Acrobat Sign making these Changes?
The use of a WAF improves Acrobat Sign's protection against harmful traffic and helps us better address security, robustness, and compliance requirements.
-
I have a custom integration into Acrobat Sign. Will my application be affected?
No, we don't expect any integrations to be negatively impacted.
-
Are there new IP address lists that can be substituted?
No.
The information on the System Requirements for Acrobat Sign page remains accurate. -
My organization has implemented network filtering using Acrobat Sign's published domain list for traffic from our corporate network. Are we affected?
No.
The network changes described here do not impact Acrobat Sign's domain list, as documented on the System Requirements for Acrobat Sign page. Domain-level filtering is unaffected. -
My organization employs IP address validation for email delivery from Acrobat Sign servers. Are we affected?
No.
The IP ranges for outbound mail relays, as listed on the System Requirements for Acrobat Sign page, are not changing. -
My organization has configured our Acrobat Sign account to restrict access to our own IP addresses. Are we affected?
No.
Acrobat Sign can be configured to validate incoming traffic against customer-chosen IP addresses, as described on the Restrict access to your account using IP address ranges page. Such usage will not be affected by this change. -
My organization has implemented network filtering using Acrobat Sign's published list of ingress IP addresses. Are we affected?
No.
The new WAF configuration is backward compatible with the existing network architecture, so no additional tuning of your security devices should be required.
Примітка.Note that this refers to IP-level filtering for the environment hosting your application. Domain-level filtering is not affected.
-
I'm using the Salesforce integration with explicitly configured IP allow-listing. Do I need to do anything?
No.
The WAF installation requires no changes for existing Salesforce installations at this time.
The existing configuration/process, as described in the help documentation, remains the same, and administrators should follow all IP allow-listing steps.
ISV and Embed Partners should contact their Success Manager for any further questions.
|
First Reported: June 2018 - Updated May 2024 |
Current |
|---|
Action Required
All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.
Access to the SOAP API will be removed for all embed partners starting March 1, 2025.
To ensure continued function, all embed partners using the Adobe Acrobat Sign SOAP API must migrate to the latest REST API V6 before March 1, 2025.
Please review the REST v6 and migration documentation for reference:
For any queries, please contact your designated Adobe Acrobat Sign PSM.
|
First Reported: June 2018 - Updated May 2024 |
Current |
|---|
Action Required
All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.
Initially announced in June 2018, the effort to sunset the Acrobat Sign SOAP API will be completed in 2024.
Customer use of the SOAP API is scheduled to be disabled through a rolling process starting in February 2024. All customers and partners using the SOAP API must migrate to REST v6 API or risk a disruption in their service.
Please review the REST v6 and migration documentation:
Access to the SOAP API will be removed per the following schedule:
|
Account type |
SOAP API Disablement Date |
|
February 1, 2024 (Completed) |
|
April 1, 2024 (Completed) |
|
The scheduled date has been moved up to July 1, 2024, replacing the previous date of December 1, 2024. |
|
March 1, 2025 |
|
First Reported: September 2024 - Updated February 2025 |
Current |
|---|
The Webhook 2.0 infrastructure has been rolled out to all customers, and with that completed, signer notifications have been deprecated. As a result, the webhookNotificationApplicableUsers parameter of the webhook payload no longer provides any useful data and will be removed from all webhook payloads.
The Sandbox environment will be updated in the March 2025 release.
The Production environments will be updated in the April release.
The sending userID and email can be found using the initiatingUserId and initiatingUserEmail parameters in the notification payload.
This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.
This update only applies to the Send (Request e-signatures) page. Structured Self-signing workflows are not yet included.
|
First Reported: March 2024 - Updated January 2025 |
Current |
|---|
Starting with the April 2025 release, the modern Request Signature environment will become the default experience when creating a new agreement.
- Users will no longer be able to switch between the new and classic environments, as switch links will be disabled.
- Administrators will still have the option to enable the classic experience and restore switch links through the admin menu.
- Customers using the Notarize integration will not be affected by this change.
This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.
|
First Reported: June 2024 - Updated January 2025 |
Current |
|---|
Final Transition to the New Request Signature Experience
With the July 2025 release, the classic Compose interface will be fully removed from availability, finalizing the transition to the new Request Signature experience.
- All commercial accounts that have not yet set the new Request Signature environment as their default will be automatically switched to it as the only option for configuring new agreements.
- The ability to configure the experience or switch between environments will be removed from admin menus.
- Customers using the Notarize integration will not be affected by this change.
|
First Reported: March 2024 - Updated February 2025 |
Current |
|---|
This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.
As of the April 2025 release, the modern Request Signature environment will become the default experience when creating a new agreement.
- Users will still be able to switch between the modern and classic environments using switch links on the page.
- Administrators will still have the option to enable the classic experience and restore switch links through the admin menu.
|
First Reported: March 2024 - Updated February 2025 |
Current |
|---|
This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.
Final Transition to the New Request Signature Experience
With the July 2025 release, the classic Send in Bulk interface will be fully removed from availability, finalizing the transition to the modern Send in Bulk experience.
- All commercial accounts that have not yet set the modern Send in Bulk environment as their default will be automatically switched to it as the only option for configuring new bulk transactions.
- Switch links to access the classic experience will no longer be available.
- The ability to configure the experience will be removed from administrator menus.
|
First Reported: November 2024 - Updated: January 2025 |
Current |
|---|
Senders can provide an additional view of agreements for mobile recipients that lists only the field within the agreement available to the recipient.
Senders can arrange the field list as they like, and group fields into logical sections to help the signers move through the field input with a minimum of scrolling.
Recipients have the option to view the mobile-friendly fields list or the original PDF view with the fields placed within the document content.
This feature is scheduled to be released:
- To be deployed on the Sandbox environment on December 11, 2024
- To be deployed on the Production environment on March 4, 2025
|
First Reported: February 2025 |
Current |
|---|
With the April 2025 release, most accounts will transition to a new Create Template authoring experience, introducing an updated UI for creating reusable templates.
- Administrators can configure accounts to continue using the classic experience at the Account or Group level.
- Users will not have the option to switch back to the classic authoring experience from the UI.
Accounts that have enabled sharing templates across multiple groups are excluded from this update.
|
First Reported: February 2025 |
Current |
|---|
The Account tab, available to Acrobat Sign account-level administrators, will be renamed Admin.
- This update applies exclusively to the Acrobat Sign Standalone environment (Acrobat Sign Solutions).
- The update will be implemented in phases, starting in April 2025 and tentatively concluding in May 2025.
Note that this change is purely cosmetic—there are no functional modifications, only updates to the tab labels.
The Group label for group-level admins will not change.
|
First Reported: September 2024 |
Current |
|---|
The Webhook 2.0 infrastructure has been rolled out to all customers, and with that completed, signer notifications have been deprecated. As a result, the webhookNotificationApplicableUsers parameter of the webhook payload no longer provides any useful data and will be removed from all webhook payloads.
The Sandbox environment will be updated in the March 2025 release.
The Production environments will be updated in the April release.
The sending userID and email can be found using the initiatingUserId and initiatingUserEmail parameters in the notification payload.
|
First Reported: September 2024 |
Current |
|---|
Action Required
All customers using the API must update their APIs to utilize the version 6 endpoints as soon as possible to ensure uninterrupted availability.
Versions 1 through 4 of the Acrobat Sign REST API have been deprecated and will be removed from service on December 1, 2025.
Updating APIs can involve considerable effort, so all customers are strongly encouraged to scope and budget their update as soon as possible so that support can be fully engaged to resolve any questions or problems that arise before the December 2025 cutoff date.
While REST API v1-4 are deprecated, they will continue to function, and your applications will continue to work until December 1, 2025, when the REST API v1-4 will be removed.
After December 1, 2025, applications built on the REST API v1-4 will cease functioning.
|
First Reported: September 2022 - Updated March 2024 |
Current |
|---|
Classic reporting will be completely removed from the Acrobat Sign interface in the first half of 2025. This includes the switch link that allows changing between environments. Once removed, customers will not be able to return to the classic environment to review classic reports, and scheduled reports will stop executing.
The modern reporting environment will remain as the only reporting solution.
All customers are strongly encouraged to recreate all of their existing reports in the new environment as soon as possible.
|
First Reported: May 2024 |
Current |
|---|
The option to use an external drive for uploading files will be limited to OneDrive only in the new Request Signature experience.
It's recommended that customers who use other options for file upload use the vendor-specific application to provide a networked drive that can be accessed through the native file picker on the user's local system.
- Dropbox: https://www.dropbox.com/desktop
- Google Drive: https://support.google.com/drive/answer/10838124
- Box: https://support.box.com/hc/en-us/articles/360043697194-Installing-Box-Sync
- Acrobat/Document Cloud: https://www.adobe.com/acrobat/hub/share-sync-pdfs.html
Additional Resources
- Community forums
- Weekly Training - Weekly Webinar covering training topics for new users and administrators
- Adobe Sign Innovation Series - Monthly Webinar covering the hottest topics in the Adobe Sign space
|
First Reported: December 2024 |
Removed from Current list: February 2025 |
|---|
Adobe Acrobat Sign will rotate the Adobe Acrobat Sign SSL Certificate on January 22, 2025.
In addition, a new SSL certificate is being deployed to support the WAF network changes being made in January 2025. This new certificate directly impacts access to the Acrobat Sign service and must be installed before the WAF goes online.
Action Required
- Every customer account that explicitly secures network activity must include the new WAF SSL certificate in its list of stored certificates.
- If you have custom-built integrations with Acrobat Sign using either the SOAP or REST APIs and if any of these integrations have ‘pinned’ the existing public key, no other action is required.
- If you are using Acrobat Sign’s SSL certificates for SSO, or if you’re pinning the certificate itself (or using other methods), you can find the new Acrobat Sign SSL certificates in the Adobe Acrobat Sign System Requirements.
- If your SSO configuration supports multiple public certs/chains, you can add the new certificates now and remove the old public cert/chain from your configuration after the January switch.
- If your SSO does not support multiple public certs/chains, you will need to sync your SSL switch with Acrobat Sign on January 22, 2025.
The new SSL certificates will be active on January 22, 2025.
|
First Reported: November 2024 |
Removed from Current list: February 2025 |
|---|
The new recipient experience contains signing improvements for both desktop and mobile web browsers. This new experience is being rolled out over the first months of 2025 but will be available in the Sandbox environment in the first week of December 2024.
|
First Reported: August 2024 |
Removed from Current list: January 2025 |
|---|
The legacy Accept-Charset header will be removed from all Webhook and Callback notifications with the November 2024 release.
All customers that rely on this header for any reason should refactor their code to account for it's absence.
|
First Reported: September 2024 |
Removed from Current list: January 2025 |
|---|
|
First Reported: November 2024 |
Removed from Current list: January 2025 |
|---|
With the November 2024 release, the editable labels in the Custom Workflow Designer have been limited to 100 characters. This limit is evaluated when the workflow is created or updated.
Preexisting workflows that have labels over 100 characters can still be sent successfully, but if the workflow is updated, the label must be reduced to 100 characters or less before it can be saved. Offending labels are outlined in red for easy discovery.
New workflows will warn about the label limit before they are saved.
Action Required
It is recommended that admins with control over custom workflows open and review each workflow to ensure that they don't have errors on their template.
Archived Notifications
Listed by the date when the notice was removed from the current notice list, most recent to oldest.
