Currently versions of Adobe Acrobat suite have 2 forms of updates.
Manual and Auto.
Unfortunately on the auto update, Minimal controls exist. So corporate users have to either deploy a server to host all auto updates and publish as they become available. OR accept that the latest version will be applied immediately as they become available.

The hosted server, is an option, but will put further pressure on VPN's as users are most likely to work in a hybrid home/office environment.

What would be useful is borrowed from googles approach with Chrome, where a simple policy or registry key can be applied via GPO to indicate the MAXIMUM installed version for auto updated.

This would mean administrators can:
Deploy to production - 21.01
Deploy to test - 21.05
and control the release cycle by simple GPO adjustment.

The other choice has too many risks, which is the current behaviour, to deploy a version (for example 20.05) and turn on auto updates at specific points of the month. On continuous updates, that means disabling the updater and will mean new built machines may stay STUCK on initial 20.05 release for a test cycle, rather than going to the last ACCEPTED build.