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 May 05, 2026 v17.1

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.

The release schedule and prerelease notes can be reviewed here >

Feature Release: Adobe Acrobat Sign – March 17^th Release Completed

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

Current Notices:

Status	Issue or Event	Execution Date
New	Planned maintenance impacting provisioning login	April 11, 2026
New Current	API document ID format update	March 17, 2026
New Current	Integration key's expiry date exposed	March 17, 2026
New	Audit reports to record the signature method	May 5, 2026
New Important	SSL Certificate rotations are accelerating	Starting March 2026
Updated Next Major Release	API Polling Threshold	May 5, 2026
Updated Current Rolling Release	Updated login experience	February 3, 2026
Next Major Release	Home page update	May 5 - 10, 2026
Current	Create a Copy controls to be removed from Admin UI	March 17, 2026
Current Informational	SMS delivery is blocked in Thailand	Current
Current	Modern e-signing experience to be promoted in February 2026.	February, 2026
Next Major Release	Modern Request Signature to be promoted in May 2026.	May, 2026
Next Major Release	Modern Request Signature to be promoted for all GovCloud accounts in May 2026	May, 2026
Rolling Release	Modern Create Template Experience Rollout Schedule	May, 2026
Rolling Release	Custom Workflow Rollout Schedule	May, 2026
Pending	Classic Reporting to be removed from service in June 2026	June, 2026
Current Informational	External source drives are not supported in the modern Request Signature environment.	Current

Planned maintenance may affect provisioning and login on April 11, 2026 at 7:30 pm Pacific Time.

First Reported: March 2026	Current Bookmark this notice

A planned database maintenance activity is scheduled for April 11, 2026, at 7:30 pm Pacific Time. The maintenance window is expected to last up to 30 minutes.

This maintenance will affect all Acrobat Sign environments and applies only to Adobe-managed accounts (IMS). Accounts that manage their users directly within Acrobat Sign are not affected.

During this time:

New account creation and user provisioning will be delayed.
A limited number of users may experience sign-in issues.
Account transaction consumption requests from Adobe administrative interfaces may fail, which can temporarily prevent entitlement assignment.

All affected services are expected to return to normal operation when the maintenance is complete.

API document ID format update

First Reported: March 2026	Current Bookmark this notice

Document IDs returned by the API now use a 16-bit encoding format instead of the previous 12-bit encoding format and may include trailing asterisk characters as part of the returned value. Acrobat Sign accepts document IDs with or without these trailing characters, but some applications may not handle the expanded format correctly, which can affect document retrieval or display.

This update reflects a change in document ID handling in the service. If your integration retrieves documents using document IDs returned by the API, review your current logic to ensure it supports the longer ID format and can accept the returned value as provided. If needed, trailing asterisk characters can be omitted before retrying the request.

Direct access through Acrobat Sign is not expected to be impacted.

Integration key expiration dates visible in Access Tokens

First Reported: March 2026	Current Bookmark this notice

As of the 17.0.1 release on March 17, the Access Tokens tab in the Personal Preferences menu displays the expiration date for each Integration key. This update improves visibility into key lifecycle management by allowing key holders to see when a key will expire.

Integration keys have a 10-year validity period. After the expiration date, the key can no longer be used and must be replaced with a new key.

This change does not affect how existing keys function and does not modify the key lifecycle. It only exposes the expiration date in the interface so administrators can monitor key age and plan replacements in advance.

No action is required. Administrators should periodically review their Integration keys and replace any that are approaching expiration to avoid service interruptions.

The "Access Tokens" tab with the integration key expiry date highlighted.

Audit reports to record the signer's signature method (Typed, Drawn, Uploaded, Mobile_Type) May 5, 2026

First Reported: March 2026	Current Bookmark this notice

Beginning with the May 5, 2026 release, Audit Reports will record the signature method used when a signer applies their signature.

For each ESIGNED and DIGSIGNED event, the audit trail identifies whether the signer used a desktop-based signature method (TYPE, DRAW, IMAGE) or a mobile-based signature method (MOBILE_TYPE, MOBILE_DRAW, MOBILE_IMAGE).

