The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c6918431c57bfc1c6f807d8dad8e6e3c96b937f0

commit c6918431c57bfc1c6f807d8dad8e6e3c96b937f0
Author: Yves Arrouye <drcrash@google.com>
Date: Tue Oct 02 16:47:02 2018

Add Zero-Touch to the options for initial enrollment

When the management server sends this new option, wire it to an
unescapable Zero-Touch flow.

Bug: chromium:891281
Test: N/A for now as the server doesn't return this option
Change-Id: Iaaa3dd531ccb8f8a5fb2788ca61171ad8abc487e
Reviewed-on: https://chromium-review.googlesource.com/1256906
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Yves Arrouye <drcrash@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595878}
[modify] https://crrev.com/c6918431c57bfc1c6f807d8dad8e6e3c96b937f0/chrome/browser/chromeos/policy/auto_enrollment_client_impl.cc
[modify] https://crrev.com/c6918431c57bfc1c6f807d8dad8e6e3c96b937f0/components/policy/proto/device_management_backend.proto

M-71 is going to Stable this week.  Should this feature be moved to target another milestone?