Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Assignment Sessions

Assignment Sessions

Every time you run the Assignments Manager's Migrate step, Assignment Sessions keeps a permanent record of it: what you uploaded, what was compared, what you selected, what actually happened per row, and — once Intune's own audit log catches up — the real Microsoft Intune audit entry for each change.

Before this feature, the results table at the end of a migration run was the only place to see what happened, and it disappeared the moment you left the page or refreshed. Assignment Sessions keeps it.

How to use it

1

Open Assignment Sessions

Go to Extensions → Assignment Manager → Assignment Sessions.

2

Browse the sessions list

Every past Migrate run is listed with when it started, who ran it, how many rows it touched, and its success rate.

3

Open a session

Click any row to see the full detail: every policy/group change in that run, its result, and its Intune audit log match.

What you'll see

The sessions list shows one row per Migrate run:

  • Start time and who ran it

  • Total rows in the run

  • Success rate

  • Overall status — Completed, Partially failed, or Failed

The session detail page shows:

  • A summary of what was compared before you selected anything — how many rows were checked, how many were ready to migrate, and how many were already in the desired state

  • A summary of the post-migration verification, if you ran one

  • For every executed row: which policy and group were affected, and what action was taken (add, remove, replace)

  • Whether it succeeded or failed, and the error message if it failed

  • Its match against Microsoft Intune's own audit log — once found, you can see the exact activity Intune recorded (its activity type, result, and the properties it changed)

A session covers one full run through Compare, Select, Migrate, and (if you run it) Validate — not just the Migrate step. If you compare a CSV but never migrate anything, that preview doesn't create an entry in the sessions list; nothing is recorded until you actually apply at least one change.

The Intune audit match can take a few minutes to appear. Intune Assistant checks for the matching entry in Microsoft's own audit log each time you open or refresh the session detail page — it isn't available the instant a migration finishes. A row shows "Checking..." for up to about 10 minutes after it ran, then "No match found" with a Check again button if nothing turned up by then.

Requirements

Available to anyone who can use the Assignments Manager — no separate license or permission is needed beyond what Assignments Manager itself already requires.

Common questions

Why doesn't a row have an Intune audit match yet? Intune's audit log isn't instant — it can take a few minutes for a change to show up there after Intune Assistant makes it. Reopen or refresh the session detail page after a few minutes; each visit checks again automatically.

Why did a row never get an Intune audit match? Occasionally Intune's own audit log doesn't retain a matching entry for a specific change, or the automatic check window (about 10 minutes) closed before anything showed up. The row's own result (success/failure) is still accurate either way — only the cross-reference to Intune's audit log is missing. Use the Check again button on the row to try once more at any time.

Does this replace the results I already see right after a migration? No — it's the same information, just kept permanently. The in-page results at the end of a Migrate run are unchanged; Assignment Sessions is where that same information lives afterward.

Can I export a session? Not yet — this first version is view-only.

How long sessions are kept

Assignments Manager keeps your sessions for 12 months by default. A customer administrator can change this under Customer → Assignments Manager history (from 1 to 120 months). Sessions older than that are removed automatically. A session that was only compared and never migrated is not kept beyond a day, and a session that stopped halfway (for example because the browser was closed) is marked as failed after 24 hours without activity.

To limit what is stored, a session keeps only the rows that were actually sent to the migration, not every row that was compared, and it does not keep the uploaded file or the full policy details.

Last updated