INTUNE EXCLUSIONS: INVESTIGATION WORKSHEET Tiago S. Carvalho | Lab edition | 19 November 2026 Ticket / operator: UTC date and time: Device name: Entra device ID: Intune managed device ID: Primary user / signed-in lab user: Last device check-in: 1. Establish the scope Policy name / ID: Workload (configuration, compliance or application): Setting name and user/device scope: Included group name, ID and member type: Direct or nested membership evidence: Excluded group name, ID and member type: Assignment filter name, mode and exact rule: Other assignments that can reach this device: Existing effective local value / policy source: 2. Record the original result Assignment saved at (UTC): Device checked in at (UTC): Policy/setting state and report timestamp: Filter evaluation and timestamp, if applicable: Local policy value and source: Screenshot filenames: What this proves: What this does not prove: 3. Change one assignment variable Correction chosen (same-type group exclusion or assignment filter): Exact change: Save time (UTC): Next device check-in (UTC): Fresh filter evaluation / deployment result: Local effective value: Screenshot filenames: Any existing value retained after the assignment stopped: 4. Restore and close Pilot assignment removed at (UTC): Baseline restored and how verified: Lab policy / groups / filter retained or removed: Outstanding evidence: Final assessment: VERIFIED / PARTIAL / NOT TESTED Do not put passwords, recovery keys, access tokens or customer data in this worksheet. An exclusion stops a targeting path. It is not proof of application removal or automatic rollback of a setting.