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 January 12, 2027 v18.0
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 – October 6th Release Completed
The release was completed to all shards with no downtime to any services.
Current Notices:
|
Status |
Issue or Event |
Execution Date |
|
Next Major Release |
January 2027 (v18.0) |
|
|
Next Major Release |
January 2027 (v18.0) |
|
|
Next Major Release |
January 2027 (v18.0) |
|
|
Next Major Release |
January 2027 (v18.0) |
|
|
Next Major Release |
January 2027 (v18.0) |
|
|
Next Major Release Rolling |
January 2027 (v18.0) |
|
|
Next Major Release Rolling |
January 2027 (v18.0) |
|
|
Next Major Release Rolling |
January 2027 (v18.0) |
|
|
Next 2 Major Releases Rolling |
January 2027 (v18.0) |
|
|
Pending |
2027 |
|
|
Recently Rolling |
Starting November 2, 2026 |
|
|
Current Recently |
Current |
|
Persistent Informational Notifications |
||
|
Current Informational |
Current |
|
|
Current Informational |
Current |
|
|
Current Informational |
Current |
|
|
Current Informational |
Current |
|
First Reported: October 2026 |
Current |
|---|
Adobe Acrobat Sign is introducing a new Review & Send step with release 18.0, beginning January 12, 2027. The feature allows senders to review agreement documents and recipient fields before sending. Availability and default settings vary by account licensing type.
Customer impact
The Review & Send experience introduces an additional step in the agreement sending process.
Account and group administrators can configure the feature under Send Settings using three options:
Disabled: Senders continue using the existing sending experience.
Optional: Senders can review agreements before sending or send directly from document preparation.
Mandatory: Senders must enter the review step before sending agreements.
The feature is not available for:
- Accounts that use Acrobat Sign's legacy (native) user management system.
- Acrobat Sign for Government.
- Custom workflows and library templates.
Timeline
| Date | Environment | Eligible accounts | Default setting value at launch |
|---|---|---|---|
| November 17, 2026 | Sandbox | Enterprise ETLA accounts | Optional |
| January 12, 2027 | Commercial | VIP / VIPMP / Adobe Acrobat Sign Trials | Mandatory |
| January 19, 2027 | Commercial | Enterprise ETLA accounts | Optional |
Recommended action
Account and group administrators should review the configuration under Send Settings when the feature becomes available.
Accounts configured as Mandatory require senders to enter the review step before sending. Administrators can change this setting to Optional or Disabled based on their organization's sending requirements.
|
First Reported: October 2026 |
Current |
|---|
With the Adobe Acrobat Sign 18.0 release, scheduled sending will be enabled by default for supported accounts. This feature allows senders to prepare agreements and schedule their delivery for a future date and time. Administrators cannot disable Scheduled Send through the Acrobat Sign interface.
Customer impact
Scheduled Send allows agreements to be scheduled from 30 minutes to 30 days in advance.
The feature is enabled by default, with no customer-facing account or group setting to disable it.
Administrators must contact Adobe Support to request disablement.
Disabling Scheduled Send prevents new agreements from being scheduled but does not cancel or prevent delivery of agreements already scheduled.
Previously scheduled agreements must be managed individually by the original sender or an authorized user with access through Advanced Sharing.
|
First Reported: March 2026 |
Current |
|---|
Inline document editing during authoring is being deployed through a phased rollout as part of the 17.1.2 release for VIP accounts and continues through 17.2.
Rollout schedule:
VIP and VIPMP customer accounts receive a gradual production rollout following the 17.1.2 release.
Inline document editing will be included in the 18.0 Sandbox deployment, and made generally available for ETLA customers after the 18.0 release.
For VIP accounts, the feature is enabled by default at the account level for both new and existing supported accounts. Account and group admins can enable or disable the feature as needed.
ETLA accounts will see the feature disabled by default, with the same controls available at the account and group level for enablement as needed.
The feature is not supported for:
- Acrobat Sign for Government accounts.
- Organizations using the legacy Acrobat Sign user management system.
For configuration instructions, see Enable or disable inline document editing
For sender workflow instructions, see How to edit text during field authoring
Schedules for the rollout are subject to change, dependent on emergent events.
|
First Reported: February 2025 - Updated November 2026 |
Current |
|---|
In the 18.0 release (January 2027), all Commercial and Government accounts will be updated to use the modern Request Signature environment.
What’s changing
In the January 2027 release (v18.0):
- All 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 from the UI.
We recommend familiarizing your users with the modern experience before the release to ensure a smooth transition.
|
First Reported: February 2025 - Updated November 2026 |
Current |
|---|
In the 18.0 release (January 2027), all Commercial and Government accounts will be updated to use the modern Create Template experience.
What’s changing
In the January 2027 release (v18.0):
- All accounts will be automatically switched to the modern Create Template experience.
- Switch links will be removed.
- The controls to revert the experience to the classic environment will be removed from the UI.
We recommend familiarizing your users with the modern experience before the release to ensure a smooth transition.
|
First Reported: April 2025 - Updated September 2026 |
Current |
|---|
The modern Compose page (produced by the modern Workflow Designer) is being enabled for all existing accounts, replacing the classic Compose experience. During the transition, administrators and users can continue to use the available fallback controls to return to the classic experience until its full retirement.
Rollout Timeline
January 2027 (v18.0)
- 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.
May 2027 (v18.1)
- All accounts are permanently moved to the new experience.
- Admin controls to revert to the classic version are removed.
- The classic Compose experience 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: September 2022 - Updated June 2026 |
Current |
|---|
Classic reporting will be completely removed from the Acrobat Sign interface in 2027. 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: March 2026 |
Current |
|---|
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
- For additional industry details, refer to DigiCert’s announcement:
Need Help?
If you have questions about certificate rotation or need assistance validating your integration, contact Adobe Support or your Adobe account representative.
|
First Reported: August 2025 - Updated February, 2026 |
Current |
|---|
To help maintain system stability and improve performance, Adobe Acrobat Sign is introducing a polling threshold for GET API endpoints. This policy limits how frequently client applications can make identical API calls to the Acrobat Sign service.
High-frequency polling creates unnecessary load on backend systems, which can degrade performance and slow response times. API developers are encouraged to use webhooks for near real-time updates instead of repeated polling.
What’s changing
The polling policy applies to all GET API endpoints for identical calls.
A limit is applied to how often the same effective user can make the same API call to Acrobat Sign. An error is returned when the same effective user makes identical calls more frequently than the applicable polling threshold allows.
For example, a repeated request to the same endpoint for the same agreement or library document is treated as an identical call. Requests for different agreements or library documents are treated as distinct calls because each object represents a different request target.
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, events, and library documents
- GET /agreements — Retrieves agreements for the user.
- GET /agreements/{agreementId}/events — Retrieves event information for an agreement.
- GET /libraryDocuments — Retrieves library documents for the user.
- GET /libraryDocuments/{libraryDocumentId} — Retrieves information for a specific library document.
Polling policy details
The Minimum Object Polling Interval (MOPI) defines how often the same effective user can make the same GET API request to the Acrobat Sign service.
The default MOPI varies by service tier:
- GLOBAL, ENTERPRISE, and DEVELOPER tiers: Three identical calls per one-minute interval.
- All other tiers: Three identical calls per three-minute interval.
If the same effective user makes identical GET requests more frequently than the tier allows, Acrobat Sign returns a 429 Too Many Requests response with a Retry-After header.
A request is considered identical when the same effective user makes the same GET request with the same request path and headers within the applicable polling interval.
ETag handling
Applications may continue to use ETags and the If-None-Match header for endpoints that support conditional GET requests.
For conditional GET requests that are allowed under the polling threshold, Acrobat Sign may return 304 Not Modified when the resource has not changed.
When the polling threshold is exceeded, Acrobat Sign returns 429 Too Many Requests with a Retry-After header, even when the request includes an If-None-Match header.
Action required
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 use client-side caching to store and reuse API responses.
- When a 304 Not Modified response is received, use the cached data instead of making another API call.
- When a 429 Too Many Requests response is received, retry the API call only after the number of seconds provided in the Retry-After header.
Resources
- Handling 429 responses: https://developer.adobe.com/acrobat-sign/docs/overview/developer_guide/apiusage#handling-rate-limiting-http-429
- API polling threshold: https://developer.adobe.com/acrobat-sign/docs/overview/developer_guide/apiusage#get-endpoints
Timeline
The updated MOPI thresholds are already in production.
- The updated ETag throttling behavior is included in the 17.1.1 release. After this change, Acrobat Sign returns 429 Too Many Requests for throttled requests, including conditional GET requests that include an If-None-Match header.
- The polling policy is set to ENFORCED for new accounts in the Sandbox environment on February 11, 2026.
- The polling policy is set to ENFORCED for new accounts in the Production environment on April 5, 2026.
Please contact your CSM if you need assistance or have any questions.
|
First Reported: February 2026 |
Current |
|---|
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.
|
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
Archived Notifications
Listed by the date when the notice was removed from the current notice list, most recent to oldest.
Streamline your work with Acrobat Sign
Manage and sign documents online quickly and easily.