This update improves compliance visibility by allowing administrators and compliance teams to verify the signature method directly in the audit report, reducing ambiguity and minimizing unnecessary agreement rejections during review and audit processes. This update is enabled by default for all customers, with no configuration option.

Not:

Applying a signature only with a stamp is not included in the types of signatures identified.

SSL/TLS certificate rotation updates: transition to shorter certificate validity periods underway

First Reported: March 2026	Current Bookmark this notice

SSL/TLS Certificate Rotation Updates – Transition to Shorter Validity Periods

The SSL/TLS industry is transitioning to significantly shorter certificate validity periods. This change is driven by updates from the CA/Browser Forum (the governing body for publicly trusted certificates) and is being adopted across major certificate authorities (CAs), including DigiCert.

As a result, certificate lifetimes will gradually reduce from the current ~398 days to as short as 47 days over the next several years.

What Is Changing?

The maximum validity period for publicly trusted TLS certificates will be reduced to 47 days. This requirement is defined by the CA/Browser Forum and applies industry-wide.

Why Is This Change Happening?

Shorter certificate lifetimes improve security by:

Reducing the exposure window if a certificate or private key is compromised
Limiting reliance on certificate revocation mechanisms
Encouraging automated certificate lifecycle management
Improving overall internet security posture

Major browser vendors (Google, Apple, Mozilla, Microsoft) support this transition.

For additional industry context, see DigiCert’s announcement:
TLS Certificate Lifetimes Will Officially Reduce to 47 Days

How This Affects You

Increased Certificate Rotation Frequency
- Certificates will rotate more frequently as maximum validity periods decrease.
Automation Is Required
- Due to the shorter validity periods, certificate renewals are expected to be fully automated. Manual renewal processes are not sustainable at this frequency.

If your environment depends on certificate pinning, manual trust stores, or static certificate references, review your configuration to ensure compatibility with frequent renewals.

Customer Notifications

Previously, notifications were sent when certificates rotated on an annual basis.

Effective at the end of June 2026, routine notifications for standard certificate rotations will be discontinued.

With shorter validity periods and automated renewals:

Routine certificate rotations will not generate customer notifications.
Notifications will be sent only in cases of:
Renewal failures
Service impact
Customer action required

This approach aligns with industry best practices for automated certificate lifecycle management.

No Action Required (If Automation Is Enabled)

If your integration relies on standard TLS trust validation and does not depend on certificate pinning, no action is required.

Certificates will continue to renew automatically before expiration.

When Action May Be Required

You may need to take action if:

You use certificate pinning (SPKI or full certificate pinning)
You maintain manual certificate stores
You have firewall rules tied to specific certificate fingerprints
You operate systems that do not support automated certificate updates

If unsure, consult your security or infrastructure team.

Frequently Asked Questions

Is this an Adobe-specific change?
- No. This is an industry-wide change mandated by the CA/Browser Forum and implemented by all major certificate authorities.
Will service availability be affected?
- No. Certificates will renew automatically prior to expiration. There is no expected downtime as part of normal rotation.
When will certificate rotation notifications stop?
- Routine certificate rotation notifications will stop at the end of June 2026. Customers will continue to be notified only if action is required or if an issue impacts service.
Where can I learn more?
- For additional industry details, refer to DigiCert’s announcement:
  https://www.digicert.com/blog/tls-certificate-lifetimes-will-officially-reduce-to-47-days

Need Help?

If you have questions about certificate rotation or need assistance validating your integration, contact Adobe Support or your Adobe account representative.

API polling threshold limit

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

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

Customers have several months following the 16.2.1 release to implement the recommended polling changes in their code. During this time window, the system will only LOG the polling interval threshold events.
After May 5, 2026, the polling protection policies will be switched to ENFORCE, and the errors will start triggering for users.

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.

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 and application types:
- Acrobat Sign partner applications: The MOPI for a partner app is determined by the tier of the user’s account.
  - GLOBAL/ENTERPRISE tier: 3 calls per one‑minute interval
  - All other tiers: 1 unique call per ten‑minute interval
