Review the Technical Notifications listed and bookmark the ones that are important to you.
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 July 22, 2025
This major release will introduce feature enhancements for users and administrators and resolutions to customer-reported issues.
Customers with a Sandbox entitlement will gain access to the new features four weeks before launch, along with prerelease documentation outlining the release content.
Feature Release: Adobe Acrobat Sign – May 20th Release Completed
The release was completed to all shards with no downtime to any services.
Current Notices:
|
Status |
Issue or Event |
Execution Date |
|
Updated |
March, 2026 |
|
|
Updated |
March 17, 2026 |
|
|
Updated |
October 7, 2025 |
|
|
New |
October 7, 2025 |
|
|
Updated Next Release |
May 22, 2025 |
|
|
New |
July, 2025 |
|
|
New Next Release |
May 20, 2025 |
|
|
Updated Next Major Release |
July, 2025 |
|
|
Next Major Release |
July 22, 2025 |
|
|
Pending |
December 1, 2025 |
|
|
Recently |
Current |
|
|
Recently |
Current April 22, 2025 |
|
|
Recently |
Current April 22, 2025 |
|
|
Recently |
Current April 22, 2025 |
|
|
Recently |
Current April 22, 2025 |
|
|
Recently |
Current March 1, 2025 |
|
|
Informational |
Current |
|
First Reported: September 2022 - Updated May 2025 |
Current |
|---|
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.
This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.
|
First Reported: February 2025 - Updated May 2025 |
Current |
|---|
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 new Request Signature experience as the standard way to configure new agreements.
What’s changing
- All commercial accounts will be automatically switched to the new Request Signature experience.
- The option to configure or switch between the classic and new environments will be removed from the admin settings.
- The new experience becomes the only available interface for composing agreements.
We recommend familiarizing your users with the new experience before the release to ensure a smooth transition.
|
First Reported: February 2025 - Updated May 2025 |
Current |
|---|
As of the April 2025 release, most accounts can access the new Create Template authoring experience in Acrobat Sign. 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)
- 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 elevated to the new experience.
- Admins can still revert their account to the classic experience through the admin configurable controls if needed.
March 2026 (v17.0)
- All accounts are permanently switched to the new experience.
- The option to revert to the classic experience is removed from the admin controls.
- The classic authoring environment is 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.
Accounts that have enabled sharing templates across multiple groups are excluded from this update.
|
First Reported: April 2025 |
Current |
|---|
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.
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.
|
First Reported: March 2025 - Updated: April 2025 |
Current |
|---|
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
|
First Reported: September 2024 - Updated April 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 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.
|
First Reported: April 2025 |
Current |
|---|
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
|
First Reported: March 2025 |
Current |
|---|
In the May 2025 release, we’re optimizing the GET /agreements API to significantly reduce response times—our internal testing shows improvements of up to 10x.
What’s changing
- Smaller page sizes: To support these improvements, we’ve reduced the maximum number of agreements returned per request to 500, but this limit may change in future releases. Each response includes:
- The actual number of agreements returned
- A link to the next page of results (if available)
- Dynamic result count: You can still request a specific number of agreements, but the API will return as many as the service can provide. Each response includes:
What to expect
In some cases, there may be a slight delay between creating an agreement and retrieving it using the GET /agreements API. This delay is typically very short; a follow-up request should return the new agreement.
Available environments: Commercial, Government | Available tiers of service: Acrobat Sign Services, Government | Configuration scope: Enabled by default; Not configurable
|
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: 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: 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 Acrobat Sign Innovation Series - Monthly Webinar covering the hottest topics in the Acrobat 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.
Archived Notifications
Listed by the date when the notice was removed from the current notice list, most recent to oldest.
