Before starting
An authorized Intune test tenant, an appropriately licensed test user, and a supported enrolled Windows VM. A harmless configuration profile must already be validated on this test device.
Introduce the fault
In the lab tenant, remove only the dedicated device from the test group assigned to the harmless profile. Avoid All users or All devices targeting. Record the original group membership and assignment.
Diagnose before changing anything
- Confirm the intended device and user, management enrollment, licensing, profile platform, and most recent check-in. Do not assume that Entra registration by itself means the device is enrolled in Intune.
- Inspect the profile’s assignment report, group membership, exclusions, filters, and per-setting state. Distinguish Pending, Error, Conflict, and Not applicable; keep screenshots of the actual status.
- Use the Intune troubleshooting view and check relevant Windows device-management events when needed. Compare the missing setting with the known-good baseline. Do not wipe or reenroll the device as a first step.
Make the smallest appropriate change
When the assignment omission is confirmed, restore membership in the intended test group. Trigger a supported device sync from Intune or Windows Settings → Accounts → Access work or school → the managed connection → Info → Sync. Allow the service to process the change and record check-in times.
Verify with the affected user
Capture the resulting assignment state and verify the harmless setting on the guest itself. A portal status alone is not enough. Confirm the assignment targets only the lab group and note the observed sync delay.
Restore the baseline
Remove the test assignment and restore the recorded group membership. Some settings persist after unassignment; verify the guest state and use the dedicated lab checkpoint when appropriate. Keep the original VM outside the test enrollment.
Know when to escalate
Escalate repeated enrollment or authentication errors, unsupported settings, security policy conflicts, or any action requiring a device wipe or production-wide policy change.
Evidence to collect
- Enrollment and check-in state with identifiers redacted
- Group assignment or exclusion before and after
- Policy report and actual device setting
- The sync time and final verification result
INTERVIEW REFLECTION
What evidence distinguished an assignment problem from a device that had not checked in?
Write the ticket
Use the downloadable ticket template. Record the symptom, scope, timeline, checks, observed cause, action, verification, rollback, and escalation decision. Leave dates, elapsed time, root cause, and result blank until the exercise is performed.
Publication gate: replace “Planned” only after the exercise is reproducible and sanitized evidence has been reviewed. Describe it as an independent lab simulation.