NOTE: an earlier version of the article contained incomplete information regarding this process. Please read below for more detail.
Recently Cisco Umbrella has added a feature flag that allows our customers to put roaming client devices on the 'stage' track, in advance of mainline releases.
Where possible, we encourage customers to have two orgs, one for production and one for acceptance testing and beta testing new features. This feature enables customers to have two 'tracks' for a subset of machines to encourage quicker adoption of the new releases after passing your internal QA/acceptance testing.
Method/What to do
The official method to do internal testing of client updates is to have certain devices on our staging track. You can do this for some devices in their org, or create a separate org for testing.
First, and most importantly, you should subscribe to updates on our release notes page. We post all roaming client release notes there, as soon as they hit the ‘stage’ track. This lets you know when a new version is available for testing to machines on the stage track.
If you observe any incompatibility issues or regressions while the build is in staging, we will prioritize investigating it and will usually halt the release process until such time that the issue can be addressed.
For exact instructions, any questions or more information, please contact support at email@example.com