Forum Discussion
Issues with Windows 11 Autopilot Hybrid Joined Since last Week
We have explored all of this already. Several third party experts have checked it all too, and confirmed it should all work. They profile is getting downloaded but then everything stops. No blob even attempted. But if we run Pre-Prov it works. Also, if we run a SSO kerberos Entra key rotation the next Autopilot device works, then the rest fail after that. Microsoft have this with their product team... they seem to think it may be a bug (perhaps related to new endpoints). We see other customers having same issue on reddit forum
https://www.reddit.com/r/Intune/comments/1ph9lse/issues_with_windows_autopilot_hybrid_joined/
Convinced this is a Microsoft back-end issue.
The fact that Pre-Provisioning works doesn’t rule this out, it just means the failure is likely in the post-credential user-driven leg (different calls/endpoints than technician flow).
What I’d suggest adding to your MS case (to speed escalation):
- Screenshot of Intune > Devices > Enrollment > Windows > Intune Connector for AD showing status + version
- Connector logs from the connector server (ODJConnectorSvc.log etc.) around a failed attempt
- Autopilot diagnostics + correlation ID/time from a failing device at the “Something went wrong” screen
As an interim workaround, you already found the most practical one: use Pre-Provisioning until MS confirms the root cause, but I’d still re-check connector currency + AFD allowlisting because many “backend-looking” cases ended up being one of those two.
And just to clarify: the ODJConnectorEnrollmentWizard XML file is fine with permissions?