Technical notifications

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. 


[Important] The next Adobe Acrobat Sign release is scheduled for March 12, 2024

This will be a major release, including feature improvements for users and administrators, as well as resolutions to customer-reported issues.  

Customers with a Sandbox entitlement will have access to the new features four weeks prior to launch. Prerelease documentation for the release content will also be available at that time.

Feature Release: Adobe Acrobat Sign – January 23rd Release Completed

The release is complete to all shards with no downtime to any services.

[Important] Disablement of the SOAP API from Adobe Acrobat Sign accounts is scheduled to start in February 2024

First Reported: June 2018 - Updated November 2023


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

  • Free
  • Trial
  • Developer

February 1, 2024

  • Enterprise
  • Business

April 1, 2024

  • Integration Only Partners

December 1, 2024

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.


[Important] Update to how Adobe Acrobat Sign Reports assess group relationships in the March 2024 release

First Reported: November 2023


Prior to the March 2024 release, the Acrobat Sign API does not have the parameters to retrieve the groupID of an agreement for accounts that do not have Users in Multiple Groups enabled. In this case, the user's current groupID is used when applying a Group filter to a report.

This impacts reporting for accounts that have moved users between groups, causing discrepancies by including and excluding agreements based on the user's current group and not the group the agreement was originally related to. Additionally, any data export containing an agreement from a user that has been moved reflects the current user's group, and may misrepresent some of the agreement's actual group.

The March 2024 release adds parameters to the API structure that include the creating groupID, thereby ensuring that group filtering will apply to the original group the agreement was created in and not the group the user is currently a member of. Customers that don't have UMG enabled should be aware that agreement numbers on reports created before the March 2024 release may change based on the number of users that have been moved between groups and their total volume of agreements.


[New] Email headers for reecipient emails will be changing in the March 2024 release

First Reported: January 2024


The format of email headers has changed to alter the From property for recipient emails, such as the initial "Please Sign" and Reminder templates. The previous format of "Adobe Acrobat Sign on behalf of <SomeUser>" has been changed to "<SomeUser> via Adobe Sign". The shorter format will ensure that the sender's name is not truncated on smaller viewing platforms.

Two email headers, one highlighting the legacy header, and the other highlighting the new header

[New] The text accompanying the Click to Sign banner is being updated in the March 2024 release 

First Reported: January 2024


The footer text that prefaces the Click to Sign banner has been updated from "By signing, I agree to this agreement, the Consumer Disclosure, and to do business with <Sender>" to "By signing, I agree to this document, the Consumer Disclosure and to utilize electronic signatures."

Both the legacy and new Click to Sign banners

[New] Bio-Pharma accounts - Enable improved authentication challenges for your account before September 10, 2024

First Reported: January 2024


The Bio-Pharma settings to enforce identity authentication were updated in the November 2023 Acrobat Sign system update and placed behind an Enable Now button to permit admins the time to review the update and elevate their account once they were comfortable with the changes. The Enable Now button is only available on the Bio-Pharma subsection of the admin menu.

The change to the enforced identity authentication settings removes the dependency between the controls, allowing admins to select any one (or more) settings as needed. Additionally, in the case of dependent controls that are checked but disabled, the checkbox is cleared to correctly reflect that the setting isn't in effect. 



Controls that are enabled will remain enabled. All agreements will continue to work as before.

Enabling the new experience through the Enable Now button updates all groups in the account and removes the callout to apply the update. The update cannot be reversed.

Starting in February 2024, accounts that have enabled the first control (Enable authentication challenges and Signing reasons), but have not enabled the improved experience, will receive two in-application engagements:

  • A dialog box appears on the Home screen after logging in. This dialog box only shows to a user one time.
  • A "hotspot" graphic on the Bio-Pharma admin menu that opens a dialog box when selected. The hotspot will show up to three times until the user selects it, with a 24-hour delay between displays.

