Hybrid joined device to Intune only in another tenant

There is no Microsoft-supported way to move an existing Windows device directly from Hybrid Microsoft Entra joined in one tenant to Microsoft Entra joined/Intune-only in another tenant without a reset or wipe.

Key points from the documented guidance:

1. No in-place conversion path
   • There is no supported process to convert an existing Hybrid Microsoft Entra joined device to Microsoft Entra joined without a Windows reset. This applies even within the same tenant, and moving to a different tenant adds another boundary.
   • For hybrid-joined devices, a full device wipe is required; Windows Autopilot Reset does not support Microsoft Entra hybrid joined devices.
2. Recommended migration pattern
   • Microsoft recommends aligning the move to Microsoft Entra Join with a complementary event such as:
     • Hardware refresh
     • OS upgrade
     • Device troubleshooting scenario where the device is already being reset
   • In these scenarios, devices are reset or replaced, then:
     • Joined to the new tenant (Microsoft Entra Join)
     • Enrolled into Intune in the new tenant (for example, via Autopilot)
3. Coexistence and phased migration
   • Microsoft Entra Join and Hybrid Microsoft Entra Join endpoints can coexist in the same environment.
   • A mixed environment increases complexity but is expected during transition. Hybrid-joined devices can be kept until they are replaced or reset and moved to Microsoft Entra Join.
4. Tenant-to-tenant Intune migration considerations
   • Intune policies can be exported from the old tenant and imported into the new tenant using Microsoft Graph PowerShell samples. This helps reproduce configuration in the new tenant but does not migrate the device state itself.
   • Users must unenroll devices from the old tenant and then re-enroll them in the new tenant.
5. iOS/iPadOS and other platforms
   • For iOS/iPadOS, when moving between MDMs or tenants, the device must not restore an old backup that contains the previous MDM profile. The old management profile must be removed, and then the device can be enrolled into Intune in the new tenant. A similar principle applies conceptually to Windows: the old management relationship must be removed, and a new one established.
6. Tools and “no-wipe” expectations
   • The documentation does not describe any supported tool that can rebind an existing Windows hybrid-joined profile to a different tenant’s Intune without reset.
   • For minimal user disruption, the supported approach is:
     • Plan and communicate a reset/reprovision window.
     • Use Autopilot in the new tenant to streamline provisioning and app/policy deployment.
     • Run a phased migration so not all 40 users are impacted at once.

In summary, for hybrid-joined Windows devices moving to Intune-only in a new tenant, a reset/wipe and re-provision into the new tenant is required; there is no supported in-place, no-wipe tenant-to-tenant device migration for this scenario.

References:

• Microsoft Entra joined vs. Hybrid Microsoft Entra joined in cloud-native endpoints
• Migration guide: Set up or move to Microsoft Intune
• Backup and restore scenarios for iOS/iPadOS