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.

[Next Release] The next Adobe Acrobat Sign release is scheduled for September 16, 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.

The release schedule and prerelease notes can be reviewed here >

Feature Release: Adobe Acrobat Sign – July 22^nd Release Completed

The release was completed to all shards with no downtime to any services.

Current Notices:

New items are added to the table as they are reported. The full list is resorted at the beginning of the month.
Status	Issue or Event	Execution Date
Rolling Release	Modern e-signing experience to be promoted in October 2025. Classic e-signing page to be retired in March 2026	October, 2025
Imminent	IPv6 access for Acrobat Sign for Government	September 15, 2025
Next Major Release	API Polling Threshold	October, 2025
Next Major Release Rolling Release	Modern Request Signature to be promoted in October 2025. Classic Compose (Send) page to be retired.	October, 2025
Next Major Release Rolling Release	Modern Request Signature to be promoted for all GovCloud accounts. Classic Compose (Send) page to be retired.	October, 2025
Next Major Release Rolling Release	Modern Create Template Experience Rollout Schedule	October, 2025
Pending	Classic Reporting to be removed from service in March 2026	March, 2026
Rolling Release	Custom Workflow Rollout Schedule	October 7, 2025
Current	Remove webhookNotificationApplicableUsers from the Webhook payload.	July, 2025
Pending	Remove REST API v1-v4 from service.	December 1, 2025
Informational	External source drives are not supported in the modern Request Signature environment.	Current

In October 2025, the modern Recipient experience for e-signing will be promoted to the default environment for all Commercial and GovCloud accounts (v16.2).

First Reported: August 2025	Current Bookmark this notice

All accounts switched to the modern environment; Admin settings remain

In the 16.2 release (Oct. 2025), all accounts will be updated to use the modern e-signing environment. Admin controls will remain in the Admin menu to enable the classic environment if needed.

Not:

The classic environment will remain available as a fallback measure for any use case where the modern environment cannot be used.

Acrobat Sign for Government to include IPv6 addresses in the system requirements on September 15, 2025

First Reported: August 2025	Current Bookmark this notice

To support FedRAMP CSP requirements, we are enabling the IPv6 protocol on our Acrobat Sign for Government environment:

2001:489a:3102:4::160/124 (IPv6)
2001:489a:3102:4::150/124 (IPv6)

API polling threshold limit

First Reported: August 2025	Current Bookmark this notice

To help maintain system stability and improve performance, Acrobat Sign will introduce a polling threshold in the October 2025 release (version 16.2). This change limits how frequently client applications can poll specific API endpoints.

High-frequency polling creates an unnecessary load on backend systems, resulting in degraded performance and slower response times. API developers are encouraged to switch to webhooks for real-time updates.

What’s Changing

This polling policy applies to all GET API endpoints for status retrieval or listing purposes.

Examples of Affected Endpoints

Status Retrieval:

GET /agreements/{agreementId) – Retrieves the current status of an agreement.
GET /agreements/{agreementId)/documents/{documentId) – Retrieves the file stream of a document within an agreement.

Listing:

GET /agreements – Retrieves agreements for the user.
GET /agreements/{agreementId)/events – Retrieves event information for an agreement.

A limit will be applied to how often the effective user can make the same API call to the Acrobat Sign service. An error is returned if the same call is made within the minimum polling interval by the same effective user.

Polling Policy Details

Minimum Object Polling Interval (MOPI): The default MOPI varies depending on the tier of service:
- Acrobat Sign Partners: 1-minute interval.
- Acrobat Sign Solutions for Enterprise: 1-minute interval.
- Developer accounts: 10-minute interval.
Duplicate Requests Within MOPI: If the same effective user makes identical GET requests (same path and headers) more than once within the MOPI, the system will return:
- 304 Not Modified status code to HTTP conditional requests using an ETag.
- 429 Too Many Requests status code with a retry-after for other requests.
ETag Handling: This policy applies when ETag values are provided in the If-None-Match header for endpoints that already support 304 Not Modified.

Action Required

Webhooks: If your application requires near real-time updates, use webhooks instead of polling. Webhooks provide a more efficient and scalable way to receive timely updates.

If webhooks cannot be implemented, applications should implement client-side caching mechanisms to store and reuse API responses. When a 304 Not Modified response is received, the cached data should be used instead of making another API call.

Customers have two months following the 16.2 release to implement the recommended polling changes in their code. During this time window, the system will LOG the polling interval threshold events.
After December 2025, the polling protection policies will be switched to ENFORCE the errors will start triggering for users.

Please contact your CSM if you need assistance or have any questions.

The sandbox environment will enable the polling policy to LOG errors on September 17, 2025, and set to ENFORCE on September 25, 2025.

In October 2025, the modern Request Signature environment will be promoted to the default environment for all accounts (v16.2).
Classic Compose will be retired and removed from the commercial interface in the March 2026 (v17.0) release.

Not:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted bythis timeline.

First Reported: February 2025 - Updated August 2025	Current Bookmark this notice

All accounts switched to the modern environment; Admin settings remain

In the 16.2 release (Oct. 2025), all accounts will be updated to use the modern Request Signature environment.

Switch links will be disabled,
Admin controls will remain in the Admin menu to enable the classic environment if needed.

Final transition to the new Request Signature experience (March 2026)

With the March 2026 release, the classic Compose interface will be permanently retired. All accounts will now use the modern Request Signature experience as the standard way to configure new agreements.

What’s changing

In the October 2025 release:

All commercial accounts will be automatically switched to the modern Request Signature experience.
Switch links will be disabled.
The option to configure or switch between the classic and modern environments will remain available in the admin settings.

In the March 2026 release:

All commercial accounts will be automatically switched to the modern Request Signature experience.
Switch links will be disabled.
The controls to revert the experience to the classic environment will be removed.
The new experience becomes the only available interface for composing agreements.

We recommend familiarizing your users with the modern experience before the release to ensure a smooth transition.

Adobe Acrobat Sign for Government accounts will promote the modern Request Signature environment for all accounts (v16.2 and v17.0).
Classic Compose will be retired and removed from the interface in the July 2026 (v17.1) release.

First Reported: August 2025	Current Bookmark this notice

All accounts switched to the modern environment; Admin settings remain

In the 16.2 release (Oct. 2025), all accounts will be updated to use the modern Request Signature environment.

Switch links will be available,
Admin controls will remain in the Admin menu to enable the classic environment if needed.

In the 17.0 release (March, 2026), all accounts will be updated to use the modern Request Signature environment.

Switch links will be disabled,
Admin controls will remain in the Admin menu to enable the classic environment if needed.

Final transition to the new Request Signature experience (July 2026)

With the July 2026 release, the classic Compose interface will be permanently retired. All accounts will now use the modern Request Signature experience as the standard way to configure new agreements.

What’s changing

In the October 2025 release:

All commercial accounts will be automatically switched to the modern Request Signature experience.
Switch links will remain enabled.
The option to configure or switch between the classic and modern environments will remain available in the admin settings.

In the March 2026 release:

All commercial accounts will be automatically switched to the modern Request Signature experience.
Switch links will be disabled.
The option to configure or switch between the classic and modern environments will remain available in the admin settings.

In the July 2026 release:

All commercial accounts will be automatically switched to the modern Request Signature experience.
Switch links will be disabled.
The controls to revert the experience to the classic environment will be removed.
The modern experience becomes the only available interface for composing agreements.

We recommend familiarizing your users with the modern experience before the release to ensure a smooth transition.

Rollout Schedule for the modern Create Template experience

First Reported: February 2025 - Updated August 2025	Current Bookmark this notice

The modern Create Template authoring experience in Acrobat Sign has been made available to all enterprise accounts. This updated interface streamlines creating reusable templates and will eventually fully replace the classic version.

All future enhancements will apply only to the new experience. The classic version will not receive updates or support for new features. We strongly recommend enabling the new experience now to stay aligned with ongoing improvements.

Rollout timeline

The new authoring environment is being promoted through the standard release cycle:

April 2025 (v16.0) for Commercial; July (v16.1)for GovCloud

The new experience becomes available for all enterprise accounts.
Admins can enable it at the account and group levels.
Once enabled, all users must use the new interface. There is no option to switch back from the user's perspective.

October 2025 (v16.2)

All new accounts default to the new experience.
Existing accounts are automatically promoted to the new experience, with the exception of accounts that share assets between multiple groups.
Admins can still revert their account to the classic experience through the admin configurable controls if needed.

March 2026 (v17.0)

All new accounts default to the new experience.
Existing accounts are automatically promoted to the new experience, including accounts that share assets between multiple groups.
Admins can still revert their account to the classic experience through the admin configurable controls if needed.

July 2026 (v17.1)

All accounts are permanently switched to the new experience.
The option to revert to the classic experience is expected to be removed from the admin controls.
The classic authoring environment is expected to be retired and no longer accessible.

For best results, enable the new experience early so your users have time to adjust before the transition becomes permanent.

Not:

Accounts that have enabled sharing templates across multiple groups are excluded from this update.

Classic reporting to be removed from service in March 2026

First Reported: September 2022 - Updated May 2025	Current Bookmark this notice

Classic reporting will be completely removed from the Acrobat Sign interface in March 2026. 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.

Rollout Schedule for the New Custom Workflow Designer

First Reported: April 2025	Current Bookmark this notice

The new Workflow Designer experience is being enabled for all existing accounts, replacing the classic version over time. During the transition, admins and users have some flexibility to revert to the previous interface until its full retirement.

Rollout Timeline

October 2025 (v16.2)

All existing accounts are automatically upgraded to the new Custom Workflow Designer.
Admins can revert to the classic experience using controls in the admin menu.
Users can switch between experiences using in-product switch links.

March 2026 (v17.0)

All accounts are again elevated to the new experience after the release (if not already).
Admins retain the ability to revert to the classic experience.
Users no longer see switch links; admins can enable them if needed.

July 2026 (v17.1)

All accounts are permanently moved to the new experience.
Admin controls to revert to the classic version are removed.
The classic Custom Workflow Designer is fully retired and no longer accessible.

We recommend preparing your users as soon as possible to ensure a smooth transition.

Not:

New accounts created after the July 2025 Acrobat Sign release will have the new experience enabled by default, and no controls will be present to step back to the legacy version.

The webhookNotificationApplicableUsers parameter is to be removed from the Webhook payload.
Sandbox is to be updated in the June 2025 release.
Production is to be updated in the July 2025 release.

First Reported: September 2024 - Updated April 2025	Current Bookmark this notice

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 June release.
The Production environments will be updated in the July 2025 release.

The sending userID and email can be found using the initiatingUserId and initiatingUserEmail parameters in the notification payload.

Adobe Acrobat Sign for Government accounts will have access to the new Request Signature experience after the July 2025 release.

First Reported: April 2025	Current Bookmark this notice

All accounts using the Acrobat Sign for Government service will gain access to enable the new Request Signature environment, along with several features recently created that are dependent upon it:

eWitnessing
Restricted access to agreements
Enforce signature type
Identity check
CCs per recipient
The recipient list and recipient properties are editable after authoring

Deprecation of the Adobe Acrobat Sign REST API v1-v4.
End of support and removal of legacy REST API versions on December 1, 2025.

First Reported: September 2024	Current Bookmark this notice

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.

External source drives to be removed from support in the new Request Signature experience

First Reported: May 2024	Current Bookmark this notice

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 Acrobat Sign SSL Certificate updates in January, 2025

First Reported: December 2024	Removed from Current list: February 2025 Bookmark this notice

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.

New Webhook limits for Developer tier accounts

First Reported: March 2025 - Updated: April 2025	Current Bookmark this notice

Starting after the May 2025 release, Acrobat Sign will implement stricter limits on the number of webhooks created in Developer-tier accounts.

These limits have been purposefully chosen to ensure the reliability of the webhooks infrastructure and better aligned for testing workflows.