After September 9, 2024, all accounts in the Acrobat Sign service will automatically be updated to use this new interface.


Customers who have configured their Bio-Pharma controls (at the account level, or for any group within the account) should manually enable the new experience in the application through their admin menu before September 10, 2024.

All groups will automatically update and properly retain all the expected authentications as configured before the update.


Customer accounts that have not manually updated their accounts will be automatically updated by the system.

System-updated accounts will not automatically clear the checked but disabled dependent controls, resulting in those controls being enabled after the update.

This will impact new agreements, prompting recipients to authenticate for the enabled control conditions.

To prevent this, manually enable the new experience and take advantage of the automated process that converts disabled settings into unchecked settings.

[New] Adobe Acrobat Sign Template: W-4 (2024)

First Reported: January 2024


The new IRS W-4 (2024) form, entitled W-4 2024 (Employee's Withholding Certificate), is scheduled to be added to the Acrobat Sign library at the beginning of February 2024.


The new W-4 form template has a new libraryDocumentId. If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

The 2023 version will be removed from the system as of March 2024 release.

Any application/API using the legacy (ver 2023) form must be updated before March 1st to ensure no disruption to successful service.

To find the libraryDocumentId in an API-enabled account:

  1. Log in as an Account Admin
  2. Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation
  3. In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 
    • Enable the library_read:self scope
  4. Click the Try it out! button
  5. In the Response Body, locate the new W-4 2024 (Employee's Withholding Certificate) form template (not ver. 2023) to see the libraryDocumentId value.  
Obtain the docID


Customers that prefer to manage the tax form within their account library can download a fully tagged PDF here.

If you need more information, please contact your Customer Success Manager.

[New] Adobe Acrobat Sign for SharePoint Online: End of service as of June 28, 2024

First Reported: January 2024


Support for the Acrobat Sign for SharePoint Online integration is set to end on June 28, 2024. 

After June 28, agreements sent for signature from this integration will remain available for recipients to sign. However, the final completed documents will not be saved back into SharePoint. The final executed agreement must be downloaded manually (or through some other automation) and uploaded to your SharePoint site if you wish to save a copy in SharePoint Online.

Advanced workflow features, such as data mapping between SharePoint lists and Acrobat Sign workflow templates, will no longer be available, but the underlying data will not be affected. Completed agreements and other data previously stored on your SharePoint site or with Acrobat Sign will not be affected. 


This end-of-service notification only applies to the SharePoint Online integration.

Other integrations that can access SharePoint Online (e.g., Microsoft Power Automate and Microsoft Teams) are not impacted.

[New] Notice to Acrobat Sign API users regarding HTTP header case insensitivity

First Reported: January 2024


Please note that HTTP headers are case-insensitive, as specified in RFC 2616 and RFC 7230. This means the header names can be written in any combination of upper and lower case letters. However, some applications or libraries may expect a certain case for the header names, such as Pascal-Case (e.g., Content-Type) or lowercase (e.g., content-type).

Due to upcoming infrastructure updates, Adobe Sign will be changing the case of some HTTP headers. This should not affect the service's functionality, but it may require some adjustments in your code or configuration if you rely on a specific case for the header names. We recommend reviewing your code and configuration to ensure they are compatible with case-insensitive headers.

For more information about HTTP headers, refer to the following resources:

Classic reporting to be removed from service in the second half of 2024

First Reported: September 2022 - Updated November 2023


Classic reporting will be completely removed from the Acrobat Sign interface in the second half of 2024. 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.


Improved Request Signature page for embedded applications 

First Reported: November 2023


Acrobat Sign has developed a version of the new Request Signature page as a  Single Page Application (SPA) for customers that have built their own custom integrations and applications. Instead of using browser cookies for the user session, this new solution uses session access tokens to access the Acrobat Sign workflows and pages.

The SPA solution overcomes a problem where browser cookies stored in an iFrame are viewed as third-party cookies, and the trend for browsers is to disable third-party cookies by default.

Customers with embedded solutions and want to take advantage of the SPA-built Request Signature page should contact support to enable the feature.


Unsanctioned page modifications may be disabled

First Reported: February 2023


Modifications to HTML pages delivered by Adobe, except for those enabled by published APIs and features, are unsupported. Such modifications may interfere with the functionality of Acrobat Sign. Adobe may, at any time, make technical changes that disable the function of any non-Adobe-sanctioned HTML page modifications.

If your use of Acrobat Sign currently relies on modifying HTML from Acrobat Sign using browser extensions,  HTTP proxies, or any other means not enabled by Adobe published APIs and features, you should migrate away from these as soon as possible to avoid disruption.

This statement applies to any mechanism by which such modifications may be made, such as browser extensions and browser configurations that allow HTTP proxies to modify page content.


New Public Key, Root, and Intermediate SSL Certificates - Completed February 1, 2024

First Reported: September 2023 - Updated December 2023


Adobe Acrobat Sign rotated the Public key (for * and *, Root, and Intermediate SSL Certificates on the morning of February 1, 2024.
There is no change to the underlying cryptographic protocols or schemes.



Use of the public key

  • 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 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 Root and Intermediate certificates in the Adobe Acrobat Sign System Requirements. The Public Key will be available on February 1, 2024.
    • 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 April switch.
    • If your SSO does not support multiple public certs/chains, you will need to sync your SSL switch with Acrobat Sign on February 1, 2024.  

The new SSL certificates will be active on February 1, 2024. 


Adobe Acrobat Sign Bulk Processor update - Completed

First Reported: January 2024


Acrobat Sign has completed the updates to the Bulk Agreement Processor, which manages the processing of the Send in Bulk feature. 

Upgrade window

JP1 (Japan) - Completed

Friday, January 19, 2024 

7:30 AM to 8:30 AM PST

IN1 and AU1 (India and Australia) - Completed

Thursday, January 25, 2024 

7:30 AM to 8:30 AM PST

NA1, NA2, and EU1 (North America and Europe) - Completed

Friday, February 2, 2024

7:30 AM to 8:30 AM PST

During the upgrade, users remained able to create new Send in Bulk transactions through the user interface or API.

  • Newly created Send in Bulk transactions were accepted, and the generation of the child agreements resumed when the update was completed.
  • Send in Bulk transactions that started but were not completed were suspended until the update was completed.

Existing transactions were not affected, and customers were able to complete their actions on existing agreements without issue.

No other services were impacted, and the Acrobat Sign service remained up and functional throughout the upgrade process.

Additional Resources

Past Notifications

Adobe Acrobat Sign Database Maintenance on December 11, 2023 for the EU1 environment

First Reported: December 2023

Removed From Current List: January 2024

On December 11, 2023, the EU1 Acrobat Sign environment completed an adjustment to the webhooks database that briefly delayed processing times for webhooks.

The adjustment started just after 10am Pacific time on Sunday, December 11, 2023, and lasted roughly 10 minutes.

Attempts to create a new webhook through the user interface or API would have failed during the maintenance period, presenting a conspicuous error message.

The service remained up and functional during this time. Recipient activities were not be impacted.

Adobe Acrobat Sign Database Maintenance completed December 3, 2023 for the NA1, NA2, and NA4 environments

First Reported: November 2023

Removed From Current List: January 2024

On December 3, 2023, the NA1, NA2, and NA4 Acrobat Sign environments completed an adjustment to the webhooks database. 

The adjustment started just after 9pm Pacific time on Sunday, December 3, 2023.

The service remained up and functional during this time. Recipient activities were not impacted.

Archived Notifications

Listed by the date when the notice was removed from the current notice list, most recent to oldest.


Saņemiet palīdzību ātrāk un vienkāršāk

Jauns lietotājs?