With the Acrobat Sign 17.2 release this month, Adobe is switching every Commercial and Government account over to the modern Request Signature and Create Template environments, and turning off the link that let people switch back. If your team still relies on the classic send screen, this is the release that ends the choice.
What the 17.2 release actually does
Adobe's own technical notifications describe two changes landing together. All Commercial and Government accounts move to the modern Request Signature environment for building and sending agreements, and separately to the modern Create Template experience for building reusable templates. The switch link that let a user flip back to the classic screen is disabled for both Commercial and Govcloud accounts.
It is not a full removal, at least not yet. Admin controls remain available in the Admin menu for accounts that genuinely need to fall back to the classic compose experience, and Adobe has said that full removal of even those fallback controls is planned for a later release. Classic reporting is a separate casualty on a separate clock: Adobe has said it will be removed entirely in 2027, at which point the switch link disappears along with the scheduled reports that depend on it.
This has been coming since the 17.0 release in January 2026 quietly moved every account to the modern signing environment for recipients. 17.2 is the step that removes the opt out for the people sending the agreements, not just the people signing them.
The backlash is not subtle
Adobe's own community forums carry threads with titles like "NO MORE SWITCH TO CLASSIC EXPERIENCE," and the complaints are specific rather than general nostalgia. One frequently echoed comment on the community boards describes a bulk send job with multiple signature fields that used to take about ten minutes now taking closer to an hour in the modern interface. Others report that admin accounts which previously had a working path back to classic no longer do.
Adobe's response, visible in the same threads, has been to acknowledge the change is disruptive and to say feature parity work is ongoing, rather than to reverse course. That is a familiar pattern for anyone who has lived through a forced UI migration: the vendor's roadmap and the customer's Tuesday deadline are not running on the same schedule.
Why this matters even if you rarely touch Acrobat Sign
Acrobat Sign is embedded in a lot of places that are not obviously "the signing app": approval steps inside Workday and Salesforce, HR onboarding packets, procurement systems, real estate transaction platforms. A bulk send workflow that quietly gets six times slower does not show up as an outage. It shows up as a team that starts finding workarounds, some of which involve emailing PDFs around and losing the audit trail that was the entire point of using an e-signature platform in the first place.
If grouped fields, bulk sends, or templated agreements are part of your process, worth testing the modern environment against a real document before the fallback disappears, not after.
What to actually do this week
- Test your heaviest workflow in the modern environment now, while the classic fallback still exists for admins. A bulk agreement with multiple signature fields and validation rules is the scenario most likely to expose a regression, so that is the one to test first, not the simplest form you can find.
- Check who has admin access to the fallback toggle. If the person who knows where that setting lives is not the person doing the sending, write it down somewhere the team can find it before it matters.
- Export or archive anything sitting in classic reporting. With that feature gone entirely in 2027 and no path back once it lands, a scheduled report you rely on for audit purposes needs a home outside Acrobat Sign before then.
- Separate the signature step from your document prep. Tools that build and edit the PDF itself, including browser based editors like Docento.app, sit outside this migration entirely. Preparing a clean, final PDF before it reaches any signing platform means a rocky vendor transition affects one step of your process instead of the whole thing.
None of this is a crisis. It is a vendor moving its own product forward on its own timeline, and the timeline happens to be this month. The organizations that will feel it least are the ones that tested the new environment against a real workload before the old one stopped being an option.
