Adobe Acrobat Sign release schedule and prerelease documentation
Adobe Acrobat Sign rolls out at least three updates per year, categorized as major or minor releases. Additional minor updates may be introduced as needed to address system or customer issues.
- Major Releases bring significant updates, new features, and multiple enhancements.
- Minor Releases focus on smaller improvements and user experience tweaks. These occur between major updates, typically one to two times per cycle.
To prevent disruptions, new features are disabled by default and must be manually enabled by an account or group admin.
For Health and Life Sciences customers requiring compliance validation, Acrobat Sign partners with a third-party vendor to provide a validation package for every major release containing features to minimize your risk factor.
This Prerelease Notes page is regularly updated as new information becomes available, so its content is relatively dynamic.
While this page is localized, the process takes time, which may result in localized versions differing slightly from the authoritative US English version.
For the most accurate and up-to-date information, we recommend referring only to the US English page.
Adobe Acrobat Sign follows a structured schedule for publishing release notes and documentation updates:
8 Weeks Before Production Release
- The prerelease page publishes a summary of expected features and updates, typically four weeks before the Sandbox launch.
- Any feature changes after this point are noted in the Errata section.
- Resolved issues are not included at this stage.
4 Weeks Before Production Release (Sandbox Launch)
- The prerelease page is updated with detailed documentation on new and updated features.
- Links to prerelease support documentation (available in US English only) are added as needed.
- The initial Resolved issues section is published, with ongoing updates over the next four weeks.
Launch Day
- The official release notes are updated with final feature details and links to production support documentation.
- The prerelease page is refreshed to highlight the next release cycle.
- Documentation is published after release verification in the live system, typically after 7 pm PT, though complex updates may take longer.
- The final Resolved issues list is added to the US English release notes, with localized versions updated later.
Government Cloud Release
- The Government Cloud environment typically updates between two days and several weeks after the production release, as some features may require additional evaluation before deployment.
Sandbox documentation is designed for the production environment. Links found in the prerelease content target production URLs, meaning those links may lead to older existing documentation or 404 results if the target page is new and hasn't been published yet (e.g., when the link is pointing to a new feature in the same release).
The new pages will be published when the release is published, and links will properly resolve to their production URLs.
Sandbox availability
Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.
- The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
- Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
- The Sandbox environment uses the same status page and outage procedures as the regular Production environment.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Adobe Acrobat Sign release v17.0.1
Sandbox deployment: February 17, 2026
Production deployment: March 17, 2026
GovCloud deployment: March 19, 2026
REST API/Webhook Updates
The below updates are presented in the prerelease notes for disclosure purposes. Full documentation for API and Webhook updates can be found in the Acrobat Sign developer documentation when the version update is delivered to the production servers.
- OEM 2.0 personalized email display – Clearer sender and recipient identity across embedded experiences, and correct email delivery.
For OEM 2.0 embedded workflows, Acrobat Sign now displays a user’s personalized email address instead of the partner-registered email across key UI surfaces and notifications. Agreements, queues such as “Waiting for you,” and “Review and Sign” emails consistently reflect the personalized identity while preserving the registered email internally for authentication and entitlements. This improves clarity for senders and signers and prevents emails from being sent to non-deliverable registered addresses.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: API
- Webhook notification for SMS delivery failures – Real-time visibility into failed SMS sends, automated remediation, and parity with email bounces.
Acrobat Sign now emits a new webhook event, AGREEMENT_PHONE_BOUNCED, when an agreement sent via SMS cannot be delivered due to issues such as invalid phone numbers, carrier rejection, or blocked lines. This enables customers to detect SMS delivery failures in near real time and automatically trigger follow-up actions like correcting phone numbers, retrying delivery, or opening support cases, eliminating blind spots and reducing delays in mobile-first signing workflows.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: API
Release errata
There are no items that have slipped from this release as of this time.
