intuneatlas login
Sign in to a tenant and confirm the token works.
| Flag | Description |
|---|---|
| --tenant <id-or-domain> | Tenant ID or domain, e.g. contoso.onmicrosoft.com |
| --client-id <id> | Your Entra app (client) ID — register one first. Omit it in a terminal and you'll be prompted once, then it's saved for next time. Can also come from INTUNEATLAS_CLIENT_ID (a per-run override, not saved). |
| --client-secret <secret> | Client secret — selects the unattended client-credentials flow instead of interactive sign-in |
| --device-code | Use device-code sign-in instead of the interactive browser flow |
$ intuneatlas login --tenant contoso.onmicrosoft.com --client-id <application-id>
intuneatlas scan
Scan the tenant's configuration, compliance and enrollment policies and build the settings index.
| Flag | Description |
|---|---|
| --tenant <id-or-domain> | Tenant ID or domain |
| --client-id <id> | Your Entra app (client) ID — register one first. Omit it in a terminal and you'll be prompted once, then it's saved for next time. Can also come from INTUNEATLAS_CLIENT_ID (a per-run override, not saved). |
| --client-secret <secret> | Client secret — unattended client-credentials flow |
| --device-code | Use device-code sign-in instead of the interactive browser flow |
| --out <path> | Write JSON to a file instead of stdout |
| --baseline <path> | Folder of baselines to use instead of your own (~/.intuneatlas/baselines). Baselines in a folder given this way can't be added, renamed or removed from the web UI. |
$ intuneatlas scan --tenant contoso.onmicrosoft.com --client-id <application-id> --out report.json
intuneatlas search
Search the last scan from the terminal: settings by name, path, category, policy or value. Each match comes with its state, the policies that set it, who each of those reaches, and its value. Nothing is asked of the tenant — run scan first, and again whenever you want fresh data.
| Flag | Description |
|---|---|
| [words...] | What to look for. A setting matches when every word appears somewhere in it. With no words, everything is listed. |
| --group <name-or-id> | Only what reaches this group: policies assigned to it, to a group containing it, or to everyone. Names need the scan to have read them (Group.ReadBasic.All); otherwise give the group's ID. |
| --state <state> | Only settings in this state: Conflict, Below baseline, Missing, Not assigned, Meets baseline or Not checked |
| --platform <platform> | Only this platform, e.g. windows10, macOS, ios |
| --baseline <folder-or-url> | Judge states against this baseline instead of the ones added in the web UI. Same forms as for check. |
| --tenant <id-or-domain> | Which tenant's scan to search, when scans of several are stored |
| --format <format> | text (default), json or csv (one row per policy) |
| --out <path> | Write to a file instead of the terminal |
$ intuneatlas search bitlocker
$ intuneatlas search --group "Pilot ring" --state conflict
intuneatlas check
Check the last scan — or one group in it — against a baseline, and list what needs attention:
settings below the baseline, in conflict, or missing. The states and verdicts are the web UI's.
It works on the stored scan and asks nothing of the tenant unless you pass --scan.
| Flag | Description |
|---|---|
| --group <name-or-id> | Check only what reaches this group. Without it, the whole tenant. |
| --baseline <folder-or-url> | The baseline, as one of: a folder of exported policies on this machine; a GitHub folder URL, as copied from the browser; a link to a .zip or .tar.gz archive; a link to one exported policy's .json. A URL is downloaded for the run and not kept. Without the flag, the baselines added in the web UI are used. |
| --scan | Scan the tenant first, then check that. Needs --tenant and a sign-in, with the same flags as scan (--client-id, --client-secret, --device-code). |
| --tenant <id-or-domain> | Which tenant's scan to check — needed with --scan, or when scans of several tenants are stored |
| --all | Report every setting, not only the ones needing attention |
| --format <format> | text (default), json or csv |
| --out <path> | Write to a file instead of the terminal |
| Exit code | Meaning |
|---|---|
| 0 | Nothing is below baseline, in conflict or missing |
| 1 | Something is |
| 2 | It couldn't be checked: no scan stored, the baseline couldn't be read, sign-in failed |
$ intuneatlas check --group "Pilot ring" --baseline https://github.com/SkipToTheEndpoint/OpenIntuneBaseline/tree/main/WINDOWS
$ intuneatlas check --scan --tenant contoso.onmicrosoft.com --client-id <application-id> --client-secret <secret> --baseline ./baselines/contoso
A URL to a branch follows that branch. To check against a fixed version, use a URL that names a
tag or a commit instead of main. A setting the baseline expects and the tenant lacks is
shown by name only if a scan has looked it up; run the check once with --scan for a
baseline the last scan didn't know.
intuneatlas ui
Open the web UI. Always signs in with your own Microsoft account — that's what runs any scan you trigger.
| Flag | Description |
|---|---|
| --tenant <id-or-domain> | Tenant to sign in to — needed the first time, or to switch tenants |
| --client-id <id> | Your Entra app (client) ID — register one first. Omit it in a terminal and you'll be prompted once, then it's saved for next time. Can also come from INTUNEATLAS_CLIENT_ID (a per-run override, not saved). |
| --report <path> | Read a report from a prior scan --out instead of scanning live |
| --baseline <path> | Folder of baselines to use instead of your own (~/.intuneatlas/baselines). Baselines in a folder given this way can't be added, renamed or removed from the web UI. |
| --host <address> | Interface to bind to (default: 127.0.0.1, this machine only). Anything else — e.g. 0.0.0.0 — shares it with a team; each teammate signs in with their own Microsoft account. |
| --persist | Register this exact command to run in the background, starting at boot and restarting on failure (Windows: Scheduled Task as SYSTEM; Linux: systemd service as root). Requires --tenant, --client-id, and an elevated/root shell — the background service can't prompt for either at boot, or read the client ID saved for your own interactive login. |
| --stop | Stop and remove a previously --persist'd background instance |
$ intuneatlas ui --tenant contoso.onmicrosoft.com --client-id <application-id>
$ intuneatlas ui --persist --host 0.0.0.0 --tenant contoso.onmicrosoft.com --client-id <application-id>
$ intuneatlas ui --stop
Where there is no command line to pass flags on, such as a container, the same settings can come from the environment:
| Variable | Stands in for |
|---|---|
| INTUNEATLAS_TENANT_ID | --tenant |
| INTUNEATLAS_CLIENT_ID | --client-id |
| INTUNEATLAS_HOST | --host |
| INTUNEATLAS_PORT | The port to listen on (default 7878) |
intuneatlas export
Export the last scan from local storage — never re-scans the tenant.
| Flag | Description |
|---|---|
| --tenant <id-or-domain> | Only export the latest scan for this tenant |
| --kind <kind> | settings (default; every setting, including what compliance policies configure), compliance (the compliance policies themselves) or enrollment (the enrollment configurations) |
| --format <format> | csv (default; only format available for now) |
| --out <path> | Write to a file instead of stdout |
$ intuneatlas export --tenant contoso.onmicrosoft.com --kind settings --out settings.csv