0x80070774: hybrid Autopilot can't reach or join the domain
A hybrid join Autopilot deployment fails because the device can't reach a domain controller or has been put in a state that can't join the domain.
From Microsoft's documentation, checked 9 Nov 2026.
Something went wrong. Confirm you are using the correct sign-in information and that your organization uses this feature. You can try to do this again or contact your system administrator with the error code 80070774.Also searched as: 80070774
What it means
This typically happens before the first restart in a hybrid Autopilot deployment, when the device times out at the initial sign-in screen. Microsoft lists the Assign user feature in a hybrid profile, a deleted Entra device behind the Autopilot object, missing permissions for the Intune Connector for Active Directory, and the connector being installed in a different domain from the one targeted.
Common causes
- The Assign user feature is configured for a Microsoft Entra hybrid join Autopilot deployment.
- The Microsoft Entra device associated with the Autopilot object was deleted.
- The Intune Connector for Active Directory lacks permission to create computer objects in the target OU.
- The Intune Connector for Active Directory is installed in a different domain from the one devices are configured for.
How to fix it
Check the connector log for event 30132
On the connector server, look for event ID 30132 ('Failed to get the ODJ Blob. The ODJ connector does not have sufficient privileges'). Newer connectors log under Applications and Services Logs > Microsoft > Intune > ODJConnectorService instead.
Get-WinEvent -LogName "ODJ Connector Service" -MaxEvents 100 | Where-Object Id -eq 30132
Unassign the user
In the Intune admin center go to Devices > Windows > Windows devices, select the device, choose Unassign user, and check the hybrid Autopilot profile is assigned before retrying OOBE. If the Entra device was deleted, delete the Autopilot object and reimport the hash.
Fix connector permissions and domain
Delegate control of the target OU to the connector's computer account (create and delete computer objects, Full Control on them), and install the connector in the domain your devices are configured for.
How to confirm it's fixed
- The device completes OOBE, joins the domain, and no new event 30132 appears on the connector.
Follow Microsoft Intune failures and fixes
A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.