UserAgent: Mozilla/5.0 (X11; CrOS x86_64 11005.1.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3532.8 Safari/537.36
Platform: 11005.1.0 (Official Build) dev-channel eve

Steps to reproduce the problem:
1. On a domain joined / managed Chromebook, enable the Crostini flag.
2. Open crosh and attempt to run `vmc`.
3. Receive the error message: "This command is not available"
4. There are no GSuite policy flags exposed to control this behavior.
5. Leave the domain, powerwash, enable Crostini - containers work fine.

What is the expected behavior?
On non-managed, but non Developer Mode CrOS devices running Dev channel, you would be able to run vmc successfully and begin experimenting with container use cases.

What went wrong?
Non-domain joined / managed Chromebook Pixelbooks work just fine, and you can start vmc and begin exploring use cases for containers on ChromeOS running dev channel.

Joining the Chromebook to a domain so that it becomes a managed device neutralizes this capability completely.  This makes it impossible for enterprises to test this feature as there do not appear to be any policy bits exposed in GSuite that would allow for re-enabling this functionality.

Did this work before? Yes This worked fine on managed devices shortly after the initial availability of Crostini, but stopped working a few weeks after this became available in Dev channel for managed Chromebooks.

Chrome version: 70.0.3532.8  Channel: dev
OS Version: 11005.1.0
Flash Version: 

While we are interested in exploring container use cases, gating this feature for managed devices does seem odd given that Crostini is otherwise available to Dev channel devices that are not managed even if they are not in developer mode.