M365 Lab Project 01 ยท COMPLETE

Windows Autopilot & Intune evidence

Sanitized proof from the live OOBE, Enrollment Status Page, compliance remediation, and post-enrollment security validation.

Autopilot OOBE

Tenant-branded work/school sign-in proves the registered device retrieved the Autopilot experience.

Tenant-branded Windows Autopilot OOBE sign-in

Enrollment Status Page

Device preparation and setup progressed through the configured ESP workflow.

Windows Enrollment Status Page with device preparation and device setup completed

Compliance troubleshooting

Intune initially identified BitLocker and Secure Boot as not compliant. Endpoint checks isolated Secure Boot as the real firmware gap.

Intune compliance settings before Secure Boot remediation

Final compliance

After Secure Boot remediation and Intune synchronization, the corporate device reported Compliant.

Intune device inventory showing final compliant state

Settings Catalog

The Windows security configuration profile reported two successes with zero errors, conflicts, not-applicable results, or in-progress assignments.

Intune Settings Catalog successful check-in status