What is changing	Previous limit	New Limit	Description
Number of active webhooks created per channel	10	1	1 webhook is allowed for the channel per webhook subscription event.
Number of active webhooks created for an account	100	2	2 account level webhooks are allowed per webhook subscription event.
Number of active webhooks created per group	100	2	2 group level webhooks are allowed per group per webhook subscription event.
Number of active webhooks created per agreement resource	50	1	1 webhook is allowed per agreement per webhook subscription event.
Number of active webhooks created per user	100	1	1 webhook is allowed per user per webhook subscription event.

Available environments: Commercial | Available tiers of service: Developer | Configuration scope: Enabled by default; Not configurable

Archived Notifications

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

Archive of Technical Notifications 2025 - 2026

Archive of Technical Notifications 2023 - 2024

Archive of Technical Notifications 2021 - 2022

Archive of Technical Notifications 2019 - 2020

Archive of Technical Notifications 2017 - 2018

Archive of Technical Notifications 2015 - 2016

Daha hızlı ve daha kolay yardım alın

Yeni kullanıcı mısınız?

Technical notifications

Review the Technical Notifications listed and bookmark the ones that are important to you.

[Next Release] The next Adobe Acrobat Sign release is scheduled for September 16, 2025

Feature Release: Adobe Acrobat Sign – July 22nd Release Completed

Current Notices:

In October 2025, the modern Recipient experience for e-signing will be promoted to the default environment for all Commercial and GovCloud accounts (v16.2).

All accounts switched to the modern environment; Admin settings remain

Acrobat Sign for Government to include IPv6 addresses in the system requirements on September 15, 2025

API polling threshold limit

What’s Changing

Examples of Affected Endpoints

Status Retrieval:

Listing:

Polling Policy Details

Action Required

In October 2025, the modern Request Signature environment will be promoted to the default environment for all accounts (v16.2). Classic Compose will be retired and removed from the commercial interface in the March 2026 (v17.0) release.

All accounts switched to the modern environment; Admin settings remain

Final transition to the new Request Signature experience (March 2026)

What’s changing

Adobe Acrobat Sign for Government accounts will promote the modern Request Signature environment for all accounts (v16.2 and v17.0). Classic Compose will be retired and removed from the interface in the July 2026 (v17.1) release.

All accounts switched to the modern environment; Admin settings remain

Final transition to the new Request Signature experience (July 2026)

What’s changing

Rollout Schedule for the modern Create Template experience

Rollout timeline

Classic reporting to be removed from service in March 2026

Rollout Schedule for the New Custom Workflow Designer

Rollout Timeline

The webhookNotificationApplicableUsers parameter is to be removed from the Webhook payload. Sandbox is to be updated in the June 2025 release. Production is to be updated in the July 2025 release.

Adobe Acrobat Sign for Government accounts will have access to the new Request Signature experience after the July 2025 release.

Deprecation of the Adobe Acrobat Sign REST API v1-v4. End of support and removal of legacy REST API versions on December 1, 2025.

Action Required

External source drives to be removed from support in the new Request Signature experience

Additional Resources

Adobe Acrobat Sign SSL Certificate updates in January, 2025

Action Required

New Webhook limits for Developer tier accounts

Archived Notifications

Daha hızlı ve daha kolay yardım alın

Bu sayfayı paylaş

Feature Release: Adobe Acrobat Sign – July 22^nd Release Completed

In October 2025, the modern Request Signature environment will be promoted to the default environment for all accounts (v16.2).
Classic Compose will be retired and removed from the commercial interface in the March 2026 (v17.0) release.

Adobe Acrobat Sign for Government accounts will promote the modern Request Signature environment for all accounts (v16.2 and v17.0).
Classic Compose will be retired and removed from the interface in the July 2026 (v17.1) release.

The webhookNotificationApplicableUsers parameter is to be removed from the Webhook payload.
Sandbox is to be updated in the June 2025 release.
Production is to be updated in the July 2025 release.

Deprecation of the Adobe Acrobat Sign REST API v1-v4.
End of support and removal of legacy REST API versions on December 1, 2025.