- Customer applications under Global/Enterprise accounts: Three identical calls per one-minute interval.
- Customer applications under Developer accounts: One unique call per 10-minute interval.
Duplicate Requests Within MOPI: If the same effective user makes identical GET requests (same path and headers) more than their tier allows 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.
When a 429 Too Many Requests response is received, retry the API call after the number of seconds provided in the Retry-After header.
- Handling 429 responses: https://developer.adobe.com/acrobat-sign/docs/overview/developer_guide/apiusage#handling-rate-limiting-http-429

Customers have several months following the 16.2.1 release to implement the recommended polling changes in their code. During this time window, the system will LOG the polling interval threshold events.
After May 5, 2026, 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.

Update to the Acrobat Sign Home page in the May 5th release (v17.1)

First Reported: February 2026	Current Bookmark this notice

The Acrobat Sign Home page is being redesigned to make it easier to start agreements, monitor activity, and access key features, including the ability to copy recently sent agreements, view action tiles in a more intuitive order, quickly identify In Progress and Waiting for You items, and experience a streamlined What’s New banner that reduces visual clutter, helping users move faster, reduce missed agreements, and navigate a more focused Home experience.

The new Home page will be released across 10 days after the release:

Date	Shards
May 5, 2026	IN1, JP1, AU1, SG1
May 11, 2026	EU1, EU2
May 14, 2026	NA1, NA2, NA3, NA4

Not:

The rollout schedule is provided as a guideline and may be adjusted as the rollout progresses.

Create a copy – Removal of admin controls on March 17, 2026.

First Reported: February 2026	Current Bookmark this notice

The administrative setting to enable or disable Create a copy will be removed in the March 17, 2026, release. The feature will remain enabled for all eligible users by default, ensuring consistent access to agreement reuse across accounts.

SMS delivery is blocked in Thailand

First Reported: February 2026	Current Bookmark this notice

Summary
Due to updated regulatory requirements in Thailand, Agreement Delivery via SMS is currently not supported for recipients with Thai phone numbers.

What’s changing
Thailand has introduced updated regulations that restrict SMS messages containing URLs from directing recipients to flows that require user interaction. Because signing an agreement requires recipient interaction, SMS delivery for this use case is restricted.

Who is affected

Agreements sent using Agreement Delivery via SMS.
Recipients with Thai (+66) phone numbers.

Impact
Recipients with Thai phone numbers may not receive SMS messages containing agreement links. As a result, recipients may be unable to access and complete the signing process when SMS delivery is used.

This limitation is regulatory in nature and is not caused by a service outage or product defect.

Timing
There is currently no confirmed timeline for when this restriction may be lifted or a technical solution will be applied. This notice will be updated when conditions change.

Required actions

Do not use Agreement Delivery via SMS for recipients with Thai phone numbers.
Include email as an alternative delivery method to ensure agreement delivery.

Additional details
This limitation applies only to SMS-based delivery. Other agreement delivery and authentication methods are not affected.

Updated Login experience for all users

First Reported: December 2025 - Updated February 2026	Current Bookmark this notice

The Acrobat Sign login page experience will be updated for all users as part of the 17.0 release, scheduled for February 3, 2026. - The new login process offers a cleaner and more consistent experience by requesting all users to provide their email address, and nothing else. As soon as the email address is accepted, the user's account is referenced, and the follow-up page displays the authentication options the account is configured to use, eliminating unnecessary steps and legacy screens. This makes logging in faster, simpler, and more intuitive for everyone.

As part of the new login experience, the email format for Acrobat Sign enterprise users who log directly into the web interface now enforces a 64-character limit to the local part of an email address (the portion before the “@” symbol).

This updated login experience is being rolled out in phases by the Acrobat Sign server environment. The rollout schedule is shown below:

Acrobat Sign environment	Rollout date
IN1 (India) SG1 (Singapore)	03 February, 2026
AU1 (Australia) NA3 (North America)	10 February, 2026
JP1 (Japan)	17 February, 2026
EU2 (Europe) NA4 (North America)	02 March, 2026
EU1 (Europe) NA2 (North America)	05 March, 2026
NA1 (North America)	10 March, 2026

