Real tenant investigation
Policies that don’t apply
Separate assignment, delivery, applicability and reporting before you change a policy.
25–35 minutes · 0 / 3 learning checkpointsOpen case 01 →Six Windows support cases
A practical Intune lab for administrators who want to explain what happened, prove the cause and know when it is safe to close the ticket.
Reading progress is saved only in this browser. It does not certify tenant tests.
Choose the ticket on your desk
Real tenant investigation
Separate assignment, delivery, applicability and reporting before you change a policy.
25–35 minutes · 0 / 3 learning checkpointsOpen case 01 →Real portal + browser exercise
Investigate 0x87D1041C and prove what a detection rule actually accepts.
30–40 minutes · 0 / 3 learning checkpointsOpen case 02 →Current + dated tenant evidence
Separate policy delivery, account management, backup and operator permissions.
25–35 minutes · 0 / 3 learning checkpointsOpen case 03 →Intune + Entra What If
Follow one laptop through three simulations and explain why the same policy appears each time.
0 / 3 learning checkpointsOpen case 04 →Real tenant before and after
Trace two Required assignments to one laptop and find which path caused Intune to offer the app.
0 / 3 learning checkpointsOpen case 05 →Real device and portal evidence
Intune lists two keys. Match the local recovery protector to the correct Entra record before closing the ticket.
0 / 3 learning checkpointsOpen case 06 →Built for a working administrator
Each case gives you a ticket, readable evidence, a decision point, a hidden hint and a practical handover. Try the question before revealing the resolution.
Use the step index on your phone, open any screenshot at its original resolution, and save a step to resume later in the same browser.
Start with the case that matches your ticket. You can save a step and return to it later.
| Case | Evidence in this edition | Boundary |
|---|---|---|
| Policies | Fresh tenant report, exact Not applicable setting, Windows Pro edition. | Supported diagnosis; no policy remediation was deployed. |
| Application detection | Fresh Win32 configuration screenshot and a tested browser exercise. | The fictional incident was not reproduced as an Intune failure. |
| LAPS | Dated October deployment evidence plus fresh November device/backup metadata. | No fresh local sign-in, forced rotation or access-denial test. |
| Outlook compliance | Intune device and setting reports, followed by three Entra What If runs. | Mailbox access was outside the simulation. |
| Assignment filters | Two Required paths, Not evaluated / App offered, then No match / App not offered after removing the unfiltered assignment. | Local shortcut presence and cleanup were not independently verified. |
| BitLocker recovery records | Current local recovery protector matched by full ID to one of two Entra records for the same lab device. | Password retrieval, denied access, managed rotation and boot recovery are documented follow-ups, not executed tests. |
Screenshots are native captures with account headers excluded. Dates identify historical evidence. Each case describes the lab changes and the limits of its evidence.
Take the investigation with you
Investigation worksheets, browser detection exercise instructions and a read-only BitLocker metadata collector. The collector exports selected fields without recovery passwords. Review the case instructions before running it on your lab device.
Download the lab kit · ZIP ↓Save each step explicitly with Save this step. Checkpoints track what you have understood; log your own test outcomes separately in the worksheet. Progress does not sync between devices, browsers, private windows or a future published URL.
No sign-in is required. Your checkpoints and saved step stay in this browser. To keep a separate record or move between devices, download the worksheet or export your progress.