Manual backend cleanup of Windows Autopilot registrations, especially for deleted or inaccessible tenants, can only be performed by Microsoft Support and not via community or self-service tools.
For this scenario (personal device tied to an expired Microsoft 365 Developer sandbox tenant with no remaining admin access), the supported path is:
- Open a support case with Microsoft as an end user:
- As an end user, contact the OEM/channel partner or Microsoft support appropriate for the Windows edition on the device. The Autopilot program documentation specifies that end users must work through their IT admin, OEM, or partner; however, in a developer-tenant scenario, direct Microsoft support engagement is required.
- Clearly describe the issue and request Autopilot deregistration:
- State that the device is enrolled in Windows Autopilot under a deleted Microsoft 365 Developer tenant and is stuck in OOBE requiring a work/school account.
- Provide the device serial number, hardware hash, and proof of purchase when requested.
- Ask to escalate as an Autopilot backend cleanup case:
- Reference that the tenant is no longer accessible and that Autopilot deregistration must be performed on Microsoft’s side, similar to the guidance that unrecoverable devices or tenant-related Autopilot issues require Microsoft support intervention.
If support determines the device is in an unrecoverable state from the customer side, they can route the case to the appropriate Autopilot/Data Protection or backend team to remove the Autopilot registration from the deleted tenant, after validating ownership.
This community or documentation-based channel cannot itself escalate or modify backend Autopilot records; only a formal support ticket can do that.
References: