Troubleshooting case study
Autopilot: Secure Boot compliance
The original physical-device validation includes Secure Boot remediation followed by Confirm-SecureBootUEFI returning True and an Intune Compliant state. Later endpoint reuse does not invalidate that retained result.
Environment
Personal physical Windows device, Microsoft 365 developer tenant, assigned Autopilot profile, pilot groups, and Intune policy.
Diagnostic process, findings & corrective action
The original physical-device validation includes Secure Boot remediation followed by Confirm-SecureBootUEFI returning True and an Intune Compliant state. Later endpoint reuse does not invalidate that retained result.
Validation & outcome
Entra join, MDM enrollment, ESP, required apps, BitLocker, Defender, firewall, VBS, Secure Boot, standard-user posture, and compliance were validated.
Lessons & limitations
Live physical-device personal-lab validation. Secrets and unique hardware/directory identifiers are excluded or redacted. Later reconfiguration of the endpoint does not invalidate the documented completed Autopilot project.
The evidence supports the specific scenario. Unestablished root causes are not presented as confirmed.