Not:

The rollout schedule is provided as a guideline and may be adjusted as the rollout progresses.

In January 2026, the modern Recipient experience for e-signing will be promoted to the default environment for all Commercial and GovCloud accounts (v17.0).

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

All accounts switched to the modern environment

In the 17.0 release (Jan. 2026), all accounts will be updated to use the modern e-signing environment.

Not:

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

In May 2026, the modern Request Signature environment will be promoted to the default environment for all accounts (v17.1).
Classic Compose will be retired and removed from the commercial interface.

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

In the 17.1 release (May 2026), all commercial accounts will be updated to use the modern Request Signature environment.

Switch links will be removed
Admin controls in the Admin menu will be removed

All GovCloud accounts will be switched to the modern environment, and the Admin settings will remain.

What’s changing

In the May 2026 release (17.1):

All commercial and govcloud accounts will be automatically switched to the modern Request Signature experience.
Switch links will be disabled for both commercial and govcloud accounts
The controls to revert the experience to the classic environment will be removed for commercial accounts; Settings remain for the govcloud accounts

In the September 2026 release (17.2):

All govcloud accounts will be automatically switched to the modern Request Signature experience.
Switch links will be removed.
The controls to revert the experience to the classic environment will be removed.

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 in May 2026 (v17.1).
Classic Compose will be retired and removed from the interface in the September 2026 (v17.2) release.

First Reported: August 2025 - Updated Oct, 2025	Current Bookmark this notice

All accounts switched to the modern environment; Admin settings remain

In the 17.1 release (May 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 (September 2026)

With the September 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 May 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 September 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.

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 October 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.

May 2026 (v17.1)

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.

September 2026 (v17.2)

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.

Classic reporting to be removed from service in June 2026

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

Classic reporting will be completely removed from the Acrobat Sign interface in June 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 - Updated October 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

May 2026 (v17.1)

All accounts are 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.

September 2026 (v17.2)

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.

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

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 May 05, 2026 v17.1

Feature Release: Adobe Acrobat Sign – March 17th Release Completed

Current Notices:

Planned maintenance may affect provisioning and login on April 11, 2026 at 7:30 pm Pacific Time.

API document ID format update

Integration key expiration dates visible in Access Tokens

Audit reports to record the signer's signature method (Typed, Drawn, Uploaded, Mobile_Type) May 5, 2026

SSL/TLS certificate rotation updates: transition to shorter certificate validity periods underway

SSL/TLS Certificate Rotation Updates – Transition to Shorter Validity Periods

What Is Changing?

Why Is This Change Happening?

How This Affects You

Customer Notifications

No Action Required (If Automation Is Enabled)

When Action May Be Required

Frequently Asked Questions

Need Help?

API polling threshold limit

What’s Changing

Examples of Affected Endpoints

Status Retrieval:

Listing:

Polling Policy Details

Action Required

Update to the Acrobat Sign Home page in the May 5th release (v17.1)

Create a copy – Removal of admin controls on March 17, 2026.

SMS delivery is blocked in Thailand

Updated Login experience for all users

In January 2026, the modern Recipient experience for e-signing will be promoted to the default environment for all Commercial and GovCloud accounts (v17.0).

All accounts switched to the modern environment

In May 2026, the modern Request Signature environment will be promoted to the default environment for all accounts (v17.1). Classic Compose will be retired and removed from the commercial interface.

What’s changing

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

All accounts switched to the modern environment; Admin settings remain

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

What’s changing

Rollout Schedule for the modern Create Template experience

Rollout timeline

Classic reporting to be removed from service in June 2026

Rollout Schedule for the New Custom Workflow Designer

Rollout Timeline

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

Additional Resources

Archived Notifications

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

Bu sayfayı paylaş

Feature Release: Adobe Acrobat Sign – March 17^th Release Completed

In May 2026, the modern Request Signature environment will be promoted to the default environment for all accounts (v17.1).
Classic Compose will be retired and removed from the commercial interface.

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