This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Devices set up in offline mode will be able to connect to available networks. Otherwise behavior will be similar to online mode.

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

commit 34b8b1f3ff2a4fdb916f2a81bd2debaf84a46c04
Author: Jun Mukai <mukai@chromium.org>
Date: Fri Aug 10 18:28:53 2018

use random GUID for the device id of the offline demo mode

Previously the device id was extracted from the offline policy,
but that means all of the offline-enrolled device shared the same
device id (since the offline policy data is stored on the device).

This isn't a big issue as long as the device stays offline,
but we should use the generated ID to allow making the transition
to the online demo mode after the offline enrollment is conducted.

BUG= 827369 
TEST=manually walked through the offline enrollment

Change-Id: I0d9713d78c08fabcd0fb49326e1acca9ee578b98
Reviewed-on: https://chromium-review.googlesource.com/1147336
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582257}
[modify] https://crrev.com/34b8b1f3ff2a4fdb916f2a81bd2debaf84a46c04/chrome/browser/chromeos/policy/enrollment_handler_chromeos.cc