IntuneAtlas
v0.0.3 · alpha

Track every setting against its baseline

Merges every Intune policy into one searchable index, matched by the real setting. Catches conflicts and baseline drift automatically. Free and open source.

$ irm https://intuneatlas.com/install.ps1 | iex
or deploy it to Azure for your team

indexes read-only, serves on localhost · install on or · headless scan for CI · getting started guide

MIT TypeScript Graph API · read-only by default
intuneatlas ui — contoso.onmicrosoft.com
$ irm https://intuneatlas.com/install.ps1 | iex

  ✓ signed in — admin@contoso.onmicrosoft.com (read-only)
  ✓ 41 policies → 1,847 settings indexed in 3m 41s
  ✓ 6 conflicts · 23 below baseline · 9 missing

  → http://localhost:7878
localhost:7878 1,847 settings · Pilot ring
Quality update deferral period (days) Windows 10 · 2 policies 14  /  2 Conflict
Tamper protection · 2 notes Windows 10 · Defender Antivirus – Baseline Disabled Below baseline
Require Device Encryption Windows 10 · No policy Not configured Missing
Enable FileVault macOS · FileVault – All Macs On Meets baseline

What it reports

Every setting gets a state

Each setting is given one of six states, so you can see at a glance what needs attention. Settings that meet a baseline, or that no baseline covers, are kept in the background.

Conflict

Two policies disagree

Same setting, different values, reaching the same group. Policies for different groups can differ without it counting. Each policy is shown with its value and who it's assigned to.

Below baseline

Weaker than the benchmark

Checked against the baselines you have active. Each finding names the baseline it comes from and explains why.

Missing

Expected, set nowhere

A baseline has a rule for a setting that no policy in the tenant configures at all.

Not assigned

Configured, reaching nothing

A policy sets it, but the policy isn't assigned to any group, so it doesn't reach any devices.

Meets baseline

Checked and passing

At least one active baseline covers the setting, and every rule that does is satisfied.

Not checked

No rule has an opinion

No active baseline covers the setting, so its value is shown but not judged either way.

Baselines

A baseline is a policy you exported.

Any Settings Catalog or compliance policy exported from Intune works as a baseline, exactly as exported: the Open Intune Baseline, a CIS build, or the policies of your own reference tenant. Nothing is converted, and nothing ships with the app.

Choose the downloaded folder on the Baselines page, or drop it into your baselines folder yourself. Settings are matched by Intune's own setting ID and compared value by value, sub-settings included.

~/.intuneatlas/baselines/ folder
oib/
  windows-v4.0/                 # one baseline
    baseline.yml                # optional
    SettingsCatalog/
      Win - OIB - ES - Defender Antivirus - D - AV Configuration - v4.0.json
      Win - OIB - ES - Encryption - D - BitLocker (OS Disk) - v3.7.json
      …
  windows-v3.8/                 # an older version, side by side
oib/windows-v4.0/baseline.yml yaml
name: Open Intune Baseline – Windows v4.0
settings:
  device_vendor_msft_policy_config_update_deferqualityupdatesperiodindays:
    compare: atMost        # this number or less
    severity: high
    rationale: >
      Deferring quality updates much beyond a week leaves patched
      vulnerabilities open for longer than necessary.
    reference: CIS Microsoft Windows 11 Benchmark, L1
  device_vendor_msft_policy_config_experience_allowcortana:
    ignore: true           # leave this setting out
Annotations

An exported policy says what a setting should be, not why. The optional baseline.yml adds severity, rationale and references per setting without changing the stored values, and can relax a number to "or less" or "or more".

Run it

Open it, query it, or wire it into CI.

One index, five entry points. The default command builds it and serves it on localhost; hosted on Azure it is the same thing for a whole team; the rest hand you a single value, a file, or an exit code instead.

For a team

Hosted on Azure — your own Container App

One template deploys the web UI into your own subscription, on its own HTTPS address. Everyone signs in with their own Microsoft account and sees only the policies their own Intune role shows them; roles decide who may stage, review and push. Notes, reminders, reviews and each setting's history are shared, and nothing leaves your tenant.

Deploy to Azure

Read the index

Web UI — intuneatlas ui

Every setting grouped by category, searchable by CSP path, with the policies that set it, each value editable with Intune's own options and ranges, note threads, reminders that come due on a schedule, and a history of what changed between scans. Configuration and compliance policies both, custom OMA-URI rows included, for the whole tenant or one group. Staged changes pass a review gate, and an Admin can push them to Intune. Runs on your machine against the report on disk, with no server and no upload.

Single value

get — intuneatlas get <path>

One setting, every profile that sets it, and each value. Five lines of output, pipeable, no index served and no browser opened.

Scheduled

Headless scan

JSON or SARIF to disk and a non-zero exit when the tenant drifts past your threshold. The Docker image takes an app registration from the environment.

Continuous

GitHub Action

The headless scan on a cron, with findings as PR annotations. Fails the run at your chosen severity.

scheduled run — sarif to disk, non-zero on drift
$ intuneatlas scan --baseline cis-l1 --fail-on high --format sarif

  41 policies · 1,847 settings · 11 findings (3 critical, 3 high, 3 medium, 2 low)
  wrote ./intuneatlas.sarif
  exit 1  — 6 findings at or above `high`

.github/workflows/tenant-drift.yml yaml
on:
  schedule: [{ cron: "0 7 * * 1" }]

jobs:
  drift:
    runs-on: ubuntu-latest
    steps:
      - uses: intuneatlas/scan-action@v1
        with:
          baseline: cis-l1
          fail-on: high        # exit non-zero at high or critical
          notes: ./intune-notes.yml

Project status

Where things stand

IntuneAtlas is still early. Windows is the most complete; support for Apple and Android devices is more limited. This is the state of each area in v0.0.3.

  • Windows configuration & update ringsSettings Catalog policies, with each setting's full path and conflicts between policies stable
  • Compliance policies & tenant settingsAll platforms, Linux included, setting by setting, with the actions for noncompliance stable
  • Enrollment, ADE tokens, certificate expiryShows when ADE and APNs certificates are due to expire stable
  • Custom OMA-URI profilesEach row is shown as a setting. Values Intune encrypts appear by file name only, and these rows can't be edited new
  • macOS & iOSScanned and shown, though some settings still appear under their technical name partial
  • Android EnterpriseWork profile restrictions. Fully managed and dedicated devices aren't covered yet partial
  • Pushing changes to IntuneOne reviewed change at a time, with a write permission you add yourself. A push is refused if the value in Intune has changed since it was staged. There's no undo yet new
  • App protection & Conditional AccessNot planned for now; they work quite differently from device configuration not planned
Disclaimer

IntuneAtlas isn't affiliated with or endorsed by Microsoft. Intune and Microsoft Graph are trademarks of Microsoft. The app reads your tenant through the documented Graph API and only writes to it when an Admin pushes a reviewed change. If a scan shows something you didn't expect, please open an issue.

Contribute

Help is welcome

Bug reports, ideas and pull requests are all appreciated. If something looks wrong for your tenant, an issue describing what you expected and what you saw is the most useful place to start.

Open an issue View on GitHub