Skip to content

Quick Start

This guide walks you from a fresh install to a running Intune enrollment in six steps.

1. Provision the container

intuneme init

This pulls the Ubuntu 24.04 container image from GHCR, extracts the rootfs, installs Microsoft Edge and Intune Portal, creates a container user matching your host UID, and writes the configuration file. It also installs a polkit rule so you can use machinectl without repeated password prompts.

See the init command reference for the full list of what init does.

Fedora / tmpfs systems

If init fails with "disk quota exceeded", your /tmp is likely a size-limited tmpfs. Use --tmp-dir to redirect temporary files to disk: 

intuneme init --tmp-dir /var/tmp
See Troubleshooting for details.

Insiders channel

To use the insiders (pre-release) container image, add the --insiders flag: 

intuneme init --insiders
The insiders image may include newer versions of Edge or the Intune agent. Use the same flag with intuneme recreate if you ever upgrade.

2. Start the container

intuneme start

This boots the container (systemd as PID 1), mounts host display/audio/GPU resources into it, configures Nvidia GPU forwarding if detected, and installs udev rules for device hotplug (YubiKey, webcam). The container is ready when intuneme status shows it as running.

3. Open a shell inside the container

intuneme shell

This drops you into an interactive login shell as the container user. From here you can run commands inside the container to check the state of services or troubleshoot enrollment.

4. Enroll in Intune

Inside the container shell (or directly from the host with intuneme open portal):

intune-portal

The Intune Portal window opens on your host display. Follow the on-screen steps to sign in with your corporate account and complete device enrollment.

5. Access corporate resources

Once enrolled, open Edge to access corporate web resources:

microsoft-edge

Or from the host without entering a shell first:

intuneme open edge

6. Stop the container

When you're done, shut down the container:

intuneme stop

This gracefully shuts down the container systemd, unmounts resources, and removes the udev hotplug rules. Enrollment state is preserved in ~/Intune/ and will be available the next time you run intuneme start.

What's next